How to fix “Page with redirect” on Next.js
If Search Console shows “Page with redirect” on your Next.js site, you are in the right place. The URL redirects elsewhere, so it is not indexed. 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.
Contents
What does this status mean?
The URL returns a redirect; Google indexes the target, not the redirecting URL. Usually healthy, but if the sitemap and internal links still point at the old URL, crawl budget is wasted.
Likely causes on Next.js
- The http address redirects to https or the non-www to www.
- Old post and product URLs were redirected to new ones.
- The sitemap or menu still lists the old URLs.
- The redirect chain has several hops.
- Next.js note: 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().
Step-by-step fix on Next.js
- 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.
- 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().
- Confirm the redirect is intended; if so this line is not a problem.
- Update the sitemap and internal links to the final target.
- Collapse chains: the old URL should 301 straight to the final one.
- If you use a temporary redirect (302) for a permanent move, change it to 301.
- Check with URL inspection that the target is indexed; if not, send it.
Extra checks for Next.js
- robots.txt: Check app/robots.ts or public/robots.txt. If you disallow preview environments, confirm the same rule does not ship to production.
- 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.
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
Does a redirecting page get indexed?
No, the target does. That is why links should point at the target.
What is the difference between 301 and 302?
301 signals a permanent move, 302 a temporary one. Use 301 for permanent moves.
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.