Three kinds of people who own too many domains

Domain investors

A portfolio of fifty or five hundred names has a strange problem: most of the domains don't have a website, so nobody looks at them. You find out a forwarding rule broke when a buyer emails to say the landing page is gone, or worse, when the renewal you thought was automatic didn't happen.

What to look at:

• Sort the CSV by days_left. Anything under 30 days is worth a second look at the registrar, especially names on accounts where auto-renew depends on a card that may have expired. RDAP gives you the registry's date, which is the one that counts.
• A for-sale name usually redirects to a marketplace page or shows a lander. Check that all four versions get there. A broken http://www version is common after moving DNS between registrars, because the old forwarding service only covered the bare domain.
• The details panel lists status codes like client transfer prohibited or redemption period. Seeing redemption period on a name you meant to keep means it already expired and you're in the expensive part of recovery.

A simple routine: keep your names in a text file, paste ten at a time, export each batch, and stack the CSVs. The browser remembers each name, so next month's run tells you which ones changed status or expiry.

SEO agencies

The first technical audit for a new client usually turns up the same few problems, and you can find most of them before anyone opens a crawler. Put the client's main domain, their country sites and any old brand domains they still own into the checker.

What tends to show up:

• www and the bare domain both serve pages, or an old brand domain answers with a full copy of the site instead of redirecting. The Canonical column goes red.
• Staging leftovers: a noindex on the home page, or Disallow: / in robots.txt, copied from staging during the last launch. These are urgent and easy to fix, which makes them good items to raise in a first call.
• Marketing wants the brand cited in AI answers; the CDN quietly blocks AI bots. The AI crawlers column shows both the robots.txt rules and whether the edge returns 403 to GPTBot. Most clients have never seen those two side by side.
• A 1.5 second TTFB on the home page isn't a full speed audit, but it tells you where the performance conversation should start.

Export the CSV and attach it to the audit. Because each row has a robots.txt hash and a timestamp, you can show later exactly when the client's file changed.

Site networks

If you run dozens of small sites from one template, one theme update or server change can break every site in the same way on the same afternoon. The value of a ten-domain spot check is that patterns jump out: if eight of ten rows go amber in the same column, it's the shared layer, not the sites.

Things to check after any change to the shared stack:

• Redirect rules: a new reverse proxy or CDN rule that adds a hop, or a trailing-slash rule that loops on some hosts.
• Networks often generate robots.txt from a template. A missing variable can produce an empty file, or one that disallows everything. Compare the hashes: if every site suddenly has the same hash, they're all serving the same file.
• Check that each sitemap URL still returns XML and not the home page.
• Domains bought in one batch expire in one batch. The Expiry column makes that visible.

Pick ten representative domains, one per server or template version, and run them after every deploy. It takes a minute and catches the change before search engines do.

Coming with monitoring

All three workflows get easier when the checks run on their own. Scheduled monitoring will check your full list daily and email you when something changes. If you'd like to try it early, write to contact@robotto.org and say roughly how many domains you have.