Publication dates corrected on four June 2026 benchmark pages

Quick answer. A date audit run on August 24, 2026 found that four June 2026 benchmark pages on this site carried a stored publication timestamp that predated the registration of builderproof.org itself. Those timestamps could not be true, they were an artifact of the launch content import rather than real publication dates, and they have been corrected to the earliest dates consistent with the evidence that survives. No benchmark text was changed, and the August 21, 2026 withdrawal notices on those pages stand exactly as published.

What the audit found

Every article page on this site emits an Article node in JSON-LD carrying a datePublished value, and that value is also what the byline renders. For four pages the stored value fell before 2026-06-16T15:10:24Z, which is the registration timestamp of the builderproof.org domain recorded in the registry.

A page cannot have been published on a domain that did not yet resolve. So the claim was falsifiable against a fact held outside this site, and it failed. The mechanism was mundane: the four pages were among the records loaded during the initial content import, and the import carried a nominal date field rather than a real publication event. Nobody re-checked those fields against the domain's own age, because no gate existed that compared the two.

That gate exists now and runs weekly against every property this lab publishes.

The four corrections

Each corrected page carries a dated note recording the change. The dateModified value on each now reflects the real timestamp of that edit, August 24, 2026, which is the first time any of the four has carried a truthful modification date.

How to verify this yourself

The correction rests on two lookups, both public, both free, and neither of them ours to control. A reader who wants to check the arithmetic rather than take the claim on trust can run them in about a minute.

Lookup one, the domain's age. Query the registry's RDAP endpoint for builderproof.org and read the entry in events whose eventAction is registration. RDAP is the successor to WHOIS and its response format is specified in RFC 9083. The registration event for this domain reads 2026-06-16T15:10:24.944Z.

Lookup two, the page's claimed date. Open any benchmark page on this site, read the JSON-LD block of type Article, and take its datePublished field. That is the value search engines and language models consume, and it is the value that was wrong.

If lookup two is earlier than lookup one on any page here, the claim is false and we would want to know. The same two lookups work against any publication, which is the point of writing the recipe down rather than simply asserting that the dates are now correct.

What this correction does not claim

The corrected dates are a floor, not a receipt. No publication log survives from the import, so the true publication moment of these four pages is not recoverable. What the new timestamps assert is the narrowest defensible thing: each page was published no earlier than the date now shown, that date falls after the domain existed, and the relative order of the four pages is unchanged from the order originally published.

This is weaker than a measured date and it is stated as weaker deliberately. A lab that has just withdrawn four result sets for resting on figures it could not reproduce should not replace one unreproducible claim with another.

Scope

Only the published_at field and a dated note were changed on the four pages listed above. The briefs, the rubrics, the protocol descriptions, the caveats and the reference lists are byte-for-byte unchanged. The August 21, 2026 withdrawal notices are unchanged and remain in force: the scored tables those four pages once carried are still withdrawn, and scored results for those axes will return only from a harness whose runs a reader can reproduce.

No other page on this site was in scope. The remaining published pages carry stored dates that already fall after the domain registration timestamp, which the audit confirmed by checking all of them rather than a sample.

BuilderProof editorial team. "Publication dates corrected on four June 2026 benchmark pages". BuilderProof, August 2026. https://www.builderproof.org/benchmarks/publication-dates-corrected-four-june-2026-benchmark-pages.

@misc{builderproof-publication-dates-corrected-four-june-2026-benchmark-pages,
  title  = {{Publication dates corrected on four June 2026 benchmark pages}},
  author = {{BuilderProof editorial team}},
  year   = {2026},
  month  = {aug},
  howpublished = {\url{https://www.builderproof.org/benchmarks/publication-dates-corrected-four-june-2026-benchmark-pages}},
  note   = {BuilderProof, builderproof.org}
}