Google impressions dropped overnight but pages are still indexed: how to diagnose it

This week r/SEO and r/TechSEO filled up with the same screenshot: Search Console impressions falling off a cliff while URL Inspection still says the pages are indexed. The dates differ (7, 11, 16, 17 and 21 October 2026), the platforms differ, and the panic is identical. An overnight drop on indexed pages has a short list of causes, and most of them can be ruled in or out from Google's own pages in under an hour. This guide puts them in the order that wastes the least time, whether the site runs on WordPress, Shopify, a headless Next.js or Astro frontend, or anything else.

Indexed only means Google has stored the page and could show it. Impressions measure whether it actually appeared for a real query. The gap between the two is where the diagnosis happens.

#What “indexed” in URL Inspection does and does not prove

The URL Inspection help explains that everything the tool shows for the indexed result is derived from the last crawled version of the page, and it prints that date under “Last crawl”. A page crawled three weeks ago can still read “URL is on Google” after its template broke yesterday. Check that date before trusting the green tick.

The same page lists what the test does not check: whether the page meets Google’s quality and security guidelines, whether the site has a manual action or a security issue, and whether the URL is subject to a legal or other removal. It also says the Google-selected canonical can only be read from the indexed data, not from a live test. In short, URL Inspection answers “can Google fetch and store this”, and the Performance report answers “does Google show it”. An overnight impression drop on indexed pages is a question for the second report.

#Is the drop real or a Search Console reporting problem

Start with the instrument. Google’s guide to debugging traffic drops includes a sketch labelled “Reporting glitch” next to the real causes and tells you to check the Search Console data anomalies page first. That page records known logging errors for the last 3 to 16 months. As of 23 October 2026 it lists nothing for October. It does list a logging error that affected impression reporting from 13 May 2025 to 27 April 2026, after which reported impressions decreased while clicks stayed untouched. A drop in impressions with flat clicks can be a measurement change, not lost visibility.

Two more reporting traps. The Performance report help says the newest data can be preliminary and is drawn as a dotted line. And different reports update on different schedules. One r/SEO poster described the mismatch:

As of October 20, my Page Indexing report was still showing October 12 as its last update.

(u/Silberzwiebel, r/SEO, 22 October 2026)

A site owner in r/TechSEO saw the same lag that week: “the latest date there is Oct 12th while the screenshot above is up to Oct 19th” (u/ddxv, r/TechSEO). Do not read a fresh Performance chart against a Page Indexing report that is a week old.

#Did Google release an update on the day traffic dropped

Open the Google Search Status Dashboard and compare the start of your drop with the listed incidents. The dashboard shows times in US/Pacific; the machine-readable feed gives UTC. For autumn 2026 it lists the September 2026 spam update from 24 September 16:15 UTC to 8 October 08:00 UTC. The Crawling and Indexing sections show no recent incidents, and the last Serving incident is from 24 February 2026.

That window overlaps with one of this week’s cases. A poster who lost about 95% of Google traffic updated the thread with exact timing:

Impressions fell from ~8,900/day to ~300 within one hour on Oct 7 (around 03:00 UTC). That’s the last stretch of the September 2026 spam update (Sep 24 to Oct 8).

(u/Longjumping-Ad1011, r/TechSEO, 23 October 2026)

The same poster added that most of roughly 120,000 sitemap URLs were programmatic pages and 86% had zero impressions in the four weeks before the drop, which is the kind of profile Google’s spam policies address. For drops on 11, 16, 17 or 21 October the picture is different: Google lists nothing for those dates, on the dashboard or on the anomalies page. Another r/TechSEO commenter put it plainly: “on Oct 21 it fell about 90% within two hours, starting around 07:00 UTC. Pages are still indexed, no manual action, and Yandex traffic didn’t move” (u/Radiant_Train_8917). An unlisted date does not prove nothing happened, since Google posts only notable updates, but it means you cannot point at an announced update and stop looking.

Also open the Manual Actions and Security Issues reports. Google’s guide names both as causes of large drops, and both take a minute to rule out.

#Is it just the weekend or seasonality

17 October 2026 was a Saturday. The most useful reply in the “drop since Oct 17” thread was about the calendar:

Oct 17 was 5 days ago and you only have data until Oct 20. You saw a dip. Could be completely random. Don’t panic over every weekend dip. If it becomes a trend, then it’s time to triage.

(u/itisoktodance, r/SEO, 22 October 2026)

A site that sells to businesses can lose a big part of its weekday demand on Saturday and Sunday. Search Console has a setting for exactly this: the Performance report offers weekly and monthly granularity to smooth “daily fluctuations (like those caused by weekends or holidays)”. Switch to weekly and see whether the drop survives.

For seasonality, Google’s guide says to set the date range to the last 16 months and check whether the same dip appeared a year earlier, then run your top queries through Google Trends to see whether demand fell across the web or only for you.

#What changed on your side: robots, noindex, canonicals, redirects, rendering

If the drop is real, not a weekend and not lined up with a listed update, look at your own release log. Google’s guide makes a distinction that matters for an overnight cliff: a misplaced noindex depends on Google recrawling each page, so it produces a slower decline, while a site-wide problem can hit fast. Typical site-wide changes:

• robots.txt. The Crawl Stats help says that if robots.txt returns 429 or 5xx and Google has no successful copy under 24 hours old, Google stops crawling the site for the first 12 hours. A misconfigured firewall rule can do this to robots.txt alone.
• Bot protection. Cloudflare’s AI bot settings put mixed-purpose crawlers used for both training and search in the Training category. I covered which options reach Googlebot in does Cloudflare block Googlebot.
• Canonicals and redirects. A theme, app or middleware release that changes how canonical tags or redirects are built can move signals to another URL or another hostname, as in my guide on a site indexed under the wrong subdomain.
• Rendering. A JavaScript or server change can leave the HTML Google receives nearly empty while the page looks fine in a browser.

One r/TechSEO reply shows how small the trigger can be:

I put an htaccess rule I thought would stop this - turns out it blocked parts of my home page from rendering as well, causing the homepage to be deindexed.

(u/emuwannabe, r/TechSEO, 22 October 2026)

Check Crawl Stats under Settings for host status (robots.txt fetching, DNS resolution, server connectivity), the share of 5xx responses and a jump in average response time on the day of the drop. Then run URL Inspection on a page that lost traffic and open the crawled HTML. A cross-check from the same thread: “Check your traffic with Bing using Bing Webmaster tools. If it’s a similar pattern, look for a technical issue” (u/sammyQc).

#How long server errors can last before indexed pages drop

Google’s page on how HTTP status codes affect its crawlers separates the two error families clearly. A 5xx or a 429 makes Googlebot slow down temporarily; already indexed URLs are kept in the index for a while but eventually dropped, and URLs that persistently return a server error are removed. For a 500 the crawl rate falls in proportion to the number of URLs returning the error, and once the server answers 2xx again Google raises the rate gradually. A 4xx other than 429 is handled differently: indexed URLs that return it are removed from the index.

Two consequences for this diagnosis. A short outage, such as the 15-minute hosting incident one commenter mentioned, does not by itself remove indexed pages overnight. A rate limiter or bot rule that answers 429 to Googlebot for days does slow crawling and, if it persists, starts removing URLs. The same page notes that a 200 response with an empty page or an error message can be reported as a soft 404, which is how a broken render shows up while every status code looks fine.

#Is the visitor your firewall blocked really Googlebot

Logs full of “Googlebot” user agents prove nothing, because any scraper can send that string. One r/TechSEO commenter blamed a two-month drop on exactly this:

Happened to me aswell. But it happened due fake Googlebot “attack”. 1st August drop. 1st October back.

(u/kimboai, r/TechSEO, 22 October 2026)

Whatever caused that case, the risk runs both ways: a rule written against fake crawlers can block the real one. Google’s guide to verifying Googlebot gives the test. Run a reverse DNS lookup on the IP from your logs, confirm the name ends in googlebot.com, google.com or googleusercontent.com, then run a forward lookup on that name and confirm it returns the same IP:

host 66.249.66.1
host crawl-66-249-66-1.googlebot.com

The alternative is matching the IP against the JSON lists of Google crawler IP ranges that the same page links. Before you tighten any firewall or CDN rule after a drop, check which of the blocked requests passed this test.

#Platform switches that hide a site from search

Every platform has one setting that can take a site out of results in a single release:

• WordPress. The Reading settings documentation says that the “Discourage search engines from indexing this site” box, since version 5.3, adds a robots meta tag with noindex,nofollow to every page that calls wp_head. A staging copy pushed to production with that box ticked is a classic cause. Because it is a page-level noindex, Google’s guide predicts a slide as pages are recrawled, not a one-hour cliff.
• Shopify. The robots.txt.liquid documentation says that adding this template replaces Shopify’s generated robots.txt, and advises saving a copy of the current /robots.txt output and comparing it with the rendered template before publishing. A theme change that ships a hand-edited robots file belongs in your release log.
• Next.js. The robots file convention lets app/robots.ts generate robots.txt, including separate rules per user agent, and the docs note it is cached by default. Read the deployed /robots.txt on production, not the source file, after each release.

#Impressions held but clicks fell: lost SERP features and AI Overviews

Google’s guide separates the two shapes. If impressions stay the same and clicks drop, the title and snippet may be weaker than they could be, or other results gained a more appealing rich result. Features also disappear from Google’s side: the anomalies page notes that FAQ rich results stopped appearing in Google Search on 7 May 2026, and sites that relied on them saw FAQ impressions fall.

AI features are counted inside the same numbers. Google’s AI features documentation says AI Overviews and AI Mode are reported in the Performance report under the Web search type, and the Search Console methodology page says all links in one AI Overview share a single position. You cannot filter AI Overviews out of the main report, so a query that now triggers an AI Overview can keep its impressions and lose clicks. My posts on generative AI in Search Console and on tracking AI search conversions cover what you can measure there.

#Which queries and pages lost the impressions

A site total hides the cause. As one r/SEO reply put it, “impressions aren’t based on your whole site holistically but the individual performance of each keyword on each page” (u/WebLinkr, r/SEO). Google’s guide gives the procedure: compare the drop period with a similar earlier period, sort the Pages table by Clicks Difference, and click through the Queries, Countries, Devices and Search appearance tabs. Check the Search type filter too, because a drop in Google Images or News looks like a site-wide drop in the default view.

Read the result like this. One page or one query group losing everything points at that page or at a SERP change for that topic. Every page, language and country losing the same share at the same hour points at a site-level cause: a ranking system, a security warning or a crawl block. Brand queries holding while generic ones collapse points at ranking, not at indexing.

A reply in the r/TechSEO thread made the same point about the 95% case: “checked manual actions and indexing in GSC? a few URLs that lost traffic would tell us more than this graph” (u/Psychological-Owl13).

#How to compare periods without fooling yourself

• Compare equal lengths that start on the same weekday, for example 28 days against the previous 28.
• Leave out the last two or three days if the chart still shows them dotted as preliminary.
• Add a year-over-year comparison before blaming an update for a seasonal dip.
• Use the 24-hour view for an hour-level cliff; Google says it shows hourly, preliminary data.
• If you pull data through the Search Analytics API, note the dataState parameter: omitted or set to final it returns only finalized data, while all includes fresh data that can still change. Mixing the two in one spreadsheet manufactures a drop on the last days.
• Hold off on new changes until you have one full week of data after your fix, so you can tell which change did what.

#Decision table: symptom, likely cause, where to check

#Worked example: one real case run through the table

The r/SEO poster from the first section published enough numbers to test the table. Search Console showed 286 impressions on 11 October 2026, 125 on 12 October, 9 on 13 October and zero by 15 October, on a bilingual site of roughly 300 URLs. The poster added that GA4 did not show a decline anywhere near as severe, that the Page Indexing report had not updated since 12 October, and that the date picker produced validation messages referring to 1 January 1970.

Run it through the rows. Clicks and impressions both fell, so the “impressions down, clicks flat” row does not fit. 11 October 2026 was a Sunday and the fall continued through the week, so the weekend row does not fit. Google lists no update, incident or anomaly for those days, so the update row does not fit either. What remains is a site-level or reporting cause, and the evidence points to checking both: a broken date picker and a stale Page Indexing report are reporting symptoms, while the poster’s note that important pages moved to “Crawled - currently not indexed” is an indexing symptom worth following with URL Inspection on those exact URLs. Neither the thread nor Google has confirmed the cause, and the table cannot either. Its job is to cut the search from eight suspects to two in a few minutes.

If you would rather have a second pair of eyes on it, my website check reads robots rules, response codes and indexing signals on any public URL, not only WordPress ones. When Crawl Stats shows slower responses around the drop, a Core Web Vitals audit covers server timing and rendering.

Last updated: 23 October 2026.