Home/Notes/How a bakery should handle CAA records
How a bakery should handle CAA records
29 Aug 2024
How a bakery deals with CAA records — and what usually goes wrong.
The problem: a robots.txt that disallows the blog. This is where CAA records breaks for a bakery.
Before you touch CAA records, take a screenshot of the current state. Half of our emergency calls come from people who cannot remember what was there before the change.
Every CMS update brings a small chance that CAA records breaks. For a bakery, we pin versions and test upgrades in a staging copy before touching production.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a bakery did not need four analytics dashboards to know that Tuesdays are slow.
Test CAA records from outside your network before you call it done. Your office Wi-Fi might cache the old answer for another six hours.
A phishing page copying a bakery appeared last year. The only reason their customers could tell it apart was that CAA records was set up correctly on the real site.
The real issue was not CAA records itself — it was a robots.txt that disallows the blog. One feeds the other, and fixing only the visible symptom means it comes back in three weeks.
We hand over a one-page document after every CAA records job. It says what was changed, what the login is, and what to check if something feels wrong. a bakery keeps it in a drawer they actually open.
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