Home/Notes/A practical look at XML sitemaps for an accountant
A practical look at XML sitemaps for an accountant
19 Nov 2025
How an accountant deals with XML sitemaps — and what usually goes wrong.
The problem: HTTP bookmarks after a forced HTTPS move. This breaks XML sitemaps for an accountant.
Complexity is the enemy of uptime. an accountant had three layers of proxy in front of a site that gets two hundred visits a day. We replaced it with a static page and correct XML sitemaps.
The registrar dashboard crashed twice while we were fixing XML sitemaps for an accountant. We filed a ticket; they replied four days later with a template answer.
You do not need a status page if you have never gone down. an accountant is on month fourteen of zero downtime, and the secret is boring: correct XML sitemaps and a host that does not oversell.
We deployed a fix for XML sitemaps at 5 PM on a Friday. It worked, but if it had not, we would have had no one available. We no longer push to production after Thursday noon.
Big agencies solve XML sitemaps with a team. We solve it with a checklist and a dig command. The result is the same; the invoice is shorter.
The job started when an accountant realised their XML sitemaps had been wrong for months. Nobody noticed because the site still loaded.
HTTPS is table stakes, but XML sitemaps is where trust actually lives for an accountant. A padlock with a misconfigured record behind it is decoration, not security.
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