Home/Notes/How a restaurant should handle XML sitemaps
How a restaurant should handle XML sitemaps
28 Feb 2024
How a restaurant deals with XML sitemaps — and what usually goes wrong.
The problem: a chat widget that blocks the submit button. This breaks XML sitemaps for a restaurant.
We quoted a restaurant half what the other firm did because we did not propose features they did not ask for. The scope was XML sitemaps, not a rebrand.
a restaurant asked us to look at XML sitemaps after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.
You do not need a status page if you have never gone down. a restaurant is on month fourteen of zero downtime, and the secret is boring: correct XML sitemaps and a host that does not oversell.
We billed a restaurant two hours for XML sitemaps. The previous agency billed forty hours and left a chat widget that blocks the submit button behind. Complexity is not expertise.
We have seen agencies charge a restaurant for a yearly XML sitemaps audit that consists of a screenshot and a paragraph. Ours is a working config file they can apply themselves.
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