"URL is unknown to Google" means Google has never come across this address: not in a sitemap, not as a link on any page it crawled, not through a submission. It is the earliest possible point of failure. The good news is that Google has formed no opinion about the page. The fix is to make the URL discoverable through a sitemap and internal links, then request indexing.
Where you see this status
Only in the URL Inspection tool (and the URL Inspection API, where the coverageState field reads "URL is unknown to Google"). The result looks like this:
- Headline: "URL is not on Google"
- Page indexing: "URL is unknown to Google"
- Discovery, Crawl and Indexing sections: mostly empty, last crawl "N/A"
It never shows up in Indexing > Pages, because that report is built from URLs Google knows. This matters more than it sounds. If a CMS bug leaves 2,000 pages out of your sitemap and unlinked, your Page indexing report will look perfectly healthy while those pages do not exist for Google at all.
Rule out the false alarms first
Before you treat it as a real problem, check these three things.
1. Are you inspecting the right URL? Google treats every variation as a separate URL:
https://www.example.com/guide
https://www.example.com/guide/
https://example.com/guide
http://www.example.com/guide
https://www.example.com/Guide
https://www.example.com/guide?ref=nav
If your canonical version is the first and you pasted the second, "unknown" may simply mean nobody ever linked to that variant. Inspect the canonical URL, the one in your sitemap and canonical tag.
2. Is the page brand new? A URL published an hour ago is unknown to everyone. That is not a fault.
3. Are you in the right property? A URL-prefix property for https://example.com/ cannot inspect https://www.example.com/ URLs. Search Console will tell you the URL is not in the property, but with similar looking prefixes it is an easy mistake to make.
Why discovery fails
Google discovers URLs in three ways: sitemaps, links from pages it crawls, and direct submission. When a URL stays unknown for more than a few days, one of the first two is broken.
Sitemap problems
| Problem | How to confirm |
|---|---|
| Sitemap was never submitted and is not referenced in robots.txt | Indexing > Sitemaps shows nothing, and /robots.txt has no Sitemap: line |
| Sitemap status is "Couldn't fetch" or "Has errors" | Status column in Indexing > Sitemaps, click the row for detail |
| The URL is missing from the sitemap | Pull all URLs with the sitemap URL extractor and search for it |
| Google has not re-read the sitemap since you added the URL | "Last read" date is older than your publish date |
| A child sitemap in a sitemap index is broken | Open the index row in the Sitemaps report and check each child |
| Sitemap is cached or generated on a schedule | Open the sitemap in a private window and look for the new URL |
| Sitemap lists a different variant of the URL | Compare protocol, host, slash and case character by character |
| Sitemap URL is blocked by robots.txt | Test the sitemap URL itself against your robots.txt |
The sitemap validator catches the format problems (bad XML, wrong namespace, more than 50,000 URLs, relative URLs) that lead to "Has errors".
One thing to know about timing: Google re-reads sitemaps on its own schedule, which for a rarely updated site can mean days between reads. The old trick of pinging google.com/ping?sitemap= no longer exists. Google deprecated the ping endpoint in 2023 and it now returns 404. An accurate <lastmod> is the supported way to signal that something changed.
Link problems
- The page is an orphan. Nothing links to it. Common with landing pages built for ads, pages created by importing data, and old posts that dropped out of paginated archives. See orphan pages.
- Links exist but Google cannot follow them. Google's guidance is that it can reliably follow only
<a>elements with anhrefattribute. These do not count:
<span onclick="location.href='/guide'">Guide</span>
<a onclick="openPage('guide')">Guide</a>
<button data-url="/guide">Guide</button>
- Links only appear after user interaction, such as a menu that is fetched on hover, a "load more" button or a search form.
- The linking pages are not crawled themselves: blocked by robots.txt, noindexed for a long time, or stuck as "Discovered - currently not indexed".
- The links are on pages behind a login.
To check what a crawler can actually see on the page that is supposed to link to your URL, run it through the page link extractor.
A note on nofollow
Links marked rel="nofollow" are treated as hints, and Google generally does not follow them for discovery. If the only links to a section of your site are nofollowed (some CMS plugins and forum platforms do this by default), that section may stay unknown.
The fix, step by step
- Confirm the page is indexable. No point in getting a URL discovered if it returns 404 or carries a
noindex. Click Test live URL in the inspection result. You want "URL is available to Google", "Crawl allowed? Yes" and "Indexing allowed? Yes". - Add the URL to your XML sitemap with the exact canonical form and an accurate
<lastmod>. If you have no sitemap, create one. For a small static site a simple generator or a hand-written file will do. - Make sure the sitemap is submitted in Indexing > Sitemaps and referenced in robots.txt:
Sitemap: https://www.example.com/sitemap.xml
- Link to the page from at least one page that is already indexed and relevant to it, ideally several. A link from the homepage or a major hub gets crawled soonest.
- Click Request indexing. For an unknown URL this does two jobs at once: it tells Google the URL exists and asks for a priority crawl. There is a daily quota, so reserve it for pages that matter. See Request indexing limits.
- Re-inspect after a few days. The status should progress to "Discovered", then "Crawled" or, ideally, "URL is on Google".
If many URLs are unknown
One unknown URL is a quick fix. Hundreds mean a structural fault, and you need to find it at the source:
- Compare your CMS or database with the sitemap. Count the published pages of each type and count the sitemap entries for that type. Gaps often come from sitemap plugins that exclude custom post types, cap the number of entries, or skip pages flagged in some obscure setting.
- Crawl your own site from the homepage and compare the crawled URLs with the sitemap. URLs in the sitemap that the crawl never reached are orphans.
- Look at how new content gets linked. If new pages only appear on a "latest" page that holds ten items, anything published in a busy week can fall off before Google visits.
Because unknown URLs are invisible in the Page indexing report, the only way to find them at scale is to inspect sitemap URLs through the URL Inspection API, which allows 2,000 inspections per property per day. That is how TurboIndex finds them: it reads your sitemaps, inspects every URL and lists the ones Google has never heard of, so you see the gap that Search Console's reports hide.
What not to do
- Do not request indexing for the same URL every day. Google says repeated requests do not speed things up.
- Do not rely on the sitemap alone for pages that matter. A sitemap gets a URL discovered. Internal links get it prioritised.
- Do not post the URL across social networks and forums expecting it to trigger discovery. Most of those links are nofollowed or sit on pages Google rarely crawls.
- Do not assume discovery means success. Discovery is step one of three, and the page still has to be crawled and then accepted.
What comes next
Once Google knows the URL, it moves through the rest of the pipeline. If it then stalls at "Discovered - currently not indexed", the issue is crawl priority, covered in Discovered - currently not indexed. If it is crawled and rejected, or you are not sure which stage you are at, follow the flow in why is my page not indexed.
Frequently asked questions
- What does URL is unknown to Google mean?
- Google has no record of the URL. It has not found it in any sitemap it processed or on any page it crawled, and nobody has submitted it. Since Google has never requested the page, the status says nothing about the quality of the page. It is purely a discovery problem.
- Why is my URL unknown to Google when it is in my sitemap?
- Usually because Google has not re-read the sitemap since the URL was added, the sitemap was never submitted or could not be fetched, the URL sits in a child sitemap that has errors, or the URL in the sitemap differs slightly from the one you inspected, for example by a trailing slash or www.
- Does URL is unknown to Google appear in the Page indexing report?
- No. The Page indexing report only covers URLs Google knows about. You will only see this status in the URL Inspection tool or the URL Inspection API. That means unknown URLs are invisible in your reports unless you inspect them one by one or use a tool that checks your sitemap URLs.
- How fast will Google discover a URL after I request indexing?
- Requesting indexing makes the URL known to Google immediately, and the crawl usually follows within hours to a few days. Google says crawling overall can take from a few days to a few weeks, and a crawl does not guarantee that the page will be indexed.