Home/Notes/Managing robots.txt at a restaurant
Managing robots.txt at a restaurant
8 Jul 2025
How a restaurant 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 restaurant.
We billed a restaurant two hours for robots.txt. The previous agency billed forty hours and left a plugin login nobody has used since March behind. Complexity is not expertise.
We checked the WHOIS for a restaurant and found the domain was registered under a former employee. Transferring it took more time than fixing robots.txt.
We do not start with a platform when handling robots.txt. We write down who types what, who gets the mail, and what must not get lost. That list is always shorter than a vendor pitch deck.
We hand over a one-page document after every robots.txt job. It says what was changed, what the login is, and what to check if something feels wrong. a restaurant keeps it in a drawer they actually open.
Every CMS update brings a small chance that robots.txt breaks. For a restaurant, we pin versions and test upgrades in a staging copy before touching production.
The registrar dashboard crashed twice while we were fixing robots.txt for a restaurant. We filed a ticket; they replied four days later with a template answer.
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