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-hiring-training space, these three signals tell us whether AI crawlers can reach, render, and trust spectrumroadmap.com. They anchor every section that follows.
lastmod misrepresents the true 1–8-year age of ~360 legacy posts (see Site Findings).Allow: /; only utility paths (/admin, /cart, /checkout, /search) are blocked. Sitemaps are declared and accessible. One indexation caveat, not an access blocker: ~340 of ~360 indexed URLs are off-topic legacy consumer posts that dilute the site's topical signal (see Site Findings).AI search is reshaping how HR and People leaders discover and evaluate neurodiversity hiring training and coaching. Buyers increasingly open ChatGPT, Claude, or Perplexity at the very start of a search — asking them to name providers, compare self-guided programs against enterprise platforms, and surface right-sized options before any sales conversation happens. For a small, founder-led business like Spectrum Roadmap, that shift is an opening: establishing GEO visibility now locks in a first-mover advantage that compounds, because early citations become self-reinforcing as AI platforms learn to trust cited domains — and late movers compete against entrenched answers rather than empty space.
This Foundation Review covers three inputs the audit depends on. First, the competitive set — which providers appear alongside Spectrum Roadmap in the queries buyers actually run, and which tier each belongs in. Second, the buyer personas — who champions, who evaluates, and who signs, and therefore how queries should be phrased. Third, the technical baseline — whether AI crawlers can access, render, and extract citable passages from your site today. Content gap analysis and citation benchmarking come next, after the audit runs against the inputs you confirm here.
The validation call is a decision-making session. Two types of decisions need to happen: (1) input validation — confirming or correcting who your real buyer is, which competitors are true head-to-head rivals, and where your capabilities are genuinely strong versus exposed — and (2) engineering triage — agreeing which technical fixes start before the audit even begins. The pre-call checklist at the end of this document aggregates every decision in one place so nothing gets dropped.
lastmod on ~360 legacy posts so crawlers don't discount your genuinely fresh /pages/ guides as noise.llm_inference, low). If a technical hiring manager isn't actually in the buying group, we drop the high-technical persona and its jargon-heavy queries and reweight the audit toward HR and DEI language.Three things to know before you dig in: what this document is for, what you need to do with it, and how to read the confidence badges.
Purpose The Foundation Review validates the knowledge graph that drives the audit's query set — the competitors, personas, features, and pain points we'll use to probe AI platforms about neurodiversity hiring training and coaching for HR teams. Get these inputs right, and the full audit measures what actually matters. Get them wrong, and the audit produces clean data on the wrong questions.
Your Job Read every section. Flag anything you disagree with. The purple callouts (like this one) are the highest-value validation points — each names a specific uncertainty and explains what changes in the audit if your answer differs from our current read. Everything you flag gets resolved at the validation call before query execution begins.
Confidence Badges High means directly observed on your site, in reviews, or in category listings. Medium means inferred from category patterns or supported by indirect evidence — treat these as our best hypotheses, not conclusions. Low means speculative and specifically flagged for your confirmation.
Category, positioning, and name usage shape every query in the audit. The most consequential thing to confirm is who Spectrum Roadmap is really selling to — because that single answer re-tiers the entire competitive set.
→ Who Are You Really Selling To? The whole knowledge graph is currently tiered on the assumption of an SMB / mid-market HR buyer — a small team that wants a self-guided program it can run without an enterprise contract (one pain point literally reads "I'm a team of two who just needs to get started"). But your positioning could also read as a right-sized alternative for larger enterprises running a formal neurodiversity initiative. Which buyer dominates your pipeline? If it's SMB/mid-market, we keep the smaller consultancies as your head-to-head set and treat Uptimize and auticon as secondary; if it's enterprise, we re-tier the competitive set and change nearly every head-to-head query.
5 personas: 2 decision-makers with veto power, 1 evaluator, and 2 influencers. All five are inferred from category patterns — no public review corpus exists for a company this size — so these are the most important inputs to validate. Personas shape how every buyer query is phrased.
Critical Review Area Personas drive query construction more than any other KG input. If a persona's influence level is wrong, the queries we test under their role will miss — or worse, simulate the wrong buyer. Because Spectrum Roadmap is a small, founder-led business with no G2 or review footprint, all five personas are llm_inference — four at medium confidence and one, the Director of Engineering, at low confidence. The buying committee below is our best reconstruction from how neurodiversity-hiring deals typically form; your reality may be smaller and flatter.
Data Sourcing Note Name, role, department, seniority, influence level, veto power, and technical level are KG fields — all inferred here from category patterns rather than mined from reviews. Role descriptions, buying jobs, and query focus areas are synthesized from that role context. Flag anything that doesn't match who actually shows up when a client buys Spectrum Roadmap — especially whether these roles exist at all at the size of company you sell to.
→ At a startup/SMB buyer, does a Chief People Officer actually sign — or does the founder/CEO hold the checkbook? If the founder signs, we swap the C-suite People persona for a founder/owner whose queries lead with cost and speed-to-value over enterprise governance and board-level ROI.
→ Given a buyer that may be "a team of two," does a dedicated VP of Talent Acquisition with budget veto actually exist in your deals, or is hiring owned by a generalist HR lead? If there's no VP TA, we demote the acquisition-stage veto queries and collapse them into a single HR-generalist voice.
→ At the small HR teams Spectrum sells to, is there a standalone Head of DEI at all, or is DEI a hat the HR lead wears? If no dedicated DEI role exists, we fold Maya's authenticity-framed queries into the HR persona and drop the DEI-title query cluster rather than testing a buyer who isn't in the room.
→ In a self-guided-program purchase, is the HR Business Partner actually the buyer-operator who picks and runs Spectrum, rather than a mere influencer? If James is the real decision-maker, we promote his role and lead the query set with hands-on "how do I run this myself" framing instead of executive-approval framing.
llm_inference) — whether an engineering manager participates in the buy is the open question.→ Priya is our lowest-confidence persona. Does a technical hiring manager actually sit in the buying group, or does the decision live entirely within HR/DEI? If engineering isn't in the room, we drop the high-technical persona and its jargon-heavy, role-specific queries and reweight the entire audit toward HR and DEI language.
→ Missing Personas? Three roles often appear in neurodiversity-hiring deals for smaller organizations — do they show up in yours? (1) Founder / CEO / Owner (at a startup, the person who personally champions inclusion and signs the check may be the founder, not a CPO); (2) L&D / Training Manager (if the self-paced training is bought as a learning-program decision rather than a hiring decision); (3) Neurodiversity ERG lead or internal champion (a self-advocate who initiates the search before HR formalizes it). Who else shows up in your deals?
10 competitors: 6 primary + 4 secondary. Tier assignments determine which providers appear in head-to-head queries vs. category-awareness queries.
Why Tiers Matter Primary competitors drive head-to-head queries like "Uptimize alternatives for small teams" or "best neurodiversity hiring training vs. alternatives" — roughly 6–8 queries per primary, so ~36–48 direct-differentiation queries across the 6 primaries. Secondary competitors appear in category-awareness queries only. There's a notable anomaly here: our two high-confidence primaries — Uptimize and auticon — are exactly the two the analysis flags as possibly too enterprise for your buyer, while the four medium-confidence primaries (NITW, NeuroTalent Works, Exceptional Individuals, Genius Within) are the closest true peers. If your buyer is SMB, moving Uptimize and auticon to secondary shifts ~12–16 queries out of the head-to-head set.
→ Validation Questions (1) Tier anomaly: Uptimize and auticon are our only high-confidence primaries, yet both are enterprise-scale — do they actually come up head-to-head in your deals, or are they aspirational names buyers mention without seriously comparing? Moving them to secondary shifts ~12–16 queries. (2) The true peers: Are NITW, NeuroTalent Works, Exceptional Individuals, and Genius Within the providers you actually lose deals to — and should any (e.g. Genius Within's self-paced catalog) be weighted above the others? (3) Irrelevant: Is Stanford Neurodiversity Learning Platform (low confidence) something buyers genuinely weigh against you, or free content that never enters the decision?
12 buyer-level capabilities mapped: 4 strong, 4 moderate, 2 weak, 2 absent. Buyer language determines how capability queries get phrased in the audit.
Self-paced training that teaches our managers how to work with, communicate with, and get the best out of neurodivergent team members
Redesign our interviews with structured rubrics so we stop screening out strong neurodivergent candidates on eye contact and small talk instead of job ability
Get one-on-one coaching from a specialist who will tell us exactly what to change in our hiring and onboarding, not just hand us a course
A private community where our people and neurodivergent employees can get ongoing peer support and answers between trainings
Give us practical accommodation playbooks we can actually put in place without guessing or over-promising
Assess our current hiring process and build an implementation roadmap tailored to our specific team and challenges
Help us keep the neurodivergent people we hire, not just get them in the door
Is this taught by people who actually understand neurodivergence, so our staff and candidates trust it
Actually connect us with neurodivergent candidates or a pipeline, not just teach us how to find them ourselves
Show me the metrics and ROI so I can prove to leadership this program is working and worth the spend
Can this scale to thousands of employees with an LMS, SSO, seat management, and reporting our IT and L&D teams require
Does our team come away with a recognized certificate or accredited CPD credit we can point to
Feature Prioritization Four capabilities are rated Strong: Manager & Team Neurodiversity Training, Inclusive Interview & Assessment Redesign, 1:1 Expert Coaching & Advisory, and Community & Peer Support Network. The audit tests all 12, but competitive-differentiation queries will emphasize 3. Which of these best represents where Spectrum Roadmap wins deals? Our working hypothesis is Inclusive Interview Redesign + Manager Training + 1:1 Expert Coaching — the first two each tie to your highest-severity buyer pains, and founder-led coaching is your clearest wedge against impersonal enterprise platforms. Community & Peer Support could displace coaching if the paid community is your true retention differentiator.
→ Feature Validation (1) The two "absent" capabilities: We marked Enterprise Platform & Scalability and Certification & Accreditation absent by inference from your site, not an explicit statement — confirm Spectrum genuinely offers no LMS/SSO/seat management and no accredited certificate. This matters because IBCCES competes specifically on certification; if you do issue a credential, we stop conceding that query. (2) The "weak" sourcing rating: Talent Sourcing & Pipeline is rated weak — is that right, or do you ever place/source candidates? auticon and SourceAbled win on exactly this; if you have no pipeline, we steer buyers away from placement-framed queries instead of competing on them. (3) Missing / merge: Is there depth in manager-behavior change or self-advocacy support that belongs in the taxonomy — and should Accommodation Frameworks and Customized Program Design be one capability or two?
10 pain points: 4 high, 6 medium severity. Buyer language is how queries will be phrased — if the framing doesn't match how your prospects describe their problem, the audit will miss.
→ Pain Point Validation (1) Severity accuracy: We rated the legal/disclosure fear ("end up with a discrimination complaint or a privacy breach") as high — is that a constant, deal-shaping worry for your buyers, or a situational concern that only surfaces once? If it's always-on, we lead with defensible-accommodation queries. (2) Buyer language: Four of these ten pains were inferred from category knowledge rather than mined from your own content (churn, no-internal-expertise, DIY-credibility, performative-DEI) — does "I'm a team of two who just needs to get started" actually match how your prospects describe the enterprise-vendor problem? (3) Missing pains: Three that often surface in this category — manager fear of "saying the wrong thing" and being seen as ableist, employee reluctance to self-disclose even in an inclusive process, and DEI budget scrutiny when programs are questioned as "political." Do any resonate with your deals?
Layer 1 analysis of spectrumroadmap.com — findings your engineering team can triage before the validation call. These are the technical and structural issues that determine whether AI crawlers can discover and extract citable content.
Actionable Now — Engineering Good news first: robots.txt is present and explicitly allows every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, ChatGPT-User, and Google-Extended all read Allow: / — so there's no access blocker to clear. There are no critical or high-severity findings. The medium-severity structural items engineering can start on now: (1) fix the multiple-H1 heading hierarchy on the homepage (4–5 H1s), /pages/about, and the product pages (the /products/community page renders ~9 H1 blocks); and (2) stop the synthetic bulk lastmod that stamps ~360 legacy blog posts as freshly modified on the same three days in September 2025. A related low-severity item — (3) noindex/redirect the ~340 off-topic legacy consumer posts — concentrates your topical signal. Your /pages/ resource guides already model clean structure and accurate dates — use them as the in-house template.
What we found: The Shopify/page-builder templates behind the highest-intent commercial pages emit several competing H1s and a flattened heading structure. The homepage and /pages/about each render 4–5 separate H1-level headings (the homepage promotes "Unlock Brilliant Neurodiverse Talent," "The Roadmap That Makes Inclusive Hiring Easy," "Neurodiverse Talent Isn't Missing," and "Start Building Inclusive Teams Today" all at H1). The /products/community page renders ~9 H1 blocks, and the Essential Training and Premium Roadmap coaching pages repeat the site name as a second H1 above the product H1. By contrast, the /pages/ resource guides are cleanly structured with a single descriptive H1 and logical H2/H3 nesting.
Why it matters: LLMs use heading structure to segment a page into citable passages and to infer what a page is primarily about. When a commercial page carries multiple H1s, no single heading anchors the page's main claim, so the page is harder to retrieve and quote for a specific buyer question. The weakness is concentrated on exactly the pages that should convert (products, homepage), while the free educational guides — which already have clean structure — are the ones best positioned to be cited.
Recommended fix: In the theme templates for the homepage, product pages, and About page, demote all but the single most important heading from H1 to H2, and make the remaining H1 a descriptive noun phrase naming the page's subject (e.g. "Essential Training: Self-Paced Neurodiversity Hiring Program"). Verify one H1 per page across the commercial set with an HTML outline tool.
What we found: The blog child sitemap (sitemap_blogs_1.xml) lists ~360 legacy posts, nearly all stamped with lastmod dates between 2025-09-21 and 2025-09-25 — the dates the old "Spectrum Strategies" catalog was bulk re-imported into the current Shopify store. The actual authored content is far older: on-page dates read November 2018 through November 2024, so the sitemap signals uniform "recently modified" freshness for content that is 1–8 years old. Separately, the product sitemap stamps all three /products/ pages with a rolling daily lastmod (changefreq: daily), which also does not reflect real content edits.
Why it matters: AI crawlers and search engines weight lastmod as a freshness signal, and citation algorithms concentrate on recently updated content. A sitemap that reports ~360 URLs as freshly modified on the same three days is both non-credible and misleading — it can waste crawl budget re-fetching stale consumer posts instead of the genuinely fresh /pages/ commercial guides, and it undercuts domain-level freshness credibility when a crawler cross-checks lastmod against visible on-page dates.
Recommended fix: Stop emitting a synthetic bulk lastmod for legacy posts. Either set each legacy post's lastmod to its true authored/last-edited date, or (preferred — see the indexation finding) remove genuinely obsolete consumer posts from the sitemap so lastmod reflects real editorial activity. Preserve the accurate per-page lastmod the /pages/ resource guides already carry.
What we found: Roughly 340 of the ~360 indexed blog posts are legacy "Spectrum Strategies" consumer content — autism-awareness pieces, life-coaching tips, "book of the month" posts, and TV-show ("Parenthood") recaps aimed at neurodivergent individuals and their families, not the current HR/employer buyer. These posts are thin (many 200–450 words), 1–8 years old, and remain fully indexed in the sitemap. The current commercial value of the site is concentrated in ~30 recently authored /pages/ guides, a small fraction of the crawlable URL set.
Why it matters: When a domain's crawlable footprint is 90%+ off-topic, dated consumer content, it sends a diluted topical signal about what the site is authoritative on. For AI retrieval, the ratio of high-quality, on-topic pages to total indexed pages affects how confidently a model associates the domain with "neurodiversity hiring for HR teams." This is an indexation / crawl-focus issue about which existing pages crawlers see — not a request to write new content.
Recommended fix: Audit the legacy /blogs/blog/* archive. For posts with no ongoing relevance to the HR/employer audience, noindex them or 301-redirect the few with residual value into the relevant current /pages/ guide, and remove the obsolete ones from the sitemap. Keep indexed only the handful of employer-facing legacy posts worth retaining. This concentrates crawl budget and topical signal on the commercial guides.
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 page text, not raw HTML, so JSON-LD schema blocks aren't visible to this method and schema coverage scored null for every page (39 unscored). This matters because the site is unusually rich in schema-ready content: every /pages/ resource guide ends in a structured FAQ section, the /pages/faq page has 7 Q&A pairs, and the three /products/ pages carry explicit price/offer data.
Recommended action: Run the product, FAQ, and resource-guide URLs through Google's Rich Results Test or the Schema Markup Validator. Where missing, add FAQPage schema to the guide and FAQ pages, Article schema to the resource guides (with datePublished/dateModified matching the visible "Last updated" dates), and Product/Offer schema to the three program pages. Verify meta robots and canonical tags at the same time.
What to check: Meta descriptions, Open Graph tags, Twitter card tags, and canonical URLs live in the HTML <head> and are not present in rendered markdown, so they weren't assessable by this method. We can't confirm whether the commercial pages have unique, descriptive meta descriptions and social preview tags.
Recommended action: Use a social-preview / head-inspection tool (or view-source) to confirm each commercial page has a unique meta description, a self-referencing canonical tag, and complete OG image/title/description tags. Fill any gaps, prioritizing the product pages and top resource guides.
What to check: Every page we fetched returned full, substantive rendered text (headings, body copy, FAQs, pricing) — a positive signal that the Shopify storefront server-renders its primary content. But our method receives already-rendered content and can't definitively distinguish server-rendered HTML from JavaScript-injected content, so we can't fully rule out client-side-rendering gaps for individual components.
Recommended action: Spot-check the homepage, a product page, and one resource guide with JavaScript disabled (or via a raw-HTML / view-source tool such as Screaming Frog in text-only mode). Confirm headings, pricing, and FAQ answers are present in the initial HTML. No action needed if they are.
Coverage Note The analysis scored 39 pages — the commercially relevant set (37 commercial pages) — and did not deep-scan the ~360 legacy consumer blog posts, which are the subject of the indexation finding above. Because the method reads rendered page text rather than raw HTML, schema markup could not be assessed on any page (39 unscored) and 4 product pages returned no detectable date (freshness scored null). The Manual Verification Checklist covers what engineering should confirm directly; the heading, freshness, content-depth, and extractability scores reflect only the pages that could be scored.
Why Now
Once the validation call resolves the open questions, the full audit will measure citation visibility across buyer queries in the neurodiversity-hiring-training space — including "how do I train managers to support neurodivergent employees," "inclusive interview process for autistic candidates," "neurodiversity hiring program for a small HR team," and "Uptimize alternatives for small teams." You'll see exactly which queries return results that include Uptimize, auticon, NITW, or Genius Within but not Spectrum Roadmap — and what it would take to appear in them. Fixing the heading hierarchy and the misleading sitemap dates before the audit runs improves your baseline before we even measure it.
45–60 minutes. We walk through this document together, resolve every purple question, confirm your target segment and competitor tiers, and lock the query set before execution begins.
We generate buyer queries across the selected AI platforms (ChatGPT, Claude, Perplexity, Google AI Overviews) — persona-weighted, category-specific, and head-to-head against your primary competitors.
Visibility analysis, competitive positioning, and a prioritized three-layer action plan: technical fixes, content priorities (now informed by what actually costs citations), and category/narrative moves.
Start Now — Engineering Three Layer 1 fixes don't depend on the rest of the audit and will improve your baseline before we even measure it: (1) demote the competing H1s to a single descriptive H1 on the homepage, /pages/about, and the three product pages, using the /pages/ resource guides as the in-house template; (2) stop the synthetic bulk lastmod on the ~360 legacy blog URLs so genuinely fresh guides aren't discounted; and (3) verify JSON-LD schema (FAQPage on the guides/FAQ, Product on the programs, Article on the guides) via the Rich Results Test, and confirm content is server-rendered with a quick CSR spot-check. Crawler access is already in good shape — robots.txt allows every major AI bot — so no robots.txt unblocking is 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.