What does “URL is unknown to Google” mean, and how do you get it discovered?

What the error means

In URL Inspection, “URL is unknown to Google” means Google has not seen this URL before. It is not a verdict that the page failed indexing; Google may simply have no discovery path to it yet. Add the URL to a sitemap or link to it from another page Google can crawl.

Why Google rejects it

New pages can be difficult to discover when they have no internal links, are missing from the sitemap, or use a URL variant that differs from the canonical site version. A page behind a login, blocked by robots.txt, or only reachable through a form may also be inaccessible to Google.

How to fix it

1. First confirm the exact URL and property. Use the preferred HTTPS hostname and path, and inspect the canonical URL rather than a tracking or alternate-host version.
2. Open the URL while logged out. It should load successfully, expose its main content, and not require a customer account or store preview session.
3. Link to the page from a relevant page that is already discoverable, such as a category, navigation item, or related article. Use a normal crawlable link.
4. Include the canonical URL in the sitemap, and check that robots.txt does not block crawling and that the page does not carry noindex.
5. Use URL Inspection’s live test, then Request indexing for a small number of important URLs. Discovery and indexing are not guaranteed or immediate.

Common causes

The page has no crawlable discovery path

A new page can be public and technically indexable yet remain unknown if no page Google already crawls links to it and it is absent from a sitemap. Orphaned product pages created by an app or campaign are especially easy to miss. Check internal links and sitemap inclusion rather than changing metadata first.

You inspected a URL variant or the wrong Search Console property

HTTP versus HTTPS, www versus non-www, a tracking parameter, or a different subdomain can make the inspected address differ from the one you meant to check. URL Inspection also requires a property that covers the URL. Confirm the exact canonical URL and selected property before diagnosing crawl problems.

The page is new or recently changed

Google may not know a URL immediately after publication. A submitted sitemap or indexing request can help discovery, but it does not guarantee a crawl or indexing decision on a fixed schedule. Check that the page is linked and wait for normal crawl processing rather than repeatedly submitting it.

The public route is blocked or unavailable

A page that requires a login, returns an error, or is blocked from crawling cannot be discovered and fetched normally. A private preview may work for the owner but not Googlebot. Test the URL without cookies and verify the final response, robots rules, and any redirects.

The page is a duplicate or points to another canonical URL

Google may treat the submitted URL as an alternate of another address. Parameters, host variants, or duplicate product routes can lead to a canonical different from the URL entered. Inspect the live page's canonical and URL Inspection's indexed canonical once Google has data; submit and link to the preferred URL.

Fix it on your platform

On Shopify

1. For a product, open Products and confirm it is Active and published to the Online Store channel; Shopify notes that products must be published there to appear in storefront search.
2. Check whether the product is Unlisted or has a search visibility setting that removes it from online search and sitemap discovery. Keep that state only if reduced discoverability is intentional.
3. Add a normal link from a relevant collection, navigation item, or related product section. Do not rely only on an admin preview or an unlinked campaign URL.
4. Fetch https://yourstore.example/sitemap.xml and confirm the canonical product or page URL appears if it should be discoverable.

On WooCommerce

1. In the product editor's Publish panel, confirm the status is Published and visibility is Public rather than Draft, Private, or password protected.
2. Check the SEO plugin's sitemap and robots settings for the post type or taxonomy; a published page can still be excluded from search or sitemap output.
3. Link the URL from a category, navigation menu, or relevant published page so crawlers have a path to find it.
4. Inspect permalink and canonical output after slug changes, then clear caches and test the public URL without a WordPress login.

On other platforms

1. Wix: confirm the page is published, visible to search engines in its SEO settings, and linked from a public page or included in the sitemap.
2. Squarespace or BigCommerce: check publication status, page-level search visibility, canonical URL, and sitemap inclusion for the exact page type.
3. For a custom site, add the page to a crawlable internal link path and XML sitemap; confirm the sitemap uses the preferred HTTPS hostname.
4. Across platforms, use the exact canonical URL in URL Inspection and avoid adding private or noindex URLs to a discovery sitemap.

How to confirm it is fixed

1. Open the exact URL without a login and confirm it returns a successful page, is not blocked by robots.txt, and does not carry noindex.
2. Check that a relevant public page links to the URL and that the canonical URL is included in the sitemap if it should be indexed.
3. Use Search Console URL Inspection in the property that covers the exact host; run Test live URL to confirm Google can access the current page.
4. For an important new or fixed page, request indexing once after correcting discovery and access. Google does not guarantee immediate crawl or indexing.

A worked example

Hypothetical case: a small kitchenware store adds a new size of a storage container as a separate product page for a seasonal campaign. The owner can preview it in Shopify admin, but the product remains Draft and is not linked from any collection. URL Inspection says the URL is unknown to Google. The owner decides the item should be public, changes its product status to Active, publishes it to Online Store, adds it to the relevant collection, and confirms the canonical URL appears in the sitemap. A live test then fetches the page. The owner requests indexing once and waits for Google to process the discovery request rather than assuming submission guarantees inclusion.

Other errors like this