Home/Notes/www redirects for a restaurant

www redirects for a restaurant

23 Aug 2025

How a restaurant deals with www redirects — and what usually goes wrong.

Browser visits restaurant.com Registrar domain owner Nameserver DNS records Host serves site www redirects a robots.txt that…

The problem: a robots.txt that disallows the blog. This is where www redirects breaks for a restaurant.

Managed hosting handles www redirects automatically — until it does not. a restaurant learned this when their provider migrated servers and a robots.txt that disallows the blog disappeared silently.

When we reviewed www redirects, the DNS panel showed a robots.txt that disallows the blog. Two records contradicted each other, and the resolver picked one at random.

Early on we tried to automate www redirects for a restaurant with a cron job. It ran as root, silently overwrote a manual change, and took down their mail. Lesson learned.

A free certificate and a correct www redirects record will do more for a restaurant than a redesign that ships with a robots.txt that disallows the blog still in place.

Nobody at a restaurant could remember who had configured www redirects. The credentials were in a text file inside a folder called OLD STUFF on a shared drive.

We check www redirects for a restaurant once a quarter. It takes five minutes and has caught two problems in the past year. Both would have caused downtime within a week.

More notes

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