URL Inspection saying “URL is unknown to Google” looks alarming but means something simpler than you’d think: the URL exists on your site, but Google has never encountered it. Not refused, not noindexed, not blocked by robots.txt — it just never entered Google’s discovery pipeline. Google’s own docs define this status plainly: “Google hasn’t seen this URL before.”
Fastest fix: open the URL in Search Console’s inspection box, click Test live URL to confirm the page returns 200 and is indexable, then click Request indexing. In parallel, make sure the URL is in your sitemap.xml and is linked from at least 2-3 other pages on your site. Then wait — discovery is the easy part; indexing still takes days.
This is the normal state for a freshly published article. Usually no panic needed: it flips to “Crawled” or “URL is on Google” within a few days to two weeks. But a handful of causes never resolve on their own, and those are the ones worth checking.
Which bucket are you in?
| What you see / know | Most likely cause | Go to |
|---|---|---|
| Page is days old, in sitemap, has internal links | Normal discovery lag | Step 1, then wait |
rg finds zero internal links to the URL | Orphan page | Cause 1 |
URL missing from sitemap.xml | Not submitted for discovery | Cause 2 |
| Search Console Sitemaps panel empty / “Couldn’t fetch” | Sitemap never registered | Cause 3 |
| Domain went live this week | Whole-site crawl not done | Cause 4 |
| Inspection says “Excluded by robots.txt” instead | Blocked, not unknown | Cause 5 |
| Slug contains non-ASCII characters | Encoding mismatch in sitemap | Cause 6 |
Note: the URL Inspection tool returns one of a fixed set of statuses. “URL is on Google”, “URL is on Google, but has issues”, “URL is not on Google”, and “URL is unknown to Google” are the live-index verdicts; a Test live URL run returns “URL is available to Google” or “URL is not available to Google” instead. If you see anything other than “unknown,” you are reading a different problem.
Common causes
1. No internal links point to it
Google discovers URLs through three main pipes: sitemap, internal links, and external links. Zero internal links plus not in the sitemap equals a permanent unknown. Google’s own discovery guidance is explicit that a sitemap alone is not enough — links are how the crawler finds and prioritizes pages.
How to confirm:
# Site-wide internal link search
rg 'href="/my-new-url/?"' src/
# Zero lines = orphan page, nothing links to it2. Not in sitemap.xml
The publish script forgot to add the new URL to the sitemap, or your sitemap is hand-maintained and someone forgot to edit it.
How to confirm:
curl -s https://yourdomain.com/sitemap.xml | grep -c "/my-new-url"
# Want >= 1If your sitemap is split into a sitemap index (sitemap-index.xml pointing at child sitemaps), grep the child file the URL belongs to, not just the index.
3. Sitemap was never submitted
Search Console’s Sitemaps panel is empty or shows “Couldn’t fetch.” Google doesn’t know you have a sitemap at all.
How to confirm: Search Console left sidebar → Indexing → Sitemaps. Check whether you’ve submitted one, whether the status reads “Success,” and whether “Discovered URLs” roughly matches your actual article count.
4. Brand-new site, Google hasn’t crawled the whole site yet
The domain only went live a few days ago. Site-wide crawling isn’t finished. Even URLs that are already in the sitemap can take a week or two to move out of “unknown.” This is expected and not a defect.
5. URL blocked by robots.txt
If robots.txt contains Disallow: /article/, Google sees the URL in the sitemap but won’t fetch it — and URL Inspection will display “Excluded by robots.txt,” not “unknown.”
If you actually see “unknown,” robots.txt isn’t the cause. Verify with the live test, which reports the robots verdict directly.
6. Special characters or encoding issues in the URL
Non-ASCII paths (Unicode characters in slugs or path segments) must be percent-encoded in the sitemap, or Google may not be able to fetch them.
How to confirm: URLs in the sitemap should be in percent-encoded form (e.g. /%E6%96%87%E7%AB%A0/...), not raw non-ASCII characters. The <loc> value must also be XML-escaped (& for &).
Shortest path to fix
Step 1: Test live, then Request indexing
Open Search Console → paste the full URL into the inspection box at the top → wait for the result. Click Test live URL first: this confirms the page returns HTTP 200, isn’t noindexed, and isn’t robots-blocked right now. If the live test says “URL is available to Google,” click Request indexing.
This is the fastest “hey Google, here’s a URL” signal. It puts the page in a priority crawl queue. Two realistic expectations:
- It does not index in 10 minutes. The status usually stays “unknown” or moves to “Crawled - currently not indexed” for a while before becoming “URL is on Google.”
- The daily quota is roughly 10-12 URLs per property (Google doesn’t publish the exact number, as of June 2026). When you hit it, the button greys out; wait ~24 hours. Save it for your important pages.
Step 2: Add the URL to sitemap.xml
If you’re on Astro / Next / Hugo with auto-generated sitemaps, new pages enter automatically on the next build and deploy. If hand-maintained:
<url>
<loc>https://yourdomain.com/articles/my-new-url/</loc>
<lastmod>2026-05-21</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>After deploy, go to Search Console → Indexing → Sitemaps and resubmit (or wait for the next automatic re-fetch).
Step 3: Add internal links from homepage / index / related
# Verify after editing
rg 'href="/articles/my-new-url/?"' src/
# Want >= 3At minimum, link the new URL from:
- The homepage “latest articles” section
- The
/articles/index page - 2-3 related articles’ “Related reading” section
These give Googlebot a real path to the page and signal that it matters, which a bare sitemap entry doesn’t.
Step 4: Submit the sitemap if you never did
Search Console → Indexing → Sitemaps → type sitemap.xml (or sitemap-index.xml) → Submit.
Status should flip to “Success” within a minute or two and “Discovered URLs” will appear. If it shows “Couldn’t fetch,” run curl -I https://yourdomain.com/sitemap.xml — it must return 200, the right content type, and not be behind a redirect chain or auth wall.
Step 5: Wait 3-14 days
For an established site, a Request-indexed URL is often crawled within a day or so. For a new site without backlinks, 10-14 days is normal and can stretch to a few weeks. During this window:
- Re-check URL Inspection roughly weekly; status migrates “unknown” → “Crawled - currently not indexed” → “URL is on Google.”
- Don’t Request indexing the same URL every day. It doesn’t speed anything up and burns your daily quota.
How to confirm it’s fixed
You’re done when, in this order:
curl -I https://yourdomain.com/articles/my-new-url/returns200.curl -s https://yourdomain.com/sitemap.xml | grep -c "/my-new-url"returns>= 1.rg 'href="/articles/my-new-url/?"' src/returns>= 2-3internal links.- Search Console URL Inspection no longer says “unknown” — it shows “Crawled - currently not indexed” (discovered, indexing pending) or “URL is on Google” (done).
- A
site:yourdomain.com/articles/my-new-url/search eventually returns the page. This is the last step to flip and can lag the inspection status by days.
Easy to misdiagnose
- “Unknown” doesn’t equal “rejected.” Google has never seen it, so rejection isn’t even possible yet. Don’t start tearing out noindex tags you never had.
- Expecting instant indexing after submission. From unknown to indexed usually takes 3-14 days. Established sites: 1-3 days. Brand-new sites: 2-4 weeks.
- Thinking sitemap resubmission speeds things up. One submission registers the sitemap; Google re-fetches it on its own schedule. Repeat manual submissions are effectively no-ops.
- Daily Request indexing wastes quota. Once per URL is enough. Save the rest for other pages.
- Confusing “unknown” with “Discovered - currently not indexed.” The latter means Google did find the URL and chose not to crawl it yet — a different problem with different fixes.
Prevention
- Your new-article publish script should do three things atomically: write the file, add the URL to the sitemap, and add internal links from homepage and index.
- Add a build-time check that every article is referenced from at least 2-3 other files (catches orphans before deploy).
- Keep the sitemap auto-generated; never hand-maintain it.
- Within 24h of publishing an important URL, manually Request indexing once.
FAQ
How long until “unknown” goes away on its own? On an established site with the URL in the sitemap and a few internal links, usually a few days. On a brand-new domain with no backlinks, 2-4 weeks is normal. Requesting indexing nudges it but doesn’t make it instant.
I clicked Request indexing and it still says unknown an hour later. Is it broken? No. The request only queues a crawl; it doesn’t index on the spot. Re-check in a day or two. If it still says “unknown” after a week, recheck that the page is in the sitemap, returns 200, and has internal links.
What’s the daily limit on Request indexing? Roughly 10-12 URLs per property per day as of June 2026 (Google doesn’t publish the exact figure). The button greys out when you hit it and resets after about 24 hours. For bulk needs, rely on the sitemap and internal links instead.
Does resubmitting my sitemap help? Only the first submission matters — it registers the sitemap. After that, Google re-fetches it on its own. Resubmitting the same unchanged sitemap does nothing.
The URL is in my sitemap but still unknown. Why? A sitemap is a hint, not a command, and it’s weaker than links. Add real internal links from crawlable pages, confirm the URL returns 200 and isn’t robots-blocked, then Request indexing once. On new sites, also just give it time.
Should I use the Indexing API?
Google’s Indexing API is officially supported only for JobPosting and BroadcastEvent (livestream) pages. Using it for ordinary articles is against its terms and won’t reliably help. Stick to sitemaps, internal links, and the URL Inspection request.
Related
External references: Google’s URL Inspection tool documentation and the Sitemaps report help are the authoritative sources for current status strings and menu locations.
Tags: #SEO #Google #Search Console #Indexing