Google deindexed a 1,800-post blog that passed technical checks

Post from r/TechSEO: blank Google-selected canonical
Post: r/TechSEO, u/lucifershane

Summary

A blog with more than 1,800 posts lost every page from Google's index while its robots.txt, crawling and indexing settings all passed, which points to a site-level quality problem.

Run the live URL Inspection test on several different URLs and confirm Google sees each page's own content.

A blogger with more than 1,800 posts reported in a Reddit thread on r/TechSEO in May 2026 that Google had dropped every page on the site, while Bing kept indexing it and sending traffic.

Search Console’s Page indexing report listed 1,015 pages as Crawled - currently not indexed. On every URL the owner inspected, the Google-selected canonical was blank. Indexed pages fell from more than 1,500 to zero in the first five days of May.

The owner’s technical checks all passed. Crawling and indexing were allowed and page fetch succeeded. Robots.txt had no stray disallow rules, WordPress was not set to discourage search engines, Yoast was set to index posts, and there was no manual action. The blank canonical worried the owner most.

The blank canonical is a symptom

Google picks a canonical during indexing. Google’s guide to how Search works says that at the indexing stage it groups pages with similar content and selects the most representative one. The likelier explanation for the blank field is that Google never chose a canonical because it had decided not to index the pages at all. The same guide lists low content quality as a common reason indexing fails.

Google search analyst Gary Illyes said much the same about the status itself. Speaking at SERP Conf 2024, as reported by Search Engine Journal, Illyes said the status covers several causes, including duplicate elimination, and that “if the number of these URLs is very high that could hint at general quality issues.” He added that a high count can mean Google’s perception of the site has changed.

Illyes also named a technical cause that produces the same report: a site error that serves the same page to every URL. An earlier case showed how JavaScript error pages can lead Google to index a different site. A commenter in the thread ruled this out. After the owner shared the domain, the commenter crawled it with Screaming Frog with JavaScript rendering on. Sampled posts returned 200 status codes, self-referencing canonicals and index, follow directives, and the rendered and plain HTML versions barely differed.

What the crawl found

The same commenter found content problems that ran across the site:

  • About 295 of roughly 1,931 sitemap URLs contained -script/, and sampled pages carried Roblox exploit code alongside terms such as Keyless, Aimbot and Undetected.
  • Ordinary guide pages, and the homepage, carried “Execute Link Is Preparing” and “Download Is Ready” gate code referencing the link gateways LootLabs and Linkvertise.
  • The Google News sitemap listed guides and link pages rather than news.

The commenter matched these patterns to scaled content abuse, misleading functionality and unwanted software in Google’s spam policies, which say violating sites may rank lower or not appear at all. That is a commenter’s reading from a sample, not a Google finding. Even so, site-wide content problems of this kind fit Illyes’s description of a quality judgement far better than any technical fault the owner or the commenter found.

The timing points the same way. The owner said traffic began a slow decline around March and dropped sharply in April, which overlaps the March 2026 core update that ran from March 27 to April 8. The commenter also pointed to a spam update that started March 24. The full deindexing came weeks after the core update finished, so the dates support a quality judgement without showing which system made it.

What to do

When a large share of a site sits at Crawled - currently not indexed while fetch and indexing settings pass, look for a site-level quality problem before touching canonical tags.

  1. Rule out the identical-page error first. Run the URL Inspection live test on several different URLs and confirm Google sees each page’s own content, not a shared error page or template.
  2. Search the whole crawl for code that loads on every page, and remove it from shared templates. Template code reaches every URL, the homepage included, so one bad block shows up across the whole site. Screaming Frog’s custom search can find strings such as the gate text across a crawl.
  3. Remove or noindex pages that fall under the spam policies. In this case that meant the exploit and script pages, plus a News sitemap trimmed to real news.
  4. Rebuild the remaining pages around first-hand evidence. The commenter recommended gameplay screenshots and author expertise in place of templated “how to get”, tier list and codes pages.

Neither Google’s documentation nor the thread gives a timeline for recovery.