"URL is unknown to Google": what it means, and two of our own posts stuck in it

You open URL Inspection in Google Search Console, paste in a page you published days ago, and get this:

URL is not on Google. URL is unknown to Google.

"URL is unknown to Google" means exactly what it says. Google has no record of the page. It has not crawled it, and it has not even logged it as discovered. A URL Google knows about but has not crawled yet shows a different status, Discovered, currently not indexed. Unknown is one step earlier than that.

We can show what it looks like from the inside, because this morning two of our own posts were in it.

Our case: two posts Google had never fetched

We run Search Console's URL Inspection API over every page on this site once a day, and we log every verified Googlebot request from our server logs. Here is where the two posts stood at 13:00 UTC on 2 October:

Post A is our explainer on the "indexing issues were detected" rejection. Post B is our 30-day guest post pilot report. Neither went through a paid indexing route before today, and our server logs show no request from Google for either page, which is what a Search Console Request Indexing click produces within minutes. For post A that was deliberate, to see what a sitemap and internal links do on their own. For post B it was an oversight.

Other crawlers did not wait. Yandex fetched both posts within two minutes of publication, on the IndexNow ping. OpenAI's crawler found it through the sitemap the same evening, and Anthropic's and Ahrefs' crawlers came the same day. Googlebot read the sitemap that listed it six times over eight days and never requested the page.

Why: Google's crawl of the site had gone quiet

Google was still visiting. It just was not spending much. Counting only verified Googlebot requests for HTML pages on rank.fast:

The 75 is inflated by us: in that week we put two new posts through paid indexing routes, one of them twice, and each submission brings Googlebot. The 18 includes one submitted post too. Take those away and what is left is the honest baseline for a six-week-old domain with few links: one or two pages a day, chosen by Google, nearly all of them pages it already had: our free tools, older posts, the about page.

Search Console also reports our /blog/ index page as last crawled on 31 August. The page that links to every new post had not been fetched in a month, so a link from it did nothing. The homepage link to post B went live at 15:00 on 1 October. Googlebot fetched the homepage at 03:34 the next morning, and the post was still unknown at the 06:33 inspection.

So a sitemap entry tells Google a URL exists. It does not make Google crawl it. On a small site, Google chooses which pages get its small daily allowance, and a new URL in a sitemap is not at the front of the queue.

The usual causes, most mechanical first

1. You are inspecting a different URL. http versus https, www versus none, a trailing slash, a capital letter, a tracking parameter. URL Inspection is exact. Copy the canonical URL from the page source and inspect that.

2. Nothing points at the page. It is not in the sitemap, and no crawled page links to it. Google has no path to it.

3. The sitemap is not being read. The Sitemaps report in Search Console shows a last read date and any errors. If the last read is weeks old, or the sitemap is not submitted at all, new URLs in it are invisible.

4. The page is new and the site is small. Our case. Everything is correct and Google simply has not got to it. It can take days, or as we saw, more than a week.

5. Google is avoiding the site. Server errors or very slow responses make Googlebot back off across the whole site. Search Console's Crawl stats report shows response codes and fetch times.

How to fix it

First, inspect the exact canonical URL and make sure Test live URL passes. If it does not, the problem is not discovery. Fix what the live test reports first, as described in our page on that rejection.

Then click Request Indexing. This is the free fix, and it works quickly. On the day we launched, Googlebot fetched our homepage 77 seconds after we clicked it. There is a daily limit, so save it for pages that matter.

Link to the page from somewhere Google actually crawls. Your server logs or the Crawl stats report show which pages those are. On our site it is the tool pages, not the blog index.

Check the Sitemaps report shows a recent read date with no errors.

If it is many pages, or you cannot use Search Console for the site, a paid indexing route triggers the crawl directly. That is the service we sell, so take this paragraph with that in mind. At 13:15:51 UTC today we put both posts through our priority route. The result is below and on the live log.

To check whether a URL is in Google without Search Console, for a site you do not own or have not verified, our free Google index checker answers one URL at a time and says why when the answer is no.

What happened after we submitted

Eight days of nothing, then a verified Googlebot fetch of each page inside twenty seconds. Search Console had not caught up a minute later: the inspection status trails the crawl, and a crawl is not an index. At 14:40 UTC Search Console reported both, and this post, as submitted and indexed. That is when we checked, so it is an upper bound, not the moment of indexing. The live log carries all three.

What this proves, and what it does not

It is one site, two posts and nine days. It shows that on a young domain with few links, a sitemap entry, a ping to other engines and links from the blog index were not enough to get a single Googlebot visit in eight days. It does not show that this is typical. Sites with more links and more frequent crawling see new URLs much faster, and our own early posts were found within hours, while we were submitting everything. The drop in crawling is partly our own doing: we stopped paying for submissions, and Google's attention went back to its baseline.