Prompt
Do I need to review robots.txt during a migration?
Latest observation
Oct 21, 2026
OpenAI APIWeb search: off
Yes — you should review robots.txt during a migration.
It can unintentionally block search engines from crawling important pages on the new site or during cutover. Common migration issues include:
- Accidentally disallowing the whole site on the staging or production environment
- Leaving staging rules in place after launch
- Blocking key paths like:
//product//blog/- CSS/JS files needed for rendering
- Preventing crawlers from seeing new URLs or following redirects
What to check:
- Whether the
robots.txtfile is present on the new domain/environment - That it does not block important sections
- That it allows access to assets needed for rendering
- That any temporary
Disallow: /rules are removed before launch - That sitemap locations are updated if needed
A good migration checklist usually includes:
robots.txt- Redirects
- Canonicals
- XML sitemaps
- Internal links
- Indexing directives (
noindex, headers, meta tags)
If you want, I can give you a migration-specific robots.txt checklist or a sample safe robots.txt for launch.