Publication Dates Corrected on Three Early ShipGarden Stack Guides

Quick Answer

Three early ShipGarden stack guides carried a publication date that predated the registration of shipgarden.com itself. A date audit on August 23, 2026 found the problem, and we have corrected all three. The old timestamps were an artifact of the initial content import that seeded this site, not a record of when anything was actually published. No article text changed. You can verify the correction yourself with two public lookups, and we show you how below.

What was wrong

shipgarden.com was registered on June 16, 2026. Three guides on this site were stamped with publication dates in May and early June 2026, which is to say they claimed to have been published on a domain that did not exist yet.

That is not a small clerical difference. A publication date is a factual claim, and search engines read it twice: once in the visible byline, and once in the Article structured data we emit on every page. Both were carrying the wrong number.

We want to be plain about the cause, because the cause is boring and it matters. When this site was first stood up, its founding articles were loaded in a single import batch. That batch assigned each piece a date on a tidy weekly cadence running backwards from launch. Nobody sat down in May and wrote these. The dates were spacing, not history.

What changed

Each of those three pages now also carries a short dated note at the foot explaining the same thing in one paragraph, so a reader who lands there from search does not have to find this page to learn what happened.

The stack picks, the reasoning, the pricing figures and the source lists are untouched. The only body change on those three pages is the note. We changed a date, not an opinion.

How to check us, in two lookups

We would rather hand you the method than ask for trust, so here it is. Neither step needs an account or a paid tool.

Lookup one: when did the domain start existing? Domain registries publish this over RDAP, the successor to WHOIS, standardised in RFC 9083. For any .com name you can request https://rdap.verisign.com/com/v1/domain/shipgarden.com and read the events array. The entry whose eventAction is registration carries the date the name was created. For this site it reads June 16, 2026.

Lookup two: what date does a page claim? Open any article here, view source, and find the block of JSON-LD structured data. The datePublished property is the machine-readable publication claim, and it is the one Google reads for Article results. Compare it against the visible byline, then compare both against lookup one.

If step two ever returns a date earlier than step one on any page of this site, something is wrong and we would like to know. That check works on any publication, not just ours, and it costs about thirty seconds.

What we are not claiming

We did not recover these dates from a publication log, because no such log survives. The new dates are the earliest timestamps the surviving record can actually support: after the domain existed, in the original relative order the three guides were written, and consistent with when each record was created in the system.

So treat them as a floor, not a receipt. That is a weaker claim than the one we were previously making, and it is the honest one.

We also want to name the temptation we declined. The tidy fix would have been to quietly rewrite the three numbers and say nothing, and almost nobody would have noticed. But a site that publishes stack recommendations is asking you to believe its facts, and you cannot ask that selectively.

Your move:

Run lookup one and lookup two on the next site that tells you it has been publishing since well before you had heard of it. Thirty seconds, no account, and the answer is public either way.