Before we run the audit, we need to make sure we're asking the right questions about the right competitors to the right buyers. This document presents what we've learned about NeuroGuard+'s market — your job is to tell us what we got right, what we got wrong, and what we missed.
Before we measure citation visibility in the concussion-reduction mouthguard space, these three signals tell us whether AI crawlers can access, read, and trust neuroguardplus.com — the baseline every downstream query result depends on.
AI assistants are quickly becoming the first place parents, athletes, and sports programs turn when they ask what gear actually protects an athlete's brain. For a direct-to-consumer startup making a bold, category-defining claim — a custom-fit performance mouthguard marketed to reduce concussion risk and boost strength through jaw alignment — that shift is a rare opening: the brand that earns AI citations in this space now becomes the default answer before the category's larger, better-funded incumbents treat generative search as a channel worth defending.
This Foundation Review lays out what we've assembled before running the audit: the competitive set that shapes how we construct head-to-head queries, the buyer personas that determine the search intent we test, and the technical baseline that decides whether AI platforms can extract and cite your content at all. Think of it as the shared brief we validate together — every competitor tier, persona role, feature rating, and finding below is a lever you can confirm or correct before a single query runs.
The validation call is a working session with real stakes. It resolves two kinds of decisions: (1) input validation — are the right buyers, competitors, and capabilities in the right tiers? — and (2) engineering triage — which technical fixes can your team start on now, before results come back? The Pre-Call Checklist at the end aggregates both so you can prepare in one pass. Your answers set the query architecture; a wrong assumption left uncorrected propagates through the entire audit.
Purpose This is a validation document, not a report card. It captures our outside-in model of the concussion-reduction mouthguard market — who buys, who you compete with, what capabilities matter, and what's technically standing between your site and AI citations. Everything here is a hypothesis you can confirm or overturn.
Your Job Read the purple boxes. Each one names a specific entity and a specific consequence for the audit if we've got it wrong. Those are the decisions that need your judgment — no one knows your deals better than you do. Skim the rest; live in the purple.
Confidence Badges Every entity carries a confidence badge. High means we sourced it directly from your site or customer reviews. Medium means we inferred it from category patterns. Low means it's a best-guess placeholder that needs your confirmation. Medium and low badges are where your input matters most.
→ Validate Your product ladder implies two very different buying motions: an individual parent or athlete buying one guard at $49.97 (or the $79.97 DoublePack), and a "Team Order" bulk channel aimed at coaches and athletic directors. Which is your real growth engine? If the team channel is primary, roughly half the query set shifts toward liability, certification, and bulk-pricing language; if DTC is primary, it stays anchored on comfort and "does it actually work." We can't weight the two clusters correctly until you tell us where the revenue comes from. (Related: third-party listings show higher "Elite/Max Professional" tiers than the $49.97/$79.97 on your site — is that a real product ladder we should query, or stale reseller data?)
5 personas — 3 decision-makers, 2 influencers — and each searches differently, which is exactly why they drive the shape of the buyer query set the audit runs.
Critical Review Area Personas are the highest-leverage input in this document — they determine the intent behind every query we generate. Two of your three decision-makers (Marcus Bell, Rebecca Ortiz) are inferred from category patterns rather than sourced from your reviews, so scrutinize their roles and buying authority closely.
Data Sourcing Note Names, roles, seniority, and veto power come straight from the knowledge graph. Buying jobs and query focus areas are synthesized from each persona's role, department, and the pain points linked to them — they're our best model of how each buyer searches, not a claim pulled verbatim from your site.
→ Is the parent the sole decision-maker, or does a coach's or trainer's recommendation gatekeep the purchase in your youth deals? If institutional recommendation drives the buy, we shift weight from parent-consumer queries toward "what does the trainer recommend" queries.
→ Does the athletic trainer actually hold veto power over gear purchases, or only advise the AD/parent? If they're advisory, we reclassify Marcus from decision-maker to influencer and drop the validation-stage liability and evidence queries written in his voice.
→ On the company profile we're asking which channel to weight; here the narrower question is who signs in the team channel — the AD (procurement/liability lens) or the trainer (evidence lens)? Whoever holds the budget determines which criteria drive the team query cluster.
→ In a club (non-school) context, does the coach actually place and pay for team orders? If yes, Tyler becomes a decision-maker for the club-team cluster and we add purchase-stage bulk-ordering queries in his voice rather than influence-stage ones.
→ Are adult combat-sport athletes a large enough slice of revenue to warrant their own query cluster, or should we fold them into the DTC consumer set? If distinct, we add MMA/boxing/wrestling performance-and-legal-edge queries; if not, we save that budget for the parent and team clusters.
→ Missing personas? These roles sometimes show up in concussion-mouthguard deals — do they show up in yours? Team dentist / orthodontist (if braces-compatibility and dental signoff is a distinct buying conversation), equipment / purchasing manager (if bulk team orders route through procurement rather than the AD), and physical therapist / return-to-play clinician (if post-concussion athletes are a referral source). Each would justify its own query cluster. Who else shows up in your deals?
5 primary + 4 secondary competitors identified — and the tier we assign each one decides whether the audit tests them as a direct head-to-head or as background category awareness.
Why Tiers Matter Primary-tier competitors get direct comparison queries — "NeuroGuard+ vs. [brand]," "best concussion-reduction mouthguard," "mouthguard you can talk and breathe through" — roughly 6–8 head-to-head queries each, so 5 primaries anchor about 30–40 comparison queries. Two primaries are medium-confidence: OPRO (assigned from category listings) and Under Armour ArmourBite (which is largely discontinued and hard to buy). If either rarely surfaces in your actual buyer's consideration set, moving it to secondary pulls ~6–8 queries out of the head-to-head set and into category awareness.
→ Validate Three tier questions before we lock the head-to-head set: (1) PowerPlus Mouthguard shares your inventor, your claims, and duplicated blog content — is it a genuine competitor we track head-to-head, or is it really you under an old brand, in which case we fold it into your entity variants? (2) Do medium-confidence OPRO and Under Armour ArmourBite actually appear in your buyers' consideration sets — ArmourBite is largely discontinued, so does it still get searched? (3) Is anyone here irrelevant, or is a real rival (a custom-lab or team-channel brand) missing?
11 buyer-level capabilities mapped — and each strength rating determines which capability queries the audit expects you to win, and which it expects you to defend.
A mouthguard that actually lowers my kid's chance of a concussion, not just protects their teeth
A guard I can talk and breathe through so I actually keep it in the whole game
Get a snug custom fit at home without a trip to the dentist
Does putting my jaw in the right position really make me stronger and more balanced?
Show me the peer-reviewed studies that prove this works before I trust my brain to it
Is it FDA-cleared, ADA-accepted, or approved by my league so I'm allowed to use it?
Will it fit over my kid's braces or do we need a different guard?
One guard that works for football, wrestling, lacrosse, and everything else my athlete plays
Is a $50 mouthguard really worth it over the $15 one at the sporting-goods store?
Outfit my whole roster with a bulk discount and simple ordering for the season
A guard that keeps its fit and doesn't get chewed to pieces halfway through the season
→ Validate The critical rating is Concussion & Head-Impact Risk Reduction: it's your central differentiator but rated only moderate, with Clinical Evidence rated weak — because there's no peer-reviewed proof and medical consensus holds that no mouthguard prevents concussions. Is this a "strong" pillar you want to lead with, or a "moderate" supporting claim? That single call changes whether the audit probes competitors' missing safety evidence as your opening, or plays defense on the credibility risk. Separately: are Braces Compatibility and Durability (both low-confidence) accurate as weak/moderate, and should At-Home Custom Fit and Braces Compatibility merge, or do buyers treat them as distinct?
10 pain points — 4 high, 5 medium, 1 low severity — and their buyer language is quite literally how the audit phrases the queries we test.
→ Validate Two severity calls to confirm: is evidence skepticism genuinely as high-severity as fear of brain injury — because if buyers demand proof before they'll even consider you, we front-load evidence-and-certification queries rather than fear-and-protection ones. And is program duty-of-care / liability (medium confidence, inferred) actually a top-tier pain, or B2B noise? Missing pains we'd expect in this category: return/refund friction on a hygiene product, shipping/turnaround before the season starts, and youth-vs-adult sizing uncertainty. Do any of these come up in your reviews or support tickets?
The technical state of neuroguardplus.com as AI crawlers see it — three diagnostic findings and three items your engineering team should verify by hand before the call.
Engineering — Verify & Fix Good news first: robots.txt is confirmed open — GPTBot, ClaudeBot, PerplexityBot, and Google-Extended can all reach the site, so nothing is blocked at the door. The one high-severity issue is that your core evidence is off-page — seven studies live behind Google Drive links and the "The Proof" page has almost no extractable text — so engineering and content should start there. Two medium structural items (stale evergreen commercial pages and broken heading hierarchy) round out the diagnostic set. These are technical fixes only — content priorities come later, once the audit shows which gaps actually cost citations.
What we found: The primary evidence page (/pages/data-research) lists seven studies only as links to Google Drive documents rather than on-page text, and the top-nav "The Proof" page (/pages/sports) is a testimonial/video showcase with roughly 150 words of extractable text (content_depth 0.10). The actual research data an AI would need to cite lives off-domain in Drive PDFs or inside videos, neither of which is reliably crawlable or attributable to neuroguardplus.com.
Why it matters: Clinical evidence and credibility are the client's single biggest vulnerability (KG rates clinical_evidence "weak" and evidence_skepticism a high-severity pain point). When the supporting studies are locked in Google Drive and the "proof" page has no extractable prose, AI assistants answering "is there proof mouthguards reduce concussions" cannot pull citable claims from the client's own domain — even though the client has written strong, well-cited evidence content elsewhere (e.g. /pages/mouthguard-concussion-research). The two pages explicitly built to carry the evidence are the two that surrender it.
Recommended fix: Transcribe each linked study's key finding (sample size, effect size, citation) into on-page HTML text on /pages/data-research, and rebuild /pages/sports ("The Proof") with extractable text summaries beside each testimonial video (athlete, sport, outcome). Cross-link both to the existing evidence-map article.
What we found: While the blog and comparison library is uniformly fresh (updated within ~30 days), several evergreen commercial pages carry old sitemap lastmod dates: /pages/how-it-works (2024-11-22, ~20 months), /pages/cheerleading (2025-02-17, ~17 months), /pages/fitting (2025-09-30, ~10 months), and /pages/stay-in-the-game (2026-02-11, ~5 months). "How It Works" is a primary-nav mechanism explainer central to the concussion/performance claim.
Why it matters: AI assistants disproportionately cite recently-updated content (Ahrefs: AI-cited pages average ~25.7% fresher than typical results; ConvertMate: ~76% of ChatGPT's most-cited pages were updated within 30 days). The fresh blog content protects most query categories, but the stalest pages are core evergreen explainers a buyer or model lands on first, and their staleness signals weaker content hygiene for exactly the mechanism claims competitors could contest.
Recommended fix: Refresh the mechanism/how-it-works and fitting pages with current claims and a visible "last updated" date, aligning their evidence language to the newer cited articles; retire or consolidate the thin /pages/stay-in-the-game landing page.
What we found: Several commercial pages break heading semantics: /pages/how-it-works uses H3 for its main section titles while H2 is reserved for step labels (inverted nesting) and appears to have no H1; the Team Order product page renders two H1s ("Team Order" and "Order 20. Get 5 free."); and product/landing pages such as /products/neuroguard-cheerleading and /pages/cheerleading repeat the identical heading "Lightweight Design, Heavyweight Protection". The comparison and blog library, by contrast, has clean single-H1 hierarchies.
Why it matters: Headings are the passage labels LLMs use to segment and extract citable answers. Inverted nesting, missing H1s, and duplicated headings make it harder for a model to attribute a self-contained claim to the right section, lowering the odds these commercial pages are cited even when the underlying copy is relevant.
Recommended fix: Enforce one descriptive H1 per page and logical H2→H3 nesting in the Shopify theme templates for product and page types; replace duplicated/stylistic headings with unique, noun-phrase section titles.
The following items could not be assessed through our analysis method (rendered markdown). We recommend your engineering team verify these manually before the validation call.
What to check: Our method fetches rendered markdown, so JSON-LD schema blocks are not visible and cannot be confirmed. Shopify typically emits Product and Organization schema, but the site's highest-value AI assets — dozens of FAQ sections across comparison and buyer-guide pages, and long-form Article pages under /pages/ — may not carry FAQPage or Article schema.
Recommended action: Verify current schema with Google's Rich Results Test / a structured-data validator (or Screaming Frog). Add FAQPage schema to every page with a real FAQ block and Article schema (with datePublished/dateModified) to the /pages/ long-form guides.
What to check: web_fetch returns rendered markdown and cannot confirm whether content is server-rendered or injected via JavaScript. Most pages returned substantial text (consistent with Shopify server rendering), but a few image/video-heavy pages returned very little extractable text: /pages/sports, /pages/stay-in-the-game, and /blogs/news.
Recommended action: Load /pages/sports, /pages/stay-in-the-game, and /blogs/news with JavaScript disabled (or use Google's URL Inspection "view rendered HTML") to confirm body content is present in the initial HTML response.
What to check: Meta descriptions, canonical tags, meta-robots directives, and Open Graph/Twitter card tags are not present in rendered markdown and therefore could not be evaluated for any page in this analysis.
Recommended action: Spot-check meta descriptions and OG tags with a social-preview tool or view-source across product, comparison, and guide templates; ensure each page has a unique, descriptive meta description and complete OG tags.
Partial Signal Freshness could not be scored on 13 of 39 pages (8 product/commercial pages carry no detectable date), and schema markup could not be read at all by our method — so the freshness and schema numbers above rest on partial coverage. Both are on the Manual Verification Checklist; engineering should confirm them directly before we treat them as settled.
Why Now The window to establish GEO visibility in this category is open, and it won't stay that way:
• AI search adoption is accelerating — how parents and athletes discover protective gear is shifting quarter over quarter.
• Early citations compound: domains AI platforms learn to trust now get cited more often as they accumulate signal.
• Competitors who establish GEO visibility first create a structural disadvantage for late movers in the same answer space.
• The concussion-reduction mouthguard category is still early-innings in GEO — right now you're competing against inaction, not against entrenched strategies.
The full audit will measure exactly how NeuroGuard+ shows up when a real buyer asks an AI "is there a mouthguard that reduces concussions," "best mouthguard you can talk and breathe through," or "best mouthguard for a youth football team" — across the AI platforms we select. You'll see precisely which of those queries return SISU, Shock Doctor, or Q-Collar but not NeuroGuard+, and what it would take to appear in them. Fixing the off-page evidence and heading issues now lifts your baseline before we even start measuring — so you enter the audit with a fair shot at the citations that are up for grabs.
45–60 minutes. We walk through this document together and lock the inputs — channels, personas, competitor tiers, and the concussion-claim strength — that drive the query set.
We generate buyer queries from your validated personas, features, and pain points, then run them across the selected AI platforms to capture how each represents NeuroGuard+.
Visibility analysis, competitive positioning across your consideration set, and a three-layer action plan — technical, content, and authority — prioritized by which gaps actually cost you citations.
Start Now Three technical fixes your engineering team can begin before the call: (1) transcribe the Drive-locked studies into on-page HTML on /pages/data-research and rebuild "The Proof" page with extractable text; (2) fix the inverted and duplicated heading hierarchy in the Shopify product/page templates (one descriptive H1 per page, logical H2→H3 nesting); and (3) verify FAQPage/Article schema with Google's Rich Results Test and add it where your FAQ and long-form guide pages are missing it. These don't depend on the rest of the audit and will improve your baseline visibility before we even measure it. robots.txt is already confirmed open to AI crawlers, so there's nothing to fix there — but a quick re-check after any theme change is cheap insurance.
Two jobs before we meet. The questions on the left require your judgment — no one knows your business better than you. The engineering tasks on the right don't require the call at all.