Setting up robots.txt for a photo studio

robots.txt for a photo studio is nothing like robots.txt for a multinational. The scale is tiny but the stakes are the same: one wrong record and nobody can reach you.

Search consoles like honest sitemaps. Every loc should be a document. Reserving ten thousand empty shells and hoping Google does not notice is not a strategy for robots.txt.

a photo studio asked us to look at robots.txt after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.

DNS propagation is not instant, but it is not magic either. We explained to a photo studio that the TTL on the old robots.txt record was 86 400 seconds — twenty-four hours.

We run a monthly diff on DNS for a photo studio. If a record changes and nobody in the team made the change, we get an alert. a plugin login nobody has used since March was caught this way last quarter.

More notes

Related notes

• Setting up robots.txt for a small hotel
• Managing robots.txt at a florist
• Setting up robots.txt for a print shop
• A practical look at robots.txt for a plant nursery