Can an empty page with HTTP 200 still fail indexing?

Definition: As of 17 October 2026, an empty page can return HTTP 200, the success response code, and still fail Google Search indexing. Google can classify a successful response containing an empty page or an error message as a soft 404, an indexing error identified from the content received.

Key facts

• Google's HTTP status documentation says a 200 response passes the received content to the indexing pipeline, which may index it.
• Google's technical requirements require accessible crawling, a working page returning 200, and indexable content for indexing eligibility.
• Google's Page indexing report documentation lists Soft 404 among indexing issues and recommends a 404 response for genuinely missing pages.
• Google's JavaScript SEO guide explains that Google uses rendered HTML, the page after JavaScript execution, for indexing.

Why can a successful response still fail indexing?

Google's HTTP status documentation describes separate stages: a successful response makes content available for processing, while an empty page or an error message can trigger a soft 404 in Search Console. Checking only the response code leaves the content assessment unchecked.

The technical requirements define indexable content as textual content in a supported file type that complies with Google's spam policies. They also require public access for Googlebot, Google's search crawler. A login requirement can prevent crawling even when a website works for a signed-in visitor. Meeting the minimum requirements makes a page eligible for indexing; selection remains a further step.

Can initially empty HTML become indexable after rendering?

Google's JavaScript SEO guide describes the app shell model: the initial HTML lacks the actual content, which JavaScript generates later. Google queues pages returning 200 for rendering unless a robots meta tag or header excludes indexing, then uses the rendered HTML to index the page.

The same guide says Google Search skips JavaScript from blocked files or on blocked pages. An investigation therefore needs to establish whether the expected content appears after rendering and whether required resources are accessible.

For single-page applications, which can route between views in the browser, the guide also documents error handling when server status codes are impractical. Its options include redirecting to a URL that returns 404 or adding a robots meta tag with noindex to the error page. That directive instructs Google to exclude the page from its index.

How is an affected URL checked and corrected?

Google's URL Inspection documentation distinguishes stored indexing information from a live test of the current page. The tool exposes the HTTP response and returned HTML through View crawled page. For a successful live fetch, the documented screenshot path is:

Test live URL > View tested page > Screenshot

The screenshot shows the page as Google's inspection tool renders it. View tested page > More info also exposes loaded resources and JavaScript output. These views help establish whether the expected page content reaches Google's rendering system.

Google's Page indexing report documentation recommends returning 404 for a genuinely missing page. For a real page incorrectly treated as a soft 404, it recommends adding information and inspecting the rendered page. If the page has moved, the same documentation recommends a 301 redirect to its new location. The response and content should reflect the URL's actual state.

Related terms

• Soft 404
• HTTP status codes
• JavaScript rendering and AI crawlers
• noindex

FAQ

Does a successful fetch prove that my page is indexed?

No. Google's URL Inspection documentation says fetching can succeed even when another reason prevents indexing. Check the tool's indexing information as well as the fetch result.

Should I keep returning 200 for a deleted page?

For a genuinely missing page, Google's Page indexing report documentation recommends returning 404. If you move the page, it recommends a 301 redirect to the new location.

Can I use robots.txt to keep an empty page out of search?

Google's technical requirements say a URL blocked from crawling can still appear in results. To exclude a page from indexing, use noindex and allow Google to crawl the URL so it can read the directive.

Sources

1. Google, "How HTTP status codes affect Google's crawlers", 4 February 2026
2. Google Search Central, "Google Search technical requirements", 18 December 2025
3. Google Search Console Help, "Page indexing report", accessed 17 October 2026
4. Google Search Central, "Understand the JavaScript SEO basics", 4 March 2026
5. Google Search Console Help, "URL Inspection tool", accessed 17 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer