Page indexed without content: why Google sees an empty page

Last updated: 2026-10-30

In short

This warning means the URL is in Google's index, but Google could not read the page content. Google names two possible reasons: the page may be cloaked to Google, or it may be in a format Google cannot index. Inspect the URL and check what Googlebot actually received.

Exact label in Search Console: Page indexed without content

What it means

Google's Page indexing help says 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 might be in a format Google can't index. Google stresses this is not a case of robots.txt blocking, and tells you to inspect the page and look at the Coverage section for details.

Google's explanation is short, so diagnosis comes down to comparing what visitors see with what Googlebot gets. In Google's spam policies, cloaking means presenting different content to users and search engines, and Google notes that hacked sites often use cloaking to hide the hack from the owner. The other branch is file format: Google publishes a list of file types it can index and determines the type mainly from the Content-Type header.

Is it a problem?

Yes, if the page matters. An indexed page without readable content gives Google nothing to rank or show in a snippet, and if cloaking is involved it can point to a security problem. Treat it as a reason to inspect the URL now, not as a reason to panic.

Common causes

Different response for Googlebot

Server, CDN or plugin rules that serve Googlebot an empty or different page, on purpose or after a hack.

Unsupported or mislabeled format

A file type Google cannot index, or a wrong Content-Type header that makes Google parse the response incorrectly.

Empty responses to crawlers

Bot protection or prerendering services that return an empty body or a challenge page to crawlers.

Possibly, content that never loads

Google does not name rendering for this status, but if the HTML Googlebot receives is essentially empty and the content comes only from scripts, check rendering too.

How to fix it

  1. Inspect the URL. Open URL Inspection, read the Coverage section, then click View crawled page to see the HTTP response, headers and HTML that Google received.
  2. Compare with a live test. Run Test live URL and look at the screenshot and rendered HTML. If they differ from what visitors see, look for rules that treat Googlebot differently.
  3. Check for hacking. Open the Security issues report and look for unexpected redirects, injected code or user-agent-based rules on your server.
  4. Check format and headers. Confirm the file type is on Google's list of indexable file types and that the Content-Type header matches the content.
  5. Remove crawler-specific blocking. Make sure bot protection does not return challenge pages or empty bodies to verified Googlebot, then request indexing.

Check it with GSC Magic

gsc_inspect_url returns the coverage state, crawl details and canonicals for a single URL, and gsc_inspect_urls_batch does the same for up to 500 URLs, so your assistant can find every page in this state and check whether they share a template, directory or file type. gsc_query_analytics shows whether these pages lost impressions recently, which helps date when the problem started.

gsc_inspect_urls_batchgsc_inspect_urlgsc_query_analytics

Prompts to copy

Inspect these URLs and list every one reported as Page indexed without content, with the last crawl time and the file extension of each URL.

Show daily impressions for these URLs over the last 3 months and tell me when they started to fall.

For the URLs indexed without content, tell me what they have in common: directory, template, file type or query parameters.

Guides on the blog

Soft 404

A soft 404 is a URL that returns a 200 (success) status code but looks to Google like a not-found, empty or error page. Google excludes these pages from Search. Return a real 404 or 410 for missing pages, 301 redirect moved ones to a real replacement, and fix rendering for real pages that Google misread.

 Indexed, though blocked by robots.txt

This warning means Google indexed the URL even though robots.txt blocks crawling it, usually because other pages link to it. Google cannot read the page, so any snippet is very limited. If you want the page out of Google, remove the block and add noindex; if you want it in Google, remove the block.

 Crawled - currently not indexed

Crawled - currently not indexed means Googlebot fetched the page but Google decided not to add it to the index, at least for now. Google says it may or may not be indexed later and that you do not need to resubmit it. For pages that matter, make them clearly distinct and useful, link to them internally and check canonical signals.

Frequently asked questions

Is this the same as being blocked by robots.txt?

No. Google says explicitly that this is not a case of robots.txt blocking. For blocked URLs that still got indexed, see Indexed, though blocked by robots.txt.

Does this mean my site was hacked?

Not necessarily, but Google names cloaking as one possible reason and notes that hacked sites often use cloaking. Check the Security issues report and compare what Googlebot receives with what visitors see.

Which file types can Google index?

Google publishes a list that includes HTML, PDF, plain text, Microsoft Word and Excel files and more, and it determines the file type mainly from the Content-Type header.

Sources