Fixes

How to fix “Excluded by 'noindex' tag” on Next.js

If Search Console shows “Excluded by 'noindex' tag” on your Next.js site, you are in the right place. The page has noindex, so Google deliberately leaves it out. 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: 15.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?

The page says "noindex" through a robots meta tag or an X-Robots-Tag header. Google obeys and does not add the page, or removes it from the index.

Likely causes on Next.js

  • A site-wide noindex turned on during development or maintenance.
  • The page is marked noindex in an SEO plugin.
  • The server or CDN adds noindex through an HTTP header.
  • A template adds noindex conditionally to certain page types.
  • Next.js note: Look for robots: { index: false } in metadata; a condition tied to an environment variable can output noindex in production by mistake. Also check that no X-Robots-Tag response header is added.

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. Look for robots: { index: false } in metadata; a condition tied to an environment variable can output noindex in production by mistake. Also check that no X-Robots-Tag response header is added.
  3. Check the page source for the robots meta tag and the response headers for X-Robots-Tag.
  4. If noindex is not intended, remove it and verify with a free indexability check.
  5. Make sure the page is not blocked by robots.txt, otherwise Google cannot see the noindex.
  6. Do not leave noindex URLs in the sitemap.
  7. After removing it, request indexing in URL inspection and send the link through an indexing panel.

Extra checks for Next.js

  • speed and crawling: Render pages statically or with ISR where possible, split heavy client bundles and use next/image. Slow server responses reduce crawl rate.
  • robots.txt: Check app/robots.ts or public/robots.txt. If you disallow preview environments, confirm the same rule does not ship to production.

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 long after removing noindex until it is indexed?

Typically days to a few weeks, depending on how often the site is crawled.

Do logged-in pages need noindex?

Yes, noindex is right for account, cart and thank-you pages.

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