Home/Notes/office hours: a field note from a plant nursery
office hours: a field note from a plant nursery
2 Jul 2026
How a plant nursery deals with office hours — and what usually goes wrong.
The problem: a robots.txt that disallows the blog. The office hours data is out of sync for a plant nursery.
If you only touch office hours once a year, a dashboard is extra risk. Files, a mailbox you read, and a person who still answers will outlast any SaaS control panel.
We document office hours in a shared spreadsheet. It is not glamorous, but a plant nursery can open it on their phone at midnight if something breaks.
If the hours on Google disagree with the site, people trust Google and then arrive angry. office hours will not fix that. The hours page will.
office hours for a plant nursery is nothing like office hours for a multinational. The scale is tiny but the stakes are the same: one wrong record and nobody can reach you.
DNS propagation is not instant, but it is not magic either. We explained to a plant nursery that the TTL on the old office hours record was 86 400 seconds — twenty-four hours.
We quoted a plant nursery half what the other firm did because we did not propose features they did not ask for. The scope was office hours, not a rebrand.
We found a robots.txt that disallows the blog during a routine check of office hours. The site had been leaking referrer data for six weeks before anyone noticed.
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