Athlete Spotlight

Category: Definitive Articles

  • Athlete Federation Profiles: Your Strongest Proof Online

    An athlete federation profile is the official record of you published by the body that governs your sport: the World Dunk Association, World Athletics, a national or state federation, a results database like TFRRS, a film platform like Hudl, a recruiting site like MaxPreps, or your school’s athletics roster. It is third-party, verified, structured data about you that you cannot fake, and it is the single strongest proof source most athletes have and never claim.

    This is the Athlete Spotlight differentiator. A business owner’s personal brand rests on press and testimonials. An athlete has something better: governing bodies that publish verified results under your exact name. When a recruiter, Google, or an AI engine asks “is this person legit?”, an official record answers with a sanctioned result instead of a self-claim. This article is the standard for finding, claiming, fixing, and interlinking every one of those profiles so they work for your name.

    Why federation profiles matter more for athletes

    Google’s Knowledge Graph, Wikidata, and AI engines treat federation and stat-site profiles as high-trust corroboration precisely because you cannot fake them. They are the proof recruiters and search engines trust most. This connects directly to how Google’s Knowledge Graph decides who an entity is and how a Knowledge Panel gets built.

    The problem is that most athletes never claim or complete these profiles. They sit half-empty, misspelled, or missing a photo, while carrying exactly the authority the athlete needs. A complete, interlinked official record is also a visible professionalism signal to a recruiter or sponsor before anyone watches a single clip.

    What official records answer that a website cannot

    A website is a self-claim. However well built, it is the athlete talking about the athlete. Federation profiles are the answer to the skeptic scenario that every recruiter and every AI engine runs: “Is this person actually who they say they are?”

    • In AI search, an assistant asked “how good is this athlete?” or “is this athlete’s vertical real?” looks for corroboration it can trust. A governing-body record with a sanctioned result is exactly that. An athlete with no official footprint gets a shrug or a hallucination; an athlete with a complete federation web gets a confident, correct answer.
    • For Knowledge Panel readiness, Wikidata identifiers pointing at athlete databases are the references that raise Google’s confidence that the entity is real and notable. Feeding those identifiers is step 5 below.
    • For general AI-encyclopedia readiness (the kind of open, machine-built reference that pulls from structured sources), the same principle holds: verified, interlinked official records are the citations these systems weight, because they are the ones that are hard to fake.

    The through-line is simple. The website is where the athlete tells their story; the federation profiles are where independent bodies confirm it. AI search and Knowledge Panels are built from that confirmation, not from the story alone.

    The profile map: find every one that applies

    Search every layer for the athlete’s exact name and known results, and inventory what you find:

    • Sport federation or governing body. The World Dunk Association, World Athletics, national and state federations for the sport. These prove sanctioned results, records, and athlete status.
    • Results and stat databases. TFRRS for college track and field, event and league results pages. These prove verified performances with dates.
    • Film and recruiting platforms. Hudl, MaxPreps, sport-specific recruiting databases. These carry film, measurables, and team history.
    • Institutional pages. A school or university athletics roster, club and team pages. These prove affiliation, position or event, and season stats.
    • Knowledge graph. Wikidata (athlete-database identifier properties) and the Google Knowledge Panel. This is the machine-readable identity that ties everything together.

    The six-step standard

    1. Inventory. Search every layer of the map for the athlete’s name and for known event results. List each profile found: URL, claimed status, accuracy, completeness, and whether a photo is present.

    2. Claim what is claimable. Hudl, MaxPreps, recruiting platforms, and many federation portals have a claim or edit flow. Use the athlete’s long-term personal email, never a school email that expires. For minors, this needs a guardian.

    3. Fix and complete. Make the exact name spelling match the entity home, add the consistent headshot, the one-line bio, the current team, and the entity home URL in the website field wherever one exists. For records that carry an error (a wrong spelling, a missed result), file the correction through the body’s official process and log the request date.

    4. Interlink. Add every federation and stat-site profile URL to the entity home in three places: the Person schema sameAs array, the Connect page official-profiles list, and the About page quick-facts table. Where a platform allows a link back, point it at the entity home. The sameAs array is where the athlete site standard consumes these, so this step is what closes the loop between the official record and the site.

    5. Feed the knowledge graph. Add athlete-database identifiers to the athlete’s Wikidata item where properties exist for the sport’s databases, with the profile URLs as references. This is the single move that does the most for Knowledge Panel confidence.

    6. Monitor per season. New results, new teams, new records: re-sweep after every season and major event, update the profiles, and re-verify that every link still resolves.

    The honesty rule that makes this work

    Never fabricate or inflate a record to a governing body. One dishonest correction request can poison an athlete’s standing, and the entire value of this layer is that it is verified. Person is not team is not event: link entities to each other, do not blur them. And a fixed record you cannot edit still counts. If you cannot change it, link to it and let it corroborate you.

    This is the same engine as everything else in the Athlete Spotlight method: one clear entity, many independent sources agreeing. Federation profiles are simply the strongest independent sources an athlete will ever have.

    Worked example: Cam Hazzard and the World Dunk Association

    Cam Hazzard is a professional dunker, one of the athletes selected for the DunkMan League. His World Dunk Association profile is a governing-body record of his identity and status as a pro dunker. Linked from camhazzard.com’s schema and Connect page, it corroborates his story, including a verified 50-inch vertical, to Google and to every AI engine that gets asked whether he is legit.

    The same-name problem makes the official link even more valuable. Cam shares a similar name with a Canadian hockey player, a known search-results collision. The World Dunk Association link pins the right person to the right sport, which is exactly what an entity home needs when a namesake competes for the same search results. This is why the federation profile is not optional polish; it is the piece that disambiguates the athlete for the machines that decide who shows up.

    Real examples

    As more athletes are onboarded and their federation profiles claimed, completed, and interlinked, each becomes another named example here, per the rule that a definitive article links to as many real examples as exist. TFRRS profiles for track athletes, Hudl and MaxPreps profiles for recruits, and state-federation records will populate this section as those builds ship.

    For athletes and parents

    If you are the athlete: your federation profile is the one page about you that nobody can argue with. Claim it, complete it, and make your site and the official record point at each other.

    If you are the parent: this is an afternoon of unglamorous work with outsized payoff, and much of it (claims and correction requests) needs a guardian’s help for minors. Do it once, then it is maintenance.

    Your edge: most competitors have unclaimed, half-empty official profiles. A complete, interlinked official record is a professionalism signal to recruiters and sponsors before anyone watches a single clip.

    Related frameworks

    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 inventory, claim, and interlink your official profiles as part of building your presence. Parents are welcome to check out on an athlete’s behalf.

    Third-party validation

    The proof in this article is, by design, third party. Cam Hazzard’s status as a pro dunker is recorded by the World Dunk Association, an independent governing body, not by us and not by him. That is the entire point of the federation layer: the corroboration comes from bodies that publish verified results, which is why Google, Wikidata, and AI engines weight it so heavily.

  • The Athlete Weekly AI Report: What Changed and What To Do

    The weekly AI report is one branded email an athlete gets every week that covers both halves of their online presence: what people said about them, and how their site is doing. It answers a simple question in plain language: what changed this week, and what should you do next. Where we have a live connection to real data, the report shows real numbers. Where we do not, it says “not yet connected” instead of inventing one.

    This is the deliverable behind the marketed promise of ongoing value. It is not a vanity dashboard of follower counts. It is built on the MAA framework (Metrics, Analysis, Action): real metrics week over week, a short honest analysis that names the weakest area, and up to three concrete actions, the first of which always targets that weakest area. This article is the standard that report is built to.

    What the weekly AI report is

    The report is the “Perform” stage of the Content Factory made systematic for one athlete. It runs weekly, reads only real data, and is generated as a file first; sending is consent-gated and idempotent, so an athlete never gets a duplicate and never gets a report for a week we did not actually measure.

    It has two halves, and both are honest about their edges. The mentions half is fully live. The site half reports every signal we can collect for free, and clearly labels every signal we cannot yet reach.

    Half one: what people said about you

    This half is the mentions digest, and it is live today. Each week it surfaces:

    • New mentions this week: organic positive mentions of the athlete found across the platforms we sweep.
    • The ad-ready spotlight: the single best quote, the kind an athlete could actually put on their site or in an ad, chosen for marketability, not just positive sentiment.
    • A game plan: what to do with the week’s mentions.
    • One-click action buttons: add a mention to the site, post it to LinkedIn, or turn it into an ad.

    This half runs on the Positive Mentions System, built by Cam Hazzard and developed with Dennis Yu. Only genuinely usable, positive mentions ever reach the report; criticism is never shown to the athlete.

    Half two: your site this week (MAA)

    This half is a Metrics, Analysis, Action block about the athlete’s website, built entirely from free, no-billing signals. Every signal is independently optional: if one cannot be collected, the report says so rather than blocking or guessing.

    Metrics (real numbers only, week over week where a prior snapshot exists)

    • Site status: up or down, the actual HTTP status code, and response time in milliseconds. An HTTP 403 from bot protection is reported as a 403, not as “down.” A network failure on our side is retried once and then reported as “check inconclusive this week,” never as a confirmed outage.
    • Uptime over the last 7 days: from a free UptimeRobot account, when the site is added as a monitor.
    • Speed score out of 100, plus LCP seconds and CLS: from Google PageSpeed Insights (mobile).
    • SSL certificate: days until renewal, from a direct TLS handshake.
    • Search basics: whether the homepage has a title tag and JSON-LD structured data present.

    Deltas name the actual prior-check date (“up from 151 ms on the 25th”), never a vague “last week.” The snapshot that drives next week’s comparison is saved only on runs that actually send, so the report always compares against the last report the athlete really received.

    Analysis (one short paragraph)

    A single rule-based paragraph that calls out the weakest area (the MAA rule: the analysis must name the weakest metric, not list what we did), names any week-over-week movement, and says “not yet connected” for anything we could not collect. It never invents a number.

    Action (up to three items)

    The first action always targets the weakest signal. The priority order, as built, is: site down or server error first, then SSL expiring or no HTTPS, then a slow response or HTTP errors, then an uptime slip, then speed and Core Web Vitals, then search basics. If uptime is not connected, an action suggests connecting it.

    What is honest to say today, and what is not

    The whole value of this report is that an athlete can trust it. So the standard draws a hard line.

    Live today (real, in the report): uptime, speed score, Core Web Vitals (LCP and CLS), SSL health, search basics, and week-over-week movement on all of them, plus everything the mentions digest already does. The single honest one-line description is: “A weekly AI report on your site and your mentions: what changed and what to do next.”

    Not connected yet (we do not claim it):

    • Google Search Console data: the queries you rank for, clicks, impressions, and average position. This needs the owner’s OAuth consent per site; there is no free keyless path. The planned next step is a Search Console connector added as another optional signal, so this becomes a real part of the report once an athlete connects it.
    • Site analytics: visitors, sessions, and traffic sources. Same reason: it needs the owner’s connection.
    • Rankings movement and follower counts: not collected here, so never claimed here.
    • Any week we did not measure: the report only compares against snapshots that actually exist.

    The conversion: what the report aims actions at

    The MAA Action section is strongest when it measures a real business result, not vanity metrics. For a business, that result is a lead or a sale. For an athlete, the “sale” is fuzzier: a sponsor inquiry, a training-program purchase, a recruiting contact.

    We recommend tracking contact events, sponsor and recruiter inquiries through the Connect page, as the first conversion. The Connect page already carries the athlete’s contact path, so treating a contact event as the conversion gives the weekly report one concrete, ownable business number to trend and to aim actions at, instead of follower counts. It is the smallest honest conversion we can measure without new plumbing.

    The right conversion can differ by athlete and goal. A recruit’s conversion is a coach’s contact; a creator’s conversion may be a sponsor reply or a program sale. We set it per athlete when the site goes live. Until it is set, the report measures site health and mentions, and the conversion line is noted as pending.

    How an athlete turns it on

    The report is opt-in per athlete and off by default, so no one is emailed without consent. Turning it on is two settings on the athlete’s config: the site URL to report on, and the report switch. Without both, the digest is byte-identical to the mentions-only version, with no new output and no network calls. A safe preview path renders the full report to a file without ever sending it, so we can check a report before an athlete sees it.

    Sending itself stays behind the same consent gate as every client email: it goes out only when the athlete has consented and the cadence window is due, it skips weeks with nothing new, and it honors any unsubscribe unconditionally. Nothing in the report auto-publishes anywhere.

    Real examples

    The report runs on the shared Positive Mentions engine that has been exercised across multiple subjects. The site-health half was built and tested against theathletespotlight.com itself and the lighthouse, camhazzard.com, using the free signals above. As athletes are onboarded and opted in, each week’s report for that athlete becomes a data point, and the build of the report is itself documented in three meta articles (how the site-health section was built, how mentions were connected to athlete sites, and how the tooling was kept in sync), each with the real free-API numbers behind it. Those meta articles link back to this standard.

    Related frameworks

    Get started

    The full breakdown of what is included, the weekly AI report among it, lives on the Athlete Spotlight package page. When you are ready, get started for $30 per month and the weekly report starts once your site is live. Parents are welcome to check out on an athlete’s behalf.

    Third-party validation

    The report only uses independent, verifiable sources: Google PageSpeed Insights for speed and Core Web Vitals, a direct TLS handshake for SSL, and UptimeRobot for uptime. Because it reads real signals and refuses to invent numbers, every figure in it can be checked against the source that produced it. The MAA structure it follows is the same measurement framework BlitzMetrics uses across client reporting.

  • How We Build an 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

    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.

  • The Athlete Spotlight User Journey: Checkout to Live Site

    Athlete Spotlight turns a $30 per month sign-up into a real personal brand website on the athlete’s own domain, built from everything findable about them, delivered with an honest audit, and improved every week after that. This article is the full map of that journey: what the athlete does, what our agents do, and where a human has to step in, from the checkout screen to the change request they send us six months later.

    We are writing this down for two reasons. First, so every athlete knows exactly what they are buying and what happens next, with no two-month silence and no surprise reveal. Second, so our own team and our agents follow one standard. Each time we onboard an athlete, that run gets documented as its own case study with real numbers attached (sales, traffic, rankings, and the weekly report). This is the standard those case studies point back to.

    What the Athlete Spotlight journey is

    The journey is the end-to-end path an athlete travels with us: they find the site, pay through our Keap checkout, buy their own domain, hand us their content and story, and our system builds their WordPress site from that plus everything already published about them online. We deliver the site alongside an audit, then keep improving it through a change-request loop and a weekly AI report.

    It is one journey, but it has honest edges. Some steps run today with no human babysitting. Others are drafted and being wired in. We name both, because a standard that pretends everything is automated would be a standard nobody could trust. The gaps below are the build order, not a disclaimer.

    The whole thing sits inside the Content Factory methodology (Produce, Process, Post, Promote, with Perform as the measurement loop). The site is the entity home; the weekly report is the Perform stage made systematic for one athlete.

    Step 1: Discover and decide

    The athlete lands on theathletespotlight.com. They see the roster (real athletes, including the lighthouse example, camhazzard.com), the What’s Included breakdown, and the price: $30 per month, no contract. Many arrive through a figurehead’s referral code, which applies 20% off (for example, code CAM), with a 50/50 revenue split behind the scenes.

    The one thing this step still needs is the promo video. A short clip from an athlete explaining what Athlete Spotlight does is committed and not yet recorded. Until it exists, the page leans on the roster and the written What’s Included section to make the case.

    State: LIVE (page and roster), with the promo video still to record.

    Step 2: Checkout

    Checkout runs through Keap today. The athlete clicks Get Started, lands on the Keap checkout for the Athlete Spotlight product ($30 per month), and if they came through a figurehead code, the 20% discount applies. Keap generates the order and the receipt, and the order lands in a queue. Parents are welcome to check out on an athlete’s behalf, which matters because a large share of our audience is 14 to 18 years old and their guardians decide and pay.

    Here is the first honest gap. Today, nothing automated fires the moment payment clears. The athlete pays, and the next move is manual. The fix is a post-payment thank-you page or email that routes the athlete straight into intake (step 3). We are reusing an existing Keap campaign pattern for this rather than building a parallel automation, so the work is coordination, not net-new plumbing.

    State: LIVE (checkout), WIRING (the automatic hand-off to intake).

    Step 3: Intake

    Right after checkout we collect what the site is built from: name, sport, position or class year, location (sport plus location feed the network-linking strategy), social handles, five to ten best clips as links, photos, the athlete’s story in their own words, and proof (stats, awards, camps, coaches, press, sponsorships). We also capture the goal persona, because a recruit and a sponsorship-seeker get a different site emphasis. The canonical field set lives in the intake schema the site factory reads from.

    The story fields are collected in the athlete’s own first-person voice and rendered close to verbatim. We do not rewrite a 16-year-old’s story into corporate copy. The open question here is the surface: a form, an email reply, or a DM-style capture. Dennis’s guidance is blunt and correct: young adults will not email. A form is the near-term answer; a DM-style surface comes later.

    State: WIRING (spec is done: 43 fields, required set, and hand-off format; it drops into the post-payment Keap flow).

    Step 4: Domain

    The athlete buys their own domain, roughly $12 a year at any registrar. Owning the domain matters: the SEO value and the entity home live on an asset the athlete controls, not on a subdomain we lease to them. We reply with the four nameservers to paste into their registrar’s DNS settings, the same process the team has run hundreds of times.

    The draft nameserver email is written (registrar steps, a generic fallback, placeholder nameserver values, and a short how-to video link). Two things stay open: who sends it, and the actual per-athlete nameserver values, which come from provisioning once a hosted zone exists for that athlete.

    State: LIVE (the process is proven), WIRING (the email template’s sender and the per-athlete values).

    Step 5: Build and audit

    This is the machine. The order, the intake, and the domain come together into a provisioning decision, and the site gets built on the company platform (WordPress, provisioned through BlitzAdmin, the company’s site builder). The system builds from the intake AND from everything findable about the athlete online, and it runs an audit at the same time. This is the Dunk Camp pattern: deliver the site and the authority audit together, not weeks apart.

    Our tooling plugs in here. The site factory template kit supplies the nine-section homepage and the full page set. Entity schema (a Person record and per-page schema types) tells Google and AI engines who the athlete is. A QA gate blocks the build on real problems (banned words, unresolved template tokens, missing alt text, broken internal links, stale hand-coded blog cards). The Rank Math loop lifts every page toward the green score. The positive-mentions feed supplies the proof section. The site standard behind this step is its own article: how we build an athlete personal brand website documents the nine-section homepage, the page set, the schema, and the QA gate in full.

    The open seam is the exact hand-off between BlitzAdmin provisioning and our site-factory content pipeline. Cam now has a BlitzAdmin login and the mapping of that seam is the next investigation.

    State: LIVE (the site factory tooling, the audit pattern, the QA gate, the Rank Math loop), WIRING (the BlitzAdmin provisioning hand-off).

    Step 6: Delivery

    We send a delivery message: congratulations, here is your site, here is your audit, and here is what to know. Crucially, this message sets the expectation that the athlete will want changes, and shows them exactly how to ask. It also carries the fix-at-the-source coaching, because the site reflects the internet: if a bio or a photo is wrong on a source platform, it should be corrected there too, not just on the site.

    The delivery email draft is done (site link, audit, fix-at-the-source coaching, the change-request path, and the referral hook). One wording decision stays open: the athlete-level referral split. The 20% off with figurehead codes is confirmed; the percentage a regular athlete earns for a referral is not, so the copy stays vague on that until Cam and Dennis lock it.

    State: WIRING (draft done; referral-split wording pending).

    Step 7: Changes and ongoing value

    This is the retention loop, and it is what makes $30 a month worth paying past month one.

    Change requests. The athlete logs into theathletespotlight.com with a username and password and types what they want changed; an agent monitors the queue and executes on their site. This login does not exist yet. Dennis calls it easy to build, and it is a pattern people already understand. The v1 fallback that works today is simple: the athlete replies to the delivery email, and we make the change. The spec for the real login (a WordPress-native login, a request form, a queue, and an agent monitor) is written and estimated at under half a day to build.

    The weekly AI report. This one is built. Every week the athlete gets one branded email covering both halves of their presence: what people said about them (new mentions, the best ad-ready quote, a game plan) and how their site is doing (uptime, speed, Core Web Vitals, SSL health, and search basics, with week-over-week movement and up to three concrete actions). Where we have a live connection, it shows real numbers; where we do not, it says “not yet connected” instead of inventing one. The report standard is its own article: the athlete weekly AI report documents its scope.

    Positive mentions keep flowing. New praise about the athlete keeps landing on the What People Are Saying page as it is found and approved. This runs on the Positive Mentions System, built by Cam Hazzard and developed with Dennis Yu.

    Define the conversion. For an athlete, the sale is fuzzy: a sponsor inquiry, a training-program sale, a recruiting contact. Part of ongoing value is defining that conversion up front so the weekly report measures a real business result, not vanity follower counts.

    State: LIVE (weekly report and mentions loop), WIRING (the change-request login; email reply works today).

    The gaps list, as a build order

    Being honest about the journey means publishing the gaps, in the order we are closing them:

    1. Post-payment intake routing (Keap thank-you page or email routes to the intake form).
    2. The nameserver-instructions email template (sender assigned, per-athlete values wired).
    3. The BlitzAdmin hand-off (how our content pipeline feeds the provisioned WordPress site).
    4. The customer login and change-request queue on theathletespotlight.com, with an agent monitoring it.
    5. A DM-style feedback surface (later; email-first v1 is acceptable).
    6. The athlete conversion definition for the weekly report’s MAA section.

    None of these blocks the core promise. An athlete can buy today, get a site, get an audit, get a weekly report, and get changes made by email reply. The gaps are what turn a good manual delivery into a hands-off one.

    Who this journey is for

    • Young athletes (14 to 18) chasing college offers with little or no online presence. Their parents usually decide and pay, which is why checkout allows a guardian and why the domain is the athlete’s own asset.
    • Athletes and athletic creators chasing sponsorships who already have content but no real web home. An Instagram page with a few hundred followers is not authority; an ownable, indexable site is the link you send a sponsor.

    The lighthouse example is camhazzard.com, which ranks number one for “Cam Hazzard.” It is the proof that this journey ends somewhere real.

    Related frameworks

    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 the journey above begins at step one. Parents are welcome to check out on an athlete’s behalf.

    Third-party validation

    Athlete Spotlight is built on the same personal-brand methodology that Dennis Yu and BlitzMetrics use for their clients, adapted for the athlete vertical. The lighthouse site, camhazzard.com, ranks number one for its owner’s name and is the primary case study. Dylan Haugen (dylan-haugen.com) is a second live athlete build on the same standard. As each athlete is onboarded, that execution is documented as a meta article with real analytics (traffic, rankings, and the weekly report), so the proof accumulates in public rather than sitting in a testimonial.