URL is unknown to Google: what the inspection result means
URL is unknown to Google means Google has no record of the exact address you inspected. Check the protocol, host, slash and property before you request indexing.
By Crawlito · 7 min read
In short
- Google's URL Inspection help says URL is unknown to Google means Google hasn't seen this URL before: it has no record of that exact address.
- URL Inspection checks the exact address you enter, so inspecting http instead of https, www instead of non-www, or /page/ instead of /page can return unknown when Google has only seen the other form.
- The URL must belong to the Search Console property you have open, and a URL-prefix property covers only one protocol and one host.
- Run Test live URL before Request indexing: Google says you cannot request indexing for a page the live test considers non-indexable.
- Requesting indexing does not guarantee inclusion, crawling can take a few days to a few weeks, and repeat requests for the same URL do not speed it up.
On this page
- What "URL is unknown to Google" means
- Did you inspect the exact URL Google would know?
- Is the URL in the property you have open?
- Run the live test before you request indexing
- What to do when the URL really is new
- Checking many URLs at once with the API
- Frequently asked questions
- Check that crawlers can reach the page
"URL is unknown to Google" means Google has no record of the exact address you typed into URL Inspection. Google's URL Inspection help puts it plainly: Google hasn't seen this URL before. Before you treat that as a discovery problem, check that you inspected the right form of the URL in the right property, because a small difference in protocol, host or trailing slash turns an indexed page into an "unknown" one.
This post covers how to read the result, the inspection mistakes that produce it, and what to do when the URL really is new. Fixing discovery itself is covered in the guides linked near the end.
What "URL is unknown to Google" means
URL Inspection first shows what Google has in its index for the URL, not a fresh fetch. When the Page indexing section reads "Page is not indexed: URL is unknown to Google", Google is telling you the address is not on its list of known pages, so it has not crawled it either.
That puts it at the very start of the pipeline Google describes in how Search works: there is no central registry of web pages, so Google finds URLs by visiting known pages, extracting links from them, and reading the sitemaps you submit. A URL that never appeared in any of those sources stays unknown.
Compare it with the statuses that sit next to it:
| Status | Google knows the URL | Google has crawled it | What it usually points to |
|---|---|---|---|
| URL is unknown to Google | No | No | Wrong URL form or property, or a genuinely new page |
| Discovered - currently not indexed | Yes | No | Crawl rescheduled, often for capacity reasons |
| Crawled - currently not indexed | Yes | Yes | Google fetched it and chose not to index it |
| Blocked by robots.txt | Yes | No | A robots.txt rule stops the fetch |
One practical consequence: the Page indexing report shows the status of URLs that Google knows about in your property. An unknown URL will not appear there under any reason, so searching that report for it tells you nothing. URL Inspection is where this status shows up.
Did you inspect the exact URL Google would know?
URL Inspection looks up the exact string you enter. Google's canonicalization guide lists protocol variants, such as the HTTP and HTTPS versions of a site, among the ways one page ends up at several URLs, and Google's note on trailing slashes says it treats each form separately. If your site redirects everything to https://www.example.com/pricing, Google may have crawled and indexed that address while never coming across https://example.com/pricing/. Inspect the second form and the answer can be "unknown".
Common mismatches:
| You inspected | The page Google knows | Why it differs |
|---|---|---|
http://example.com/pricing | https://example.com/pricing | Different protocol |
https://example.com/pricing | https://www.example.com/pricing | Different host |
https://example.com/pricing/ | https://example.com/pricing | Trailing slash, see trailing slash URLs |
https://example.com/pricing?ref=nav | https://example.com/pricing | Query string makes a new URL |
| A staging or preview hostname | The production hostname | Different host entirely |
Redirects add one more trap. Google's help says that when a URL redirects, the inspection results reflect the tested URL in the index, not the redirect target. So inspecting an old address tells you about the old address only.
The quickest way to get the right form is to let the server tell you where the page ends up:
# Follow redirects and print each hop's status and Location header
curl -sIL https://example.com/pricing/ | grep -iE '^(HTTP|location)'HTTP/2 301
location: https://www.example.com/pricing
HTTP/2 200Inspect the final URL, the one that returns 200. Then check that the page's rel="canonical" points to that same address, and that your sitemap and internal links use it too. If all three agree and the page still shows as unknown, the mismatch is not the cause.
Is the URL in the property you have open?
Google's help says the URL must be in the current property. Which URLs a property covers depends on its type, as described in Google's property help:
- A URL-prefix property includes only URLs that start with the exact prefix, including the protocol.
https://example.com/does not coverhttp://example.com/orhttps://www.example.com/. Google says that if your site supports both protocols, you must add a separate property for each. - A Domain property, verified with a DNS record, covers all subdomains and protocols, including
www,m,httpandhttps.
If you added https://example.com/ but the live site serves https://www.example.com/, you are inspecting inside the wrong scope. The missing subdomain guide walks through mapping real landing pages to the property that owns them. A Domain property removes most of this ambiguity, because one inspection box accepts any host and protocol on the domain.
Run the live test before you request indexing
The default inspection view is the indexed record. Test live URL fetches the page in real time and follows any redirects first, so it answers a different question: could Google index this page if it crawled it now? For an unknown URL, read three fields in the live result:
- Page fetch: whether Google retrieved the page. A 404, 403, 5xx or redirect error here means the address you plan to submit is broken, or blocked by a firewall.
- Crawl allowed?: whether your site allowed Google to crawl the page or blocked it with a robots.txt rule. If it reads "No", change the rule before you do anything else.
- Indexing allowed?: whether a
noindexmeta tag orX-Robots-Tagheader blocks indexing. Google notes this field always reads "Yes" when robots.txt blocks crawling, because it cannot see the directive.
This order matters because Google says you cannot request indexing if the page is considered non-indexable in the live test. Fix the block first, re-run the test, then request.
Know what a passing live test does not tell you. Google's help says it does not check whether the URL is in a sitemap or has referring pages, does not test for duplicates or canonical choice, and cannot predict "Discovered" or "Crawled - currently not indexed". A green live test means the page is indexable, not that Google will find or keep it.
What to do when the URL really is new
If the form is right, the property is right and the live test passes, the page is simply new to Google. Click Request indexing. Google's help says the page is submitted to the indexing queue if it passes a quick check, and that both inspections and indexing requests have a daily limit per property. Google's recrawl guide adds that crawling can take a few days to a few weeks, that repeat requests for the same URL do not speed it up, and that a request does not guarantee indexing. The Discovered - currently not indexed guide covers when a request is worth making.
Request indexing is a nudge for one page. The lasting fix is to make the URL discoverable through the two routes Google names: links from pages it already knows, and sitemaps. Link the page from a relevant hub or navigation path (the orphan pages guide shows how to find pages with no route in), and list it in your XML sitemap with its canonical URL. For large batches of new URLs, Google recommends a sitemap over individual requests.
After a few days, inspect the URL again. If it moves to "Discovered - currently not indexed", discovery worked and the next question is crawl scheduling. If it stays unknown, check that the linking page itself is indexed and that the sitemap was fetched successfully.
Checking many URLs at once with the API
Pasting URLs into the inspection box one at a time does not scale for a launch or migration. The URL Inspection API returns the indexed record for one URL per call, and the inspectionUrl must be under the property you name. The siteUrl must match the property exactly: a URL-prefix property needs the trailing slash, and a Domain property uses the sc-domain: form.
{
"inspectionUrl": "https://www.example.com/pricing",
"siteUrl": "sc-domain:example.com",
"languageCode": "en-US"
}The response's indexStatusResult includes coverageState, pageFetchState, robotsTxtState, lastCrawlTime, sitemap (sitemaps Google knows list the URL) and referringUrls (pages that link to it). An unknown URL has not been crawled, so there is no crawl data to read. Google's usage limits for URL Inspection are 2,000 queries per day and 600 per minute per site at the time of writing, so check your most important URLs first. The API reference documents reading status only, with no method for requesting indexing, so use the Search Console interface or a sitemap for that.
Frequently asked questions
Is "URL is unknown to Google" an error?
No. It is a statement of fact: Google has no record of that exact URL. It becomes a problem only if the URL is the correct, canonical form of a page you want indexed.
Why is the page in Google search results but unknown in URL Inspection?
You almost certainly inspected a different form of the URL, such as another protocol, host or trailing slash variant. Find the address that appears in search results and inspect that one in a property that covers it.
Does submitting a sitemap fix an unknown URL?
A sitemap gives Google the address, which is the missing step. Google may then move it to "Discovered" and crawl it later, but neither a sitemap nor Request indexing guarantees indexing.
Does "unknown to Google" mean AI search tools cannot find the page?
Not directly. Google says a page must be indexed to be eligible as a supporting link in AI Overviews or AI Mode, but Bing and other AI search crawlers discover URLs on their own, so this status describes Google only. A page Google has never seen is still a sign that its links and sitemap entries may be missing for every crawler.
Check that crawlers can reach the page
Once the URL form, property and live test are in order, confirm the page is reachable for crawlers beyond Google. Run the free check on the canonical URL to see whether the main AI crawlers can fetch and read it.
Filed under Structure and schema. Topics: search-console, google, indexing, internal-links, sitemaps