Home/Notes/How an accountant should handle robots.txt
How an accountant should handle robots.txt
31 Mar 2026
How an accountant deals with robots.txt — and what usually goes wrong.
The problem: an inbox shared between the office and the webmaster. This breaks robots.txt for an accountant.
When we onboard an accountant, the first thing we check is robots.txt. It tells us more about the previous provider than any sales call.
The vendor portal had silently rotated the key for robots.txt, but an accountant was still using the old one. Every outbound message bounced quietly.
Complexity is the enemy of uptime. an accountant had three layers of proxy in front of a site that gets two hundred visits a day. We replaced it with a static page and correct robots.txt.
Most of the damage we see in robots.txt comes from doing too much. A single correct record beats three that were supposed to be clever.
We moved robots.txt for an accountant to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
We solved robots.txt for an accountant by moving it behind a reverse proxy. The old configuration stayed live as a fallback for forty-eight hours, then we pulled it.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com