When Our Domain Page Said More Than the Contract

by Dennis Yu / September 2026

This is the companion meta-article for the domain-education cluster published on
theathletespotlight.com — the pages that explain domains and
hosting to young athletes and the parents who sign up for them. It documents how the pages got
built, how a line in our own marketing copy ended up contradicting our own signed Terms of Service,
and how that got fixed the same afternoon it was found. Published per the
BlitzMetrics meta-article SOP.

Version 1.0 — September 7, 2026 — BlitzMetrics × Athlete Spotlight

1. The Task Summary

Assignment: Fix a set of orphaned, inconsistent domain pages on theathletespotlight.com and give
young athletes and their parents a plain explanation of what a domain is, what hosting is, who
actually owns the domain during a membership, and what happens if the family leaves.

About: Athlete Spotlight is a managed personal-brand website service for young athletes —
$30/month, a real domain and a real site, built and maintained by BlitzMetrics so the athlete (or
their guardian, for athletes 13–17) has one canonical place online that Google and AI tools can
point to. The domain and transfer terms sit inside the site’s Terms of Service, which covers
minors, refunds, cancellation, and — in Section 8 — domain registration and transfer.

Source material:
– domain-consistency-plan.md, a 92,384-byte, 1,302-line plan drafted 2026-08-11, containing
canonical long-form, short-form, and micro-form paragraphs meant to be the single source of truth
for every page that mentions a domain
– The live Terms of Service page at theathletespotlight.com/terms/ (published 2026-08-15, last
modified 2026-09-04 — three weeks after the plan was drafted)
– The existing BlitzMetrics article at /domain-transfer-to-godaddy/ (post 105679), unmodified
since 2026-04-21, GoDaddy-only, with its core step locked inside screenshots and no text
equivalent, and linked from nothing
– Two drafted articles from the 08-11 plan that had not yet been published

Goal: Publish /domain-vs-hosting/ and /domain-transfer/ on theathletespotlight.com, make sure
both agree with whatever the live Terms of Service actually says (not what the August plan assumed
it would say), and de-orphan the BlitzMetrics article by linking the whole cluster together.

2. Step-by-Step Process

1. Pulled the 08-11 plan and extracted the canonical paragraphs. The plan’s three
   template forms (long, short, micro) were written to be copy-pasted, not reinvented, so the draft
   pages started from that language rather than from scratch.
2. Drafted and published /domain-vs-hosting/ (page 807) and /domain-transfer/ (page 808)
   . Both went live using the plan’s language, including its claim that the athlete
   “owns it from day one” and can move the domain “for any reason at all,” with no stated timing
   rules.
3. Checked the two live pages against the live Terms of Service. This step happens
   after publish, not before — the 08-11 plan predates the Terms page by three weeks, and nothing in
   the workflow forced a re-check against a document that didn’t exist when the plan was written.
4. Found the contradiction. Terms §8 states plainly: “Until transfer, the domain remains in Your
   Content Factory LLC’s registrar account,” and transfer is only available “after at least one
   paid, non-refunded month,” requestable “during the paid period or within 90 days after.” The
   published pages said neither of those things — they said the athlete owned the domain outright
   from day one and could transfer it whenever, for any reason, with no waiting period.
5. Rewrote both pages to match the contract. WordPress records /domain-vs-hosting/
   as published at 21:32:52 UTC and last modified at 21:36:17 UTC the same day — under four minutes
   between the page going live with the wrong claim and the correction landing.
6. Discovered the site’s static-export behavior while verifying the fix was actually live
   . A raw header check on the homepage returned x-lss-served: static plus an etag
   and a last-modified date — evidence the page is served from a pre-built static file. The same
   check on the two new pages returned neither header. The mechanism: WordPress is the authoring
   tool; a static export is served if one exists for that URL, and the request falls through to
   live PHP/WordPress only when it doesn’t. A brand-new page has no static file yet, so it renders
   immediately. An edit to an existing page is invisible until the next export runs.
7. Identified three link insertions needed on existing pages to complete the cluster and staged
   them in WordPress. Because those are edits to pages that already have a static file,
   none of the three will be visible on the live site until the next static export runs.
8. Rewrote blitzmetrics.com/domain-transfer-to-godaddy/ (post 105679). Made it
   registrar-agnostic instead of GoDaddy-only, added an explicit fee policy (BlitzMetrics never
   bills for registration or renewal fees it already paid; the receiving registrar’s own inbound fee
   is the customer’s to pay), added the premium/auction/aftermarket exclusion, and added the 60-day
   registry-lock reality that applies regardless of which registrar is involved.
9. Cross-linked the cluster and verified the links resolve. /domain-vs-hosting/ now
   links to blitzmetrics.com/domain-transfer-to-godaddy/ and to BlitzMetrics’ GoDaddy and
   Namecheap DNS guides; the BlitzMetrics post now links back to both new theathletespotlight.com
   pages. Confirmed live in both directions.
10. Wrote this meta-article.

3. Critical Decision-Making

Decision 1 — Treated the live Terms page as the authority, not the 08-11 plan, even though the
plan was explicitly marked “settled — do not re-open.” The plan was correct when it was written;
it predates the Terms of Service page by three weeks. A less careful pass would have shipped the
plan’s language as-is because it read as “approved” and moved on. The rule that actually applies:
when a marketing draft and a signed contract disagree, the contract wins, and a plan written against
an old snapshot of the site needs to be re-verified against whatever exists now, not trusted because
it was once signed off.

Decision 2 — Recognized which direction the error ran, and treated that as more urgent than a
typo would be. The published pages promised the customer more than the Terms actually grant
(“day one” ownership, no waiting period, no stated reason required). That is the dangerous direction
for a company to be wrong in: it creates a real gap between what a parent reads on the marketing
page and what they’re actually bound by when they sign up. A page that under-promises is merely
unclear; a page that over-promises against its own contract is a liability and a trust problem the
moment a parent tries to act on it.

Decision 3 — Diagnosed the static-export behavior from response headers instead of assuming a
caching bug or a failed save. The tell was the x-lss-served: static header present on the
homepage and absent on the two brand-new pages. That distinction — new pages fall through to live
PHP and appear instantly; edits to existing pages wait for the next static export — is the difference
between “this edit didn’t save” and “this edit saved correctly and just isn’t visible yet.” Getting
that wrong would have meant re-publishing the same three link insertions repeatedly, assuming each
attempt had failed.

Decision 4 — Made the BlitzMetrics rewrite registrar-agnostic instead of patching the existing
GoDaddy-only piece in place. The new cluster links to both a GoDaddy guide and a Namecheap guide,
so a customer who registered somewhere else would hit a page written as if they hadn’t. Rewriting the
governing article to work regardless of registrar was the difference between “fixed for the
customers we thought about” and “fixed for the customers we’ll actually get.”

Decision 5 — Reported the sequence honestly: the contradiction was caught after publish, not
before, and three of the cross-links are staged, not live. It would read better to say every fix
landed before anything went public. That isn’t what happened, and the static-export mechanism means
some of today’s work is genuinely not visible on the site yet. Both facts are stated plainly in this
article rather than smoothed over.

4. Effort and Cost Comparison

Every timestamp below is a WordPress modified_gmt value you can pull yourself from the REST API.
I am not going to invent per-step stopwatch numbers or a token bill I did not measure.

Publish to contract-correction: 3 minutes 25 seconds. Whole cluster, first publish to last
write: about 8 minutes.

What I will not claim: a dollar figure. I have no session billing data, and a made-up decimal in a
cost table is the same species of error as the one this article is about — a number stated with more
confidence than its evidence supports. The honest comparison is directional. A person doing this
by hand would spend the bulk of the time on the two things that were nearly free here: converting a
1,300-line plan into publishable HTML, and re-reading a live Terms page line by line against
marketing copy.

The speed is not the interesting part. The interesting part is that a human following that same
August plan would very likely have published the same over-promising language and never caught the
contradiction — because nothing prompts a person to re-read a settled plan against a contract page
that did not exist when the plan was written. The check that caught it was a plain text comparison
against the live Terms, run as a matter of course rather than skipped because the plan said
“settled.”

5. What the Agent Can and Cannot Do

Handled autonomously:
– Reading and extracting canonical language from a 1,302-line plan document
– Drafting and publishing both new pages from that language
– Fetching the live Terms of Service and comparing it, sentence by sentence, against the published
pages
– Identifying the specific two-point contradiction (registrar custody, timing rules) and rewriting
both pages to match the contract exactly
– Diagnosing the static-export serving behavior from raw HTTP response headers rather than guessing
– Rewriting the BlitzMetrics article for registrar-agnostic accuracy, fee policy, and the
premium/auction exclusion
– Verifying every cross-link resolves in both directions

Required Dennis (the human):
– The original policy decisions baked into the 08-11 plan (standard-priced domains only, no premium
purchases, absorb standard transfer costs) — those are business decisions, not something to infer
– The decision that the Terms of Service, once live, governs over an older marketing plan
– Final sign-off that the corrected language is what the business actually intends to promise

Couldn’t do:
– Force the static export to run immediately. The three staged link insertions sit in WordPress and
will not appear on the live site until the next export cycle runs — that’s an infrastructure
schedule, not something this session controls.
– Confirm that the Terms of Service language itself is legally sufficient. Matching marketing copy
to the contract is not the same as reviewing whether the contract is airtight; that’s a job for
counsel, not for this pass.
– Confirm that a parent or guardian reading either page actually understands it. Text accuracy was
verified against the Terms; comprehension on the other end wasn’t and can’t be, from here.

6. Information Ingestion Inventory

• Source documents read: domain-consistency-plan.md (92,384 bytes / 1,302 lines); the live
  Terms of Service page; both new theathletespotlight.com pages as published; the BlitzMetrics
  domain-transfer article before and after rewrite
• Live pages fetched for verification: theathletespotlight.com/terms/,
  theathletespotlight.com/domain-vs-hosting/ (WordPress page 807),
  theathletespotlight.com/domain-transfer/ (WordPress page 808),
  blitzmetrics.com/domain-transfer-to-godaddy/ (post 105679),
  blitzmetrics.com/changing-domain-dns-nameservers-in-godaddy/,
  blitzmetrics.com/a-simple-guide-changing-domain-dns-nameservers-in-namecheap/
• Response headers compared: x-lss-served, etag, last-modified across an existing
  (static-served) page and the two brand-new pages, to confirm the static-export lag
• Structured data checked: datePublished / dateModified timestamps in each page’s JSON-LD to
  confirm the ~3.5-minute gap between the original publish and the correction
• Links verified live, both directions: 4 (BlitzMetrics → 2 new pages; new pages → BlitzMetrics
  domain-transfer post and 2 DNS guides)
• Files created/edited today: 2 new WordPress pages, 1 rewritten WordPress post, 3 staged link
  edits, this meta-article

7. Guidelines Compliance Scorecard

8. What’s Next

Two things are still open. First, the three link insertions staged in WordPress will not be visible
on theathletespotlight.com until the next static export runs — this article should not be read as
confirmation that the full cluster is live end to end; that needs a follow-up check after the next
export. Second, the corrected language on both pages should get one more read against Terms §8 by a
human before this article itself goes out, since a first-pass agent verification is not a substitute
for the sign-off in Section 5.

The broader point worth keeping: exact-match domains matter far less than they used to, because
people don’t type addresses anymore — they search a name and read an AI-generated summary of the
answer. The win is being clearly identified as the person behind that name, with one site and
consistent facts, not owning a keyword. That argument is now stated once, correctly, and linked from
every page that touches it.

This meta-article was produced by a Claude Code agent as a first-pass draft. STATUS: needs a voice
pass and a final fact check against Terms §8 before publishing. Total estimated agent cost for the
build plus this article: cost not measured; see Section 4.

Originally published September 7, 2026.