Skip to content
SiteFaults

URL is not on Google

How to read the reason beneath the headline, a map to the fix for each status, and the honest truth about what requesting indexing can and cannot do.

By Max7 min read

“URL is not on Google” is the verdict the URL Inspection tool gives when the page you checked is not in the index. On its own it tells you the outcome, not the cause — and the cause is what decides the fix. The useful information is in the reason shown just below that headline. This page is a map from each common reason to what it means and how to resolve it.

Read the reason, not just the headline

Every not-indexed page shows the same top line. Underneath, in the Page indexing detail, Search Console gives the actual reason — “Discovered, currently not indexed,” “Blocked by robots.txt,” “Excluded by noindex tag,” and so on. Two pages can both say “URL is not on Google” for completely different reasons and need opposite fixes. Find that reason first; everything else follows from it.

What each reason means, and where to fix it

Discovered — currently not indexed. Google has the URL but has not crawled it, usually a crawl-priority problem. See Discovered, currently not indexed.

Crawled — currently not indexed. Google fetched the page and chose not to index it, usually a quality judgment. See Crawled, currently not indexed.

Excluded by noindex tag. A noindex is keeping the page out, often correctly. See Excluded by noindex tag.

Blocked by robots.txt. A crawl block is stopping Google reading it. See Blocked by robots.txt.

Page with redirect. The URL forwards elsewhere, so the destination is indexed instead. See Page with redirect.

Alternate page with proper canonical tag or a duplicate status. A canonical is consolidating this URL onto another. See Alternate page with proper canonical tag and Duplicate without user-selected canonical.

Not found (404) or soft 404. The page is missing or looks empty. See Soft 404.

If the reason is “URL is unknown to Google”

This is the one case where Google has never encountered the URL at all — there is nothing to diagnose because it was never discovered. Add the URL to your sitemap, link to it from pages that are already indexed (the homepage is best), confirm it is indexable, and request indexing. Discovery follows from links and the sitemap, not from waiting.

Test the live URL before you request indexing

The inspection result reflects the last time Google crawled the page, which may pre-date your fix. Use “Test live URL” to check the current state: it re-fetches the page and tells you whether it is indexable right now. Only once the live test is clean is it worth clicking Request Indexing — otherwise you are asking Google to re-crawl a problem you have not fixed yet.

The honest part: requesting indexing is a nudge, not a guarantee

Request Indexing moves a URL up the queue; it does not force Google to index a page it has judged not worth indexing. On a new or low-authority site, pages wait longer no matter how many times you request them. If many URLs are stuck, the lever is site-level — stronger internal links and a few external ones — which is covered in Discovered, currently not indexed and, for the whole-site view, why your website is not showing up on Google. For the full status list, see the Page indexing report reference, or run a full site check.

Frequently asked questions

What does 'URL is not on Google' mean?
It is the URL Inspection tool's verdict that the page you checked is not in Google's index. It reports the outcome, not the cause. The reason shown underneath it — such as 'Discovered, currently not indexed', 'Blocked by robots.txt', or 'Excluded by noindex tag' — is the information that tells you why and how to fix it.
How do I fix 'URL is not on Google'?
First read the specific reason Search Console gives beneath the headline, because the fix depends entirely on it. A noindex tag, a robots.txt block, a redirect, a canonical, a soft 404, and low crawl priority all produce the same headline but need different actions. Resolve the underlying reason, use 'Test live URL' to confirm, then request indexing.
What does 'URL is unknown to Google' mean?
It means Google has never encountered the URL — it was never discovered, so there is nothing to diagnose. Add the URL to your sitemap, link to it from pages that are already indexed such as your homepage, confirm it is indexable, and request indexing. Google discovers pages through links and sitemaps, so the fix is to give it those paths.
Should I use 'Test live URL' or 'Request Indexing' first?
Test live URL first. The inspection result reflects the last time Google crawled the page, which may be before your fix, so 'Test live URL' re-fetches the page and confirms it is indexable right now. Only once the live test is clean should you click Request Indexing — otherwise you are asking Google to re-crawl a problem that is still there.
Does requesting indexing guarantee my page gets indexed?
No. Request Indexing moves a URL up the crawl queue but does not force Google to index a page it has judged not worth indexing, and on a new or low-authority site pages wait longer regardless. If many URLs are stuck, the real lever is site-level: stronger internal links and a few external ones to raise the whole domain's crawl priority.

Run a free check on your own site

Paste any URL and get your score, your Core Web Vitals and every issue we find in about 30 seconds. No signup, no card.

Free, no signup, no card. Results in about 30 seconds, and your report is deleted automatically after 30 days.