Managing robots.txt at a florist

We told a florist that an inbox shared between the office and the webmaster was a ticking clock. They agreed to fix it the same week — which is rare. Most clients wait until it actually detonates.

We billed a florist two hours for robots.txt. The previous agency billed forty hours and left an inbox shared between the office and the webmaster behind. Complexity is not expertise.

The owner at a florist asked why robots.txt matters. We showed them the error page their customers see when it breaks. That ended the conversation.

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 solved robots.txt for a florist by moving it behind a reverse proxy. The old configuration stayed live as a fallback for forty-eight hours, then we pulled it.

More notes

Related notes

• Managing robots.txt at a restaurant
• How an accountant should handle robots.txt
• Why robots.txt matters for a roofing crew
• A practical look at robots.txt for a plant nursery