AI search is reshaping how buyers find and vet a performance and concussion-reduction mouthguard — and the brands that establish visibility now lock in an advantage before the category catches on. 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 how often AI assistants cite NeuroGuard+ in performance-mouthguard answers, these three signals tell us whether AI crawlers can reach your site, trust its freshness, and parse what's there. They anchor everything below.
Allow: /. The sitemap is accessible. One caveat for engineering (detailed in Site Findings): the product child-sitemap reports identical auto-generated lastmod dates — but crawler access itself is unobstructed.AI search is changing how parents, athletes, and team programs discover and vet a performance and concussion-reduction mouthguard. A buyer who once typed a query into Google and skimmed ten blue links now asks an assistant "what's the best mouthguard to prevent concussions?" and reads one synthesized answer — and the brands named in that answer compound their lead, because AI platforms learn to trust the domains they already cite. NeuroGuard+ is a startup-stage challenger entering this shift early, which is exactly when visibility is cheapest to win.
This Foundation Review presents three inputs we need you to validate before the audit runs: the competitive set that shapes which head-to-head queries we test, the buyer personas that determine the search intent behind every query, and the technical baseline that determines whether AI platforms can access and trust your content in the first place. Each section is something we're confirming together — the audit is only as accurate as the inputs below.
The validation call is a working session with real stakes. Two kinds of decisions get made there: input validation — are the right buyers, competitors, and capability ratings in the right places? — and engineering triage — which technical fixes can start immediately, before any results come back? Your answers set the architecture of the query set; the specific items are aggregated in the Pre-Call Checklist near the end of this document.
What this is This Engagement Foundation Review presents what we've learned about NeuroGuard+'s market — the performance and concussion-reduction mouthguard category — before we run the GEO audit. It's the knowledge graph that will drive every buyer query we test across AI platforms.
What we need from you Validate the inputs. Tell us what we got right, what we got wrong, and what we missed. The accuracy of the audit depends on the accuracy of what's below — a wrong competitor tier or a misjudged persona role changes which queries we run and how we read the results.
Confidence badges Each item carries a confidence level. High = sourced directly from your site or customer reviews. Medium = inferred from category patterns or a single source. Low = a starting hypothesis we most need you to confirm. Spend your time on the Medium and Low items — those are where your answer moves the audit most.
→ NeuroGuard+ runs three buying motions at once — DTC to parents and athletes, bulk team orders to programs, and a wholesale retail program. Do all three drive real revenue today, or is one (likely retail wholesale) still aspirational? Each live channel becomes its own query cluster with its own buyer language; if a channel isn't real yet, we reallocate those queries to DTC and team-program intent rather than splitting the audit three ways.
5 personas, all modeled as decision-makers — each can independently drive or veto a purchase in their channel (DTC, team program, or retail). These personas determine the search intent behind every query we run.
Critical review area This is the input most worth your scrutiny. If a persona's role, authority, or channel is wrong, every query built on that intent is aimed at the wrong buyer. Two of these five — the Athletic Trainer and Athletic Director — are inferred rather than sourced, because no review-platform data exists for a consumer product. Confirm they reflect how you actually sell.
Data sourcing note Names, roles, departments, seniority, veto power and technical level are pulled from the knowledge graph (site scrape, review mining, or inference — see each card's source tag). The buying-jobs and query-focus lines are synthesized by us from those fields to show how each persona would search — they're our read, not your data, so they're fair game to correct.
→ For a youth purchase, does Melissa make the final call — or does the kid's refusal-to-wear effectively veto it? If athlete rejection is the real gate, comfort and lower-teeth "talk & breathe" queries should outweigh concussion-safety queries in the DTC set, not the other way around.
→ Darnell spans combat, strength, and contact sports — do those buy the same way? If the combat athlete searches on concussion protection while the strength athlete searches on jaw-alignment performance, this is really two query clusters, and we should split the athlete intent rather than test one blended set.
→ Priya is inferred, not sourced — does an ATC actually specify mouthguards for a program, or only advise the Athletic Director who holds the budget? If she's advisory rather than a decision-maker, her clinical-evidence queries fold into the AD's evaluation cluster instead of standing as their own.
→ Ray is also inferred — is a team mouthguard a real budget line an Athletic Director approves, or does this decision actually sit with a head coach or booster fund? If team programs aren't a live purchasing motion, the entire team-bulk query cluster shrinks and we shift weight to DTC.
→ Beyond whether wholesale is a live channel (the company-profile question), Jordan carries a contradiction: medium individual influence but full veto. Is the retail buyer a true sole decision-maker, or a gatekeeper recommending into a committee? If it's a committee, retail queries should target collective criteria (margin, return rate, planogram fit), not one buyer's taste.
Who else shows up? These roles sometimes appear in performance-mouthguard and team-safety deals — do they show up in yours? (1) Equipment / Gear Manager — often the person who actually places and reorders team gear, distinct from the AD who approves the budget. (2) School-District Risk / Procurement Officer — if concussion-liability purchasing routes through district procurement rather than the individual program. (3) Dentist / Orthodontist as referrer — the trusted voice braces-and-custom-fit buyers ask before they buy. Who else is in the room when a purchase happens?
5 primary + 4 secondary competitors. Tier assignments decide which brands get head-to-head testing in the audit — and which AI answers we watch most closely.
Why tiers matter Each primary competitor draws roughly 6–8 head-to-head queries, so these five primaries generate about 30–40 of the audit's most competitive queries (e.g., "NeuroGuard+ vs. Shock Doctor," "best performance mouthguard for concussion protection"). Three primaries sit at medium confidence — Under Armour Performance Mouthwear, Zone, and OPRO — so their tier placement is worth a second look at the call. (PowerPlus is no longer listed here: you've confirmed it's the legacy name for NeuroGuard+ itself, not a rival, so it now lives in your brand's name variants.)
→ Two things to confirm: (1) The concussion-wearable adjacencies — do Q-Collar and Guardian Caps actually surface when your buyers deliberate, or should they drop out of the safety-budget comparison set (and free up secondary-tier queries)? (2) Anyone missing — is a cross-shopped brand we didn't list (Battle, Venum, SafeJawz) showing up in your deals?
11 buyer-level capabilities — 5 strong, 4 moderate, 2 weak. These determine which capability queries the audit tests and where NeuroGuard+ is positioned to win or lose them.
A mouthguard that actually lowers the G-forces to my head and protects my (or my kid's) brain from concussions.
Aligns my jaw so I get more strength, balance, power, and endurance when I compete.
Sits on my bottom teeth so I can talk to my coach and breathe normally without spitting it out.
Thin and comfortable enough that I forget it's in and can still breathe hard during play.
Works whether I'm playing football, hockey, boxing, lifting, cheer, or bull riding.
Molds to my exact bite so it stays put — without paying for a dentist-made guard.
Fits over my braces and still protects my teeth and mouth.
Worth ~$50 versus a $25 boil-and-bite or a $150 dentist-made guard.
I can outfit my whole roster with the right sizes and reorders without a fitting nightmare.
Show me the peer-reviewed studies that prove this really reduces concussions and isn't just marketing.
Do real teams, pros, and trainers I recognize actually use and trust this brand?
Which strengths do we lean on? The audit tests all 11 capabilities, but competitive-differentiation queries will emphasize three. Five are currently rated Strong:
• Concussion / Brain-Injury Risk Reduction
• Neuromuscular Jaw Alignment for Performance
• Lower-Teeth Design (Talk & Breathe)
• Comfort, Low Bulk & Breathability
• Multi-Sport Versatility
Which three best represent where NeuroGuard+ actually wins deals — the capabilities buyers choose you for, not just ones you do well? Your answer sets which three we overweight in the head-to-head set.
→ (1) Clinical Evidence & Research Credibility is rated weak — we found field studies of 4,000–7,000 athletes and testimonials, but no linked peer-reviewed concussion study, no FDA clearance, and no Virginia Tech rating. Is that accurate? If real independent proof exists, this flips from your single biggest vulnerability into a head-to-head strength against FDA-cleared Q-Collar — and changes how we test every "does it actually work" query. (2) Are the five Strong ratings right against specific rivals — is your jaw-alignment performance genuinely stronger than Zone's MORA claim? (3) Should any capabilities merge — do Lower-Teeth Design and Comfort/Breathability read as one buyer benefit rather than two?
10 pain points — 4 high, 6 medium severity. The buyer language here is literally how we'll phrase queries, so the wording matters as much as the list.
→ Two of the four High-severity pains — claims skepticism and program liability pressure — are inferred, and both hinge on the same evidence gap flagged in Features. Are those severities right, and is the buyer language how your customers actually talk? And which category-specific pains are we missing — hygiene/odor and cleaning ("it gets gross and smells after a few weeks"), losing and replacing guards ("he loses one every season, so cost-per-replacement matters"), or league/referee legality and color rules ("our league won't allow a clear or dark guard")? Each missing pain is a query cluster we wouldn't otherwise test.
These are the technical findings from our crawl — the things that determine whether AI platforms can access and cleanly cite your content. Engineering and Content can start on these before the validation call.
Start here — Engineering & Content None of these depend on the audit results, so the team can begin now. There are no critical blockers: robots.txt is clean and every major AI crawler (GPTBot, ClaudeBot, PerplexityBot) is explicitly allowed. The one high-severity item is freshness — your core product-mechanism pages (/pages/how-it-works, /pages/fitting) are stale while your editorial hub is current. The rest are medium-severity structure issues: thin shell pages with little extractable text, multiple-H1 headings on product templates, and uninformative product-sitemap dates. Three more items need manual verification because our rendered-markdown method couldn't assess them.
What we found: Several high-value, commercially central pages carry sitemap lastmod dates far outside the dominant AI-citation freshness window: /pages/how-it-works (last modified 2024-11-22, ~19 months old), /pages/sports (2025-02-19) and /pages/cheerleading (2025-02-17, both >365 days), and /pages/fitting (2025-09-30, ~9 months). This contrasts sharply with the /pages/ editorial hub (comparisons and buyer's guides), most of which were updated within the last 30–90 days. The product pages themselves carry no usable freshness signal at all — every /products/* URL reports an identical lastmod equal to the crawl time.
Why it matters: AI assistants concentrate citations on recently-updated content (Ahrefs found AI-cited pages are ~25.7% fresher on average; ConvertMate found 76.4% of ChatGPT's most-cited pages were updated within 30 days). The "how it works" page is the canonical explanation of the product's core mechanism — exactly the passage an assistant would cite to answer "how does NeuroGuard+ work" — yet it is the stalest commercial page on the site. The freshness the brand built in its content hub does not extend to the pages that actually describe and sell the product.
Recommended fix: Refresh /pages/how-it-works, /pages/fitting, /pages/sports, and /pages/cheerleading with a current "last updated" date and a substantive content pass, prioritizing how-it-works. Ensure the storefront theme exposes a real content-modified date (not just the Shopify product-sync timestamp) so crawlers can distinguish genuine updates.
What we found: Three internally-linked, sitemap-listed pages render with almost no body text: /pages/sports (~50–75 words, testimonial-video thumbnails only), /pages/stay-in-the-game (~80–100 words, image carousel only), and /pages/coach-kelly-interview (~50 words, image-only shell with no interview transcript despite the title promising one). Two product pages are also thin: /products/the-powerplus-elite-mouthguard-white (~280 words) and /products/max-professional-neuroguardplus (~450 words, mostly positioning). Content-depth scores for these pages fall to 0.2–0.4.
Why it matters: Pages with little extractable text give AI crawlers nothing to cite and can dilute the site's overall quality signal. The "Coach Kelly Clark Interview" page is the clearest example — it's indexed and linked as social proof but contains no quotes, outcomes, or transcript an assistant could surface for a "who trusts NeuroGuard+" query. These pages occupy prime brand-trust real estate while contributing nothing to AI visibility.
Recommended fix: Either build out these pages with real transcribed text (interview Q&A, named-athlete outcomes, sport-by-sport proof) or, where a page won't carry text, add a substantive text layer alongside the media. If a page is genuinely not meant to rank, consider removing it from the sitemap to avoid diluting crawl quality.
What we found: Core storefront pages have heading structures that work against passage extraction. /products/neuroguardplus renders two H1s ("NeuroGuard+ (Case Included)" and "Why Every Athlete Needs NeuroGuard+"). /pages/about-us and /pages/data-research use full marketing sentences as H2s (e.g., "Scientific studies consistently demonstrate that maintaining physiological jaw alignment reduces risk of concussion.") and the rendered H1s carry stray markdown artifacts ("> About Us"). Several product pages use sentence-fragments as section headings. The /pages/ hub articles, by contrast, use clean single-H1, descriptive-H2 structures.
Why it matters: LLMs use heading structure to segment a page into citable passages; a single descriptive H1 plus noun-phrase H2s lets a model lift a self-contained answer. Multiple H1s and sentence-as-heading patterns blur that structure and make the storefront pages harder to excerpt cleanly than the brand's own hub content.
Recommended fix: Enforce one H1 per page on product and brand templates, and convert sentence-style section headings into descriptive noun phrases (e.g., "Why jaw alignment matters" rather than a full assertion). Strip the stray markdown characters leaking into rendered headings on /pages/about-us and /pages/data-research.
What we found: Every URL in the products child sitemap reports the same lastmod (2026-06-22T13:29:46, equal to the crawl time). This is a Shopify behavior where the product sitemap timestamp tracks catalog/sync state rather than content edits, so all product pages appear to have changed simultaneously and continuously. The sitemap index itself contains no lastmod values.
Why it matters: When every product page claims to have just changed, the lastmod signal becomes noise: crawlers cannot tell which product content genuinely changed, and the freshness advantage the brand earns on its dated hub articles does not transfer to the commercial pages. It also means product pages cannot be credited with any real recency in freshness scoring (they were scored null in the inventory).
Recommended fix: Where the theme/platform allows, surface a real content-modified date on product pages (visible "last updated" text and/or accurate lastmod) so meaningful product updates are distinguishable from routine catalog syncs. At minimum, add visible update dates to the highest-value product pages.
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 analysis captures rendered markdown, not raw HTML, so we can't distinguish content hidden behind client-side rendering from content that simply doesn't exist. /pages/sports, /pages/stay-in-the-game, and /pages/coach-kelly-interview returned very little text (heavy image/video galleries). Text may be present that didn't surface in the rendered fetch — or the pages may be genuinely thin.
Recommended action: Load these pages with JavaScript disabled (or use a server-rendered fetch / view-source / Screaming Frog) to confirm what text is in the initial HTML. If content is CSR-only, ensure it's server-rendered or pre-rendered for crawlers; if the pages are genuinely thin, route them to the content build-out above.
What to check: Because our method reads rendered markdown rather than raw HTML, JSON-LD structured data is not visible in our capture; all schema_coverage scores are null. As a Shopify storefront the site likely auto-emits some Organization/Product schema, but the presence and completeness of the most specific applicable types (Product on product pages, FAQPage on /pages/faq and article FAQ sections, Article on the hub guides) is unconfirmed.
Recommended action: Validate each template with Google's Rich Results Test / Schema.org validator. Confirm Product schema on product pages, add FAQPage schema to /pages/faq and to article FAQ blocks, and add Article schema (with datePublished/dateModified matching the visible "last updated" dates) to the hub guides.
What to check: Meta descriptions, Open Graph tags, and canonical tags are not visible in rendered-markdown capture, so they're recorded as non-assessable across the inventory. We can't confirm whether they're present or well-formed. The note that /pages/custom-fit-mouthguards appears to redirect to /pages/custom-vs-boil-and-bite-mouthguards makes canonical verification worthwhile to avoid duplicate-URL ambiguity.
Recommended action: Spot-check meta descriptions, OG tags, and canonical URLs via view-source or an SEO crawler. Confirm canonicals resolve to a single URL per page and that redirecting slugs (e.g., custom-fit-mouthguards) point cleanly to their canonical target.
Partial-assessment note Two metrics are limited by method, not by your site: schema coverage couldn't be scored on any of the 36 pages (our crawl reads rendered markdown, not raw HTML, so JSON-LD is invisible to it), and 10 pages carry no detectable freshness date — 6 of them product pages on the Shopify catalog-sync timestamp. Both are flagged in the Manual Verification Checklist above; treat their scores as "unverified," not "failing."
Why now The window to win AI visibility in this category is open, and it won't stay that way:
• AI search adoption is accelerating — buyers are shifting from "search and skim ten links" to "ask and read one answer," quarter over quarter.
• Early citations compound: the domains AI platforms learn to trust now get cited more often as that behavior reinforces itself.
• Competitors who establish GEO visibility first create a structural disadvantage for everyone who moves later.
• Performance-mouthguard and concussion-safety GEO is still early innings — acting now means competing against inaction, not against entrenched strategies.
Once the inputs above are validated, the full audit measures how often AI assistants cite NeuroGuard+ across the queries your buyers actually run — "best mouthguard to prevent concussions," "performance mouthguard you can talk and breathe in," "NeuroGuard+ vs. Shock Doctor," "mouthguard that fits over braces." You'll see exactly which of those return your competitors but not NeuroGuard+, and what it would take to appear in them. Fixing the Layer 1 freshness and structure issues now means the audit measures an already-improved baseline rather than a handicapped one.
45–60 minutes. We walk through this document together and lock the inputs — competitors, personas, capability ratings, and the open channel and evidence questions.
We build the buyer query set from the validated knowledge graph and run it across the selected AI platforms, capturing who gets cited and who doesn't.
Visibility analysis, competitive positioning, and a prioritized three-layer action plan — including the content recommendations we deliberately hold until query data can rank them.
Start now — Engineering & Content Three Layer 1 fixes don't depend on the rest of the audit and will improve your baseline visibility before we even measure it: (1) Content refreshes /pages/how-it-works and /pages/fitting with real "last updated" dates and a content pass; (2) Engineering exposes a genuine content-modified date on product pages instead of the Shopify catalog-sync timestamp, and enforces one H1 per product/brand template; (3) Engineering verifies JSON-LD schema and confirms whether the thin pages are client-side rendered. robots.txt is already confirmed open to every major AI crawler, so no verification is needed there.
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.