Robots.txt accessible and doesn't block Googlebot from content, CSS, or JS
Why it matters
A Disallow rule on /_next/static/ or /assets/ blocks Googlebot from fetching the CSS and JavaScript it needs to render the page — Google then sees unstyled, scriptless markup and may classify your pages as broken or low-quality. Mobile-first indexing amplifies this: rendered content that depends on blocked resources gets scored as if it were missing, dropping rankings on the pages you care about most.
Severity rationale
Medium because blocked render resources degrade ranking signals but core HTML still reaches the crawler.
Remediation
Keep public/robots.txt narrow — disallow only admin, API, and private paths; never block static asset directories. Reference the sitemap explicitly:
User-agent: *
Disallow: /admin
Disallow: /api/internal
Sitemap: https://yoursite.com/sitemap.xml
Verify with Search Console's URL Inspection tool after changes.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Advanced SEO Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from seo-advanced·automated