---
title: "Three New Doors Opened the Day a Wrong Byline Slipped Out"
canonical: https://dxdev.com/everyday-ai/easier-to-find-easier-to-spread/
datePublished: 2026-06-13
---
A page on this blog briefly went live with a real name on a byline that was supposed to stay pseudonymous. It was caught and corrected. We don't know how long it was live, only that it was live at all, and I'd rather write that down plainly than soften it.

It happened in the middle of a long stretch of work with a different goal: making this blog [something an AI system could read](/blog/ai-crawler-rules-coordination/) properly instead of just fetching and skimming. That meant a feed carrying the whole article instead of a teaser, a machine-readable map of the site, and plain-text copies of every post sitting next to the styled version. It also meant structured labels tying posts and author together, so a system could parse them without guessing. All of it is useful infrastructure, and it pays off exactly when you want more of your work to reach more places.

## Why this mistake was different from a typo

The same hours that built the full-text feed, the site map and the plain-text copies also made the site more thoroughly copyable. That was on purpose, because it was the whole point of the work.

"We caught it and fixed it" is a true statement about the page. It is a different statement from "nothing already has a copy of the earlier version," and after this work there is no honest way to check the second one. A feed reader, an index or a mirror could have grabbed the wrong version before the correction landed. Nobody can reach into someone else's cache and take it back.

Nobody names this trade when they talk about making content easier to find. Investing in a site's reach also invests in how far and how fast a mistake on that site can travel before anyone notices. With a full feed, a machine-readable index, raw copies and automated readers let in, a fast correction contains less, because some of those channels may already have fetched the bad version.

## What we changed

The fix for the mistake itself was simple. The byline is a handle, not a person, and it went back to being one.

What changed that day was the number of places the same wrong byline could live. Before, it could be read in one place, the visible page. The same stretch of work added a full-text feed, a machine-readable site map and raw text copies. That makes three more places where the exact wrong byline could be read, copied or cached on its own, separate from the page it came from. Every pass over this site now includes checking that the byline stayed a handle, because there are three more doors it could walk out through.

## If you're making your own work easier to find

Count the new doors along with the front one. Before this work, a wrong byline had one way out, the page a reader loaded in a browser. After it, the identical mistake had at least three more, a feed, a site map and a raw copy, each readable independently. A correction that only fixes the page doesn't close the other three. We still can't check whether any of them carried the wrong version out before we caught it.

Before you add a feed, an export or a mirror to your own work, list every new place the same content will be readable. Then decide how you would correct a mistake in each one. A fix to the page doesn't reach copies that were already fetched elsewhere, so check sensitive details like a byline before you publish.