Technical SEO

Mueller: A 200 Status on a Down Site Can Get Pages Deindexed

When your site goes down, the worst thing your server can do is pretend everything is fine. Google's John Mueller posted two reasons why it is bad to serve a 200 status code to Googlebot when a site or its pages are down, and Search Engine Roundtable reported his comments on November 17, 2026. The first problem is visible: the error message itself can end up shown in Google's search results. The second is slower and more damaging: if the same error text appears on all your pages, Google can treat them as duplicates and drop them from the index.

The two problems Mueller named

A 200 status code tells Google the page loaded successfully. When the page actually shows an error message, Googlebot takes the response at face value and indexes what it finds. That means the error text becomes the page's content in Google's eyes, and it can appear in the search results as the snippet for a query the page used to rank for. A user searching for your content sees "something went wrong" instead of your page, and may never click through to find out whether the site is back.

The second problem is worse. If every page on the site returns the same error message with a 200 status, Google sees hundreds or thousands of pages with identical content. Its deduplication systems treat those pages as copies of each other, and the pages can drop out of the index entirely. The site does not just look broken in the results. It stops appearing in them. Recovery then takes time, because Google has to recrawl the pages, see the real content again, and decide they are worth indexing a second time.

What to serve instead

The correct response for a down site is a 5xx status code, typically 503, which tells Google the failure is temporary and the page should be retried later. A 503 says the content will be back, so Google keeps the page in the index and comes back to check. A 200 with an error message says the content has changed to an error, and Google acts on that. The difference between the two is the difference between a brief outage and a deindexing event.

This is not a new rule, but it is one that keeps getting broken, usually by accident. Load balancers, CDN configurations, and custom error pages can all return 200 by default when the backend is unreachable. The site owner sees a friendly error page and thinks the outage is handled. Googlebot sees a successful response full of identical error text and starts deduplicating. The fix is to check what status code your error pages actually return, and to make sure a down backend produces a 503, not a 200 with a smile.

Why this matters during a core update

The timing of Mueller's comment is worth noting. The November 2026 core update is still rolling out, and Google's own Search Console data is only now showing which sites moved and when. An outage that returns 200s during a core update is doubly dangerous, because the site's pages can be dropped from the index at the exact moment Google is recalculating quality across the web. The owner then faces two problems at once: the core update's reassessment and a self-inflicted deindexing, and no easy way to tell which one caused the traffic drop.

There is a related trap in the same week. Google warned on November 11 that CDN or firewall challenges can make its crawlers back off, and that pages will begin to drop out of Search if the block stays in place. Both warnings point the same way: make sure Googlebot can reach your real pages, and make sure your server tells the truth about when it cannot.

What it means for SEOs and link builders

For SEOs, this is a checklist item that belongs on every site audit: what status code does each error page return, and what happens when the backend is down. It takes minutes to test and can save weeks of recovery. If a client reports a sudden traffic drop after an outage or a migration, check the status codes before assuming the core update is to blame. A site that served 200s on error pages during an outage has a self-inflicted wound, and the fix is technical, not content-related.

For link builders, the lesson is about protecting the pages your links point to. A link to a page that drops out of the index because of a status code error is a link to nowhere. When you build links to a client's key pages, confirm those pages are actually indexed and returning the right status codes, not just live in a browser. The browser can show a pretty error page. Googlebot sees the status code, and the status code decides whether the page stays in the index.

What to watch next

Watch your own sites first. Test the error pages, check the status codes, and confirm that a down backend returns a 503. Then watch Search Console for any pages that dropped during a recent outage, and request reindexing once the fix is in place. Mueller's advice is simple, and the cost of ignoring it is measured in weeks of lost visibility.

Sources

Sources: Search Engine Roundtable, November 17, 2026.

Related reading on this site: November 2026 Core Update Still Rolling Out as Volatility Peaks on November 14, Google Tests Temporary Chats in AI Mode, Borrowing the Feature From Gemini, Mueller: Crawled or Discovered, Not Indexed Is a Quality Signal, AI Overviews Showed Up in Only 20% of Local Searches, and Mostly Copied the Map Pack, Semrush Rebuilds Traffic and Market Data With a New Model, and Old Numbers Will Change, and Domain Authority Barely Correlates With AI Citations, Search Atlas Finds.

More from Linkbaits

Turn this playbook into links

Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.

Start free trial