stillindexedStart monitoringOpen the app

Search Console Page indexing: Improve page experience

Page indexed without content: what it means

Google indexed the URL but could not read its content: cloaking, often accidental, or a format it cannot index. How to compare what Googlebot gets.

Google indexed the URL but could not read its content. Google names two possible reasons: the page is cloaked, serving Googlebot something different from visitors, or it is in a format Google cannot index. It is not a robots.txt block. Compare what Googlebot and a browser receive, then serve both the same content.

What "Page indexed without content" means

Google: "This page appears in the Google index, but for some reason Google could not read the content. Possible reasons are that the page might be cloaked to Google or the page might be in a format that Google can't index. This is not a case of robots.txt blocking." It sits in the Improve page experience table as a warning: the URL is indexed, with nothing in it to rank.

Is it a problem?

Usually a problem

Yes. An indexed URL whose content Google could not read has nothing to rank for, and Google points this status at its documentation on cloaking.

Causes, most likely first

  1. A CDN, firewall or bot protection layer serving Googlebot a challenge or block page while visitors get the real page. Usually unintended, but it is the shape of cloaking.
  2. Server logic that varies the response by user agent and sends crawlers an empty or stripped-down document.
  3. A file type Google cannot index.
  4. A page whose content is rendered entirely by JavaScript that fails for Googlebot, leaving an empty shell.

How to confirm it

  1. Run the crawler versus browser checker. It fetches the URL as Googlebot and as a browser and compares status, directives and content.
  2. Inspect the URL and open View crawled page to see the HTML Google stored. Google notes the live test cannot check this status, so the indexed result is what counts.
  3. Check CDN and firewall logs for challenges or blocks served to verified Googlebot IPs.

Crawler versus browser checker

How to fix it

  1. Serve Googlebot the content a visitor gets: exempt verified Googlebot from bot challenges, or remove user-agent-based variations.
  2. If the format is the problem, publish the content in HTML or another file type Google can index.
  3. If the content depends on JavaScript, make sure it renders without blocked resources, or render it on the server.
  4. Once Googlebot receives the content, request indexing for the affected URLs and click Validate fix.

How long recovery takes

Google has to recrawl the page to read the content, which can take "anywhere from a few days to a few weeks". Request indexing asks for one URL sooner but does not guarantee it.

After a fix, Validate fix on the issue asks Google to recheck the affected URLs. Google says validation "typically takes up to about two weeks, but in some cases can take much longer". Without it, the count still updates as Google recrawls, and an issue leaves the table once 90 days pass with no instance.

Would monitoring have caught it?

No. Nothing in this status is a change to a status code, a robots.txt rule, a noindex, a redirect or a canonical tag, which are what the monitor watches, so it would not have warned you before Google reported it. The checks above are how to investigate it.

Further reading

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-06. If Google has changed a page since, Google's page wins and we would like to know.