Menu

1 / 5

Next.js pages not indexed by Google: causes and the fix path

DEV Community: nextjs·Nayan Kyada·13 days ago
#Gyurn1B7
#devtonextjs#devto#dev#pages#sitemap
Reading 0:00
15s threshold

Your developer launched the Next.js and Sanity site, the pages look fine, and Google still shows half of them as "Discovered - currently not indexed" or "Crawled - currently not indexed". If you are searching for why your Next.js pages are not indexed, the cause is almost always one of five fixable things, and none of them require a rebuild.

What the symptoms look like

Open Search Console and go to the page indexing report. The reason attached to each URL is the most useful clue you have. These are the patterns I see most often on Sanity-backed sites:

Pages excluded by a noindex tag, even though nobody meant to add one.

Alternate page with proper canonical tag, where Google thinks your page is a copy of another one.

Discovered or Crawled but not indexed, where Google found the URL and chose not to keep it.

Soft 404, where an empty or error-like page returns a normal status.

Submitted URL not found in the sitemap report, where the sitemap lists URLs that no longer exist.

Traffic that never arrives is…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.