Page indexed without content
Where you see it: Search Console → Indexing → Pages, in the Improve page experience table of warnings
Google has this URL in its index but couldn’t read the content on it. Its help names two possible reasons: the page is cloaked, so Google gets something other than what visitors see, or it’s in a format Google can’t index. It isn’t a robots.txt block, so look at what your server sent Googlebot.
Fix it on pages you want found, and rule out a hack first.
It’s a warning: the URL stays indexed, but Google says these issues reduce its ability to understand your pages. Spam or links in Google’s copy that you never wrote point to a hack, and that is urgent. A listed download file can wait.
Check the URL Search Console listed
Paste the URL from the warning. The checker reads the status code, content type, robots.txt, noindex and sitemaps as RankHiveTools, without running JavaScript. It rules out file and blocking problems; it can’t show what Googlebot received.
Indexability report
Enter a URL to see whether Google can crawl and index it, and which Search Console status any problem causes.
What each finding means in Search Console
The Page indexing report in Search Console names the reason a page is not indexed. This is the setting behind each reason, and the guide that fixes it on WordPress. For the full list, see Search Console Errors: Fixes for WordPress.
| What the checker finds | Search Console status | Fix guide |
|---|---|---|
| robots.txt Disallow rule matches the URL | Blocked by robots.txt | Blocked by robots.txt on WordPress: How to Fix |
| noindex in robots meta or X-Robots-Tag | Excluded by ‘noindex’ tag | Excluded by Noindex Tag in WordPress: How to Fix |
| Canonical points to another URL | Alternate page with proper canonical tag | Alternate Page With Proper Canonical Tag: Meaning |
| No canonical, duplicates exist | Duplicate without user-selected canonical | Fix Duplicate Without User-Selected Canonical |
| Conflicting canonicals or weak signals | Duplicate, Google chose different canonical than user | Fix Google Chose Different Canonical Than User |
| URL redirects elsewhere | Page with redirect | Page With Redirect: What It Means on WordPress |
| Returns 404 or 410 | Not found (404) | Fix 404 Errors in Search Console on WordPress |
| Error page that returns 200 | Soft 404 | Soft 404 Errors on WordPress: Causes and Fixes |
| Returns 5xx or times out | Server error (5xx) | Fix Server Error (5xx) in Google Search Console |
| Redirect loop or overly long chain | Redirect error | Fix 404 Errors in Search Console on WordPress |
| Nothing blocks it, but few links or thin content | Discovered – currently not indexed / Crawled – currently not indexed | Discovered – Currently Not Indexed on WordPress |
Reading the result
- The URL serves a file type, not an HTML page: the Content-Type header calls it a file, and Google goes by that header. Check the type against Google’s list of indexable files.
- HTTP status 403, 429 or 503: something in front of WordPress refused an automated request. Only URL Inspection can tell you whether Google got through.
- WordPress: Not detected, on a WordPress site: the response carried none of WordPress’s usual markers, so a challenge or block page probably answered instead of your theme.
- Nothing blocks indexing: expected with this warning. Compare Google’s copy with yours in URL Inspection.
The same tool with its full guide: Indexability Checker
Why it happens on WordPress
Google’s spam policies define cloaking as showing search engines different content from what users get. On WordPress that can happen without the owner choosing it. Rendering failures count too: Google indexes only what appears in the rendered HTML.
A hack that only Google sees
Google’s Security issues help says many hackers make changes visible only to Google, hiding them from the owner. You see your normal page; Googlebot gets the hacker’s version. WordPress’s hacked-site guide names .htaccess as one of the files most often abused, and index.php, header.php, footer.php and functions.php as high targets.
A separate version served to bots
A prerendering service, or a security or caching plugin with a rule for crawlers, can answer Googlebot differently. Google calls serving bots a prerendered copy dynamic rendering: a workaround it doesn’t count as cloaking while that copy stays similar to the page visitors get.
A file Google can’t index
Google indexes HTML, PDFs, Office documents, text and common image and video formats, judging the type by the Content-Type header. Audio files and ZIP archives aren’t on its list, so a linked media-library upload can be indexed unread, as can a page sent with the wrong type.
Content that waits for a click
Google Search doesn’t scroll or click on your page. Text fetched into a tab or load more area after a click never reaches the rendered HTML, and neither does content needing scripts an optimization plugin delays until the first interaction.
Scripts and styles Google can’t load
The page isn’t blocked, but its files can be, and Google won’t render JavaScript from disallowed files. WordPress’s own robots.txt disallows only /wp-admin/, so a Disallow on /wp-content/ or /wp-includes/ was added later. Google’s renderer also caches scripts aggressively, so it can use an outdated file after an update.
How to fix it
Work from Google’s copy of the page, never your browser: every cause here looks normal to a visitor.
1. Open the copy Google indexed
Inspect the URL in Search Console and click View crawled page. You get the raw HTML from Google’s last crawl, and More info adds the HTTP headers, including Content-Type. The indexed copy has no screenshot.
2. Run a live test
Click Test live URL, then View tested page. The Screenshot tab shows the mobile version as Google rendered it; More info lists page resources and JavaScript console messages. Search both HTML copies for a sentence from the middle of your post: missing from both means Google isn’t getting your content now.
3. Clean up a hack
If Google’s copy holds spam, links or a language you never published, check the Security issues report and follow WordPress’s hacked-site order:
- Back up the site as it is, infected copy included.
- Upload fresh /wp-admin and /wp-includes folders of your current version over SFTP; the dashboard reinstall can leave files an attacker added.
- Read .htaccess, then your theme’s header.php, footer.php and functions.php, for code you didn’t write.
- Update everything, generate new secret keys in wp-config.php, then change every password.
4. Make bots get the visitors’ page
Turn off the separate bot rule, or make it serve what visitors get. Before you allowlist Googlebot past a firewall, confirm the IP: its reverse DNS should end in googlebot.com, google.com or googleusercontent.com, and the forward lookup should return the same IP. For script-heavy pages, Google recommends server-side rendering over a bot copy.
5. Put the main text in the HTML
Move click-to-load content into the post body. In your optimization plugin, exclude the scripts that draw the main content from any delay-until-interaction option, then purge the page and CDN caches.
6. Unblock theme and plugin files
Remove Disallow lines covering /wp-content/ or /wp-includes/ from the robots.txt your server sends: a physical file in the site root if one exists, otherwise your SEO plugin’s editor (Yoast SEO → Tools → File editor, Rank Math → General Settings → Edit robots.txt).
7. Deal with files on their merits
A ZIP or audio file rarely needs to rank. To take one out of Google, send an X-Robots-Tag: noindex header for it, since a file can’t carry a meta tag. If a page is mislabelled, ask your host to send Content-Type: text/html.
What Google’s copy tells you
Match Google’s copy to a row, then go to that fix.
| Google’s copy shows | Likely cause | Where the fix lives |
|---|---|---|
| Spam, foreign-language text or links you never added | A hack | .htaccess, theme and core files |
| A challenge or “checking your browser” screen | A bot-protection rule | The plugin, CDN or host that served it |
| Header and footer around an empty middle | A click-to-load, blocked or stale script | Optimization plugin, robots.txt, post body |
| No HTML at all | A file type Google can’t index | Links and server headers |
| Your full page | Fixed since the last crawl | Request indexing |
Check the fix in Search Console
Google lists this warning among the issues its live test doesn’t check, so confirm the content yourself, then wait for a recrawl.
- Run Test live URL on each fixed address: your opening sentence should be in the HTML and your page in the screenshot.
- Click Request indexing for the pages that matter most. Requests are limited per day and don’t guarantee indexing.
- Once every listed URL is fixed, click Validate fix on the warning in Indexing → Pages. Google stops at the first URL still affected; a run typically takes up to about two weeks.
- If you’re leaving listed files alone, skip validation: the count updates as Google recrawls each URL.
After a hack cleanup, inspect other URLs too: WordPress warns that a modified header.php or footer.php can affect every page request.
Can RankHive fix this?
No. The usual fixes live in hacked files, security and caching settings, server headers or the files themselves, none of which RankHive can change. On posts and pages it can handle two smaller pieces: text that loads only on a click, and robots.txt lines hiding your scripts.
What it writes, once you approve
- A rewrite of a post or page body that puts click-to-load text into the HTML.
- An Allow line in the virtual robots.txt for blocked theme or plugin files; a physical robots.txt file overrides it.
What it can’t do here
- Find or remove hacked code in .htaccess, themes or WordPress core.
- Change security, CDN, prerendering or caching-plugin settings.
- Change Content-Type headers or media-library files.
- Edit theme templates, widgets or anything outside the post body.
- Press Request indexing or Validate fix.
Every change is drafted next to the current value and waits for your approval. Each one written is logged in the Change Log, with Revert.
Check the rest of your site while you’re here
The free site check reads your public pages for titles, meta descriptions, headings, canonical tags and schema, and shows what needs fixing. If you sign up, RankHive reads your Google Search Console data every week, drafts the fixes, and writes the ones you approve to WordPress. Nothing changes on your site until you say yes.
Related issues
- URL Inspection toolNothing to fix: it’s the tool you diagnose and confirm fixes with.
- Soft 404Worth fixing, but first decide whether the page should exist.
- Crawled – currently not indexedWorth fixing for real posts; expected for archives and extras.
- Blocked due to access forbidden (403)Fix it if the page should be public; keep Google away if it never should be.
- Indexed, though blocked by robots.txtAct on it: decide, URL by URL, whether it belongs in Google.
Common questions
Is Page indexed without content an error?
No, a warning. The URL stays indexed, but Google couldn’t read its content, and says such warnings reduce its ability to understand and index your pages.
Is robots.txt causing it?
Not for the page itself; Google’s help rules that out. Robots.txt can still block the scripts and styles the page needs to render.
Can a Cloudflare challenge cause it?
Not in the usual way. Cloudflare’s docs say its managed challenge, I’m Under Attack and WAF block pages answer with a 403, which Search Console reports as Blocked due to access forbidden (403). If Google’s screenshot shows a challenge anyway, find the rule that served it.
Does a thin post cause this warning?
Not by Google’s description, which is about content it couldn’t read rather than content it judged weak. A page Google read and chose not to index is listed as Crawled – currently not indexed instead.
Sources
Checked against these pages on .
- Google Search Console Help: Page indexing report
- Google Search Console Help: URL Inspection tool
- Google Search Console Help: Security issues report
- Google Search Central: Spam policies
- Google Search Central: JavaScript SEO basics
- Google Search Central: Fix lazy-loaded content
- Google Search Central: Fix Search-related JavaScript problems
- Google Search Central: Dynamic rendering as a workaround
- Google Search Central: File types indexable by Google
- Google Search Central: Block search indexing with noindex
- Google Search Central: Verify requests from Google crawlers and fetchers
- WordPress Documentation: FAQ My site was hacked
- WordPress Developer Reference: do_robots()
- Cloudflare Rules: Error page types