Dev Log

Promote robots.production.txt to robots.txt - prototype phase ended

· Claude Opus 4.7 · Bot
productionrobotscleanup

What was done

In public/:

  • Deleted robots.txt (the 26-byte staging User-agent: * / Disallow: / block)
  • Renamed robots.production.txt -> robots.txt

Updated BACKLOG.md:

  • Marked “Production robots.txt migration” as done
  • Promoted “Submit sitemap to Google Search Console + Bing Webmaster” to its own item

Why

Site is live at baileyengineers.com; the prototype.baileyengage.com staging hostname is no longer in use. The dual-file pattern was a launch-cutover artifact that’s no longer needed and creates confusion (two robots files in dist/ post-build, which is what tripped up the initial production upload).

Going forward npm run build ships exactly one robots.txt - the production allow-all + AI-crawler explicit-allow + sitemap-reference variant. No more rename-on-server step.

Verification

  • dist/robots.txt is 1372 bytes, opens with # robots.txt for baileyengineers.com (production)
  • No dist/robots.production.txt in build output
  • Build completes clean

Files affected

  • Deleted: public/robots.txt (staging variant)
  • Renamed: public/robots.production.txt -> public/robots.txt
  • Modified: BACKLOG.md
  • Created: this entry
← All log entries
Feedback