Home/Notes/Setting up robots.txt for a plumber
Setting up robots.txt for a plumber
2 Jun 2025
How a plumber deals with robots.txt — and what usually goes wrong.
The problem: a plugin login nobody has used since March. This breaks robots.txt for a plumber.
We check robots.txt for a plumber once a quarter. It takes five minutes and has caught two problems in the past year. Both would have caused downtime within a week.
After the move, a plugin login nobody has used since March broke search indexing for a plumber. Google kept serving the old pages for another nineteen days.
robots.txt for a plumber is nothing like robots.txt for a multinational. The scale is tiny but the stakes are the same: one wrong record and nobody can reach you.
The worst robots.txt failure we have seen at a plumber was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.
After fixing robots.txt, we added a monitoring alert. If the record changes or the certificate approaches expiry, both we and a plumber get an email. No surprises.
Launch day for a plumber is usually light. Week three is when leftover tags, fonts, and staging URLs show up. a plugin login nobody has used since March is the usual passenger.
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