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 D2L'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 learning management system space, these three signals tell us whether AI crawlers can access and trust D2L's site content.
AI search is reshaping how higher education institutions, K-12 districts, and corporate training departments discover and evaluate learning management systems. Buyers who once relied on RFPs and peer referrals are increasingly asking AI platforms to compare LMS options — and the platforms that show up in those responses gain compounding visibility as AI models learn to trust cited domains. D2L operates across four distinct market segments with a multi-product portfolio, which means the query surface is unusually broad and the audit architecture must reflect which segments actually drive pipeline.
This document presents the competitive landscape that shapes which head-to-head matchups the audit will test, the buyer personas that determine search intent patterns across higher education and corporate training, and the technical baseline that determines whether AI platforms can access D2L's content at all. These inputs are what we're validating together before the audit runs — every persona, competitor tier, and feature rating directly shapes the queries we generate.
The validation call is a decision-making session with two jobs. First, input validation: are the right entities in the right tiers? The knowledge graph spans four market segments, and the query set changes substantially depending on which segments D2L prioritizes. Second, engineering triage: technical items from the site analysis can start before results come back, giving the engineering team a head start on improving the baseline before we even measure it.
What This Is This document presents the inputs that will drive D2L's GEO visibility audit — the competitive set, buyer personas, feature taxonomy, and pain point landscape for the learning management system category. Everything here was built from outside-in research: your website, review platforms, competitive intelligence, and category analysis. The audit's accuracy depends on whether these inputs match your reality.
What We Need From You Throughout this document, you'll see purple question boxes like this one. Each asks about a specific data point where your insider knowledge matters more than our outside-in research. Before the validation call, review each purple box and note your answer. The more corrections you provide, the more accurate the audit queries will be.
Confidence Badges Every data point includes a confidence badge — High Medium Low. High-confidence items come from multiple corroborating sources. Medium and low items are where your corrections have the biggest impact on audit quality. Focus your review time on medium and low confidence items first.
The company profile anchors the audit — category and segment determine which competitive conversations the queries target.
→ D2L serves four distinct segments — higher education, K-12, corporate training, and government. Does one segment drive the majority of new pipeline, or should the audit weight all four equally? If higher ed dominates, we'd narrow the persona set and deprioritize corporate training queries; if corporate is growing fastest, the VP of L&D persona becomes central and Docebo/Absorb move up in competitive priority.
5 personas: 2 decision-makers, 2 evaluators, 1 influencer. Each persona generates a distinct query cluster — getting the roles and influence levels right determines which buyer intents the audit tests.
Critical Review Area Personas have the highest downstream impact of any KG input. Each persona drives 15-25 distinct queries in the audit. A misclassified role or incorrect influence level doesn't just produce wrong queries — it produces queries for a buyer who doesn't exist in your deals, displacing queries for one who does.
Data Sourcing Note Role titles, departments, seniority, influence levels, and veto power are sourced from the knowledge graph (G2 reviewer profiles, case studies, product marketing). Buying jobs and query focus areas are synthesized from the role context — they represent our best inference of what each persona would search for, not observed search behavior.
→ Does IT hold LMS budget authority at D2L's target institutions, or does the academic side control procurement? If academic-controlled, we shift decision-maker queries toward the Provost pathway and reclassify the CIO as an evaluator.
→ Does the Provost drive initial LMS evaluation, or only approve after a selection committee recommends? If approval-only, we deprioritize early-stage awareness queries for this role and shift discovery-stage queries to the Director of Online Learning.
→ Does this role own the RFP process and drive vendor shortlisting, or serve as a technical advisor to a broader committee? If she owns the RFP, we reclassify as decision-maker and add contract-stage queries targeting evaluation criteria and vendor negotiation.
→ Does D2L actively close deals through corporate L&D buyers, or is Brightspace for Business a secondary go-to-market motion? If secondary, we remove this persona entirely and redistribute its 15-20 queries to higher-ed buyer intents where D2L's pipeline is concentrated.
→ Does the LMS Administrator formally influence vendor selection beyond technical feasibility, or is this role consulted only for migration and integration assessment? If feasibility-only, we narrow this persona's queries to migration, integration, and admin-specific topics and deprioritize comparison-stage queries.
Missing Personas? Are there additional roles that show up in D2L's sales process? Consider: Dean / Department Chair (if individual departments run independent LMS evaluations rather than institution-wide procurement), VP of Student Success (if student retention metrics are a primary driver of LMS decisions), or Procurement / Compliance Officer (if RFP compliance and vendor security reviews are a formal gate in D2L's deal cycle). Who else shows up in your deals?
5 primary + 4 secondary competitors identified. Tier assignments determine which head-to-head matchups the audit tests.
Competitive GEO Context Tier assignments determine which queries test direct competitive differentiation. Primary competitors generate head-to-head queries like "Canvas vs Brightspace for universities" or "best LMS for higher education" — approximately 30-40 queries across 5 primary competitors. Getting these tiers right determines whether we're testing the matchups that actually appear in D2L's deals. Three secondary competitors — Absorb LMS, Sakai, and TalentLMS — have medium confidence on tier assignment; if any of them actually appear in competitive deals, moving them to primary would add 6-8 head-to-head queries each.
→ Three secondary competitors — Absorb LMS, Sakai, and TalentLMS — have medium confidence. Are any of these showing up in competitive deals and should be promoted to primary? Conversely, is Sakai still relevant given its declining market share, or should it be replaced with a more active competitor? Are there vendors we're missing entirely — for example, a regional LMS provider or a newer entrant like Coursera for Campus that appears in D2L's deal cycles?
12 buyer-level capabilities mapped. Feature names and strength ratings determine which capability queries the audit tests and how D2L's positioning is framed against competitors.
Tools for faculty and instructional designers to build engaging online courses with multimedia, interactive content, and reusable learning objects
Flexible quiz types, rubrics, competency-based grading, and an integrated gradebook that handles complex weighting schemes
Dashboards and predictive models that identify at-risk students and measure learning outcomes across programs
Automatically adjust course content and pacing based on individual learner performance and mastery levels
WCAG 2.1 AA compliance, screen reader support, and built-in accessibility checking so all learners can participate regardless of ability
Connect the LMS to our SIS, video platforms, plagiarism tools, publisher content, and other edtech through LTI and open APIs
A mobile app that lets students access courses, submit assignments, participate in discussions, and view grades from any device
AI tutoring, automated feedback generation, intelligent content recommendations, and AI-assisted course design
Discussion boards, group workspaces, peer review, video conferencing integration, and real-time messaging for student-faculty interaction
Manage thousands of users, courses, and organizational units with granular role-based permissions and bulk operations
Map learning outcomes to competencies, track student mastery across programs, and generate accreditation reports
Deploy mandatory compliance training, track completions across the workforce, and manage certifications with automated reminders
→ Are the "weak" ratings for Mobile Learning Experience and Collaboration & Communication Tools accurate relative to Canvas and Blackboard — or has D2L made recent improvements that would move these to moderate? These ratings drive defensive queries where we test whether AI platforms cite competitors' mobile or collaboration strengths over D2L's. Also: is AI-Powered Learning Tools (medium confidence, rated moderate) underselling D2L Lumi's capabilities, or is the moderate rating fair given Docebo's and Canvas's more established AI features? Any missing capabilities — for example, a content marketplace or digital credentialing — that belong in the taxonomy?
9 pain points: 5 high, 4 medium severity. Buyer language from these pain points is how the audit phrases problem-aware queries — the words real buyers use when searching for solutions.
→ Two pain points have medium confidence: Peak Performance Issues was sourced from reviews but may reflect older Brightspace versions — is this still a current problem, or has D2L resolved it? If resolved, we remove it from 3 personas' query sets. LMS Migration Risk was inferred from general market dynamics, not D2L-specific data — does D2L actually see migration fear as a selling point (switching from Blackboard) or a barrier (switching to Brightspace)? The framing changes the query strategy. Also missing: are pricing transparency or contract lock-in concerns pain points that appear in D2L's competitive conversations?
Technical signals that affect how AI crawlers access, parse, and trust D2L's content.
Engineering Action No critical blockers found — D2L's WordPress stack is well-configured for AI crawler access. The findings below are medium and low-severity structural items that engineering should verify and address. Priority items: fix the multi-H1 heading pattern on commercial pages and add freshness dates to comparison pages and case studies. Schema markup should also be verified — our analysis method couldn't assess it directly.
What we found: Several high-value commercial pages use multiple H1 tags as section headers rather than a single H1 for the page topic. The homepage has 12+ H1 elements, the main Brightspace product page has 12+ H1s, and the Why D2L hub page has 10+ H1s. Other pages commonly use 2 H1 tags. This appears to be a WordPress theme pattern where each section block generates its own H1.
Why it matters: AI models use the H1 tag to identify the primary topic of a page. When multiple H1s are present, the page's topical focus becomes ambiguous to both search engines and LLMs. Pages with clean single-H1 hierarchies are more reliably indexed and cited.
Recommended fix: Audit heading tags across the site. Ensure each page has exactly one H1 describing the page's primary topic. Convert additional H1 tags to H2 or H3 as appropriate for their nesting level. Most WordPress themes allow heading level configuration per block.
What we found: Multiple content marketing pages — including comparison pages (vs Canvas, vs Schoology, vs Sakai) and customer case studies — lack visible publish or last-updated dates. Blog posts consistently display dates, but comparison pages and case studies do not. Some comparison pages show only data-attribution dates (e.g., "Data as of December 2024") rather than page update dates.
Why it matters: Research shows 76.4% of AI-cited pages were updated within 30 days. AI crawlers deprioritize content without detectable freshness signals, especially for competitive comparison queries where recency directly affects credibility.
Recommended fix: Add visible "Last Updated" dates to all comparison pages and customer case studies. For comparison pages, update the date whenever G2 data or competitive claims are refreshed. Consider implementing a content freshness review cycle for comparison pages (quarterly) and case studies (annually).
What we found: Our analysis method returns rendered page content as markdown text, which does not include JSON-LD schema markup, meta tags, or other HTML-only signals. We cannot determine whether appropriate schema types (Product, FAQPage, Article, Organization, HowTo) are implemented on D2L's pages.
Why it matters: Structured data helps AI models understand page content type and extract specific claims. Pages with appropriate schema markup are more likely to be surfaced in structured AI responses. D2L's WordPress stack (Yoast SEO detected) likely generates basic schema, but verification is needed.
Recommended fix: Test key commercial pages using Google's Rich Results Test or Schema.org validator. Verify that comparison pages use FAQPage schema, product pages use Product or SoftwareApplication schema, blog posts use Article schema, and case studies use Article schema with datePublished.
What we found: Meta descriptions, Open Graph tags, and Twitter Card markup cannot be assessed from rendered markdown output. Yoast SEO typically generates these automatically, but custom optimization per page cannot be confirmed.
Why it matters: Meta descriptions appear in search result snippets and AI-generated summaries. Well-crafted meta descriptions with specific claims improve click-through rates and may influence how AI models summarize page content.
Recommended fix: Verify meta descriptions are present and customized on the top 20 commercial pages. Ensure OG titles, descriptions, and images are set for comparison pages, product pages, and solution pages.
What we found: All 44 pages returned substantial rendered content, and the site runs on WordPress (server-side rendered by default). CSR issues are unlikely, but interactive elements or JavaScript-heavy page builders may render client-side.
Why it matters: Content rendered exclusively via client-side JavaScript is invisible to AI crawlers that don't execute JavaScript. If critical content — product features, comparison tables, pricing — is loaded via JavaScript, it may be absent from AI responses.
Recommended fix: Spot-check 3-5 key pages by viewing with JavaScript disabled. If all content remains visible, no action is needed.
Partial Freshness Data 18 of 44 pages have no detectable freshness signal — 17 are product/commercial pages and 1 is structural. The product page freshness score (0.90) is based on only 5 of 22 product pages. The actual freshness of the remaining 17 product pages is unknown and should be verified manually by checking for visible dates or sitemap lastmod entries.
Why Now
• AI search adoption is accelerating — buyer discovery patterns in education technology are shifting quarter over quarter as institutions use ChatGPT, Perplexity, and Copilot to compare LMS platforms
• Early citations compound: domains that AI platforms learn to trust now get cited more frequently as training data accumulates
• Competitors who establish GEO visibility first create a structural disadvantage for late movers — once Canvas or Blackboard dominate AI responses for "best LMS" queries, displacing them becomes exponentially harder
• The learning management system category is still early-innings in GEO optimization — acting now means competing against inaction, not against entrenched strategies
The full audit will measure D2L's citation visibility across buyer queries in the LMS space — including queries like "best LMS for competency-based education," "Canvas vs Brightspace for universities," and "LMS that's easy for faculty to adopt." You'll see exactly which queries return results that include Canvas, Blackboard, or Moodle but not D2L — and what it would take to appear in those responses. Fixing the heading hierarchy and freshness signals now improves the technical baseline before we even measure it.
45-60 minutes. Walk through this document together, confirm or correct personas, competitor tiers, feature ratings, and pain point framing. Your corrections directly shape the query set.
Validated inputs generate buyer queries tested across selected AI platforms. Queries reflect actual buyer language, competitive matchups, and pain-point phrasing confirmed at the call.
Complete visibility analysis, competitive positioning across AI platforms, and a three-layer action plan: technical fixes, content priorities, and strategic positioning recommendations.
Start Now — Don't Wait for the Call These technical items don't depend on the rest of the audit and will improve D2L's baseline visibility before we even measure it:
• Fix heading hierarchy: Audit the WordPress theme's multi-H1 pattern on the homepage, /brightspace/, and /why-d2l/ — ensure each page has exactly one H1 describing its primary topic
• Add freshness dates: Add visible "Last Updated" dates to all 6 comparison pages under /why-d2l/compare/ and customer case studies — undated competitive content gets deprioritized by AI platforms
• Verify schema markup: Run Google's Rich Results Test on /brightspace/, comparison pages (check for FAQPage schema), and blog posts (check for Article schema) — confirm Yoast is generating the most specific applicable types
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.