TL;DR
A May 2026 engineering audit of a 474-site WordPress publishing network found that 80% of output was landing on 38 sites while 249 sites received no posts. Operator Thorsten Meyer AI attributed the imbalance to separate placement and supply problems, then applied caps, broader feed sourcing, and higher controlled throughput.
A 28-day audit of a 474-site WordPress publishing network run by Thorsten Meyer AI found that 80% of posts were published to just 38 sites, while 249 sites received no posts, exposing a distribution failure hidden by normal throughput metrics.
According to Thorsten Meyer AI, the network is fed by two separate systems: Stenvrik, a news-intelligence layer that ingests and scores feeds, and DojoClawAI, a content engine that rewrites stories for individual sites and distributes them across the catalog.
The audit found that the top 38 sites, about 8% of the catalog, carried 80% of all posts during the review period. The top four sites, all technology titles, each received more than 200 articles per week. At the same time, 249 sites, or 53% of the catalog, received zero posts.
The operator said the imbalance was not traced to a single bug. DojoClawAI was repeatedly selecting broad technology sites once stories passed its relevance checks, while Stenvrik was supplying far more technology and AI content than the catalog could evenly absorb. Thorsten Meyer AI said 53% of supplied content was technology or AI-related, while only about 13% of sites in the catalog were technology-focused.
Why It Matters
The finding matters because automated publishing systems can appear healthy when measured only by total output. In this case, the system kept producing posts, but much of the network was inactive while a small number of sites absorbed most of the load.
For publishers, advertisers, search teams, and operators of automated content systems, the case highlights a practical risk: placement metrics and supply mix can diverge even when each individual publishing decision appears valid. A network can keep meeting volume targets while weakening site coverage, category balance, and the usefulness of its own catalog.
The reported fix also points to a broader operational issue. Distribution problems in multi-site systems may require changes on both the content supply side and the placement side, rather than a single adjustment to ranking or scheduling logic.
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.
Background
Thorsten Meyer AI described the incident as an engineering finding from a May 2026 audit, not as a public outage. The network involved 474 WordPress sites and two decoupled systems: Stenvrik for supply and scoring, and DojoClawAI for rewriting and placement.
The repair had three parts. On the placement side, DojoClawAI added a per-site weekly cap, a global least-recently-used ordering method, and a floor intended to keep idle eligible sites within selection reach. On the supply side, Stenvrik audited feeds, removed broken RSS sources that returned HTTP 200 but no items, added verified feeds across non-technology categories, and flagged throttled feeds for replacement.
The scheduler was also adjusted. Thorsten Meyer AI said fan-out width increased from 5 to 7 sites and quota depth increased from 2 to 3, raising the daily ceiling from about 188 posts to about 280 posts, a reported 49% increase. The operator said a separate documented target of about 950 posts per day was not activated because of a code-units issue and remains gated behind approval.
“A 474-site network quietly collapsed onto 38 of its own favorites while half the catalog went dark.”
— Thorsten Meyer AI
“Not one bug — two independent causes.”
— Thorsten Meyer AI
“The change is behavioral: it shapes future placement, it doesn’t retroactively rescue the month sites sat dark.”
— Thorsten Meyer AI
Software Architecture with C# 14 and .NET 10: Build enterprise applications using microservices, DevSecOps, EF Core, and design patterns for Azure
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear how quickly the dormant sites will recover publishing activity, because the source material reports a behavioral change rather than completed post-fix results. The operator said proof will come from the next weeks of instrumentation.
The source also does not provide independent verification of the network data, traffic effects, search effects, revenue impact, or whether any individual sites were harmed by the imbalance. Those outcomes remain unreported.
Extracting Intelligence from RSS News Feeds Using Python and AI: From Global Headlines to Actionable Intelligence
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
The next milestone is post-fix monitoring across the 474-site catalog. The key measures will be whether the share of posts concentrated on the top sites declines, whether the 249 dormant sites begin receiving eligible content, and whether the higher daily ceiling avoids recreating the same concentration pattern.
![Express Schedule Free Employee Scheduling Software [PC/Mac Download]](https://m.media-amazon.com/images/I/41yvuCFIVfS._SL500_.jpg "When a Content Network Starts Publishing to Itself 6")
Express Schedule Free Employee Scheduling Software [PC/Mac Download]
- User-friendly drag & drop planning: Simple shift scheduling interface
- Manage time-off and leave: Add sick leave, breaks, holidays
- Email schedules to staff: Send schedules directly via email
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What happened in the publishing network?
A 28-day audit found that most posts were landing on a small group of sites. Thorsten Meyer AI said 38 of 474 sites received 80% of output, while 249 sites received none.
Was this caused by one software bug?
According to Thorsten Meyer AI, no. The operator attributed the issue to two separate causes: placement logic that favored already-selected technology sites and a supply mix heavily weighted toward technology and AI stories.
What changes were made?
The operator said it added per-site caps, global recency ordering, an idle-site floor, broader verified feed sources, and higher scheduler limits intended to spread posts across more eligible sites.
Has the fix worked?
That is still unclear. The source says the repair changes future placement behavior, but the results must be measured over the following weeks.
Source: Thorsten Meyer AI
