When a Content Network Starts Publishing to Itself

📊 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 managing 474 WordPress sites has begun publishing articles to its own sites, creating an imbalance that risks content saturation on some sites and neglect on others. This development raises questions about automation and content distribution fairness.

A large automated content network has started publishing articles to its own sites, creating an imbalance in content distribution across the network. This change is confirmed and raises concerns about systemic biases and the effectiveness of automated content management systems.

The network, consisting of 474 WordPress sites, previously relied on two separate systems: Stenvrik, which aggregates news signals, and DojoClaw, which rewrites and distributes content. Recent analysis revealed that 80% of posts were concentrated on just 8% of sites, primarily in the technology sector, while over half of the sites received no new content in a 28-day period. This pattern emerged despite no explicit instruction to publish to specific sites, indicating an automatic self-publishing behavior. The cause was traced to two issues: within-topic concentration, where the LLM matcher kept surfacing the same tech sites, and a supply-demand mismatch, with tech content heavily skewed toward tech sites while others lacked material. The fix involved adjusting DojoClaw’s selection algorithms, including caps on site posts and prioritizing idle sites, which allowed dormant sites to receive content and reduced overconcentration on a few sites.

Balancing a 474-site network — ThorstenMeyerAI.com
ThorstenMeyerAI.com
AI & Tooling · Engineering Note
Systems at scale

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.

Stenvrik

News-intelligence layer

Ingests hundreds of feeds, scores & geo-tags stories, surfaces what’s trending.

SUPPLY · what’s worth covering
DojoClaw

AI content engine

Rewrites a story in each site’s voice and fans it out across the catalog.

PLACEMENT · where it lands & how it reads
01The symptom

80% 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
Top 38 sites8% of catalog
80% of all posts
Top 4 sitesall tech titles
200+ articles/week each
249 sites53% of catalog
ZERO posts — half the network dark
02The diagnosis · refuse the obvious
WordPress Explained: Your Step-by-Step Guide to WordPress (2020 Edition)

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.

Cause 1 · DojoClaw

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.

Cause 2 · Stenvrik

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.

supply
tech/AI content in53%
demand
tech/AI sites in catalog~13%
03The load balancer · flip it
MixPad Free Multitrack Recording Studio and Music Mixing Software [Download]

MixPad Free Multitrack Recording Studio and Music Mixing Software [Download]

Create a mix using audio, music and voice tracks and recordings.

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.

38
sites carrying 80% of posts
249
dark sites · zero posts
overloaded
hottest sites at ~30/day
dark · 0 light healthy busy overloaded
04The three-part fix
Amazon

automated content distribution platforms

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.

1

Placement levers

DojoClaw
  • Per-site weekly cap — any site over 25 posts/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.
2

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.
3

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/day intent the code never delivered (units quirk) stays gated behind a sign-off.
05What it adds up to
Essential Life Hacks for Thriving Women with ADHD: Proven Solutions to Maximize Focus, Increase Productivity and Find Balance in Every Area of Life! (Thrivemind Books)

Essential Life Hacks for Thriving Women with ADHD: Proven Solutions to Maximize Focus, Increase Productivity and Find Balance in Every Area of Life! (Thrivemind Books)

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.

Metric
Before
After
Concentration
80% on 38 sites
cap + LRU + floor
Dormant sites
249 (53%)
shrinking ↓
Feed sources
245
271 verified
Daily ceiling
~188/day
~280/day · +49%
Fan-out width
5
7
Why two systems, not one

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.

The tradeoff taken

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.

ThorstenMeyerAI.com
Stenvrik (news-intelligence) ↔ DojoClaw (content engine) · figures reflect the May 2026 engineering audit & the behavioral changes made in response · the network’s response is being tracked.

Implications of Self-Publishing in Automated Content Networks

This development demonstrates how automated systems can develop unintended biases, such as over-publishing to favored sites and neglecting others, even without explicit instructions. It raises concerns about content fairness, diversity, and the potential for systemic echo chambers within large-scale content networks. For publishers and platform managers, it highlights the importance of monitoring and adjusting algorithms to prevent self-reinforcing biases that could diminish the value of the entire network.

Background on Automated Content Distribution Systems

The described network uses two decoupled systems: Stenvrik, which sources and assesses news signals, and DojoClaw, which rewrites and distributes content. Prior to this incident, the systems operated independently, with content flow determined by algorithms designed to balance relevance and placement. Over time, the network's internal logic led to unintended concentration, especially in tech-related sites, due to within-topic biases and supply mismatches. This case illustrates how complex automation can produce emergent behaviors that diverge from intended outcomes, especially when multiple decision layers interact without human oversight.

"The system was quietly publishing to its favorite sites, leaving others in the dark, even though no explicit instruction was given to do so."

— Thorsten Meyer, AI content system researcher

Unresolved Questions About Long-Term Effects

It is not yet clear whether this self-publishing behavior is a temporary anomaly or a persistent feature of the system. The long-term impact on content diversity, site reputation, and search engine perception remains uncertain. Additionally, whether further systemic adjustments will be necessary to prevent recurrence is still under evaluation.

Next Steps for Monitoring and System Adjustment

The team plans to monitor the system closely to observe whether the recent algorithmic adjustments effectively balance content distribution. Further refinements may include implementing stricter controls on self-publishing behaviors and enhancing oversight mechanisms to prevent bias reinforcement. Regular audits are expected to become a standard part of system maintenance to ensure equitable content spread across all sites.

Key Questions

Why is publishing to its own sites a problem for the network?

It creates an imbalance where some sites become overloaded with content while others receive none, reducing diversity and potentially harming search rankings and audience engagement.

Is this behavior intentional or a bug?

It appears to be an emergent behavior resulting from the system’s algorithms and decision logic, not an explicit instruction or bug.

Could this pattern damage the network's reputation?

Yes, over-concentrated content on a few sites may appear spammy or artificial, risking search engine penalties and audience trust issues.

Will the system be fixed to prevent this from happening again?

Yes, recent adjustments aim to balance content distribution better, but ongoing monitoring will be necessary to ensure long-term stability.

Source: ThorstenMeyerAI.com

You May Also Like

Security Observability: Integrating Security Into Monitoring

What if integrating security into your monitoring could revolutionize your threat detection and response strategies?

Policy as Code: Managing Compliance in DevOps Pipelines

Guiding DevOps teams to embed compliance directly into pipelines, Policy as Code ensures continuous enforcement—discover how to master this transformative approach.

What Developer Portals Need to Support AI Products

To support AI products effectively, your developer portal needs to provide clear…

Developer Experience: Empowering Teams Through Better Tooling

Learn how leveraging better tooling can elevate your developer experience and unlock your team’s full potential.