Home/Notes/A practical look at robots.txt for a plant nursery
A practical look at robots.txt for a plant nursery
7 Sep 2026
How a plant nursery deals with robots.txt — and what usually goes wrong.
The problem: three unused font weights. This breaks robots.txt for a plant nursery.
A friend of the owner at a plant nursery had set up robots.txt years ago. When we audited, the config still pointed at a server they stopped paying for in 2024.
robots.txt for a plant nursery 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.
We check robots.txt for a plant nursery once a quarter. It takes five minutes and has caught two problems in the past year. Both would have caused downtime within a week.
Email deliverability is nobody’s favourite topic, but a plant nursery lost two bookings because robots.txt was misconfigured and replies landed in spam for a week.
We underestimated how long robots.txt migration would take for a plant nursery. The estimate was two hours; the reality was a full day because three unused font weights had never been documented.
The worst robots.txt failure we have seen at a plant nursery was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.
The best robots.txt setup is the one nobody has to think about. For a plant nursery, that means auto-renew, auto-redirect, and a monitoring ping every four hours.
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