Home/Notes/How a plant nursery should handle canonical URLs
How a plant nursery should handle canonical URLs
1 Sep 2026
How a plant nursery deals with canonical URLs — and what usually goes wrong.
The problem: a www record that disagrees with the apex. This breaks canonical URLs for a plant nursery.
Automate canonical URLs if you can. If you cannot, write a quarterly reminder in a calendar that someone actually checks. a www record that disagrees with the apex is what happens when nobody does either.
DNS propagation is not instant, but it is not magic either. We explained to a plant nursery that the TTL on the old canonical URLs record was 86 400 seconds — twenty-four hours.
We once forgot to renew canonical URLs for a weekend project and it took down a page that a plant nursery linked to from a print flyer. We now set auto-renew on everything.
We billed a plant nursery two hours for canonical URLs. The previous agency billed forty hours and left a www record that disagrees with the apex behind. Complexity is not expertise.
Email deliverability is nobody’s favourite topic, but a plant nursery lost two bookings because canonical URLs was misconfigured and replies landed in spam for a week.
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