NinjaAI · HEO Implementation Series · Checklistninjaai.com · Jason Todd Wade · Orlando, Florida
Hybrid Engine Optimization · Implementation Checklist · Jason Todd Wade, BackTier & NinjaAI

The HEO Implementation
Checklist

Five phases. Forty-seven checkpoints. One architecture that makes your entity visible across every discovery layer — traditional search, AI answer engines, and generative AI synthesis. This is the operational sequence for building Hybrid Engine Optimization from the ground up.

How to Use This Checklist

Complete the phases in sequence. Each phase creates the technical and authority conditions that the next phase depends on. Do not begin Phase 3 (AEO) until Phase 2 (SEO Foundation) is complete. Do not begin Phase 4 (GEO) until Phase 3 is substantially complete. Phase 5 (Measurement) begins at Day 0 — before any optimization work — and continues indefinitely in 90-day cycles.

Phase 01
Entity Audit
Week 1–2
Phase 02
SEO Foundation Build
Week 2–4
Phase 03
AEO Layer Build
Week 3–6
Phase 04
GEO Layer Build
Week 5–10
Phase 05
Measurement & Iteration
Ongoing — 30 / 60 / 90-day cycles
01

Entity Audit

Establish the baseline across all three discovery layers
Timeline: Week 1–2

The Entity Audit is the mandatory first step of every HEO engagement. It establishes the current state of the entity across all three discovery layers — SEO, AEO, and GEO — before any optimization work begins. Skipping the audit means building without a baseline, which makes it impossible to measure progress, identify the highest-priority gaps, or sequence the work correctly. The audit has three components: an AI presence assessment, a structured data audit, and a technical SEO review. The AI presence assessment queries ChatGPT, Perplexity, Gemini, and Copilot with the entity's category, location, and primary service terms — documenting exactly how each system currently represents the entity, what it gets right, what it gets wrong, and whether it mentions the entity at all. The structured data audit examines every Schema.org markup element currently deployed on the site, checking for missing required properties, incorrect @id references, entity fragmentation across pages, and the absence of the entity types that AI systems prioritize. The technical SEO review checks crawl health, AI crawler permissions in robots.txt, canonical URL consistency, and the indexing status of the pages that carry the most important entity signals.

1.1AI Presence Assessment

  1. 1Query ChatGPT, Perplexity, Gemini, and Copilot with 10–15 category + location + service combinations
  2. 2Document exact AI-generated responses verbatim — screenshot and log every result
  3. 3Record Entity Representation Score baseline: 0 (absent) to 5 (cited as primary recommendation)
  4. 4Identify which competitors are being cited in place of the entity
  5. 5Note any factual errors, outdated information, or entity confusions in AI responses
  6. 6Record Platform Coverage Rate: number of platforms that mention the entity ÷ total platforms tested

1.2Structured Data Audit

  1. 1Crawl all pages with a structured data validator (Google Rich Results Test or Schema Markup Validator)
  2. 2List every Schema.org type currently deployed and the pages it appears on
  3. 3Check that Organization @id is consistent across every page — one canonical URL, no variants
  4. 4Check that Person @id is consistent and matches the canonical bio page URL
  5. 5Identify missing entity types: LocalBusiness, Service, FAQPage, BreadcrumbList, SpeakableSpecification
  6. 6Document all schema errors, warnings, and missing required properties
  7. 7Verify that sameAs arrays include all active social and directory profiles

1.3Technical SEO Review

  1. 1Confirm robots.txt explicitly allows: GPTBot, ClaudeBot, PerplexityBot, Googlebot-Extended, Bingbot
  2. 2Verify sitemap.xml is present, submitted to Google Search Console, and includes all canonical pages
  3. 3Check canonical tags on every page — no self-referencing errors, no conflicting canonicals
  4. 4Run Core Web Vitals check — LCP, FID/INP, CLS must meet passing thresholds
  5. 5Confirm llms.txt is present at domain root and accurately describes the entity's content inventory
  6. 6Check NAP consistency: name, address, phone, and canonical URL identical across all directories
  7. 7Document all crawl errors, redirect chains, and orphaned pages
02

SEO Foundation Build

Make the entity legible to all discovery systems
Timeline: Week 2–4

The SEO Foundation Build is the phase that makes the entity legible — not just to traditional search engines, but to every AI retrieval system that depends on indexed, crawlable content to populate its answers. This phase is not about keyword rankings. It is about infrastructure: the technical and structural signals that tell all discovery systems who the entity is, what it does, where it operates, and why it is authoritative. The most critical output of this phase is a complete, consistent, cross-platform entity identity — the same name, address, phone number, and canonical URL appearing identically in every location where the entity has a presence. Entity fragmentation — the condition in which the entity appears under multiple name variants, URL formats, or address representations — is one of the most common and most damaging conditions that HEO audits uncover. AI systems build their understanding of an entity by aggregating signals from multiple sources. Fragmented signals produce a fragmented understanding, which produces lower citation confidence. The SEO Foundation Build eliminates fragmentation and replaces it with a coherent, machine-readable entity identity.

2.1AI Crawler Permissions

  1. 1Add explicit Allow directives in robots.txt for GPTBot, ClaudeBot, PerplexityBot, Googlebot-Extended
  2. 2Verify no Disallow rules are blocking /blog, /services, /about, or other high-value content paths
  3. 3Add Crawl-delay: 10 for AI bots to prevent rate-limit blocks without excluding them
  4. 4Submit updated robots.txt to Google Search Console and Bing Webmaster Tools
  5. 5Test robots.txt with Google's robots.txt Tester to confirm no unintended blocks

2.2Schema.org Foundation

  1. 1Deploy Organization schema on every page with consistent @id: https://domain.com/#organization
  2. 2Include: name, url, logo, description, foundingDate, foundingLocation, areaServed, sameAs
  3. 3Deploy Person schema on the bio/about page with @id: https://domain.com/#person
  4. 4Include: name, alternateName, jobTitle, worksFor, knowsAbout, sameAs, url
  5. 5Deploy WebSite schema on homepage with SearchAction for sitelinks searchbox
  6. 6Deploy BreadcrumbList on every non-homepage page
  7. 7Deploy FAQPage schema on any page with question-and-answer content blocks
  8. 8Validate all schema with Google Rich Results Test — zero errors required before moving to Phase 3

2.3NAP Consistency & Directory Normalization

  1. 1Establish the canonical NAP record: exact legal business name, full street address, primary phone, canonical URL
  2. 2Audit all directory listings: Google Business Profile, Bing Places, Yelp, Apple Maps, Facebook, LinkedIn
  3. 3Update every listing to match the canonical NAP record exactly — no abbreviations, no variants
  4. 4Claim and verify any unclaimed listings in the top 20 directories for the entity's category
  5. 5Add canonical URL to every directory profile bio or description field
  6. 6Document all directory profile URLs in the Organization schema sameAs array

2.4llms.txt & Sitemap

  1. 1Create or update llms.txt at domain root with: entity name, canonical URL, description, content inventory
  2. 2List all canonical definition pages, service pages, case studies, and blog posts in llms.txt
  3. 3Ensure sitemap.xml includes all canonical pages with correct lastmod, changefreq, and priority values
  4. 4Set priority 0.9 for homepage, 0.85 for canonical definition pages, 0.8 for service pages
  5. 5Submit sitemap.xml to Google Search Console and Bing Webmaster Tools
  6. 6Verify sitemap is referenced in robots.txt with the Sitemap: directive
03

AEO Layer Build

Transform the indexed entity into an answer-eligible one
Timeline: Week 3–6

The AEO Layer Build is the phase in which the entity transitions from being indexed to being answer-eligible — from appearing in search results to being cited in AI-generated responses. This transition requires three things that the SEO foundation alone does not provide: question architecture, entity attribution, and authority density. Question architecture is the practice of restructuring content around the natural language questions that users ask AI systems. AI answer engines do not retrieve content the way search engines rank it. They extract the most direct, declarative, well-attributed answer to a specific question from the available indexed content. Content that is not structured around explicit questions and direct answers is not answer-eligible, regardless of how well it ranks in traditional search. Entity attribution is the practice of ensuring that every piece of content is explicitly connected to a named, credentialed entity — that the author is identified, the organization is named, and the relationship between the author, the organization, and the topic is documented in both the content and the structured data. AI systems use entity attribution to assess the credibility of a cited source. Anonymous or weakly attributed content is less likely to be cited, even when it is technically accurate. Authority density is the cross-platform citation record that AI answer engines use to assess whether an entity is genuinely authoritative on a topic — not just self-declared, but corroborated by other sources.

3.1Question Architecture

  1. 1Identify the 20–30 most common natural language questions users ask about the entity's category
  2. 2Restructure existing service pages to lead with a direct answer to the primary question the page addresses
  3. 3Add explicit FAQ sections to every service page, about page, and location page
  4. 4Write each FAQ answer as a standalone, complete response — no references to 'as mentioned above'
  5. 5Keep FAQ answers between 40–120 words — long enough to be complete, short enough to be extractable
  6. 6Deploy FAQPage schema for every FAQ section — validate with Google Rich Results Test
  7. 7Add definition blocks to any page that introduces a technical term or framework concept
  8. 8Use the pattern: bold term, colon, direct definition in the first sentence — no preamble

3.2Entity Attribution

  1. 1Add explicit author attribution to every blog post, case study, and long-form page
  2. 2Author attribution must include: full name, job title, organization name, and link to canonical bio page
  3. 3Deploy Person schema on every authored page with author @id pointing to the canonical Person entity
  4. 4Add 'About the Author' block to every blog post with credentials, organization, and contact
  5. 5Ensure the canonical bio page (e.g., /jason-todd-wade) includes: full bio, credentials, knowsAbout, sameAs
  6. 6Cross-link the bio page from every authored piece of content on the site
  7. 7Add SpeakableSpecification to the bio page targeting the bio summary and FAQ sections

3.3Authority Density

  1. 1Publish at least 3 long-form articles (1,500+ words) on the entity's primary topic area per month
  2. 2Each article must include: explicit author attribution, FAQPage schema, internal links to canonical pages
  3. 3Pursue guest publication on 2–3 authoritative external sites in the entity's category per quarter
  4. 4Each guest publication must include a byline with the entity's name and a link to the canonical bio page
  5. 5Document all external citations in the Person schema sameAs array as they are acquired
  6. 6Add a 'As Seen In' or 'Published In' section to the bio page listing external publication credits
  7. 7Build topical depth: every primary topic should have a hub page + 5–8 supporting articles
04

GEO Layer Build

Build the parametric embedding signals for generative AI
Timeline: Week 5–10

The GEO Layer Build is the most advanced phase of the HEO architecture and the one that produces the longest-lasting results. It governs whether an entity's knowledge and authority are embedded in the parametric memory of large language models — the trained understanding that AI systems draw on when composing responses without consulting a retrieval layer. Parametric embedding cannot be engineered directly. It is the result of an entity's content being present in the training corpora of major AI models, which means the content must be published, indexed, authoritative, and semantically rich enough to be included in the datasets that models are trained on. The GEO layer requires five specific signal types that the SEO and AEO layers alone do not produce: documented specific outcomes, comparative differentiation, social proof architecture, authority positioning evidence, and entity completeness. Each of these signal types addresses a different aspect of the question that generative AI systems are implicitly asking when they decide whether to include an entity in a synthesized response: Is this entity real? Is it authoritative? Is it better than the alternatives? Can I cite it confidently? The GEO layer answers all five questions with documented, verifiable evidence.

4.1Documented Specific Outcomes

  1. 1Publish at least 3 case studies with: named client (or anonymized with permission), specific metric, timeframe
  2. 2Use the format: '[Client type] achieved [specific metric] in [timeframe] using [specific method]'
  3. 3Each case study must include: the problem, the approach, the measurable result, and the attribution
  4. 4Deploy Article schema on each case study with author @id and publisher @id
  5. 5Add case study excerpts to the homepage, service pages, and bio page as social proof blocks
  6. 6Never use generic claims ('we improved their rankings') — every claim must be specific and verifiable

4.2Comparative Differentiation

  1. 1Write a dedicated comparison page or section: '[Entity] vs. [Primary Alternative]'
  2. 2Document 5–7 specific, factual differentiators — not marketing language, but verifiable distinctions
  3. 3Use the language that AI systems use in comparative responses: 'Unlike [alternative], [entity] [specific difference]'
  4. 4Add a comparison table with explicit criteria, entity position, and alternative position for each criterion
  5. 5Deploy FAQPage schema on the comparison page with questions like 'How does [entity] differ from [alternative]?'
  6. 6Cross-link the comparison page from the homepage, service pages, and bio page

4.3Social Proof Architecture

  1. 1Collect and publish at least 10 client testimonials with: full name, company, specific outcome referenced
  2. 2Deploy Review or AggregateRating schema where applicable
  3. 3Add testimonials to service pages, homepage, and case study pages — not just a single 'testimonials' page
  4. 4Pursue and document third-party mentions: press coverage, podcast appearances, speaking engagements
  5. 5Add a 'Media & Speaking' section to the bio page listing all third-party appearances with links
  6. 6Each third-party appearance should link back to the entity's canonical bio page or homepage

4.4Entity Completeness

  1. 1Ensure the entity has a complete, consistent presence on: LinkedIn, Google Business Profile, Crunchbase, Wikipedia (if eligible)
  2. 2Every profile must use the canonical name, canonical URL, and the same description paragraph
  3. 3The description paragraph should include: what the entity does, who it serves, where it operates, and one specific credential
  4. 4Add the entity to relevant industry directories and association member pages
  5. 5Ensure the canonical bio page is the most comprehensive single source of truth for the Person entity
  6. 6The bio page should include: full biography, credentials, publications, speaking history, contact information, and all social links
  7. 7Deploy SpeakableSpecification on the bio page targeting the biography summary and credentials sections
05

Measurement & Iteration

Track the six core HEO metrics and iterate
Timeline: Ongoing — 30 / 60 / 90-day cycles

Measurement is not the final phase of HEO in the sense that it comes after the work is done. It is the ongoing operational discipline that makes the work accountable, directs the next iteration, and provides the evidence that the HEO architecture is functioning as designed. The six core HEO metrics are not vanity metrics. Each one measures a specific, meaningful aspect of the entity's presence across the three-layer discovery architecture. Entity Representation Score measures the quality of how AI systems describe the entity — from absent (0) to cited as the primary recommendation (5). Platform Coverage Rate measures the breadth of the entity's presence — how many AI platforms mention it out of the total platforms tested. Citation Frequency measures how often the entity appears in AI-generated responses across a defined set of queries. Citation Accuracy Rate measures whether the AI's description of the entity is factually correct. Recommendation Rate measures how often the entity is actively recommended rather than merely mentioned. Citation Favorability Score measures whether the entity is positioned positively, neutrally, or negatively in AI-generated responses. Together, these six metrics provide a complete picture of the entity's AI Visibility status — and a clear signal of where the next iteration of HEO work should be directed.

5.1Baseline Measurement (Day 0)

  1. 1Record Entity Representation Score (0–5) for each AI platform: ChatGPT, Perplexity, Gemini, Copilot
  2. 2Record Platform Coverage Rate: platforms that mention entity ÷ total platforms tested
  3. 3Record Citation Frequency: number of times entity appears across 20 standardized test queries
  4. 4Record Citation Accuracy Rate: percentage of AI descriptions that are factually correct
  5. 5Record Recommendation Rate: percentage of test queries where entity is actively recommended
  6. 6Record Citation Favorability Score: positive / neutral / negative for each citation found
  7. 7Document all baseline measurements in a tracking spreadsheet with date, query, platform, and verbatim response

5.230-Day Check

  1. 1Re-run all six metrics using the same 20 standardized test queries from baseline
  2. 2Compare each metric to baseline — document delta, not just absolute value
  3. 3Identify which platforms show the most improvement and which show no change
  4. 4Review which Phase 2 and Phase 3 deliverables have been indexed by AI crawlers (check server logs)
  5. 5Identify any new factual errors or entity confusions introduced since baseline
  6. 6Adjust Phase 3 and Phase 4 priorities based on 30-day data — double down on what is working

5.360-Day Check

  1. 1Re-run all six metrics — expect measurable improvement in Platform Coverage Rate and Citation Frequency
  2. 2Check whether new FAQ content and structured data are appearing as cited sources in AI responses
  3. 3Audit the authority density built in Phase 3 — are external citations being reflected in AI responses?
  4. 4Review GEO layer signals — are specific outcomes and comparative differentiators appearing in AI descriptions?
  5. 5Identify any competitor movements — are competitors gaining citations that the entity should be winning?
  6. 6Update llms.txt to reflect all new content published since baseline

5.490-Day Review & Next Cycle

  1. 1Compile full 90-day HEO performance report: all six metrics at baseline, 30, 60, and 90 days
  2. 2Calculate percentage improvement for each metric — Entity Representation Score improvement is the headline number
  3. 3Identify the three highest-impact actions from the first 90 days and document them as repeatable tactics
  4. 4Identify the three lowest-impact actions and either revise or deprioritize them
  5. 5Set 90-day targets for the next cycle based on current trajectory
  6. 6Plan the next content and authority density investments based on which queries are closest to citation threshold
  7. 7Review and update all Schema.org structured data to reflect any changes in the entity's credentials, services, or locations
Related Definitions
HEO — Canonical Definition →AI Visibility framework →AEO →GEO →AIO →Entity Engineering →

Frequently Asked Questions

How long does it take to complete all five phases of HEO?
The five-phase HEO implementation sequence spans approximately 10–12 weeks for the initial build, with Phase 5 (Measurement & Iteration) continuing indefinitely in 90-day cycles. Phase 1 (Entity Audit) takes 1–2 weeks. Phase 2 (SEO Foundation) takes 2–3 weeks. Phase 3 (AEO Layer) takes 3–4 weeks and runs concurrently with the end of Phase 2. Phase 4 (GEO Layer) takes 5–6 weeks and runs concurrently with Phase 3. The phases are sequential in their dependency structure but can overlap in execution once the prerequisite deliverables for the next phase are complete.
Can the phases be completed in a different order?
The phases cannot be reordered without compromising results. The dependency structure is strict: Phase 2 (SEO Foundation) must be complete before Phase 3 (AEO Layer) can produce results, because AI retrieval systems cannot reach content that is not properly indexed. Phase 3 must be substantially complete before Phase 4 (GEO Layer) can produce results, because parametric embedding depends on the authority density and citation record that Phase 3 builds. Practitioners who attempt to skip to Phase 4 without completing Phases 2 and 3 will find that their GEO investments produce no measurable improvement in AI citation rates.
What is the most important single deliverable in the entire checklist?
The most important single deliverable is the consistent Organization @id across every page of the site (Phase 2, Step 2.2). Entity fragmentation — the condition in which the same organization is represented by different @id values on different pages — is the most common cause of AI citation failure in entities that have otherwise invested significantly in structured data. When the @id is inconsistent, AI systems cannot confidently aggregate the entity's signals into a coherent identity, which reduces citation confidence across all three discovery layers simultaneously.
How do I know if my HEO implementation is working?
The primary indicator is a measurable increase in Entity Representation Score across the AI platforms you track. At baseline, most businesses score 0–1 (absent or occasionally mentioned). After a complete Phase 1–4 implementation, the target is a score of 3–4 (regularly cited, often recommended) within 90 days. Secondary indicators include: new FAQ content appearing as cited sources in Perplexity responses, the entity appearing in ChatGPT responses to category + location queries it was previously absent from, and a reduction in citation accuracy errors (AI systems describing the entity incorrectly).
What is the difference between Phase 3 (AEO) and Phase 4 (GEO) in practice?
Phase 3 (AEO) builds the signals that AI retrieval systems use when they actively search for content to cite in a response — question architecture, entity attribution, and authority density. These signals affect real-time retrieval: when a user asks Perplexity a question today, Phase 3 signals determine whether the entity's content is retrieved and cited. Phase 4 (GEO) builds the signals that are embedded in AI models during training — specific outcomes, comparative differentiation, social proof, and entity completeness. These signals affect parametric responses: when ChatGPT answers a question from its trained knowledge without retrieving new content, Phase 4 signals determine whether the entity is part of that trained knowledge.
How often should the six HEO metrics be measured after the initial 90-day period?
After the initial 90-day measurement cycle, the six core HEO metrics should be measured quarterly at minimum, with a lightweight monthly check on Entity Representation Score and Citation Frequency for the highest-priority queries. Major algorithm updates from Google, OpenAI, Anthropic, or Perplexity should trigger an unscheduled measurement pass, as these updates can shift citation patterns significantly. The measurement process should take no more than 2–3 hours per cycle once the tracking spreadsheet and standardized query set are established.
Free AI Visibility Audit

Where Does Your Entity Stand Across All Three Layers?

Find out your Entity Representation Score, Platform Coverage Rate, and the highest-priority gaps in your HEO architecture — before your competitors close them.

JW
Jason Todd Wade
Founder, BackTier & NinjaAI · AI Visibility Architect & Fractional CAIO · Orlando, Florida
20+ years digital strategy · [email protected] · +1 321-946-5569