robots.txt blocking all crawlers
What this means
Section titled “What this means”Disallow: / under User-agent: * tells every crawler to avoid every path on your site. No pages will be indexed. If this is your production domain, your site is invisible to search engines.
This configuration is standard on staging environments and is the most common way it ends up on production: a staging robots.txt gets deployed without being changed.
How to fix it
Section titled “How to fix it”Open your robots.txt and remove or replace the blocking rule.
A minimal robots.txt that permits all crawlers:
User-agent: *Allow: /
Sitemap: https://yourdomain.com/sitemap.xmlIf you want to block specific paths only (admin panels, API routes), disallow those explicitly:
User-agent: *Disallow: /admin/Disallow: /api/
Sitemap: https://yourdomain.com/sitemap.xmlFile locations by framework
Section titled “File locations by framework”| Framework | robots.txt location |
|---|---|
| Next.js App Router | app/robots.ts (compiled) or public/robots.txt |
| Next.js Pages Router | public/robots.txt |
| SvelteKit | static/robots.txt |
| Nuxt | public/robots.txt |
| Astro | public/robots.txt |
| Plain HTML | robots.txt at project root |
Verify the fix
Section titled “Verify the fix”Check the live robots.txt content:
curl https://yourdomain.com/robots.txtConfirm there is no Disallow: / under User-agent: *. Re-run orino audit to confirm the check passes.