Fixes

How to fix “URL is unknown to Google” on Next.js

If Search Console shows “URL is unknown to Google” on your Next.js site, you are in the right place. Google has never discovered the URL. This page covers the causes and a step-by-step fix for Next.js. A React framework. Server-side and static generation hand Googlebot ready-made HTML; metadata is managed with the Metadata API.

Updated: 05.11.2026 · 2 min read · Türkçe

Contents
  1. What does this status mean?
  2. Likely causes on Next.js
  3. Step-by-step fix on Next.js
  4. Extra checks for Next.js
  5. After fixing
  6. More information

What does this status mean?

URL inspection says Google has never seen this address. The page may be new, or no link or sitemap entry leads to it.

Likely causes on Next.js

  • The page is very new and not discovered yet.
  • It is missing from the sitemap and has no internal links (an orphan).
  • The page is reachable only through a JavaScript-created link.
  • A site-wide noindex or robots block stops discovery.
  • Next.js note: Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.

Step-by-step fix on Next.js

  1. In your Next.js admin go to: The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.
  2. Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.
  3. Add the URL to the sitemap and resubmit the sitemap in Search Console.
  4. Link to it from the home page or a hub page with a visible HTML link.
  5. Send the URL with "Request indexing" in URL inspection.
  6. For bulk URLs send through an indexing panel and watch crawl status in Search Console.
  7. If it is discovered but still not indexed, look at content quality.

Extra checks for Next.js

  • canonical and duplicate URLs: Give every page an absolute canonical with metadata.alternates.canonical and set metadataBase. On dynamic routes make sure parametrised URLs do not repeat content.
  • redirects and 404: Define permanent (permanent: true) redirects with redirects() in next.config.js and avoid chains and loops. On missing routes return a real 404 with notFound().

After fixing

In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.

More information

Frequently asked questions

How soon is a new page discovered?

Hours on frequently updated sites; days or weeks on new sites.

Does social sharing speed up discovery?

It can help sometimes but is not guaranteed. Sitemap and internal links are more reliable.

Where are these settings on Next.js?

The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.

Related pages