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 Spectrum Roadmap'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 neurodiversity inclusive-hiring training space, these three signals tell us whether AI crawlers can reach, read, and trust spectrumroadmap.com. They're a baseline, not the audit — but they orient everything that follows.
AI search is reshaping how HR and people leaders find and evaluate solutions in the neurodiversity inclusive-hiring and workplace inclusion training category — self-paced manager training, toolkits, and 1:1 coaching that help teams find, hire, accommodate, and retain neurodivergent employees. When a buyer asks an assistant which programs to consider, the answer is assembled from whatever the model has already learned to trust. As a founder-led, startup-stage challenger, Spectrum Roadmap has a real first-mover opening: the companies that establish AI visibility now lock in citations that compound before larger, better-funded names treat this channel as a priority.
This Foundation Review presents three things we need you to validate before the audit runs: the competitive set that shapes how we construct head-to-head queries, the buyer personas that determine which search intents we test, and the Layer 1 technical baseline that determines whether AI platforms can access your content at all. Each section exists because a downstream step of the audit consumes it. The goal of this document is alignment — confirming we're modeling your real market before we spend the audit measuring it.
The validation call is a working session with real stakes. It resolves two kinds of decisions: input validation — are the right buyers, competitors, and capabilities in the right tiers? — and engineering triage — which technical fixes can your team start before results come back? A wrong answer on either propagates through the entire audit, so the call is where we lock the inputs that everything downstream depends on. The checklist near the end of this document is everything you need to prepare.
Purpose This is the foundation for your GEO audit. We've modeled the neurodiversity inclusive-hiring training market the way an AI assistant sees it — your buyers, your competitors, your capabilities, and the technical state of your site. Validating these inputs now is what makes the audit's findings trustworthy later.
Your Job Read each section and tell us what's right, wrong, or missing. The italic purple questions throughout are the highest-value moments — each one names a specific decision where your answer changes how we build the audit. Bring those answers to the validation call.
Confidence Badges Every entity carries a confidence badge. High means we sourced it directly from your site or category listings. Medium means we inferred it and want you to confirm. Low means it's a candidate we're least sure about. Focus your attention on medium and low items.
→ Your three products split across two very different buyers — HR teams buying Essential Training and Premium Roadmap + Coaching, versus individuals and families buying Community Membership. Should the audit model one employer-focused query cluster, or two? If both motions matter to the business, we add a separate consumer-intent cluster and the persona set needs a B2C buyer — if only the employer side matters for this audit, we drop the community-membership intent entirely.
5 personas — 1 decision-maker, 2 evaluators, 2 influencers. These drive the audit's query set: each persona searches differently, so each shapes a distinct slice of the buyer queries we test.
Critical Review Area Personas are the input most worth your scrutiny. If we've mislabeled who holds budget authority or who initiates the conversation, the query set will target the wrong search intents. Read each role description and influence label against how purchases actually happen in your real deals.
Data Sourcing Note Role, department, seniority, influence, veto power, and technical level come straight from the knowledge graph. Three personas (Danielle, Sofia, Priya) were sourced from your site and category signals (High); two (Marcus, Greg) were inferred (Medium). The "buying jobs" and "query focus areas" rows are synthesized — our read of how each role would search — and are exactly what we want you to confirm or correct.
→ We inferred Marcus holds the budget veto — but does a startup-segment buyer this small actually route training spend through a CPO, or does the HR Director sign the check? If the Director is the real economic buyer, we demote Marcus and shift validation-stage queries onto practical implementation criteria rather than C-suite ROI framing.
→ If Danielle is the actual economic buyer in your SMB deals rather than just the evaluator, we promote her to decision-maker and weight the query set toward her "can we actually implement this" criteria over executive ROI language. Which one signs — Danielle or Marcus?
→ Does a dedicated DEI/Belonging Lead actually exist in your typical buyer's org, or is neurodiversity owned directly by HR at your startup/SMB segment? If DEI is folded into HR, Sofia overlaps Danielle and we merge their query clusters instead of testing two distinct intents.
→ Does Talent Acquisition initiate the neurodiversity-hiring conversation, or only execute once leadership has decided? If TA is the entry point, we add a top-of-funnel sourcing query cluster ("where to find neurodivergent candidates") in Priya's voice; if they only execute, we keep her queries downstream.
→ We inferred line managers like Greg participate in the purchase — but do individual managers ever evaluate vendors, or only consume the training after HR buys? If they don't influence the purchase, we drop manager-as-buyer queries and treat his pain only as a content target, not a search-intent cluster.
Missing personas? These roles sometimes appear in neurodiversity inclusive-hiring deals — do they show up in yours? Legal / HR Compliance counsel (if disclosure and ADA accommodation risk is a distinct buying conversation, given the legal-fear pain point below); Fractional / external HR or DEI consultant (small companies often buy through an outside advisor rather than an internal team); Disability ERG or employee-resource-group leader (if employee advocates drive the request upward). Each could warrant its own query cluster. Who else shows up when you actually sell?
6 primary + 4 secondary competitors identified. Tier assignments decide which vendors we test head-to-head versus which we treat as category context.
Why Tiers Matter Primary competitors become direct-comparison matchups — queries like "Spectrum Roadmap vs. [competitor]" and "best neurodiversity manager training for HR teams." With 6 primaries, that's roughly 36–48 head-to-head queries. Three of those primaries carry only medium confidence — Cognassist (UK/enterprise-oriented), NeuroTalent Works (consultative nonprofit), and Neuro Sparks Solutions (closest self-paced match). If any of them rarely appear in your actual deals, moving them to secondary pulls roughly 6–8 queries each out of the head-to-head set.
→ Three questions on the competitive set: (1) Who's missing? No "vs" or comparison pages exist on your site, so this list came from category searches — which vendor actually comes up most when a prospect compares you? (2) Tier accuracy: Cognassist, NeuroTalent Works, and Neuro Sparks sit in the primary tier on medium confidence — do all three genuinely appear in your US SMB deals, or are Cognassist/Praxis42 (both UK/enterprise) really category noise? (3) Anyone irrelevant? Specialisterne and auticon operate at enterprise/staffing scale — do your buyers ever actually weigh them against you, or should they drop out entirely?
11 buyer-level capabilities mapped. These determine which capability queries the audit tests — and the strength ratings shape where we expect you to win or lose head-to-head.
Fix an interview process that screens out great neurodivergent candidates — alternative formats, structured questions, and interview question banks.
Get our managers a real training course on how to lead, communicate with, and evaluate neurodivergent team members.
Practical, low-cost accommodation strategies and workplace modifications we can actually implement — plus accommodation request forms.
Keep the neurodivergent talent we hire — onboarding checklists, performance evaluation guidance, and conflict resolution.
Give me job description templates, interview rubrics, and forms I can use today instead of building everything from scratch.
We need someone experienced to coach us through actually rolling this out, not just a video library.
Help the whole team understand neurodiversity, not just managers — interactive workshops for all employees.
A private community where neurodivergent professionals, parents, and advocates can get peer support and expert access.
Help me prove the business case and ROI of neurodiversity hiring to get budget approved.
We want a recognized neuroinclusive-workplace certification or accredited credential we can show externally.
We need SCORM-compliant content that drops into our LMS and scales across thousands of employees and multiple sites.
Prioritization Question Seven capabilities are rated Strong. The audit tests all 11, but competitive-differentiation queries will emphasize about 3. Which of these seven best represents where Spectrum Roadmap actually wins deals against the primary set?
→ Three checks on the taxonomy: (1) Strength accuracy vs. named rivals: we rated Formal Certification & Accreditation weak and LMS Integration & Enterprise Rollout absent because IBCCES, Cognassist, and Praxis42 lead there — is that right, or do you offer a credential/SCORM path we missed? If you do, those move up and change the defensive queries. (2) Missing capabilities: is there a buyer-level capability your prospects ask about that isn't on this list? (3) Merge candidates: do Employee Education & Awareness Workshops and Manager Training & Enablement read as one capability or two distinct ones to your buyers?
10 pain points — 5 high, 5 medium severity. The buyer language here is literally how the audit phrases queries, so the wording matters as much as the ranking.
→ Three checks on the pain set: (1) Severity: "Fear of legal/compliance missteps" is rated high but was inferred (medium confidence) — is fear of an ADA/disclosure misstep really a top-tier driver in your deals, or a secondary worry? It changes whether we lead with risk-framed queries. (2) Buyer language: does the wording above sound like your buyers, or is it too polished — the exact phrasing becomes the query text. (3) Missing pains: these sometimes surface in this category — fear of tokenism or employee backlash ("are we just checking a box"), scaling a program across multiple sites/locations, or measuring whether the program actually worked. Do any of those come up?
A technical read of 38 pages on how easily AI crawlers can access, parse, and cite your content. These are the engineering fixes your team can act on now — content recommendations come later, with the full audit's query data.
For Engineering — Verify & Refine The good news first: there are no critical or high-severity blockers. robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, and Google-Extended, all 38 pages render server-side, and freshness is healthy. The work is medium-severity structural cleanup — fixing broken heading hierarchy on the product and booking pages, expanding thin content on the two paid product pages, and resolving near-duplicate mission pages — plus two items engineering should verify directly (JSON-LD schema and meta/OG tags, which our markdown-based fetch can't read).
What we found: Several commercially important pages don't use a single descriptive H1 with nested H2/H3. /pages/schedule and /pages/community-group each render three full marketing sentences as stacked H1s; /pages/spectrum-strategies uses multiple sentence-length H1s with no H2 layer; the /products/essential-training and /products/premium-spectrum-roadmap-coaching pages flatten body and footer labels (e.g. "Navigation", "Contact") into H2/H3; /products/community stacks multiple emotional headlines as H1; /pages/about uses emoji-only H2s.
Why it matters: AI crawlers use heading structure to segment a page into citable passages and to infer what each section answers. Multiple H1s and sentence-as-heading patterns collapse that structure, so the highest-intent commercial pages (the two paid product pages and the booking page) are harder for an LLM to excerpt and attribute than the well-structured /pages/* guide cluster.
Recommended fix: Give each page one descriptive H1 naming the page's subject, demote marketing sentences to body copy, and use a logical H2→H3 hierarchy with noun-phrase headings. Remove footer navigation labels from the heading outline on the product templates.
What we found: The two revenue pages return very little substantive body text. /products/premium-spectrum-roadmap-coaching (content depth 0.40) has a single H2 and a short benefit paragraph; /products/essential-training (content depth 0.50) lists 9–11 module titles with one line each and no sample content. Both currently display "sold out." They render server-side (no CSR failure) — the text is simply sparse.
Why it matters: These are the pages an AI assistant would cite to describe what Spectrum Roadmap actually sells, what it costs, and what's included. With only module titles and slogans present, an LLM can't extract a defensible, specific answer about the offering and will fall back to competitors' richer product descriptions.
Recommended fix: Expand each product page with self-contained passages: who it's for, what's inside each module (2–3 sentences), outcomes, format/time commitment, price, and an FAQ. Keep claims specific and citable rather than aspirational.
What we found: /pages/schedule and /pages/community-group render essentially identical content — the same three mission sentences as H1s plus the same Debra Solomon founder bio — despite different URLs and page purposes (booking vs. community).
Why it matters: Duplicate or near-duplicate bodies on distinct URLs split ranking and citation signals between the two pages and can lead crawlers to pick the "wrong" canonical, so neither page accumulates authority for its intended intent.
Recommended fix: Differentiate the two pages so each has unique, purpose-specific content (a real scheduling/booking flow on /pages/schedule; community value, format, and join path on /pages/community-group), or consolidate and 301-redirect one to the other and set canonical tags accordingly.
What we found: The /blogs/blog/* sitemap contains ~190 legacy "Spectrum Strategies"-era posts, the large majority dating from 2015–2020 and oriented to individuals/families and life-coaching (camp recaps, book-of-the-month, college tips) rather than the current employer/HR audience. Only a handful are employer-relevant. All carry a sitemap lastmod of 2025-09-25 (the migration date), not genuine recent updates.
Why it matters: A large volume of stale, off-audience posts dilutes the site's topical signal around employer neurodiversity hiring and competes internally with the fresh, high-quality /pages/* guide cluster for crawl attention and topical association.
Recommended fix: Audit the legacy corpus: keep and refresh the employer-relevant posts (consolidating into the new guide cluster where overlap exists), and prune, consolidate, or noindex the off-audience individual/family life-coaching posts. Do this as a deliberate content-hygiene pass, not a bulk delete.
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 reads rendered markdown via web_fetch, which strips JSON-LD, so we couldn't confirm whether Product schema is present on product pages, FAQPage schema on the FAQ and guide-page FAQ sections, Article schema on guides, or Organization schema sitewide. (An /agents.md commerce file and an agentic-discovery sitemap suggest the Shopify theme may emit Product/Organization schema, but this was not verified.)
Recommended action: Validate each template with Google's Rich Results Test / the Schema.org validator. Ensure Product+Offer on product pages, FAQPage on every page with a Q&A block, Article (with datePublished/dateModified and author) on guides, and Organization sitewide.
What to check: Meta description and Open Graph/Twitter card tags aren't visible in rendered markdown and couldn't be assessed from our fetch method.
Recommended action: Spot-check page source or use a social-preview/SEO tool to confirm each commercial page has a unique, specific meta description and complete OG tags (title, description, image, url).
What to check: All 38 fetched pages returned substantive server-rendered text with no obvious client-side-rendering failure. Because web_fetch can't fully simulate a JS-disabled crawler, confirm that no critical content (e.g. embedded video transcripts, dynamically loaded module lists) depends on JavaScript.
Recommended action: Load key pages with JavaScript disabled (or use Screaming Frog / a crawler in HTML-only mode) and confirm body content, headings, and product details are present in the raw HTML.
Partial Sample This analysis covered 38 pages — the current commercial pages and guide cluster — not the full site, which also carries ~190 legacy blog posts. Treat scores as representative of your active commercial content, not the entire domain. Schema coverage couldn't be scored at all (all 38 pages unscored) because our fetch method strips JSON-LD; engineering should verify it directly.
Why Now The neurodiversity inclusive-hiring training category is still early-innings in GEO — and that's the opening.
The full audit will measure citation visibility across real buyer queries in the neurodiversity inclusive-hiring space — from "best neurodiversity training for HR teams" and "how to make our interview process inclusive for neurodivergent candidates" to "neurodiversity manager training course" and head-to-head comparisons against your primary set. You'll see exactly which queries return answers that include your competitors but not Spectrum Roadmap — and what it would take to appear in them. Fixing the medium-severity structural items now (heading hierarchy, thin product pages, duplicate mission pages) strengthens your baseline before we even start measuring.
45–60 minutes. We walk through this document together and lock the inputs — personas, competitor tiers, feature priorities, and the single vs. dual buyer-motion question.
We generate buyer queries from the validated inputs and run them 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 intentionally hold back until query data tells us what actually costs you citations.
Start Now — Engineering Three technical items don't depend on the rest of the audit and will improve your baseline visibility before we even measure it: (1) fix the broken heading hierarchy on the product and booking pages — one descriptive H1 each, a logical H2→H3 outline, footer labels removed from the heading structure; (2) validate JSON-LD schema coverage with Google's Rich Results Test (Product/Offer, FAQPage, Article, Organization), since our fetch couldn't read it; and (3) resolve the near-duplicate mission pages (/pages/schedule and /pages/community-group) by differentiating or 301-redirecting and setting canonicals. Crawler access is already confirmed open — no robots.txt action needed.
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.