Next.js robots.txt checker
Paste your robots.txt to see if it blocks Google from the files your Next.js pages need. It runs in your browser, so nothing you paste leaves this page.
Googlebot is blocked from 4 of 5.
- Home pageAllowed
/Line 2: Allow: / - JavaScriptBlocked
/_next/static/chunks/app.jsLine 4: Disallow: /_next/ - CSSBlocked
/_next/static/chunks/app.cssLine 4: Disallow: /_next/ - Fonts and imported mediaBlocked
/_next/static/media/font.woff2Line 4: Disallow: /_next/ - Optimized imagesBlocked
/_next/image?url=%2Fhero.jpg&w=1200&q=75Line 4: Disallow: /_next/
What it checks
It tests your rules against the paths every Next.js site uses: compiled JavaScript and CSS under /_next/static/, fonts and imported media, and optimized images under /_next/image.
It follows Google’s robots.txt rules: the most specific user agent group applies, the longest matching path wins, and on a tie the less restrictive rule wins. The test URLs are typical examples, so a rule aimed at one exact file name may behave differently on your site.
If something is blocked
Remove the line shown in the result. These files are public anyway, so blocking them hides nothing, and Google needs them to render your pages. Here’s why it matters and how to fix it. Then check your tags with the Next.js metadata checker.