Bing’s algorithmic deindexing of a spam site with 90,000+ ChatGPT citations is the clearest enforcement signal AI-search practitioners have seen in 2026. The site — a YMYL domain no source has named — was reportedly surging in ChatGPT answers while remaining nearly invisible in Google, and within roughly two days of a public flag, its entire Bing index footprint went to zero.
The episode matters well beyond one anonymous domain. When SEO consultant Glenn Gabe asked Bing why the action looked so different from Google’s manual-action playbook, Microsoft Bing Principal Product Manager Krishna Madhavan gave an answer that doubles as a policy statement: “we do not do one offs....not scalable....” In other words, Bing’s stated approach is to build a spam algorithm for the pattern and apply it to every site exhibiting that pattern — not to hand-penalize the one domain that got attention on X.
This guide assembles the full dated arc — from Gabe’s June 22 case study to the July 10 deindexing to the July 13 policy write-up — disentangles the two different “90K” figures that most coverage blurs together, corrects a likely misattribution (the statements came from Madhavan, not the recently retired Fabrice Canel), and translates “algorithmic at scale” into a practical resilience playbook for anyone whose AI-search visibility depends on a search index they don’t control.
- 01Bing says spam gets an algorithm, not a case file.Per Krishna Madhavan (Principal PM, Microsoft Bing, posting on X), Bing does not do one-off indexing or ranking penalties because they don’t scale — it builds a detector for the spam pattern and applies it across every site matching it.
- 02The proof case went from ~90K Bing URLs to zero in days.An anonymized YMYL site documented by Glenn Gabe on June 22 was completely deindexed from Bing on July 10 — roughly two days after a public flag on X and about 18 days after the original case study, by our derived timeline.
- 03Two different ~90K numbers collide in this story.90,000+ is the ChatGPT-citation count (Semrush Brand Radar, June 22). “Close to 90K” is the separate Bing-indexed-URL count on July 9. They measure different things and only coincidentally land near the same figure.
- 04One engine was carrying the site’s AI visibility.Bing is an official search partner for ChatGPT grounding, and the site’s Copilot citations correlated with its Bing rankings. Ranking in a single engine was enough to drive 90K+ AI citations — until the index disappeared.
- 05AI-search visibility inherits search-index fragility.There was no dashboard warning, no manual-action entry, and no published reconsideration path. If your ChatGPT citations ride on one index, an unannounced algorithmic sweep can remove them overnight.
01 — The CaseSurging in ChatGPT, dead in Google.
The story starts on June 22, 2026, when Glenn Gabe of G-Squared Interactive published a case study titled “Surging in ChatGPT, Dead in Google”. The subject: a site publishing on YMYL (Your-Money-Your-Life) topics, filled with AI-generated content, with no author bylines, no company information, and no contact details. Gabe deliberately did not name the site, and neither has any subsequent coverage — it remains anonymized in every source.
What made the case remarkable was the asymmetry. Per Semrush’s Brand Radar tool, the site was being cited in over 90,000 ChatGPT prompts as of Gabe’s June 22 check. Yet in Google, it had barely any organic search visibility and no meaningful presence in AI Overviews or AI Mode — despite Google having indexed 45,000+ of its URLs. Bing, meanwhile, had indexed 88,000+ URLs from the site and was ranking it well.
Prompts citing the site
Measured via Semrush Brand Radar on Gabe’s June 22 check. This is the AI-citation figure — a different metric from the Bing index count that later also lands near 90K.
URLs indexed, near-zero visibility
Google had indexed the pages but surfaced almost none of them — no meaningful organic visibility and zero meaningful presence in AI Overviews or AI Mode, per Gabe’s check.
URLs indexed and ranking
Roughly twice Google’s indexed count, and — unlike Google — actively ranking. This was the index that would grow to “close to 90K” URLs before going to zero on July 10.
Gabe’s read of the content profile was blunt: this looked like scaled content abuse — the same AI-generated, thin-authorship pattern that Google’s March 2026 spam update targeted when it decimated AI-generated page networks. He also flagged his own uncertainty about whether Bing would act, writing that he would hope Bing’s systems would eventually understand what was going on and drop the site over time.
"So in my opinion, this still means you should look to perform well in organic search to perform well in ChatGPT, but Bing was the driver for this example... with over 45K urls indexed in Google and 88K+ in Bing, I'd say this sure looks like scaled content abuse to me."— Glenn Gabe, President, G-Squared Interactive, GSQI Marketing Blog, June 22, 2026
02 — The Bing ConnectionOne engine was doing all the lifting.
How does a site with almost no Google visibility rack up 90,000+ ChatGPT citations? The answer is grounding. Gabe’s case study points to OpenAI’s own help documentation confirming Bing is an official search partner used for ChatGPT search grounding — when ChatGPT reaches out to the live web, Bing’s index is a primary source of candidate results. The site’s Copilot citations were also very strong, correlating directly with its Bing organic rankings. When Gabe checked Brave Search and DuckDuckGo as other possible grounding sources, results were mixed or weaker — leaving Bing as the dominant driver of the site’s AI-search footprint.
This is the second time Gabe has documented what he calls a “Mt. AI” event — his term, coined in an earlier case study, for sites whose search-engine demotions or promotions ripple downstream into AI-platform citation swings. The mechanics mirror what our AI-search citation ranking factors study found across platforms: assistants ground on search indexes, so search-index standing is upstream of AI citations — for better and, in this case, for worse.
The anonymized site’s index footprint · by engine and date
Source: GSQI (Jun 22) + Glenn Gabe via Search Engine Roundtable (Jul 9–10); percentages computed against the ~90K July 9 countThe strategic lesson cuts both ways. On the one hand, the case proves that strong rankings in a single engine — even the second-place engine — can drive enormous AI-assistant visibility, which is the core premise of generative engine optimization. On the other, it shows exactly how concentrated that dependency is: one index decision, and 90,000+ prompt citations lose their grounding source overnight.
03 — TimelineEighteen days from case study to zero.
No single source lays out the complete arc — Search Engine Roundtable’s coverage starts mid-story at the deindexing, and Gabe’s case study predates the action by weeks. The table below assembles every dated event from the primary sources into one timeline.
| Date (2026) | Event | Who | Source |
|---|---|---|---|
| June 22 | GSQI publishes “Surging in ChatGPT, Dead in Google”: anonymized YMYL site with 90K+ ChatGPT citations, 45K+ Google-indexed URLs, 88K+ Bing-indexed URLs, near-zero Google visibility | Glenn Gabe | GSQI Marketing Blog |
| July 1 | Fabrice Canel — the ~30-year Bing veteran who led indexing and crawling and created IndexNow and Bing Webmaster Tools — retires from Microsoft | Fabrice Canel | Search Engine Land / Search Engine Journal |
| July 8 | Lily Ray and Barry Schwartz tag Krishna Madhavan about the site on X; Madhavan replies: “thank you for flagging. We will take a look at this!” | Krishna Madhavan | X, via Search Engine Roundtable |
| July 9 | “Close to 90K” URLs still indexed in Bing — per Gabe’s July 10 post referencing the count “as of yesterday” | Glenn Gabe | X, via Search Engine Roundtable |
| July 10 | The site is completely deindexed from Bing; Madhavan posts “we do not do one offs....not scalable....” and, in a reply to Lily Ray, name-checks his retired colleague Canel | Glenn Gabe / Krishna Madhavan / Lily Ray | X, via Search Engine Roundtable |
| July 13 | Search Engine Roundtable publishes the policy write-up: Bing builds a spam algorithm per pattern and applies it across every site exhibiting that pattern | Barry Schwartz | Search Engine Roundtable |
Three gaps in that timeline are worth computing (these are our own derivations from the dated sources, not figures any single source states): roughly 18 days from Gabe’s original case study to the deindexing (June 22 → July 10), roughly 2 days from the public X flag to the deindexing (July 8 → July 10), and roughly 9 days between Fabrice Canel’s retirement and the action (July 1 → July 10). The middle number is the one that should recalibrate expectations: once the right person at Bing saw the pattern, removal was nearly immediate — and Gabe’s July 10 report described the result in plain terms: “The site has been completely deindexed. There were close to 90K urls indexed as of yesterday. Now gone. Poof.”
Lily Ray’s same-day reaction captured the community’s surprise that Bing acted at all: “Well there goes the article I was about to write. Looks like Bing is indeed paying attention to these spammy sites after all.”
04 — Bing’s Philosophy“We do not do one offs.”
The most consequential part of this story is not the deindexing — it’s the explanation. Asked about the action on X, Krishna Madhavan, Principal Product Manager at Microsoft Bing, stated that Bing does not perform one-off search or indexing penalties because they are not scalable. Per Barry Schwartz’s write-up of Madhavan’s statements, Bing’s method is to build a spam algorithm that detects the specific spam pattern, then apply it across every site exhibiting that pattern simultaneously — not just the one site that got flagged.
"we do not do one offs....not scalable...."— Krishna Madhavan, Principal Product Manager, Microsoft Bing, on X, July 10, 2026
Two hedges belong on the record here. First, these are statements from a Microsoft employee’s personal X account, reported by Search Engine Roundtable — not an official Microsoft or Bing blog post. Second, Microsoft has never publicly stated why this site was deindexed. The causal link to gaming ChatGPT visibility is the SEO community’s own reading — connecting Gabe’s June 22 case study to the July 10 action — which Madhavan did not publicly dispute, and implicitly reinforced by confirming Bing would look into the flagged site and engaging after the action.
The exchange also carried a personnel subtext. Nine days before the deindexing, Fabrice Canel retired from Microsoft after nearly 30 years — the engineer-PM who led Bing’s indexing, crawling, and URL discovery, and who created the IndexNow protocol and the Bing Webmaster Tools platform we covered in our Bing Webmaster Tools AI Citation Share guide. Replying to Lily Ray on July 10, Madhavan leaned into the moment: “my friend the great @facan would never have retired if he thought we would drop the ball….”
05 — Enforcement MechanicsSweep vs manual action — what site owners actually get.
Madhavan’s one-liner is best understood against the enforcement system most SEOs know: Google’s two-tier split between manual actions and algorithmic demotions. Google’s long-documented public position — repeated across Search Central documentation and Search Liaison communications — is that most ranking losses are algorithmic, not manual, and that algorithmic demotions have no reconsideration-request path: you fix the issue and wait for the next crawl or refresh. Bing’s stated model, per Madhavan, goes a step further by removing the one-off tier entirely. No published piece we found puts the three mechanisms side by side, so we built the comparison below from Google’s documented policies and the case data above.
| Mechanism | Google manual action | Google algorithmic demotion | Bing algorithmic sweep* |
|---|---|---|---|
| Detection trigger | Human reviewer confirms a policy violation, often after algorithmic or spam-report signals | Spam systems detect a pattern during crawl, indexing, or a named update rollout | A flagged example becomes input for a pattern detector — the algorithm, not the report, drives enforcement |
| Who takes action | Google’s webspam team, case by case | Ranking systems, automatically | Bing’s spam algorithms, applied to every site exhibiting the detected pattern |
| Site-owner visibility | Manual-action entry plus notification in Search Console | None — no dashboard entry, no notification | None observed in this case; SER has separately reported Bing emailing owners when a blocked site is unblocked |
| Appeal path | Reconsideration request after cleanup | None — fix the issue and wait for the next crawl or refresh | No published reconsideration path for penalties; support channels exist for other index issues |
| Scope of impact | The named site (or specific pages) in the action | Every site the system’s thresholds catch, over rollout windows | Every site matching the pattern, swept simultaneously and unannounced |
| In the July 2026 case | No equivalent — Bing says it does not do one-offs | The site’s near-zero Google visibility despite 45K+ indexed URLs is consistent with algorithmic suppression (Gabe’s read) | ~90K URLs removed from Bing’s index, reported July 10, 2026 |
*The Bing column reflects Madhavan’s July 10 X statements and Schwartz’s reporting, not published Microsoft policy documentation. The Google columns reflect Google’s long-documented two-tier enforcement system. Note the important nuance on appeals: the “no one-offs” claim is specifically about penalties — it does not mean Bing has zero site-owner communication, since Bing has separately been observed notifying owners when previously blocked sites are unblocked.
The pattern-sweep model also isn’t alien to Google’s history. From the Panda and Penguin eras through the 2024–2026 spam-update waves — including Google’s June 2026 spam update — large-scale enforcement has generally arrived as batch algorithmic sweeps rather than individual reviews. What’s new here is Bing saying the quiet part out loud, and the SEO community getting a timestamped, before-and-after demonstration.
06 — ImplicationsAI visibility inherits index fragility.
Here is our interpretation of what this episode actually changes. For a year, a quiet arbitrage existed: Google’s spam enforcement was the one that hurt, and Bing’s was widely assumed to be passive. A site could be suppressed to near-zero in Google, keep ranking in Bing, and still harvest enormous ChatGPT and Copilot visibility because assistants ground on Bing’s index. This case demonstrates that the arbitrage carries an expiry date — and that when it expires, it expires all at once. A pattern-based sweep has no rollout blog post, no dashboard warning, and no partial demotion phase. The index count goes from “close to 90K” to zero.
Projecting forward, the asymmetry that made this case possible is likely to keep narrowing. Every publicized sweep gives Bing’s spam systems another confirmed pattern, and every “Mt. AI” collapse teaches AI platforms how fragile single-index grounding is. The rational expectation for 2026–2027 is more simultaneous, unannounced enforcement — and for sites running correlated tactics, the practical risk is that a detector built from someone else’s flagged site sweeps yours in the same pass. That is the operational meaning of “we do not do one offs”: the pattern gets the penalty, not the domain.
Single-engine grounding
The site’s 90K+ ChatGPT citations rode almost entirely on Bing rankings — Brave and DuckDuckGo were mixed or weaker, Google near-zero. If one index supplies your AI visibility, one index decision can end it.
Correlated-tactic exposure
Bing’s stated model penalizes the pattern, not the domain. If your playbook matches a spam pattern other sites also run, a detector built from any one of them can sweep all of you — simultaneously and unannounced.
Missing trust signals
The profile Gabe flagged — AI-generated YMYL content, no bylines, no company info, no contact details — is exactly what pattern detectors key on. Authorship and entity signals are cheap insurance.
No warning system
There is no manual-action dashboard for an algorithmic sweep. The first signal is the index count itself — which means index monitoring across engines needs to be part of your weekly reporting, not an annual audit.
07 — PlaybookThe resilience playbook for AI-search visibility.
If your business benefits from ChatGPT, Copilot, or Perplexity citations today, this case is the prompt to stress-test how durable that visibility is. Three moves cover most of the risk surface, and none of them requires waiting for a penalty to find out where you stand.
Audit your grounding dependency
Measure where your AI citations originate. Track citation volume (e.g. Semrush Brand Radar), Bing Webmaster Tools citation data, and indexed-URL counts in both Google and Bing. If citations correlate with one engine’s rankings, you have found your single point of failure.
Harden the trust profile
Every marker Gabe flagged on the deindexed site is fixable: add real author bylines, company information, contact details, and editorial provenance — especially on YMYL topics. These signals separate scaled-but-legitimate content operations from the pattern detectors are built to catch.
Diversify the surfaces
Earn visibility that survives any single index: rank in both major engines, build citation-worthy proprietary assets, and grow branded demand that doesn’t route through an assistant at all. Grounding sources change; being the primary source is the durable position.
The uncomfortable part for high-velocity content operations: the line between “scaled content” and “scaled content abuse” is drawn by the detector, not by your intent. Our own editorial system publishes at volume, which is exactly why we hold it to named-author, verified-source, E-E-A-T-forward standards — the approach behind our agentic SEO service. If your AI-visibility strategy can’t survive a pattern detector trained on the worst site using your tactics, it isn’t a strategy — it’s a countdown.
08 — ConclusionThe pattern gets the penalty, not the domain.
AI-search visibility is only as durable as the index beneath it.
The July 2026 Bing deindexing is the first public, timestamped demonstration of what algorithmic enforcement looks like on the engine that grounds ChatGPT. An anonymized YMYL site rode 88,000+ Bing-indexed URLs to 90,000+ ChatGPT prompt citations, and lost everything roughly two days after the right person at Bing saw the flag — no warning, no dashboard entry, no published appeal path for the penalty.
Krishna Madhavan’s framing deserves to be taken at face value, with its hedges intact: it is one Principal PM’s statement on a personal X account, and Microsoft never published an official rationale. But it aligns with everything observable in the case — and with how large-scale spam enforcement has worked at Google for a decade. Detectors are built for patterns. Sites exhibiting the pattern get swept together. The single-site penalty, as a unit of enforcement, is dying on both engines.
For practitioners, the takeaway is neither panic nor schadenfreude. It’s portfolio thinking: know which index your AI citations depend on, fix the trust signals that separate you from the spam pattern, and build visibility that survives any single sweep. The sites that win the AI-search era will be the ones that were never one detector away from zero.