URL is not on Google
Where you see it: Search Console → URL Inspection (the search bar at the top of every page)
URL Inspection looked up this exact address and found it isn’t in Google’s index, so it can’t appear in search results. The reason sits one click down, under Page indexing. Some reasons are faults to fix; others mean Google indexed a different URL and this one is fine where it is.
Fix it if you want this page in search, after reading the reason.
Expand Page indexing and read the line that starts “Page is not indexed”. A noindex, a robots.txt block, a 404 or a server error on a page you want found is a real fault. Discovered or Crawled – currently not indexed is Google’s call, not a setting.
Check the URL Search Console listed
Paste the URL you inspected. The checker runs the same gates live: redirects, robots.txt, status code, noindex, canonical and sitemap. URL Inspection reports Google’s last crawl; this shows whether the reason still applies now.
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 404 Errors in Search Console on WordPress |
| 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
- Not indexable as it stands: a blocker is live. The finding names it and the Search Console reason it causes.
- Indexable, with warnings, usually a canonical to another URL: Google may index that address instead of this one.
- Nothing blocks indexing while URL Inspection still says not on Google: either Google hasn’t recrawled since your fix, or the reason is Discovered or Crawled – currently not indexed, which no setting changes.
- Could not check this URL: your site didn’t answer. With a server error in URL Inspection too, start with your host.
- A 403 here but a clean live test in Search Console: your firewall is refusing this checker, not Googlebot.
The same tool with its full guide: Indexability Checker
Why it happens on WordPress
Page indexing gives one reason, worded like the Page indexing report. These are the ones WordPress sites hit most, read for a single URL.
URL is unknown to Google
Google has no record of the address. New posts that nothing indexed links to, and post types your SEO plugin leaves out of its sitemap, start here.
Excluded by ‘noindex’ tag
The page asked to stay out. On WordPress that comes from the post’s own SEO setting, a content-type default in your SEO plugin, or Settings → Reading → “Discourage search engines from indexing this site”, which has added noindex to every page since WordPress 5.3.
Blocked by robots.txt
Crawl allowed reads No: a Disallow line matches the path, often carried over from staging. A robots.txt file in your site root replaces the one WordPress generates.
Not found (404) or Soft 404
A 404 means the post is a draft, private, scheduled or trashed, or its slug changed without a redirect. A soft 404 answers 200 but looks empty or broken to Google, like a category with no posts.
Server error (5xx) or Blocked due to access forbidden (403)
Page fetch failed: a PHP error, a host resource limit, maintenance mode, or a security plugin or CDN rule turned Googlebot away. If the live test fetches fine, it may have been temporary.
Discovered or Crawled – currently not indexed
Nothing is blocking. Discovered means Google knows the URL but postponed the crawl, often to avoid overloading the site. Crawled means Google read the page and left it out for now. Links and better content move these.
Page with redirect, an alternate, or a duplicate
An http, non-www or slashless variant that redirects, or a URL whose canonical names another page, reads not on Google while the real page is indexed. Inspect the final address before fixing anything.
How to fix it
Work from the reason, not the verdict, and prove the fix with a live test before you ask Google back.
1. Inspect the address you want in search
Use https, your site’s host and the trailing slash your permalinks produce. A verdict on a variant describes the variant.
2. Read the three gates in order
Crawl allowed, Page fetch and Indexing allowed are the checks Google ran on its last crawl. Indexing allowed always reads Yes when robots.txt blocks the page, because Google never got far enough to see a noindex.
3. Fix the setting behind the reason
Each reason has a usual home on WordPress.
- noindex: the Advanced settings of the post in Yoast SEO, Rank Math or SEOPress, the same plugin’s default for that content type, or Settings → Reading.
- robots.txt: your SEO plugin’s robots.txt editor, or the physical file in your site root if there is one.
- 404: publish or restore the post; if it moved, add a 301 from the old address.
- 403 or 5xx: your host’s error log, your security plugin’s log of blocked requests, and any CDN firewall rules.
- Discovered or Crawled: links from your strongest related posts, and content that does more than the pages already ranking.
4. Run Test live URL
Purge your page cache and CDN first. URL is available to Google means nothing blocks indexing now, though it isn’t a promise of indexing. URL is not available to Google means something still blocks it; Page availability says what.
5. Click Request indexing once
Google accepts the request only when the live test finds the page indexable, and it caps requests per day. For dozens of URLs, resubmit your sitemap instead.
When “not on Google” is the right answer
Google’s help notes this verdict isn’t always an error. Expect it on WooCommerce cart, checkout and account pages, ?replytocom and campaign links, old slugs that redirect, tag archives you noindexed, and the http twin of every page.
Check the fix in Search Console
URL Inspection has no Validate fix button. The proof is the next inspection.
- Google’s help suggests allowing at least a week after a sitemap submission or indexing request before assuming a problem.
- Inspect the URL again without a live test. The top should read URL is on Google, and Last crawl should show a date after your fix.
- URL is on Google, but has issues still means indexed; Enhancements & Experience shows the issue.
- If the URL also sits under a reason in Indexing → Pages, click Validate fix there only when every URL listed under it should leave that reason. A mix of real faults and pages you meant to exclude would fail; skip it and let the report catch up as Google recrawls.
URL is on Google means the page can appear, not that it ranks. Performance shows whether it earns impressions.
Can RankHive fix this?
Partly. RankHive can run the URL Inspection API on your pages during an analysis, so it sees the same reason you do, and on posts and pages it can write the link, content, redirect and canonical fixes. Noindex, server errors and firewall blocks stay with you.
What it writes, once you approve
- Internal links to the page from related posts, for unknown or Discovered URLs.
- A rewrite of thin content on a post or page, for Crawled – currently not indexed.
- A 301 redirect from a removed post’s old address to its replacement.
- Lines in the virtual robots.txt WordPress generates, and a canonical on a post or page in Yoast SEO, Rank Math or SEOPress.
- Publishing or scheduling a post that is still a draft.
What it can’t do here
- Set or remove noindex, or change Settings → Reading.
- Override a physical robots.txt file in your site root.
- Fix 403s, 5xx errors, or firewall, CDN and hosting settings.
- Edit or submit sitemaps, or click Test live URL, Request indexing or Validate fix.
- Change WooCommerce products or category, tag and author archives.
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.
- Excluded by ‘noindex’ tagKeep it on pages you hid on purpose; remove it from pages you want found.
- Blocked by robots.txtFix it only for URLs you want found in Google.
- Discovered – currently not indexedGive new posts time; act when posts you care about stay stuck.
- Crawled – currently not indexedWorth fixing for real posts; expected for archives and extras.
Common questions
What does “URL is not on Google” mean?
That Google’s index holds no copy of that exact address, so it can’t show in search. The reason is under Page indexing in the same panel.
The live test says “URL is available to Google”. Why is it still not on Google?
Because the live test only checks that nothing blocks indexing. Indexing happens after Google recrawls the page and decides to keep it, and the test doesn’t judge duplicates or quality.
How long after Request indexing will my page be on Google?
There’s no set time. Google says crawling can take from a few days to a few weeks, and requesting the same URL again won’t speed it up.
Why is my new WordPress post not on Google?
Usually Google hasn’t found or crawled it yet, so it reads URL is unknown to Google or Discovered – currently not indexed. Link to it from posts that are already indexed and check it’s in your sitemap. If it reads Excluded by ‘noindex’ tag, check Settings → Reading first.
Sources
Checked against these pages on .
- Google Search Console Help: Inspect and troubleshoot a single page
- Google Search Console Help: URL Inspection tool
- Google Search Console Help: Page indexing report
- Google Search Console Help: Why is my page missing from Google Search?
- Google Search Central: Ask Google to recrawl your URLs
- Make WordPress Core: Changes to prevent search engines indexing sites