Trenton Sandler Committed to Arkansas on June 29. His Website Still Said LSU.

Trenton Sandler’s mile PR is 4:01.91. He holds a Guinness World Record. And as of this week, his own “Short Bio (For Media Use)” still called him a Junior running for a school he’d already left three months ago.

Trenton Sandler is a distance runner and creator — a client we’ve built a whole personal-brand system around (see the young-athlete personal-brand system). He entered the NCAA transfer portal on May 28, 2026, after three years at LSU. On June 29, he committed to the University of Arkansas — reigning 2026 NCAA outdoor national champions. Real event, real date, real Instagram post. Dennis’s instruction was simple: “update his site to reflect that… show that he did run for LSU where it makes sense.” That last part is the whole lesson in this doc: a status-change update is not a find-and-replace job. Delete the wrong things and you’ll erase real history that still belongs on the page.

Catch what the automation missed

Trenton’s site runs a weekly MAA task that already does safe auto-updates. It had caught the main “About Trenton Sandler” bio paragraph on the Media page and rewritten it correctly. What it missed: three paragraphs down, a second, near-identical bio block labeled “Short Bio (For Media Use)” — same facts, different wording, still saying “Junior… LSU” with no Arkansas mention at all. Same page, same topic, invisible to a pass that was only checking the paragraph it already knew about.

The takeaway for any future fleet pass: when a fact changes, grep the whole page for every mention of the old fact — not just the block your last automated pass already touched. A page can carry the same claim twice in two different voices (a public bio and a “for media use” bio), and only checking one leaves stale content live in plain sight.

Keep the history, don’t erase it

Two places on the site needed the LSU record to survive the update, not disappear:

The schema. The About page carries an inline Person JSON-LD block with an alumniOf field. It pointed only at LSU. Deleting LSU and swapping in Arkansas would have been the lazy fix — instead, alumniOf became an array of two CollegeOrUniversity entries: Arkansas first (current), LSU second (historical). Search engines and AI systems reading that schema now see the accurate, complete affiliation record, not a rewritten one.

The old blog post. Trenton’s May 29 transfer-portal post said, truthfully at the time, “I’m staying school-agnostic about the future.” That sentence is now wrong — but it wasn’t a lie when he wrote it, and rewriting history to make an old post look prescient is exactly the kind of thing that makes a personal brand feel fake. Instead of touching the original text, we added a dated editor’s note directly above it:

Same pattern journalists use for corrections: leave the original record intact, timestamp what changed and when. It also directly satisfies Dennis’s brief — “show that he did run for LSU, where it makes sense.”

Ship the new chapter as its own post

An editor’s note tells people the news happened. It doesn’t tell the story. So the update also shipped a full new post — “I’m a Razorback: Why I Committed to Arkansas” — written first-person in Trenton’s voice, covering why Arkansas, what LSU will always be, and what’s next. It carries a live Instagram oEmbed of his actual commitment announcement, full RankMath SEO (focus keyword, custom title/description), category and tags matching the rest of the site, and the site’s standard “Connect With Me” CTA block.

The featured image on the new post — an existing, already-live media-library asset, not a new upload.

Never touch a byte you don’t have to

Dennis said Trenton “has pictures and videos” of the commitment. The instinct is to pull those files and upload them. We didn’t move a single new image or video through this process. Two moves did the job with zero binary transfer:

Both are hard rules for this project: never move base64 image data through model context. Reusing what’s already hosted, and letting the source platform’s own embed do the work, gets the same visual result with zero risk of a corrupted upload or a wasted round-trip.

Every page, what was stale, what changed

The reusable pattern

This isn’t a one-off for Trenton. Any personal-brand site eventually needs this exact playbook — an athlete transfers schools, an employee changes companies, a founder rebrands a company. The pattern holds regardless of the specific facts: