📊 Full opportunity report: When a Content Network Starts Publishing to Itself on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
A content network of 474 WordPress sites is automatically publishing content predominantly to a few favored sites, leaving more than half inactive. This self-publishing behavior creates imbalance, risking spam signals and diminishing content diversity. The issue stems from both site selection and content supply mismatches.
A large automated content distribution system is currently publishing the majority of its output to only a small fraction of its sites, leaving more than half inactive, which may impact content diversity and search engine perception.
The network comprises 474 WordPress sites managed by two interconnected systems: Stenvrik, which sources and evaluates news signals, and DojoClaw, which rewrites and distributes content. Despite the system’s technical correctness at each decision point, an audit revealed that 80% of all posts were concentrated on just 8% of the sites, mainly technology-focused outlets. Meanwhile, over half the sites received no content over a 28-day period, risking spam detection and reducing the network’s overall value.
The root causes include a topic concentration bias—where the system repeatedly favors tech and AI sites due to the nature of the input signals—and a supply mismatch, as most content is tech-related while the majority of sites cover other categories like health, food, and fashion. These issues resulted in a self-reinforcing cycle where content is pushed to favored sites, leaving others dormant. Fixes implemented include adjusting the content placement algorithm to cap the number of posts per site and prioritize less active sites, thereby promoting a more balanced distribution.
When a content network starts publishing to itself
A 474-site network quietly collapsed onto 38 of its own favorites while half the catalog went dark. The throughput graph looked fine. The fix wasn’t one thing — it was two causes and a three-part repair across two decoupled systems.
News-intelligence layer
Ingests hundreds of feeds, scores & geo-tags stories, surfaces what’s trending.
SUPPLY · what’s worth coveringAI content engine
Rewrites a story in each site’s voice and fans it out across the catalog.
PLACEMENT · where it lands & how it reads80% of output on 8% of sites
A 28-day audit, bucketed per site, was lopsided in a way the totals had hidden. Every individual placement was “correct” — the aggregate was a slow-motion failure.
Where 28 days of syndication actually landed
474-site catalog · per-site audit
WordPress Explained: Your Step-by-Step Guide to WordPress (2020 Edition)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Not one bug — two independent causes
The tempting move is to blame the matcher and move on. The data showed two distinct problems living on two different systems, each needing its own fix.
Within-topic concentration
The matcher kept surfacing the same broad tech sites for every tech story, and rotation only shuffled candidates within the matched pool. A site that never entered the pool could never get a turn — fair only among the already-chosen.
Supply ≠ demand
53% of supplied content was tech/AI — but only ~13% of sites are. The catalog skews the other way, so those sites starved for on-topic material.
Fundamentals of DevOps and Software Delivery: A Hands-On Guide to Deploying and Managing Software in Production
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Watch the network rebalance
Each square is one of the 474 sites; color is how much it’s publishing. Toggle the selection logic to see placement spread off the red-hot favorites and into the dark long tail.
Placement simulator
Same matcher relevance gate either way — the only change is how candidates are ordered after it.
Google Ads (AdWords) Workbook: Advertising on Google Search, the Display Network, and Video (2026 Marketing – Social Media, SEO, & Online Ads Books)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Placement, supply, throughput
Two causes meant the fix had to touch both systems — and only then could the ceiling rise without re-concentrating the load.
Placement levers
DojoClaw- Per-site weekly cap — any site over
25posts/7d drops from the pool, pushing selection into the long tail (relaxes only if it would starve a fan-out). - Global LRU — order by network-wide recency, not just within-topic, so sites idle across the whole network float to the top.
- Starvation floor — guaranteed by construction: the most-idle eligible site is always within the picks.
Supply rebalance
Stenvrik- Audited existing feeds for liveness — removed ones returning HTTP 200 but zero items (broken RSS).
- Added a verified batch across Home, Garden, Health, Food, Fashion, Auto, Science, Pets & more — every feed fetched live first, weighted to the most idle categories.
- Flagged throttled feeds (big publishers exposing only 1–2 items) for replacement rather than burying the risk.
Throughput raise
Scheduler- Fan-out width
maxSites 5 → 7— the extra slots land on fresh sites because the cap is now enforcing. - Quota depth
K 2 → 3— every category’s daily cap scaled ×1.5. - Honest note: a documented
~950/dayintent the code never delivered (units quirk) stays gated behind a sign-off.
Master Your Time in 10 Minutes a Day: Time Management Tips for Anyone Struggling With Work-Life Balance (How to Change Your Life in 10 Minutes a Day)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The scoreboard — with an honest asterisk
The change is behavioral: it shapes future placement, it doesn’t retroactively rescue the month sites sat dark. The proof is in the next weeks of data — which is why the instrumentation is the real deliverable.
Supply and placement are genuinely separate concerns. Diagnosing the imbalance meant looking at both sides and seeing they disagreed. A clean boundary made a failure that spanned both legible — good system boundaries organize thought, not just code.
Ordering by load & idleness sacrifices a little topical ranking for dramatically better coverage. All candidates already cleared the relevance gate — so it’s a deliberate trade, not a regression.
Implications of Self-Publishing in Automated Content Networks
This development highlights a systemic challenge in large-scale automated publishing: systems that operate correctly at each decision point can still produce unintended outcomes at scale, such as content concentration and site inactivity. For publishers and content networks, such imbalance can lead to search engine penalties, reduced content diversity, and diminished user engagement. It underscores the importance of holistic system design that considers supply-demand balance and long-term network health, especially as automation becomes more prevalent in digital publishing. Learn more about best practices in content network management.
Background on Automated Content Distribution Systems
This system was designed to automate news aggregation, rewriting, and distribution across a large network of WordPress sites. It employs two main components: Stenvrik, which sources and evaluates news signals, and DojoClaw, which rewrites and distributes content based on site-specific voice and placement rules. Previous challenges in such systems include managing content relevance, avoiding spam signals, and ensuring even distribution across diverse categories. The recent discovery of publishing to favored sites only is a new manifestation of these ongoing systemic issues, exacerbated by the interaction of placement logic and supply constraints. For more insights, see similar case studies.
"Even when each decision is correct, the aggregate can still produce a skewed output. The real challenge is managing the overall system health."
— Thorsten Meyer, system operator
Unresolved Questions About Long-Term Effects
It is not yet clear whether these adjustments will fully resolve the imbalance or if the system will revert to favoring certain sites over time. The long-term impact on content quality, search rankings, and network health remains to be seen. Additionally, whether similar issues exist in other automated content systems is still unknown, as this case may be a specific instance of broader systemic challenges.
Next Steps for System Balancing and Monitoring
The system operators plan to monitor the effects of recent changes, with ongoing adjustments to content caps and site prioritization algorithms. They will also evaluate the supply of on-topic content across categories to ensure a more balanced distribution. Further audits are expected in the coming months to assess whether the imbalance persists or improves, alongside exploring methods to diversify source signals and prevent over-concentration.
Key Questions
Why is publishing to only a few sites problematic?
Concentrating content on a small number of sites can lead to search engine penalties, reduce content diversity, and diminish the network's overall value and user engagement.
What caused the imbalance in content distribution?
The imbalance was driven by a combination of topic concentration—favoring tech and AI sites—and a supply mismatch, as most input signals were tech-related while many sites covered other categories.
Are these issues specific to this system or common?
While this case is specific, similar challenges can occur in other automated content networks, especially those relying on complex decision algorithms without holistic oversight.
Will the system be able to fix this problem permanently?
Adjustments like content caps and site prioritization can improve distribution, but long-term balance depends on managing supply-demand dynamics and ongoing monitoring.
Source: ThorstenMeyerAI.com
