The exposure audit

← Previous Next →
Build Log · 2026-08-19

The exposure audit

Pushing the whole local folder to the repo published pages that had never been public, including an unlisted draft that a sitemap I generated was advertising.

Why we looked. Tracking down neo@matrix.com surfaced a detail worth pulling: the Email Lab page had never been published on HostGator. It was live only because the entire local folder went into the repo at migration time. That implied others were in the same position.

Root cause

Being in the repo is being published. There is no separate step, and no warning. Files that were private for years became public the moment the deployment model changed from "upload what you choose" to "deploy the repo".

What was reachable

  • An unfinished draft with its photographs, on a subject not ready to be published.
  • A document written for one specific recipient rather than for the site.
  • Internal dev notes describing this site's own infrastructure.
  • Mockups whose own text advertised "drafts and legacy pages not listed in the main navigation".
  • Internal component templates.

None of it was linked from anywhere. All of it was one URL away.

The part that was my fault

That unfinished draft already carried noindex, nofollow and was linked from no page. A deliberate precaution, correctly taken.

The sitemap.html I had generated listed it anyway, with a clickable link, along with all six of its photographs. I had ported sitemap.php's scan-everything behavior faithfully without once asking whether some files were unlisted on purpose. A convenience feature quietly undid a deliberate privacy decision.

Fixed at the class level rather than the instance: build-sitemap.py now skips any HTML file carrying a noindex tag, so a page kept out of view cannot be advertised by the index again, including pages nobody has thought about yet.

What would catch it sooner

Three different questions, three different controls. Conflating them is how this happens:

QuestionControl
Is it committed?.gitignore
Is it served?.assetsignore
Is it indexed?noindex, if honoured

noindex is not privacy. It asks well-behaved search engines not to list a page. It does nothing about anyone holding the URL.

A second lesson came from the fix itself. Checking [ -f "$path" ] to verify links still worked was wrong, because an excluded file still exists on disk. That check passed while the homepage's Email Lab card would have 404'd live. Verify what is served, not what is present. The link check now cross-references .assetsignore.