Page Indexed Without Content: Why It Happens and How to Fix It

This guide explains what page indexed without content means in Google Search Console, how to see exactly what Googlebot received, and the step by step fix for the causes I find most often. It is a rare warning, but when it appears on important pages it deserves fast attention, because Google has the URL and nothing useful to show for it.

What does page indexed without content mean?

It means Google has the URL in its index but, for some reason, could not read the page content, and the problem is not a robots.txt block. That is the wording on Google’s Page indexing report help page, which lists it as a warning rather than a reason for non-indexing. The page suggests possible causes such as cloaking or a format Google cannot index, and tells you to inspect the page.

In plain terms, Google can show the URL but has little or nothing to rank it with. If it is a key page, that is close to not being indexed at all.

From the cases I have looked into, the causes fall into these groups:

• Empty response to bots. A CDN, firewall or anti-bot layer sends Googlebot a blank page, a challenge page or a 200 with no body.
• Different content for Googlebot. A plugin or server rule serves bots something else, which is cloaking territory even when it is accidental.
• Content that only loads with JavaScript from resources Google cannot fetch, such as a blocked API or script.
• Unsupported or broken file formats, such as a corrupt PDF or a file served with the wrong content type.
• Server responses with no body, such as HTTP 204. Google’s documentation on how status codes affect its crawlers notes that with a 204 Google was not able to receive any content.

Can Cloudflare cause page indexed without content?

Yes, a CDN such as Cloudflare can cause it when a security or bot feature serves Googlebot a challenge or an empty response instead of the real page. The URL stays indexed from earlier crawls or links, but the latest fetch has no usable content.

Check your CDN’s security event log for requests from Google’s crawlers around the dates the warning appeared. If you see challenges or blocks, exempt verified search engine crawlers from that rule rather than turning off protection. The same logic applies to hosting firewalls and WordPress security plugins.

How do I check what Googlebot sees on my page?

You check what Googlebot sees with the URL Inspection tool: View crawled page shows the HTML and HTTP response headers Google stored from its last crawl, and Test live URL shows what Google gets right now, including a screenshot. Compare both with what a browser shows.

The live test is the only place you get a rendered screenshot, so always run it when you suspect a rendering problem.

How do I fix page indexed without content?

You fix it by finding which layer stripped or changed the content for Googlebot, removing that cause, and confirming that a live test returns the full page. Work through these steps.

1. List the URLs. In Pages, open the warning “Page indexed without content” and export the examples.
2. Inspect the crawled page. In URL Inspection, open View crawled page and read the HTML and response headers Google stored.
3. Run Test live URL. Check the screenshot, the HTML and the More info panel for blocked resources and JavaScript errors.
4. Compare with a normal browser. If the browser shows content that Google does not get, the difference is in your bot handling, caching or rendering.
5. Check the CDN and firewall. Look for challenges, blocks or rate limits applied to Google’s crawlers, and exempt verified crawlers.
6. Check plugins and server rules that change output by user agent, such as optimisation, caching or “lite mode for bots” features. Make Googlebot get the same content as users.
7. Fix rendering. If content loads by JavaScript, make sure the scripts and API endpoints it needs are not blocked by robots.txt and respond quickly. Server-side rendering of the main content is the most robust option.
8. Fix the file. For PDFs or other files, check the file opens, is not password protected and is served with the right content type.
9. Request indexing for the most important fixed URLs.

Rendering and CDN issues often overlap with crawl problems elsewhere on a site. The Search Console indexing errors guide covers the related statuses, and my robots.txt tester confirms whether scripts and API paths are crawlable.

How do I validate the fix in Search Console?

You validate by confirming a full page in the live test, then clicking Validate fix on the warning so Google rechecks the affected URLs. Do this only once every URL group you found has been fixed.

1. Run Test live URL on a fixed page and confirm the screenshot and HTML show the real content.
2. Repeat for one URL per template or folder.
3. Open the warning in Pages and click Validate fix. Do not click it again until it passes or fails.
4. Allow up to about two weeks, sometimes longer, as Google notes.
5. If it fails, open See details, inspect the failed URLs and compare them to the ones that passed. The difference usually points to the remaining rule.

After validation passes, use View crawled page again on one URL a few weeks later to be sure Google’s stored copy now contains your content.

What does this problem look like in a real investigation?

If you cannot find the layer responsible, a technical SEO audit that compares server logs with what Google stored is usually the quickest route.

Frequently asked questions

Sources

Facts checked against these official pages. Read how I check facts in my editorial policy.

• Google Search Console Help: Page indexing report
• Google Search Central: How HTTP status codes affect Google's crawlers