A polished athlete website can be built quickly. Keeping it accurate and maintained is ongoing work. DIY tools can fit a family that wants to manage hosting, updates, accessibility, and technical decisions. The Athlete Spotlight is the managed alternative for $30 per month and can help the customer plan a clean exit under the Terms.

Tools and a managed service solve different jobs

Migration is an implementation project

An existing site can preserve useful URLs when redirects, canonical URLs, sitemaps, analytics, and search-tool verification are handled carefully. Missing those steps can break links or discard history. No platform switch automatically improves or damages search performance.

The domain rule

We register an included standard new .com after payment settles. Until transfer, it remains in Your Content Factory LLC’s registrar account. After one paid, non-refunded month, the adult athlete—or the guardian for an athlete age 13–17—may request transfer under the Terms. A new registration or registrant change can be subject to a 60-day transfer lock, so completion may be delayed.

Current scope versus roadmap

The package page is the source of truth for what the $30 subscription includes today. A feature shown on the roadmap is not a current benefit until the package page says it is included.

Choose based on who will operate the site

Choose DIY when your family wants responsibility for the technical stack and has the time or help to maintain it. Choose a managed service when you want a team to maintain the public home while the adult athlete—or both the minor athlete and guardian—controls what is published.

Review what the $30 package includes, read the Terms, or run the free brand-readiness audit. The audit is an informational readiness signal, not a measure of athletic talent or future income.

Content workflow template

How one approved interview can support five distinct articles

This is a reusable editorial model, not a case study or a claim that every interview produces search traffic. Publication requires source verification and permission for every personal detail, quote, image, and recording.

Five useful angles

1. An approved first-person profile on the athlete’s own site.
2. A performance or training explainer grounded in verifiable facts.
3. A recruiting or sponsor FAQ with a direct contact path.
4. A source-led article for the relevant sport community.
5. A process note explaining how the material was reviewed and organized.

Do not duplicate the transcript

Each article should answer a different reader question, add original context, link to primary sources, and point back to the athlete’s maintained entity home. Thin copies and fabricated details do not help the reader.

This workflow does not guarantee rankings, traffic, recruiting, sponsorships, press, or AI citations. For an athlete age 13–17, the athlete must assent and the parent or legal guardian must approve the material and its promotional use.

Search visibility guide

How athletes can present clearer information to search and AI systems

Search engines and AI systems rely on accessible, corroborated information. An athlete cannot control whether a system ranks, summarizes, or cites a page, but can make official facts easier to verify.

Start with one maintained entity home

Use a standard .com with the athlete’s approved identity, sport, current goals, verified results, source links, media, and contact path. Keep dates explicit and correct errors when they are found.

Connect the surrounding evidence

Link to official team, federation, event, school, or press sources where appropriate. Use structured data that matches the visible page. Repurpose only material an adult athlete has authorized or, for an athlete age 13–17, material covered by the athlete’s assent and the parent’s or legal guardian’s approval.

Measure without promising

Track impressions, clicks, crawl health, and conversions after measurement is connected. No website can guarantee rankings, traffic, recruiting, sponsorships, press, or AI citations.

See the managed website package or run the free brand-readiness audit.

The Athlete Spotlight is designed as one maintained public source for approved athlete information. The useful part is not a decorative diagram or an automated promise. It is the connection between clear service terms, authorized source material, a structured website, and a repeatable update process.

The four parts of the current product

1. A readiness check. The free brand-readiness audit gives an informational starting point. It is not a measure of athletic talent or a promise of recruiting, rankings, sponsorships, or income.
2. A defined package. The What’s Included page states what the $30 monthly service includes today. Roadmap concepts are not current benefits unless that page says so.
3. A permission record. An adult athlete approves their own material. For an athlete age 13–17, the athlete must assent and the parent or legal guardian must approve before material is published. The audit and paid service are not offered to children under 13.
4. A maintained website. Approved facts, results, links, photos, and clips are organized into a clear public home with routine maintenance and one content request in each paid month.

How one content request moves through the system

The adult athlete or guardian starts with source material they have authority to use: a factual update, interview, clip, result, or correction. Our team checks the requested change against that source, prepares either one article from supplied material or simple factual edits to one page, and returns it for the required approval. After approval, the change is published and linked to the most relevant part of the athlete’s site.

Unused requests do not roll over, and work outside that monthly scope is quoted separately. This keeps the public offer understandable and gives the customer a predictable way to keep the site current.

Structure helps interpretation; it does not guarantee an outcome

Descriptive page titles, accessible headings, internal links, and appropriate structured data can make approved information easier for people and software to interpret. Those practices do not control search engines, schools, recruiters, media outlets, brands, or social platforms. The service does not promise a knowledge panel, ranking, recruiting contact, coverage, sponsorship, free product, contract, or income.

Where privacy and control fit

Operational information needed to answer a request or administer a purchase is separate from optional marketing. A public profile or paid subscription is not permission to use an athlete in a testimonial, gallery, advertisement, case study, or social post. Those promotional uses require a separate, use-specific release; for a minor, that means both the athlete’s documented assent and the guardian’s documented approval.

The customer controls cancellation and may request eligible content and domain transfer under the Terms. The parent and guardian guide explains the age-specific rules in plain language.

Choose the next useful step

If you are still deciding what the athlete’s public information needs, start with the free brand-readiness audit. If you already want a managed website, review the exact scope, domain rules, renewal terms, and cancellation route on the package page before paying.

Product specification

The planned athlete findability report

This page describes a report in development, not a current recurring customer email. The current $30/month package does not include it.

Intended inputs

The planned report may combine approved public mentions with measured site-health signals when the required data connections are available. Missing data must be labeled; it must never be estimated or invented.

Intended output

The specification calls for a short summary of what changed, the weakest measured area, and up to three possible next actions. Recommendations are informational and do not guarantee rankings, traffic, recruiting, sponsorships, press, or AI citations.

Consent and delivery

Production delivery must be opt-in. An adult athlete must approve the account, destination, and use of personal information. For an athlete age 13–17, the athlete must assent and the parent or legal guardian must approve. Previewing a prototype does not prove scheduled delivery.

The public roadmap is the source of truth for launch status.

An athlete website is a maintained record, not a one-time design file. The build starts with approved facts and ends with a site that can be updated as the athlete’s career changes.

1. Establish the publishing authority

An adult athlete can approve their own material. For an athlete age 13–17, a parent or legal guardian contracts for the service, the athlete assents, and the guardian approves what is public. The service is not offered to children under 13.

2. Build from source material

The athlete or guardian supplies facts, results, links, clips, and images they have the right to use. We organize that material into a clear biography, results record, media section, and contact path. Unsupported claims stay out.

3. Create a portable web home

The managed $30 monthly package includes the current services listed on the What’s Included page. A standard new .com is registered after payment settles and follows the transfer rules in the Terms. Premium and aftermarket domains are separate.

4. Add structure without promising an outcome

Accessible page structure, descriptive metadata, internal links, and schema can help systems interpret approved information. They do not promise a search position, panel, recruiting contact, sponsorship, coverage, or income.

5. Maintain the record

The subscription includes routine maintenance and one content request in each paid month. A request can be one article from a supplied clip or interview, or simple factual edits to one page. Unused requests do not roll over, and extra work is quoted separately. Experimental reporting and automation remain roadmap items until the package page says they are included.

Start with the free brand-readiness audit or review the current package.

Product journey

From intake to an approved athlete website

1. Readiness audit: collect the information the visitor chooses to submit.
2. Decision: review the current package, terms, and cancellation policy.
3. Consent: obtain approval from the adult athlete or, for an athlete age 13–17, document the athlete’s assent and the parent’s or legal guardian’s approval.
4. Source review: verify facts, links, dates, and rights to media.
5. Build: organize approved material on a managed standard .com.
6. Publication: complete accessibility, schema, link, and consent checks.
7. Ongoing updates: provide routine maintenance and process one approved content request in each paid month. Unused requests do not roll over.

The current $30/month package includes the managed site, hosting and HTTPS, baseline entity markup, a standard available .com under the published terms, routine maintenance, and one approved content request in each paid month. A recurring weekly findability email remains on the roadmap. None of these steps guarantees search, recruiting, sponsorship, traffic, press, or AI outcomes.

Two systems, one athlete. That is the whole idea. The Positive Mentions System can find and score what people say about someone online, while the Athlete Spotlight site factory can build a website. The prototype tested a guarded bridge between those separate systems.

The prototype uses a bridge with read-only access and human approval gates. This article documents what the code can render when configured; it does not establish automatic proof refresh or recurring member delivery. The site tooling cannot publish or write to the mentions database on its own.

What the prototype connects, and why positive mentions matter

The assignment: test whether an athlete’s proof section could be prepared from the mentions knowledge base without letting automation publish or letting site tooling write to production data. The sources were the mentions engine, the site factory’s template kit, and a wiring contract written first.

The deliverable was two small bridge scripts, pma_feed.py (286 lines) and onboard_map.py (154 lines), shipped with the site factory on 2026-07-02. They demonstrate a draft-rendering path; they do not prove that every member receives a recurring proof refresh.

How the loop runs, per athlete

The prototype workflow has five steps when an authorized run is executed. Routine weekly member delivery has not been proven.

1. Prepare an authorized intake. An adult athlete must explicitly opt in. For an athlete age 13–17, the athlete must assent and the parent or legal guardian must approve before onboard_map.py converts the intake into a pilot signup payload.
2. Create the pilot subject (human gate 1). A person submits the authorized payload. This creates a pilot subject; it does not activate a purchased recurring digest.
3. Run collection when authorized. The engine can collect mentions across supported sources, score them with the marketability rubric, and export. Scheduler capability is not evidence that every member receives a weekly run.
4. Render a draft proof feed. pma_feed.py can pull eligible quotes into a machine-readable feed and a website-ready testimonials block marked DRAFT. A person still has to review and publish it.
5. Review and publish (human gates 3 and 4). A person reads every quote, verifies attribution at the source URL, trims platform openers, then pushes the reviewed block to the live page through a logged-in session.

Four human gates are defined in the contract: adult-athlete approval or, for ages 13–17, documented athlete assent and parent/legal-guardian approval; site-package review; quote review; and live publish. Nothing in the prototype auto-publishes, auto-emails, or writes to the mentions database.

The design decisions

Read-only in the tested code path. The bridge opens a configured SQLite database in read-only mode, which blocks writes through that connection. This is code-level evidence, not proof of a live production integration or recurring member delivery.

Only usable rows leave the database. The filter is the same marketability-over-sentiment rule the digest and the activation tools use. One gate, shared everywhere. “Fire episode!” is data; it is never a deliverable. The research pile and hidden rows never reach an athlete-facing surface.

A synthetic pilot that can’t leak. The pipeline test athlete is fictional, so a fixture flag loads a clearly synthetic feed and never touches the database at all, and the onboarding script refuses fixtures outright. The fake athlete can never be onboarded into the real engine. The tooling favors isolation over speed.

DRAFT stamped into the output itself. The testimonials block carries a DRAFT header comment, so even the file tells you it has not passed review yet. The verify-before-publish rule applies before any top-tier quote goes live.

What it cost, honestly

Honest label: no token receipt exists for this build (the metrics extractor is still an open gap), so these are documented estimates.

The second row estimates the planned operating model. It is not evidence of routine paid-member delivery.

What the agent did, and what a human owns

Code capability: convert an authorized intake to a pilot payload, pull eligible quotes, render a draft feed and website block, restyle cards to the site’s design tokens, and scrub em dashes by construction.

Human required: approval from the adult athlete or, for an athlete age 13–17, documented athlete assent and parent/legal-guardian approval (gate 1); site-package review (gate 2); source verification for every quote (gate 3); and publication through a logged-in session (gate 4). Any profile or promotional image must be authorized for this use; public availability or re-hosting alone is not consent.

What the implementation used

Inputs reviewed for the prototype included the mentions engine’s usable-row predicate and database layout, the testimonial-card shape, the template kit’s proof pattern, and the intake schema. Outputs included the wiring contract, two bridge scripts, the fixture feed, and builder tests. Token use was not measured; see the cost section for the documented estimates.

How it scores against our own gate

This published revision is a dated prototype note, not a live-delivery case study. It carries explicit product-status and consent requirements. Any future promotional imagery or outcome proof requires recorded permission and source verification before it is added.

What the prototype demonstrates, and what remains

The prototype bridge can prepare a draft proof block for a configured Athlete Spotlight website, and the planned mentions half of the weekly findability report is designed to use the same engine; recurring customer delivery remains on the roadmap. This is one of three meta articles on that build; a companion covers how the report’s site-health half was built. The whole thing operationalizes the Perform stage of the Content Factory.

The $30 subscription includes the managed site, hosting, HTTPS, a standard new .com under the published Terms, baseline entity markup, and one approved content request per paid month. Unused requests do not roll over. It does not currently include an automated recurring proof refresh or weekly report; follow the public roadmap for launch status.

Dunking and business are the same game. The collection run, scoring, review gates, and source check come before any approved quote can appear on a live site.

Internal prototype build, documented July 2, 2026.

Engineering note

How the site-health report prototype was designed

This is a technical prototype note. It does not establish a live recurring integration or a delivered customer feature.

Design constraints

• Read only from explicitly configured sources.
• Label missing connections instead of inventing a metric.
• Render a preview before any delivery step.
• Require consent and an approved recipient before sending.
• Keep retries idempotent so a run cannot create duplicates.

What a prototype proves

Passing fixture and preview tests can demonstrate code behavior in the tested path. It does not prove production scheduling, monitoring coverage, deliverability, support readiness, or routine member use.

The recurring findability email remains in development and outside the current $30 package. Follow the public roadmap for release status.