~/search-console/url-unknown-to-google

§ url inspection

blocking

"URL is unknown to Google" in Search Console

Google has never seen this URL. Nothing is broken and nothing is blocked; there is simply no route to it. Here is how to build one.

This URL is not indexed and it should be. Something is in the way.

check a url →

§ check your url

Is it still happening?

Paste the URL. We look for the routes Google uses: we read your robots.txt for sitemap declarations, fetch those sitemaps and follow a sitemap index one level down, then check whether your homepage links to the URL.

what this proves

Whether your sitemaps list this URL, and whether it is linked from your homepage. If neither, nothing is pointing Google at it.

what it cannot prove

We only check the homepage for links, so a page linked from deeper in the site will show as unlinked here even though Google can reach it. We also cannot see external links, which are a discovery route of their own, and we read at most a handful of sitemaps.

§ what google is telling you

What this error actually means.

This is the emptiest status in the report, and it is good news compared with most of them. Google has no record of this URL at all. It has not crawled it, judged it, or excluded it.

Google finds URLs two ways: by following links and by reading sitemaps. If neither route leads here, the page can be perfect and still never be seen. Publishing a page does not announce it to anyone.

Most often you see this immediately after inspecting a brand new URL, in which case the answer is simply time plus a request for indexing. It is worth investigating when the page has existed for a while, because then something structural is keeping it isolated.

§ causes

6 things that produce this error.

Ordered by how often they turn out to be the cause, not by how obvious they look.

The page is genuinely new

You published it minutes or hours ago and inspected it straight away. Nothing is wrong. Discovery is not instant and there is nothing to fix beyond asking Google to look.

Nothing on the site links to it

An orphan page. It exists, it works, and no navigation, listing, or article points at it. This happens most with landing pages built outside the CMS, pages deliberately kept out of the menu, and content whose only link was on a page that has since been removed.

It is missing from the sitemap

A sitemap generated once and never regenerated, a section excluded by a filter, or a page created outside the tooling that builds the file. Google reads what the sitemap says, not what your site actually contains.

The only links to it are ones Google will not follow

Links inside a form, behind a button that runs JavaScript, in a menu rendered only after a client-side fetch, or every link marked nofollow. A crawler follows anchor tags with an href; it does not click things.

html

<!-- Not a link Google can follow -->
<button onclick="location.href='/page'">Read more</button>

<!-- A link it can -->
<a href="/page">Read more</a>

It is buried too deep to be reached

Reachable only through many clicks of pagination, or through a filter combination nothing links to directly. Google crawls broadly rather than exhaustively, and a URL twelve pages into a listing may never come up.

You are inspecting a URL that is not the one on your site

A trailing slash difference, a www mismatch, http instead of https, or different letter case. Search Console treats these as separate URLs, and the version you pasted may genuinely be unknown while the real one is indexed perfectly.

§ the fix

How to clear it.

step 1

Check you are inspecting the exact URL your site serves

Before anything else, confirm the protocol, host, trailing slash, and case match the canonical form. This is the single most common reason for the status and it takes ten seconds to rule out.

step 2

Add it to your sitemap and confirm the sitemap is being read

The sitemap must list the URL, be referenced from robots.txt, and be submitted in Search Console. A sitemap Google cannot find does nothing, and one generated at build time from a stale source will silently omit anything added since.

text

# robots.txt
Sitemap: https://example.com/sitemap.xml

step 3

Link to it from a page that is already indexed

This matters more than the sitemap entry. A sitemap says the URL exists; an internal link from an indexed page says it matters and passes ranking signals to it. One good contextual link beats a sitemap entry on its own.

step 4

Then use URL Inspection and request indexing

Once there is a real route, request indexing for the URL directly. That queues it rather than waiting for the next natural crawl. Do it after adding the link and the sitemap entry, not instead of them, or the URL goes back to being isolated as soon as the queue clears.

§ related

Next to check.

blockingDiscovered - currently not indexedGoogle knows this URL exists and has not fetched it yet. Unlike its near-namesake, this one usually has a measurable cause: your server is slow, or you are asking for more crawling than you have earned.judgement callCrawled - currently not indexedThe most common and least actionable row in the report. Google fetched the page, read it, and decided not to index it. No tool can verify a fix for this one, including ours.blockingBlocked by robots.txtGoogle was told not to fetch this URL at all. Here is which line of your robots.txt is doing it, why the page can still appear in search anyway, and how to fix it correctly.toolSitemap ValidatorValidate your sitemap.xml file format and URL count.

→ Your Sitemap Is Probably Broken. Here's How to Fix It

LintPage rules covering this: sitemap-presence, broken-internal-links

§ faq

Questions, answered.

How long does it take Google to discover a new page?

Anywhere from hours to weeks, depending on how often your site is crawled and how well the new URL is linked. A frequently updated site with the page linked from the homepage can see it within a day. A rarely-crawled site with the page in a sitemap and nothing else can take several weeks. Requesting indexing shortens this considerably.

Is a sitemap enough on its own?

It works, but it is the weaker of the two routes. A sitemap tells Google a URL exists; an internal link tells it the URL matters and passes ranking signals to it. A page that appears only in a sitemap, with nothing on the site linking to it, tends to be crawled slowly and indexed reluctantly.

What is an orphan page?

A page with no internal links pointing to it. It is reachable if you know the URL and effectively invisible otherwise. Orphans are usually accidental: a page removed from a menu, a landing page built outside the CMS, or content whose only link lived on a page that has since been deleted.

Does requesting indexing guarantee the page gets indexed?

No. It queues the URL for a crawl. Google still decides afterwards whether to index it, and a page it crawls and declines moves to a different row of the report. Requesting indexing solves discovery, which is the only problem this particular status describes.

Why does it say unknown when the page is in my sitemap?

Check three things: that the sitemap is referenced in robots.txt and submitted in Search Console, that the sitemap Google fetched actually contains the URL rather than a stale copy from an earlier build, and that the URL in the sitemap matches exactly, including the trailing slash and protocol. A near-match is a different URL as far as Google is concerned.

§ before the next deploy

Catch this one before Search Console does.

Search Console tells you weeks after the fact. LintPage runs 60 checks against a URL in about 30 seconds. Free, no signup.

run a full scan →