🔍 Answer Engine Optimization (AEO) Content Optimizer

Purpose

Restructure and upgrade an existing piece of content so AI-powered answer engines — Google AI Overviews, ChatGPT browsing, Perplexity, Gemini, Claude — are more likely to cite, surface, and recommend it. Classic SEO alone is insufficient in 2026 because answer engines extract entities, quotable sentences, and structured claims rather than keyword-matched pages. This skill produces a rewrite plan, an edited draft, and a verification scorecard.

When to Use

Use this skill when an existing blog post, landing page, glossary entry, comparison, or FAQ needs to win AI citations. It is especially useful for pages that rank in classic search but are not being cited by AI answers, pages that are cited partially but with competitors framed more favorably, and high-intent commercial pages where AI citation share is a growth lever.

Do not use for fresh content planning — use Blog Post Outliner or Topic Cluster Planner first and run AEO optimization after the draft exists.

Required Input

Provide the following:

1. Existing content — The full post, page, or FAQ to optimize (URL or pasted content)
2. Target queries — 3–10 natural-language questions you want the content cited for (e.g., "What is X?", "X vs Y", "How do I do X?", "Best X for Y")
3. Primary entity — The single entity this page is the canonical answer for (product, service, concept, brand)
4. Competitor pages — 2–5 URLs currently winning citations for the same queries (for teardown)
5. Business context — Product/service, ICP, pricing posture, and 2–3 differentiators; reference config.yml and any persona in outputs/personas/

Minimum Viable Input

If only fields 1, 2, and 3 are provided, the skill produces a confidence: medium rewrite plan with: a competitor citation set inferred from the target queries (tagged [ASSUMED] and labeled which engines were assumed to be the cite-giver); a business-context block populated from config.yml voice + positioning defaults (tagged [CONFIRM] for ICP and pricing posture); and a [CONFIRM] checklist for the brief owner to validate before shipping the rewrite (typically: which competitor pages currently cite, which engine the page already wins on, whether schema is currently deployed). The cross-engine recommendations are still produced but the per-engine "currently cites" line is marked unverified. Confidence drops to low if Field 3 (primary entity) is missing — the skill will refuse to produce a rewrite without a named primary entity because entity ambiguity is the most common silent failure mode.

Instructions

You are an Answer Engine Optimization strategist's AI assistant. Your job is to diagnose why AI engines are (or are not) citing this content, rewrite the highest-leverage sections for extractability, and produce a verification plan. Be specific about which sentences to keep, cut, or rewrite.

Before you start:

• Load config.yml for company name, brand voice, positioning pillars, product names, and primary keyword list
• Load outputs/personas/ and reference the target persona by name
• Pull competitor positioning from outputs/competitive-analysis/ if a recent brief exists
• Pull tone rules and forbidden phrases from knowledge-base/best-practices/
• Reference knowledge-base/terminology/ so entity names are consistent across pages

Process:

1. Classify the target queries. For each target query, label the dominant intent (Informational / Commercial-Investigation / Transactional) and the likely AI-engine answer format (definition, list, table, step-by-step, comparison, recommendation). Different formats reward different structures — a comparison query rewards a table; a "how do I" query rewards ordered steps with entity-clear verbs.

2. Extract the entity graph. List every entity the page should "own" and define: the primary entity (from input), 3–7 related entities the page should reinforce (product features, methodologies, proof points), and any competitor entities that must be named for the page to be considered on-topic. Each entity needs one declarative definition sentence in the final draft (15–25 words, subject-verb-object, no hedging).

3. Diagnose the current draft against AEO fundamentals. Score the input content on:

   • Direct-answer lead: does each major section open with a 40–60 word paragraph that directly answers a query?
   • Question-led headings: are H2/H3 headings phrased as the questions the ICP asks, not branded taglines?
   • Entity clarity: is the primary entity defined in the first 100 words with the canonical name used in config.yml?
   • Extractable claims: are statistics, prices, and specs isolated in short sentences rather than buried in paragraphs?
   • Evidence & sourcing: do numeric claims cite a date-stamped source (study, publication, first-party data)?
   • Schema readiness: are FAQs, how-tos, and definitions formatted so Article / FAQ / HowTo schema could be applied without rewriting?
   • Freshness signals: is there a visible "last updated" date and any 2025–2026 reference?
   • Comparison fairness: when competitors are named, are they characterized in a way an engine would repeat (vs. dismissive marketing language that engines tend to skip)?

4. Produce the rewrite plan. For each section that fails the diagnostic, state the specific change: (a) which sentence or heading to replace, (b) the rewritten version, and (c) the reason (e.g., "adds direct-answer lead for the 'What is X?' query" or "isolates the 28% stat for extraction"). Prioritize changes by expected citation lift: direct-answer leads and entity definitions first, then headings and evidence, then schema and freshness.

5. Write the direct-answer blocks. For each target query, produce a standalone 40–60 word paragraph written as the answer an engine would want to quote: subject-first, one claim per sentence, no first-person brand voice, no hedges ("may," "can sometimes"), and no in-sentence CTAs. These blocks go at the top of the section that covers that query.

6. Rewrite the headings. Turn branded or vague headings into the natural-language questions the ICP asks. Keep the target keyword but prioritize the question phrasing that matches how people type or speak to an AI engine. Maintain a sensible H1 → H2 → H3 hierarchy.

7. Add an FAQ block. 4–8 Q&A pairs mapping to the target queries not already answered in the body. Each answer is 40–80 words, self-contained, and safe to lift without context. Mark the block so FAQPage schema can be applied.

8. Apply the cross-engine verification rubric. For each of the five major answer engines (Google AI Overviews, ChatGPT with browsing, Perplexity, Gemini, Claude), note:

   • Whether the engine already cites the current page (if known)
   • Which structural element is most likely to earn citation for that engine (AI Overviews prefers lists + FAQs; Perplexity prefers cited stats + comparisons; ChatGPT prefers entity-clear definitions; Gemini prefers schema-rich structured blocks; Claude prefers sourced, hedge-free prose)
   • One specific edit that would raise citation probability for that engine

9. Build the AEO audit scorecard. A pass/fail checklist the content owner can run on the rewritten draft:

   • Direct-answer paragraph within first 100 words of each H2 (40–60 words, no hedges)
   • Primary entity defined in first 100 words using the canonical name from config.yml
   • At least 3 question-led H2 or H3 headings matching target queries
   • Every numeric claim paired with a source and date
   • FAQ block present, each Q&A self-contained, 4–8 pairs
   • Competitor entities named factually (no adjective attacks)
   • "Last updated" date visible; at least one 2025–2026 reference
   • Article / FAQ / HowTo schema applicable without further rewriting
   • Alt text on images includes entity names
   • Internal links use entity-descriptive anchors (not "click here")

10. Flag assumptions and gaps. Anything assumed (target query priority, competitor citation state, schema currently deployed) that the owner should verify before shipping. If first-party proof points are missing, recommend a specific data capture so the next pass can replace hedged claims.

Output requirements:

• Diagnostic section (what's wrong and why, by section)
• Rewrite plan (ordered by expected citation lift)
• Rewritten draft or tracked-changes rewrite
• Direct-answer blocks (one per target query)
• FAQ block (4–8 Q&A pairs)
• Cross-engine verification notes (5 engines × 1 recommendation each)
• AEO audit scorecard (pass/fail)
• Assumptions & gaps
• Saved to outputs/aeo/ if the user confirms

Calibration Notes

• AI engines reward extractability, not prose quality. A page with beautiful writing but no direct-answer paragraphs loses to a plainer page that leads every section with a quotable sentence. Quotable sentences are 15–30 words, subject-first, single-clause, no hedges, no first-person, and stand alone without surrounding paragraph context.
• Entity consistency matters more than creativity. Use one canonical name for each entity across the site; pull it from config.yml rather than inventing variants. Engines build entity graphs across the site; inconsistent naming dilutes authority on the canonical entity and creates phantom entities the engine doesn't recognize.
• Hedged claims do not get cited. "May help," "can sometimes reduce," "is generally considered" are pass-over language for answer engines. Replace with named-source factual framing — even a hedged claim with a citation outperforms a hedged claim without one.
• Negative adjectives about competitors get skipped. Factual framing ("Competitor X focuses on enterprise contracts and requires a sales call to access pricing") survives extraction; dismissive framing ("Competitor X is bloated and overpriced") does not. AI engines deprioritize content that reads as marketing-team-paraphrased competitor smear.
• Answer-engine citation is a leading indicator of classic rank. Pages that start getting cited by Perplexity or AI Overviews typically see classic rank follow within 30–60 days — stay the course. The reverse is not true: a page can rank in classic search and still be invisible to AI engines.
• First-party data beats third-party citations. Original benchmarks, survey results, and customer outcomes are the highest-leverage upgrade for an already-decent page. Engines disproportionately cite first-party numerical claims because they're harder to dispute and easier to attribute.
• Direct-answer paragraph placement matters more than length. A 45-word direct-answer paragraph in the first 100 words of an H2 outperforms an 800-word section that meanders to the answer. Lead with the answer; explain after.
• Schema markup is the floor, not the ceiling. FAQPage, HowTo, Article, and Product schemas are minimum table stakes for engine extraction in 2026. They don't guarantee citation but their absence is a citation-blocking failure for FAQ-style and how-to-style queries.
• AI engine citation patterns differ enough to warrant per-engine edits. AI Overviews favor list + FAQ structure (47% of cited blocks per Conductor 2026 benchmark); Perplexity favors cited statistics + comparisons (62% of citations include a numerical claim); ChatGPT favors entity-clear definitions (definitional sentences with subject-verb-object structure are 3.2× more likely to be quoted); Gemini favors schema-rich structured blocks; Claude favors sourced hedge-free prose.
• Cited-source freshness compounds. Pages with a visible "last updated" date within 90 days are cited 2.4× more frequently than pages without one (Conductor 2026 AEO benchmark). Rolling refresh cadence beats one-time optimization.
• Don't conflate AEO with link-building SEO. Citation authority and link authority are different graphs. A page can earn AI citations from sources that don't link back; conversely, high-DR pages with no quotable sentences get linked but not cited. The optimization unit is the quotable sentence × the citation source, not the backlink.
• Refresh cadence: AEO scorecard re-run every 60 days for high-priority pages (commercial intent, AI traffic share >5%, current top-3 organic rank); every 90–120 days for everything else. Re-run after any major engine update (Google AI Mode rollouts, Perplexity index refreshes, ChatGPT browsing model upgrades) or any first-party data release that warrants a re-cite.

Anti-Patterns

• The hedged opener — H2 leads with "AI search optimization can sometimes help your content..." instead of a direct-answer paragraph. Engines pass over hedges. Replace with a 45-word factual lead: subject-first, single-clause, no "can," "may," or "could."
• Entity drift across the page — Same entity referred to as three variants ("our platform," "the tool," "ProductName 2.0") in the first 200 words. Engines build entity associations from first mentions; fragmented naming dilutes the canonical entity. Pick one canonical name from config.yml and use it for the first three mentions before introducing variants.
• The buried statistic — A 28% lift number wrapped in a 90-word narrative paragraph. Engines extract numbers that sit in short standalone sentences. Isolate: "The 90-day lift averaged 28% across the n=47 cohort (Threadline 2026 benchmark)."
• Competitor smear — "Competitor X is overpriced and clunky" gets skipped on extraction. Reframe factually: "Competitor X requires a sales-led contract and pricing is not published publicly."
• The undated stat — Numerical claim with no source or date. Engines deprioritize unsourced numbers because they can't be verified. Pair every number with (Source: [name], [year]) in the same sentence.
• Brand voice in the direct-answer block — Direct-answer paragraph reads in the brand's first-person voice ("We believe..."). Engines extract third-person factual prose; first-person brand voice gets paraphrased away or skipped. Write direct-answer blocks in subject-third-person.
• Schema afterthought — Page is structured for FAQ extraction but FAQPage schema is not deployed. Floor-level oversight that costs 30–50% of citation potential on FAQ-style queries. Verify schema deployment in the AEO audit scorecard, not just the on-page structure.
• One-time AEO pass — Page optimized once, never re-run. AEO is a recurring program; engines re-index continuously, citation patterns shift, and competitor pages move. Set the 60-day re-run cadence in the production calendar before declaring the page done.
• The "last updated" lie — Page says "Last updated: 2026" but content is 18 months old. Engines penalize the mismatch when the prose contains stale references (e.g., "in 2024, this was..."). Either refresh the prose or remove the date.
• AEO without first-party proof — Page has perfect structure but every numerical claim is third-party. Defensible but ceiling-bound. Pair structure work with a first-party data capture (benchmark study, customer survey, n-cohort outcome) for the next refresh.

Integration Notes

• Pair with Blog Post Outliner — When the page is a new draft (not yet published), Blog Post Outliner produces the heading hierarchy, direct-answer block placeholders, and FAQ scaffolding pre-AEO; this skill optimizes them post-draft. Sequence: Outliner → write → AEO Optimizer → publish.
• Pair with Topic Cluster Planner — The AEO scorecard run on each cluster page surfaces cluster-level entity inconsistencies (the same primary entity defined three different ways across pillar + cluster + supporting). Route entity drift findings back to Topic Cluster Planner for cluster-level entity-name standardization in config.yml.
• Pair with Persona & ICP Builder — Target-query selection in Required Input #2 should mirror the persona's actual question phrasing, not the marketer's preferred query. Pull verbatim questions from the persona's "where they shortlist" and "what they ask AI engines" sections.
• Pair with Brand Voice Style Guide Generator — The direct-answer blocks must respect the brand voice anti-examples (banned phrases, hedges, marketing-cliche list) while still being engine-extractable. The voice guide's preamble is the constraint set for the direct-answer rewrite.
• Pair with Customer Review & Insight Miner (VoC) — Buyer-language verbatims from the VoC mining surface the actual question phrasings buyers use with AI engines, which often differ from the marketer's preferred query. Use VoC as the source for query selection and FAQ-block phrasing.
• Pair with Competitive Analysis Brief — Competitor pages currently winning citations (Required Input #4) should pull from the competitive analysis's "where competitors win citations" section. If no recent analysis exists, run Competitive Analysis Brief first.
• Pair with AI Search Visibility Audit — The category-level Share of Model output of AI Search Visibility Audit names which engines and which prompt patterns the brand is invisible on. AEO Optimizer is the per-page execution layer for closing those category-level gaps.
• Pair with B2B Buying Committee AI Optimizer — When the page targets a B2B buying committee, the persona-specific direct-answer blocks should serve the underserved persona slots from the AXO scorecard (typically CFO and IT Security). One persona-variant page per underserved cell beats one generic page.
• Pair with Landing Page Conversion OS — When the AEO-optimized page is a conversion page (demo signup, product trial, contact form), Landing Page Conversion OS handles the message-match + decision-flow + friction layer; AEO Optimizer handles citation-extractability. Run AEO first to win the AI traffic, then LPC OS to convert it.
• Pair with Multi-Channel Content Repurposer — The direct-answer blocks and FAQ pairs produced by AEO Optimizer are paste-ready inputs for the Repurposer's email / LinkedIn / Twitter framings. The 45-word direct-answer block is the same building block that anchors a 1,400-character LinkedIn post.
• Pair with Campaign Performance Narrator — AEO citation lift is a leading indicator that should be tracked alongside organic ranking and AI-referred traffic share in the next campaign performance report. Define the comparison baseline (citation count by engine, last 30 days) before the rewrite ships.

Example Output

Input Recap

• Existing content: https://threadline.com/blog/ops-cycle-time-revenue-leading-indicator (1,847 words, published Jan 2026, currently ranks #4 organic for "ops cycle time" but cited by 0 of 5 major AI engines for the target queries)
• Target queries:
  1. "What is ops cycle time?"
  2. "How is ops cycle time measured?"
  3. "Is ops cycle time a leading indicator of revenue?"
  4. "Ops cycle time vs sales cycle length"
  5. "Best tools to measure ops cycle time"
• Primary entity: Ops cycle time (canonical name in config.yml → entities.primary)
• Competitor pages:
  1. clearops.com/blog/cycle-time-metric-guide (currently cited by Perplexity + ChatGPT for queries 1, 2, 3)
  2. revopsleaders.com/2026/cycle-time-leading-indicator (cited by AI Overviews for query 3)
  3. gartner.com/articles/revops-cycle-time-2026 (cited by Claude + Gemini for queries 1, 2, 4)
• Business context: Threadline RevOps Diagnostic, ICP = Series B–D SaaS RevOps leaders, premium pricing posture (annual contract $48K–$120K), differentiator = first-party 47-customer benchmark cohort
• Confidence: high

Diagnostic — Section-by-Section

Rewrite Plan (ordered by expected citation lift)

1. (Critical) Add direct-answer block at top of H2 #1. Replace 184-word brand-backstory lead with a 47-word direct-answer paragraph defining ops cycle time. Reason: query 1 is the highest-volume query and currently has zero citation-eligible structure on the page.
2. (High) Rewrite H2 headings as question-led. Replace "What we measure" → "What is ops cycle time?"; "Why it matters" → "Is ops cycle time a leading indicator of revenue?"; "Compared to other metrics" → "Ops cycle time vs. sales cycle length: what's the difference?". Reason: question-led headings are 2.8× more likely to anchor a citation than branded headings (Conductor 2026 AEO benchmark).
3. (High) Isolate the 21-day claim. Lift the first-party finding from paragraph 3 of H2 #2 into a standalone sentence with attribution: "Ops cycle time leads revenue plan attainment by 21 days in B2B SaaS at 100–500 FTE (Threadline 2026 benchmark, n=47 customer cohort)." Reason: numerical claims in standalone sentences are extracted 3.4× more often than the same claim in narrative prose.
4. (High) Reframe competitor section factually. Replace "unlike sloppy sales-cycle metrics" → "Sales cycle length measures the time from opportunity creation to closed-won and is downstream of ops cycle time. Ops cycle time measures the time spent in cross-functional handoffs and predicts the next quarter's revenue plan attainment." Reason: dismissive framing gets skipped; factual comparison gets quoted.
5. (Medium) Add 6-pair FAQ block before the conclusion. Maps directly to the 5 target queries plus one "How long until I see results?" question. Reason: FAQ blocks are the highest-citation-rate structural element on AI Overviews (47% of cited blocks per Conductor 2026).
6. (Medium) Deploy FAQPage + Article schema. Schema markup deployment moves citation eligibility from "structural" to "machine-extractable." Reason: floor-level move; absence is a 30–50% citation-potential cost on FAQ-style queries.
7. (Medium) Add visible "Last updated: April 2026" date and one 2025–2026 reference in body. Reason: pages with <90-day freshness signal are cited 2.4× more frequently (Conductor 2026).

Direct-Answer Blocks (one per target query)

Query 1: "What is ops cycle time?" (target placement: H2 #1, first 100 words)

Ops cycle time is the total elapsed time a deal spends in cross-functional handoffs between marketing-qualified, sales-qualified, and customer-onboarding stages. It excludes time spent in front of a sales rep and isolates the operational friction in the funnel. In B2B SaaS at 100–500 FTE, ops cycle time averages 18 days and leads revenue plan attainment by 21 days (Threadline 2026 benchmark, n=47 customer cohort).

Query 2: "How is ops cycle time measured?" (target placement: H2 #2, first 100 words)

Ops cycle time is measured as the median time-in-stage across the operational handoff stages of a CRM funnel: marketing-to-sales handoff, sales-to-customer-success handoff, and onboarding-to-renewal handoff. It is calculated per-deal and aggregated as a 30-day rolling median. Median (not mean) is the correct aggregation because outlier deals stuck in handoffs distort the mean (Threadline 2026 methodology).

Query 3: "Is ops cycle time a leading indicator of revenue?" (target placement: H2 #3, first 100 words)

Ops cycle time leads revenue plan attainment by approximately 21 days in B2B SaaS at 100–500 FTE. A 10% reduction in ops cycle time correlates with a 7.4% lift in next-quarter revenue plan attainment (Threadline 2026 benchmark, n=47 customer cohort, FY26). The relationship is causal, not coincident: ops cycle time captures the cross-functional friction that determines whether a deal closes in-quarter or slips.

Query 4: "Ops cycle time vs sales cycle length" (target placement: H2 #4, first 100 words)

Sales cycle length measures the time from opportunity creation to closed-won and is downstream of ops cycle time. Ops cycle time measures the time spent in cross-functional handoffs (marketing-to-sales, sales-to-CS, onboarding-to-renewal) and excludes time spent in active selling. Ops cycle time predicts the next quarter's revenue plan attainment; sales cycle length describes the prior quarter's outcome (Threadline 2026 framework).

Query 5: "Best tools to measure ops cycle time" (target placement: H2 #5, first 100 words)

Tools that measure ops cycle time fall into three categories: (1) RevOps-specific platforms like Threadline that aggregate handoff time across CRM stages; (2) general-purpose CRM dashboards (Salesforce Revenue Intelligence, HubSpot Operations Hub) that require custom field configuration; (3) BI-tool implementations (Looker, Tableau) on top of CRM raw data. RevOps-specific platforms generally produce results in days; CRM-native dashboards in weeks; BI-tool implementations in 4–8 weeks.

Rewritten Heading Hierarchy

H1: Ops cycle time: the leading indicator of B2B SaaS revenue plan attainment
H2: What is ops cycle time?
  H3: How ops cycle time differs from sales cycle length
H2: How is ops cycle time measured?
  H3: Why median (not mean) is the correct aggregation
H2: Is ops cycle time a leading indicator of revenue?
  H3: The 21-day lead time finding (Threadline 2026 benchmark, n=47)
H2: Ops cycle time vs. sales cycle length: what's the difference?
H2: Best tools to measure ops cycle time
H2: Frequently asked questions

FAQ Block (6 pairs)

Q1. What is ops cycle time? A. Ops cycle time is the total elapsed time a deal spends in cross-functional handoffs between marketing-qualified, sales-qualified, and customer-onboarding stages. It excludes time spent in active selling and isolates the operational friction in the revenue funnel. In B2B SaaS at 100–500 FTE, ops cycle time averages 18 days (Threadline 2026 benchmark, n=47).

Q2. How is ops cycle time different from sales cycle length? A. Sales cycle length measures the time from opportunity creation to closed-won — a backward-looking output. Ops cycle time measures the time spent in handoffs and is a forward-looking leading indicator. A team can have a stable sales cycle length while ops cycle time deteriorates, signaling a coming revenue shortfall 3 weeks before it shows up in the closed-won line.

Q3. Why is ops cycle time a leading indicator of revenue? A. Ops cycle time captures the cross-functional friction that determines whether a deal closes in-quarter or slips. Threadline's 2026 benchmark across 47 customers found ops cycle time leads revenue plan attainment by 21 days, with a 10% reduction in ops cycle time correlating with a 7.4% lift in next-quarter plan attainment.

Q4. What's a healthy ops cycle time benchmark? A. In B2B SaaS at 100–500 FTE, the 50th-percentile ops cycle time is 18 days and the 25th-percentile (top quartile) is 11 days. Teams above 24 days typically show revenue plan-attainment shortfalls in the following quarter (Threadline 2026 benchmark, n=47).

Q5. What tools measure ops cycle time? A. RevOps-specific platforms (e.g., Threadline) aggregate handoff time across CRM stages out-of-the-box. Salesforce Revenue Intelligence and HubSpot Operations Hub require custom field configuration. BI-tool implementations on raw CRM data take 4–8 weeks. The platform-native approach typically produces results in days; the BI-tool approach in weeks.

Q6. How long does it take to reduce ops cycle time? A. Most Threadline customers see a 15–30% reduction within 90 days of implementing the diagnostic and acting on the surfaced handoff bottlenecks. The customer cohort that hit the top quartile (sub-11 day ops cycle time) did so within two consecutive quarters (Threadline 2026 customer cohort, n=12 of 47 reaching top quartile).

(Mark this block with FAQPage schema)

Cross-Engine Verification (5 engines × 1 recommendation)

AEO Audit Scorecard (post-rewrite)

• Direct-answer paragraph within first 100 words of each H2 (40–60 words, no hedges) — 5 of 5 H2s
• Primary entity defined in first 100 words using the canonical name from config.yml — "ops cycle time" defined sentence 1 of H2 #1
• At least 3 question-led H2 or H3 headings matching target queries — 5 of 5 H2s are question-led
• Every numeric claim paired with a source and date — 8 numerical claims, 8 sourced
• FAQ block present, each Q&A self-contained, 4–8 pairs — 6 pairs
• Competitor entities named factually (no adjective attacks) — Salesforce + HubSpot + Looker + Tableau named with neutral framing in H2 #5
• "Last updated" date visible; at least one 2025–2026 reference — "Last updated: April 2026"; FY26 referenced 4×
• Article / FAQ / HowTo schema applicable without further rewriting — FAQPage on Q&A; HowTo on measurement steps; Article on root
• Alt text on images includes entity names — image 1 alt = "Ops cycle time vs sales cycle length comparison chart"
• Internal links use entity-descriptive anchors (not "click here") — 4 internal links retitled

All 10 boxes checked. Page is shippable.

Assumptions & Gaps

• Confirmed: competitor citation state (verified by manual prompt-pattern scan Apr 22, 2026); current organic rank (#4 per Ahrefs Apr 26); first-party 21-day claim and n=47 cohort (verified against Threadline 2026 internal benchmark report)
• Assumed: target query priority order (highest-volume query ranked first by SEMrush 2026 keyword data; verify against the actual Search Console click-through data for the page in the next refresh)
• Gap: No outputs/competitive-analysis/ brief exists for Q2 2026 — recommend running Competitive Analysis Brief before next AEO refresh, especially to verify the ClearOps and revopsleaders.com framing
• Gap: First-party customer-quote support for query 5 ("Best tools") is missing — recommend capturing 3 customer quotes naming Threadline as the diagnostic-first tool, to deploy in the next refresh
• Gap: Schema deployment is the engineering team's task — verify with Threadline web team that FAQPage + HowTo + Article schemas can be deployed within 2 sprints

Confidence: high

Refresh Cadence

• AEO scorecard re-run: every 60 days (next: June 27, 2026)
• Re-run immediately after any of: Google AI Mode rollout in this category, Perplexity index refresh, ChatGPT browsing model upgrade, new Threadline first-party benchmark release, competitor major page rewrite
• Annual full-page rewrite (vs. patch refresh) at 12-month mark (Apr 27, 2027)