Home/Notes/How a garage should handle robots.txt
How a garage should handle robots.txt
9 Jan 2025
How a garage deals with robots.txt — and what usually goes wrong.
The problem: three unused font weights. This breaks robots.txt for a garage.
If the hours on Google disagree with the site, people trust Google and then arrive angry. robots.txt will not fix that. The hours page will.
We quoted a garage half what the other firm did because we did not propose features they did not ask for. The scope was robots.txt, not a rebrand.
The vendor promised a garage that robots.txt was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.
The fix was to delete the old entry, wait for TTL to expire, and re-add robots.txt with the correct value. We scheduled it for 3 AM so nobody lost traffic.
The most expensive outage for a garage was not a hack — it was three unused font weights. Nobody attacked anything. The config just drifted.
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