Tag: athlete personal brand website

An athlete personal brand website is the one page on the internet that Google and every AI engine treat as the most authoritative source about who that athlete is. It is not a link-in-bio and not a social page. It is a real site on the athlete’s own domain, built from the content they already have, structured so a recruiter, a sponsor, and a search engine all understand the same thing: this person is real, this is what they have done, and here is the proof.

This article is the standard we build every Athlete Spotlight site to. It covers the exact page set, the nine-section homepage, the entity schema that makes an athlete machine-readable, and the quality gate that has to pass before a site goes live. Our nine-section homepage extends the published eight-section athlete standard from the personal brand website agent; the extra section is real placements, never filler. The lighthouse we build against is camhazzard.com, which ranks number one for “Cam Hazzard.”

What an athlete personal brand website is

The site is the entity home. Google reads links, structured data, and consistent facts to decide who an entity is and how confident it should be. When an athlete’s name, photo, sport, results, and profiles all agree across the site and its schema, that confidence goes up, and the site starts winning the athlete’s own name in search. That is the whole point: own your name on Google so that when a recruiter or sponsor looks you up, they find you and you look legitimate.

Two rules sit above everything else. First, the homepage is provable facts linked to their sources; the About page is the stories behind those facts. Second, a missing section is better than a fake one. If an athlete has no press yet, we omit the placements section entirely rather than invent one. Every claim on the page traces back to a real intake field.

The page set we ship

Every athlete site ships the same nine pages (one of them conditional), plus one seeded launch post so the blog is never empty:

• Home (/), the nine-section homepage below.
• About (/about/), the story page in the athlete’s first-person voice, carrying the full Person schema; Rank Math schema type ProfilePage.
• Highlights (/highlights/), the sport proof page: featured film, all clips, contest results that deep-link to video proof.
• What People Are Saying (/what-people-are-saying/), tiered social proof and the on-site home for the positive-mentions feed.
• Blog (/blog/), a real query loop of posts, categories Interviews and Milestones, never Uncategorized; schema type CollectionPage.
• Gallery (/gallery/), conditional: built and added to navigation only when the athlete has eight or more real photos.
• Connect (/connect/), the contact page with platform cards and official profiles; schema type ContactPage.
• Links (/links/), footer-only, the link-in-bio replacement that routes traffic back into the site instead of out to a third-party page.
• Accessibility Statement (/accessibility-statement/), footer-only, honest commitment copy required by the site QA checklist.

Athlete sites are personal brand sites, so on-page copy is first person (“My Story,” “What I Do”), and the WordPress author on every page and post is the athlete, never an admin account. That POV rule comes straight from the blog posting guidelines.

The nine-section homepage

The homepage carries one call to action per section, except the hero, which carries two. A minimum of five distinct real images sit across the page. In order:

1. Hero. A two-column layout with a real portrait or action photo on the right. The H1 begins with the athlete’s literal name plus a one-sentence differentiation (“{Name}. {Role} out of {State}.”). Two buttons: a gold “My Story” and a secondary “Watch My Highlights.”
2. Stats bar. Up to four real, provable numbers from intake (measurables, rankings, wins, verified marks). Numbers, not adjectives. Omitted entirely when the athlete has none.
3. Story teaser. A short “My Story” pull with a plain link to the full About page.
4. What I Do. Exactly three persona-driven cards aimed at the buy box (recruiting, sponsorship, coaching, or content), each with one call to action.
5. Featured clip. The single best highlight, embedded when it is embeddable so the homepage meets the video-on-homepage bar.
6. What People Are Saying. Three attributed quote cards; the whole card deep-links to the original post when a source URL exists.
7. As Seen On. Real placements only (league, press outlets, sponsors). Omitted entirely when empty. This is the section our nine extends past the published eight; it is provable placements, never filler.
8. From the Blog. A real latest-three query loop, never static hand-coded cards, seeded by the launch post.
9. Connect band. A social row and one gold call to action to the Connect page.

Media rules: fast is part of the standard

A slow site fails the standard no matter how good the content is. The lighthouse sites paid real Core Web Vitals penalties for a 1.6MB hero before we fixed them, so the media rules are baked into every pattern:

• The hero is a real image, preloaded, marked high priority, served as a WebP rendition of 100KB or less. We never serve a multi-megabyte original and never use a CSS background image for the largest element.
• Every image carries width, height, and alt text, so layout never shifts and every image is described.
• Everything below the fold lazy-loads.
• Schema image references keep full resolution even though the visible image is downsized.
• Real photos only. The factory never sources or substitutes stock imagery; photo selection is a human step.

Entity schema: making the athlete machine-readable

Structured data is what lets Google and an AI engine actually understand an athlete instead of guessing. This is the difference between a pretty site and an entity. It builds on Google’s Knowledge Graph methodology.

• Person schema, defined once, in full, on the About page, with a single @id of {site-url}/#person. Every other page references that same @id rather than redefining the person (which avoids the duplicate-graph mismatch we found on one reference site). The Person record carries the name, job title, image at full resolution, sameAs (every social and official profile), knowsAbout (sport and position), home location, and email.
• Per-page schema types through Rank Math: About is ProfilePage, Connect is ContactPage, Blog is CollectionPage, posts are Article, and everything else is WebPage.
• The sameAs array is the athlete’s proof web: social profiles plus the federation profile, the league or team page, and the Wikidata item when one exists. Claiming and interlinking those official profiles is its own step, covered in the federation profiles standard.
• Validate every page with Google’s Rich Results Test before launch. That is a human step on the deploy checklist.

The QA gate: what has to pass before launch

Before a site ships, an automated gate checks it against the article guidelines. It exists to catch two failure modes: AI slop and site defects we have seen on real builds. The gate blocks the build (not just warns) on these, among others:

• Zero unresolved template tokens anywhere.
• Zero em dashes, and zero banned words, AI patterns, or salesy phrases in any generated copy.
• Person and WebSite schema parse, and every page’s embedded schema matches its standalone file exactly.
• Balanced Gutenberg block markup, and alt text on every image.
• Every internal link resolves to a real page slug (a stale gallery link is a hard failure, not a soft 404).
• The homepage carries the nine sections in order, and the From the Blog section is a real query loop, not static cards (that static-cards defect is a real one we corrected on a reference site).
• The export file parses as valid XML and every item imports as a draft, so the human gate is never skipped.
• Intake constraints hold: five to ten clips, at most two featured, exactly one hero.
• Unique meta titles and descriptions across pages, and no testimonial quote rendered twice on one page.

Warnings (which a human resolves or documents) cover things like meta descriptions carrying the athlete’s name, a featured clip that is not embeddable, and page-photo alt text that does not include the athlete’s name.

Rank Math to 81 and above

A green Rank Math score starts at 81, not 80. We do not chase it in a single pass; we run the Rank Math loop until each page clears the bar. The homepage focus keyword is the athlete’s full name, targeting the lighthouse bar of 84 and above. Every other page targets one entity or topic, never reused across posts, and every page clears a floor of 70. New posts iterate to 81 and above. Draft scores are supposed to start low; the loop is what produces green.

Real examples

camhazzard.com is the lighthouse. It ranks number one for “Cam Hazzard,” implements the nine-section homepage, carries the full Person schema with one canonical @id, uses per-page ProfilePage, ContactPage, and CollectionPage types, and serves its hero as a roughly 316KB rendition while keeping full-resolution images in schema. It is the site every other build is measured against.

dylan-haugen.com is a second live athlete build on the same standard, a professional dunker’s personal brand site. It also documents what to avoid: an earlier version shipped stale hand-coded blog cards and a duplicate-schema @id mismatch. We fixed those patterns in the standard precisely because we saw them on a real site.

jordan-tate is a synthetic pilot fixture, not a real athlete. We use it to test the builder end to end: the intake goes in, the full package comes out (nine pages, the launch post, schema, the deploy runbook), and the QA gate runs against it. It exists so we can prove the machine works before a real athlete’s data ever touches it. It should never appear in marketing or be presented as a client.

As more athletes are onboarded and their sites verified, each becomes another named example here, per the rule that a definitive article links to as many real examples as exist.

Related frameworks

• The Athlete Spotlight User Journey, the end-to-end path this site standard sits inside at step 5.
• Google’s Knowledge Graph and the Knowledge Panel, what the entity schema feeds.
• The Content Factory, the methodology behind turning an athlete’s clips and posts into the site’s content.
• Own Your Name on Google, the outcome the whole standard exists to produce.

Get started

The full breakdown of what is included lives on the Athlete Spotlight package page. When you are ready, get started for $30 per month and we build your site to this standard. Parents are welcome to check out on an athlete’s behalf.

Third-party validation

This standard is not theoretical. camhazzard.com ranks number one for its owner’s name using exactly the page set, schema, and QA gate above. The methodology is the same personal-brand system Dennis Yu and BlitzMetrics use for their clients, extended for athletes. Google’s own Rich Results Test validates the schema on every build before launch, an independent check that the structured data is correct.