{"slug": "google-stopped-distributing-runtimewire-we-kept-growing", "title": "Google stopped distributing RuntimeWire. We kept growing.", "summary": "Google Search impressions for AI-native newsroom RuntimeWire fell roughly 97% in five days, from 42,237 on August 12th to 1,327 on August 17th, following a rollout of translated pages, and the English reporting remained suppressed even after the translations were removed. RuntimeWire founder Ryan Merket documented the sequence and criticized Google's lack of an appeal process, noting that The Wall Street Journal published an AI-assisted column under Stanley Druckenmiller's byline without visible disclosure, which Google surfaced immediately.", "body_md": "# Google stopped distributing RuntimeWire. We kept growing.\n\n**The fall began before Google's August spam update and persisted after translated pages were removed from Search.**\n\nBy [Ryan Merket](/author/ryan-merket)\n· Published\n\nPrimary source: [The Wall Street Journal](https://www.wsj.com/opinion/let-the-bond-market-speak-81529d74)\n\n## Why it matters\n\nA young AI-native publisher can lose discovery across an entire domain without a manual action or direct appeal path. That gives Google's automated systems broad power over which original reporting reaches readers.\n\nGoogle Search impressions for RuntimeWire fell roughly 97% in five days. The English reporting did not suddenly change. Readers kept arriving. Our investigations kept spreading. Google went missing.\n\nToday, The Wall Street Journal published a column written with AI under the byline of billionaire Stanley Druckenmiller. The page carried no visible AI disclosure when RuntimeWire reviewed it. Google found it immediately.\n\nFine. AI-assisted writing is allowed under Google's own rules.\n\nWe would like those rules applied to us, too.\n\n### What happened to RuntimeWire\n\nRuntimeWire launched in May as an AI-native newsroom covering startups and technology. We use AI throughout the reporting process. Humans make the editorial decisions, review the sources, verify the claims, contact the people involved and take responsibility for every published word.\n\nBy August, Google Search was sending RuntimeWire tens of thousands of impressions per day. Search impressions reached 42,237 on August 12th.\n\nFive days later, they were 1,327.\n\nThe collapse affected unrelated English stories across the site. Articles that had ranked normally stopped receiving meaningful impressions. New investigations struggled to appear even when RuntimeWire created the underlying search demand.\n\nOur investigation into Anthropic's unreleased Project Parka is the cleanest example. RuntimeWire uncovered the project by examining artifacts inside Claude Desktop builds. Other publications and social accounts repeated our findings. Google's AI Mode could explain Project Parka using those details while initially citing downstream sources.\n\nWhen asked for the original source, Google identified RuntimeWire and linked our investigation. When asked why RuntimeWire was absent from its first response, it apologized and said we deserved credit for breaking the story.\n\nGoogle knew where the reporting came from. Its products used the information. Search still declined to surface the source.\n\n### The translation rollout\n\nThe collapse followed a large rollout of translated versions of existing RuntimeWire articles.\n\nThose pages were created for international readers. They were not keyword variations, doorway pages or fabricated articles. They were translations of work we had already reported and published in English.\n\nGoogle's systems apparently saw something else.\n\nSearch Console's \"Discovered - currently not indexed\" inventory surged to approximately 1,786 URLs. We responded aggressively. The translated pages were removed from Google, the sitemaps were rebuilt around the English publication, and the questionable inventory was retired.\n\nThe affected category subsequently fell from 1,786 URLs to 68. RuntimeWire's indexed share increased from approximately 52% to 73%.\n\nThe English reporting remained suppressed.\n\nWe cannot inspect Google's internal systems, so we cannot prove which classifier acted or whether the translation rollout caused the collapse. We can document the sequence:\n\n- The English articles ranked.\n- The translations appeared.\n- Search distribution collapsed across the domain.\n- The translations were removed from Search.\n- Google's coverage reports recognized the cleanup.\n- Distribution of the unchanged English articles remained near the floor.\n\nGoogle provides no meaningful appeal process for an algorithmic sitewide judgment. We contacted people at Google. We publicly asked Google's Search Liaison for help. So far, we have received no explanation.\n\n### Then the Journal published this\n\nOn August 24th, billionaire investor Stanley Druckenmiller published [\"Let the Bond Market Speak\"](https://www.wsj.com/opinion/let-the-bond-market-speak-81529d74) in The Wall Street Journal.\n\nThe following morning, [Jeff Stein reported for NOTUS](https://www.notus.org/media/stanley-druckenmillers-wsj-op-ed-bessent-ai) that Druckenmiller had used AI to write it.\n\n\"Of course I used AI,\" Druckenmiller said.\n\n\"I write everything using AI now for the same reason I use a calculator when I do math problems.\"\n\nDruckenmiller disputed the suggestion that AI wrote the entire column and said he rejected many of its recommendations. His position was straightforward: the ideas were his, he approved the final copy, and his name was attached to it.\n\nThat sounds familiar.\n\nThe Journal article was indexed immediately and amplified across Google, Reuters, Axios, the Financial Times, the Guardian and other publications. Its institutional history and Druckenmiller's expertise plainly carry enormous authority.\n\nRuntimeWire publishes under a different set of practical conditions. We disclose our use of AI. We link the underlying records. We show readers how conclusions were reached. Our investigations frequently contain several independent sources and substantially more reporting than competing coverage.\n\nWe even tested that claim.\n\nFor a [same-story reporting audit](https://runtimewire.com/in-public), RuntimeWire collected 1,996 articles published by us and 11 competing technology newsrooms. Candidate matches were clustered, publication branding was removed and 120 clean-text article pairs were used for the headline comparison.\n\nRuntimeWire won 98 comparisons, tied one and lost 21, an 81.7% win rate. We published the methodology, the workbook and the raw files. We also reported the result that made us look worse: VentureBeat beat RuntimeWire 17 to four in its direct comparison, with one tie.\n\nGoogle does not have to accept our audit as a ranking signal. Anyone can download the evidence and challenge it.\n\nThe claim that RuntimeWire is flooding the web with thin rewrites does not survive contact with the work.\n\n### Readers did not leave\n\nGoogle Search distribution collapsed. RuntimeWire continued growing through direct readership, referrals, social distribution and people sharing stories with each other.\n\nOur leading stories in the current public record include:\n\n- An investigation into OpenAI agents rebuilding a secret message board: 14,761 views.\n- The Project Parka investigation: 11,333 views.\n- Reporting on an Apple engineer who says he was fired after refusing to send customer device identifiers to AT&T: 9,426 views.\n- Coverage of Anthropic's developer backlash: 7,300 views.\n- Our Grok Bot settings investigation: 5,927 views.\n\nThese are people choosing to read RuntimeWire while Google sends almost nobody.\n\n[We publish those figures in public](https://runtimewire.com/in-public), along with weekly results, methodology, corrections and the publications that cite our reporting. The numbers come from first-party logs with obvious automated traffic removed.\n\nThe newsroom has kept moving. The audience has kept growing. Sources keep bringing us material. Competitors keep following stories we break.\n\n### Google, pick up the damn phone\n\nGoogle says generative AI content is eligible for Search when it is useful, original and created for people. Its spam policy targets scaled material created to manipulate rankings, regardless of whether humans or machines produced it.\n\nWe agree with that standard.\n\nOur request is narrow: examine what happened to RuntimeWire and judge the English reporting on its actual merits.\n\nIf an automated system mistook a translation rollout for a sitewide spam operation, fix the false positive. If another problem exists, tell us what it is. If Google's real policy gives established publishers broad freedom to use AI while treating the same technology as a risk signal on young domains, say that plainly.\n\nWe have already removed the translations from Search. We have supplied the numbers. We have shown that Google's own AI systems recognize RuntimeWire as the original source of reporting they fail to cite. We have contacted Google privately and publicly.\n\nThe work continues either way.\n\nRuntimeWire will keep breaking stories, publishing the evidence and earning readers one at a time. Search traffic would help. Permission is unnecessary.\n\nThis is Day 1.\n\nBuckle up.\n\nGoogle, pick up the damn phone.", "url": "https://wpnews.pro/news/google-stopped-distributing-runtimewire-we-kept-growing", "canonical_source": "https://runtimewire.com/article/google-stopped-distributing-runtimewire-we-kept-growing", "published_at": "2026-08-25 18:55:47+00:00", "updated_at": "2026-08-25 19:14:36.749416+00:00", "lang": "en", "topics": ["ai-policy", "ai-products", "ai-ethics"], "entities": ["RuntimeWire", "Google", "The Wall Street Journal", "Stanley Druckenmiller", "Anthropic", "Project Parka", "Claude Desktop", "Ryan Merket"], "alternates": {"html": "https://wpnews.pro/news/google-stopped-distributing-runtimewire-we-kept-growing", "markdown": "https://wpnews.pro/news/google-stopped-distributing-runtimewire-we-kept-growing.md", "text": "https://wpnews.pro/news/google-stopped-distributing-runtimewire-we-kept-growing.txt", "jsonld": "https://wpnews.pro/news/google-stopped-distributing-runtimewire-we-kept-growing.jsonld"}}