Page indexing report · Search Console
Page indexed without content
The URL is in Google’s index, but Google couldn’t read what’s on it.1 It sits in the report as a warning, yet it usually means Google is being blocked, and the pages will drop out if nothing changes. Here’s how to find the block when outside tests show nothing wrong.
Check the URL first
The checker shows whether the URL returns a normal HTML page to an ordinary request. It can’t reproduce a block on Google’s IP addresses, which is the usual cause. For that you need URL Inspection and your logs.
In 30 seconds
- Google indexed the URL but couldn’t read its content. Google names cloaking or an unreadable format as possible causes.1
- John Mueller says it usually means your server or CDN is blocking Google, often by IP address.2
- It’s urgent: Mueller warned these pages will start dropping out of the index.2
- It’s not robots.txt, Google says,1 and not JavaScript, according to Mueller.2
What the status means
Google’s description: the page appears in the index, but for some reason Google couldn’t read the content. It suggests the page might be cloaked or in a format Google can’t index, and states this isn’t a case of robots.txt blocking.1 Google added the status to the report in January 2021.5
It’s listed in the “Improve page experience” table, with warnings that don’t stop indexing but reduce Google’s ability to understand your pages.1 In practice it’s more serious than that table suggests.
Where it happens
The status is reported for URLs that are in the index, so it shows at the serving stage. The problem is in what Google receives when it crawls. Select a stage to see what happens there.
Discover
Google learns that a URL exists, mostly from links on pages it already knows and from XML sitemaps.
What goes wrong: Nothing links to the page and it isn’t in a sitemap, so Google never hears about it.
Report statuses at this stage
- URL is unknown to Google (shown in URL Inspection, not in the report)
Crawl
Googlebot checks robots.txt, then requests the URL. It spaces requests out so it doesn’t overload the server.
What goes wrong: The URL is blocked, returns an error, or the server is slow, so Google backs off and crawls less.
Report statuses at this stage
Render
Google runs the page’s JavaScript in a recent version of Chrome to see the finished page.
What goes wrong: Content only appears after a click or scroll, or the scripts fail, so the rendered page is nearly empty.
Report statuses at this stage
- No status of its own. Problems show up at the next stage as thin pages or soft 404s.
Index
Google decides which version of the page to keep and whether it is worth storing at all.
- Group duplicates. Pages with the same or very similar content go into one group.
- Pick a canonical. One URL represents each group. Canonical tags, redirects and sitemaps are hints, not commands.
- Select for the index. Google decides whether the canonical page is worth keeping. Google says this largely depends on quality.
What goes wrong: The page duplicates another, is marked noindex, or Google decides it adds too little to keep.
Report statuses at this stage
Serve
Indexed pages can appear in search results. Being indexed is not the same as ranking; an indexed page can still get no clicks.
What goes wrong: The page is indexed but doesn’t match what people search for, or other pages answer it better.
Report statuses at this stage
- Page is indexed
- Indexed, though blocked by robots.txt
- Page indexed without content (this page)
Is it a problem?
Usually fine
- Stray URLs you don’t want in search anyway
- A file type you don’t expect Google to index
Worth fixing
- Any page you want traffic for
- Many URLs at once, which points to a site-wide block
- Ranking drops on the same pages
- A count that rose after a CDN, hosting or security change
In the case Mueller answered, a Webflow site behind Cloudflare saw its homepage fall from first to fifteenth place.2 His advice was blunt:
“…it’s a good idea to treat this as something urgent.”
John Mueller, Google, r/TechSEO, January 20262
Find the cause
URL Inspection’s live test can’t check for this status directly.3 It still shows what Google’s request gets right now, which is the best evidence you have. Answer a few questions.
Your server or CDN is blocking Google
Mueller called it a fairly low-level block, sometimes based on Googlebot’s IP address, and stressed: “This isn’t related to anything JavaScript.”2 Google’s Martin Splitt and Gary Illyes have described how CDN flood protection can add crawlers to a blocklist on its own, and how hard that can be to control.4
Google gets a challenge page
A bot-check interstitial is all a crawler sees. Google recommends a 503 for crawlers instead.4 Where an error page comes back with a 200 status, Google may treat it as a hard error and remove the URL, or drop pages with the same error as duplicates.4
The format can’t be read
Google reads files by their Content-Type header, with some fallback when it’s missing or wrong.7 Check the header and the file type before anything else for non-HTML URLs.
Different content for Google
Cloaking is Google’s other named cause.1 Look for rules that change the response by user agent, IP or country, and rule out a hack: Google notes hackers often cloak to stay hidden.8
Causes and how to check them
Pick a cause to see how to check it. The last tab explains why outside tools miss IP-based blocks.
IP-based CDN or firewall blocks
Mueller’s explanation: “Usually this means your server / CDN is blocking Google from receiving any content.” He added that the block is often low-level and sometimes based on Googlebot’s IP address.2
Google’s own crawling team has written that CDN protection can block crawlers automatically, without the site owner knowing.4
Check: CDN and firewall security events, filtered to Google’s published IP ranges.9 Fix: allow verified Google crawlers.
Bot challenge pages
When a CDN shows a “verify you are human” page, that’s all a crawler sees. Google strongly recommends sending crawlers a 503 instead, so content isn’t dropped from the index.4
Check: the live test screenshot. Google says a page with a bot challenge means you should talk to your CDN.4 Fix: exempt verified crawlers from challenges.
Wrong Content-Type or unsupported format
Google’s report names a format Google can’t index as a possible cause.1 Google decides a file’s type from the Content-Type header, though it may use the extension or re-parse the file if the header is missing or wrong.7
curl -sI https://example.com/page | grep -i '^content-type'
# content-type: text/html; charset=utf-8Fix: serve the correct header, and check the format is on Google’s list of indexable file types.7
Cloaking
The report names cloaking as the other possible cause.1 Google defines cloaking as showing search engines different content from users, to manipulate rankings and mislead users, and notes that hackers often use it to hide a hack from the owner.8
Check: every rule that changes responses by user agent or IP, and your Security issues report. Fix: serve Google what a visitor from the same country sees.
Why outside tests miss it
Mueller said these blocks will “probably be impossible to test from outside of the Search Console testing tools”.2 A browser, curl or a crawler on your own IP gets your page, even with a Googlebot user agent, because the rule keys on Google’s IPs.
What does work: URL Inspection’s live test, and your own logs filtered to IPs verified as Google.9 Keep in mind the live test runs as Google-InspectionTool, not Googlebot.10
# Googlebot requests for one URL: IP, status, bytes sent
# (combined log format: IP = field 1, status = 9, bytes = 10)
grep 'Googlebot' access.log | grep ' /your-page ' | awk '{print $1, $9, $10}' | tail -20
# Verify an IP is really Google: reverse, then forward DNS
host 66.249.66.1
host crawl-66-249-66-1.googlebot.comHow to fix it
- Inspect an affected URL and run the live test. Open View tested page for the screenshot, HTML and headers, if available.3
- Check CDN, firewall and host security logs for requests from verified Google IPs.9
- Allow verified Google crawlers past blocks and challenges. Return 503, not a challenge, where a check must stay.4
- Check the Content-Type header and file format on non-HTML URLs.7
- Remove any rule that serves Google different content from visitors.8
- When the live test shows your page, request indexing for the most important URLs.3
What doesn’t cause it
| Often said | What’s actually true |
|---|---|
| A robots.txt block | Google states it’s not a case of robots.txt blocking.1 Some guides still list it.11 |
| JavaScript rendering problems | Mueller says it isn’t related to JavaScript.2 Some guides lead with it.12 |
| Too few words | The status means Google couldn’t read the content at all, so length is beside the point.1 Some guides suggest a word count.11 |
| Testing with a Googlebot user agent shows what Google sees | Blocks are often by IP, so Mueller says they’re probably impossible to test from outside Search Console’s tools.2 |
How long it takes
- Soonis when Mueller says pages start dropping out of the index, if they haven’t already.2
- A day or sofor a URL you request after the fix, by Google’s estimate, though it can take much longer.3
- Up to about 2 weeksfor Search Console to validate a fix, sometimes much longer.1
Google publishes no timeline for how quickly the pages drop out or recover rankings.
Without content vs soft 404
| Page indexed without content | Soft 404 | |
|---|---|---|
| Indexed? | Yes, for now | No |
| What Google got | Nothing it could read1 | A page that looks like an error or is empty, served with 2006 |
| Usual cause | A server or CDN block, often by IP2 | Not-found or empty pages that don’t return 404 |
| Reproducible from outside? | Often not | Usually yes |
Questions
What does “Page indexed without content” mean?
The URL is in Google’s index, but Google couldn’t read anything on it. Google names cloaking or an unreadable format as possible causes; Google’s John Mueller has said it usually means a server or CDN is blocking Google.
Is “Page indexed without content” urgent?
Yes, for pages you care about. It appears as a warning, but John Mueller has said pages with this problem will start dropping out of the index, and advised treating it as urgent.
Can Cloudflare cause “Page indexed without content”?
Any CDN or firewall can, if it blocks or challenges Google’s requests. The case Mueller answered involved a site behind Cloudflare. Check its security events for Google’s IP addresses and exempt verified crawlers.
Is it caused by JavaScript?
Google’s John Mueller has said it isn’t related to JavaScript and usually means a server or CDN is blocking Google. Check those before changing how the page renders.
Why can’t I reproduce the problem with curl or a crawler?
Because the block usually keys on Google’s IP addresses, not on the user agent. Use URL Inspection’s live test and check your server logs for requests from verified Google IPs.
Will Request indexing fix it?
Only after the cause is fixed. Google can’t index content it can’t receive. Once the live test shows your page, request indexing for the most important URLs.
Sources
- Google, “Page indexing report”, Search Console Help
- John Mueller (Google), r/TechSEO, reported by Search Engine Journal, January 2026
- Google, “URL Inspection tool”, Search Console Help
- Martin Splitt and Gary Illyes (Google), “Crawling December: CDNs and crawling”, Search Central Blog, December 2024
- Tal Yadid (Google), “Index Coverage Data Improvements”, Search Central Blog, January 2021
- Google, “How HTTP status codes affect Google’s crawlers”, Google Crawling Infrastructure, updated February 2026
- Google, “File types indexable by Google”, Search Central, updated February 2026
- Google, “Spam policies for Google web search”, Search Central, updated August 2026
- Google, “Verify requests from Google crawlers and fetchers”, Google Crawling Infrastructure, updated March 2026
- Google, “Google’s common crawlers”, Google Crawling Infrastructure, updated July 2026
- Rank Math, “How to Fix ‘Page Indexed Without Content’ Issue in Google Search Console”
- Onely, “How To Fix ‘Page indexed without content’ in GSC”, January 2023