How to fix “Blocked by robots.txt” on Next.js
If Search Console shows “Blocked by robots.txt” on your Next.js site, you are in the right place. robots.txt stops Googlebot from fetching 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.
Contents
What does this status mean?
A Disallow rule in your robots.txt forbids crawling this URL. Google cannot read the content; if other sites link to it, it can still appear in the index without content.
Likely causes on Next.js
- A "Disallow: /" rule added during development was forgotten live.
- A broad pattern (for example /*?) also catches pages you want.
- The CMS or a plugin rewrote robots.txt on its own.
- Sitemap URLs sit in folders closed by robots.txt.
- Next.js note: Check app/robots.ts or public/robots.txt. If you disallow preview environments, confirm the same rule does not ship to production.
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.
- Check app/robots.ts or public/robots.txt. If you disallow preview environments, confirm the same rule does not ship to production.
- Use the Search Console robots.txt report or a robots tester to find which rule closes the URL.
- Narrow or delete the rule; close only folders that really should not be crawled.
- Verify that sitemap URLs do not conflict with robots.txt.
- After fixing, give Google a day to refresh its robots.txt cache or request a recrawl in the report.
- Send the URL for indexing and follow progress with URL inspection.
Extra checks for Next.js
- 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().
- sitemap: Generate a dynamic sitemap with app/sitemap.ts; split large sites with generateSitemaps. List only canonical URLs that return 200.
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 robots.txt remove a page from the index?
No. It blocks crawling, it does not remove from the index. To remove, allow crawling and use noindex.
How do I test robots.txt?
Enter the file and a URL in our free robots.txt tester to see the Googlebot allow status.
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.