An in-house operating model, not a campaign
Most brands approach Answer Engine Optimization the way they approached SEO in its early years: they hand it to whoever has capacity, publish a few updated pages, and hope something changes. Nothing does.
The brands building real Share of Answer in 2026 do it differently. They run an internal operating model — a structured, phase-gated 90-day system that moves them from near-zero presence in AI answers to measurable, defensible recommendation share. They know what their team does in week one, what ships in week five, and what the LBOX dashboard shows on day ninety.
This playbook is that model, built for brand teams running AEO in-house on LBOX as the operating system at every stage, worked through Ardent, a fictional mid-market B2B software brand.
Who it's for: Content Leads who need a production framework built around AI-recommendation logic, not keyword rankings; SEO Leads extending their workflow into answer-engine visibility; Brand Managers protecting how AI engines frame the brand; and VP Marketing / Head of Content making the internal business case, setting the roadmap, and reporting to leadership.
The core premise: AEO is not a campaign — it is a compounding system. The brands that build lasting share treat it as an ongoing operating model, not a one-time project. LBOX is the infrastructure that makes that system visible, measurable, and improvable over time.
The Ardent context: a mid-market B2B SaaS company selling project-management software to operations teams at 200–2,000-employee companies. Their in-house team of four (Content Lead, SEO Lead, Brand Manager, VP Marketing) chose to run AEO internally. They had strong domain authority (DR 58), a 14-page library written for keyword rankings, and zero intentional AEO architecture. Two competitors were already recommended in AI answers for Ardent's core questions — at roughly 31% Share of Answer. Ardent's was near 4%.
The metric everything reports to: Share of Answer
Fix the scoreboard before the phases. Share of Answer (SoA) = the share of answers, on a frozen set of real buyer questions, in which the AI engines recommend you — not merely mention you — averaged over n runs per question × engine, with a confidence interval. Anchor on recommended, not mentioned; score unbranded questions (the market, not the mirror); and report movement as difference-in-differences against a held-out control so a rise is attributable, not coincidental.
How the 90-day model is structured
Three phases, each building on the last. One rule before you start: run Phase 1 completely before producing any new content. The most common in-house mistake is publishing first and strategizing second.
| Phase | Timeframe | Primary objective | Key output |
|---|---|---|---|
| 1 · Baseline & Prioritization | Days 1–30 | Establish the SoA baseline, map question opportunities, align on strategy | Query priority map + production roadmap |
| 2 · Production & Technical Rollout | Days 31–60 | Produce and publish optimized content, ship the technical layer, track first recommendations | Published content, schema, movement report |
| 3 · Optimization & Scale | Days 61–90 | Analyze the data, remediate underperformers, build the quarterly roadmap | Performance report + Q2 roadmap |
Internal roles throughout
In-house AEO has no dedicated account manager or separate strategist — your team wears multiple hats. A named owner beats a committee every time; on smaller teams one person covers two roles.
| Role | Primary responsibilities |
|---|---|
| Content Lead | Brief development, production oversight, writer coordination, publication |
| SEO Lead | LBOX subject setup, question mapping, technical audit, schema |
| Brand Manager | Stakeholder communication, brand-voice review, internal approvals |
| VP Marketing / Head of Content | Phase-gate sign-off, resource allocation, executive reporting |
Phase 1 · Baseline & Prioritization (Days 1–30)
Objective: understand exactly where you stand in AI answers today, identify the highest-value question opportunities, and build a production plan — before writing a word. Phase 1 is the most important phase; everything after depends on the quality of the work done here.
Week 1 — Subject setup & baseline
Focus: configure your LBOX subject and capture a verified SoA baseline before anything changes.
LBOX workflow: in Live View, create your subject, enter your domain, add 2–3 competitor domains, and configure an initial set of 20–30 questions across your core clusters. Run the AI Visibility scan — it returns Share of Answer, Share of Voice, and citation frequency across the full engine panel at once, a single comparable baseline you track for 90 days.
SEO Lead: set up the subject and run the scan; document the day-zero SoA and Share of Voice. Open Answers & Citations and note which competitors are recommended, how often, in what context. Open Sources to see which pages the engines currently lean on.
Content Lead: audit the existing content inventory — URLs, dates, topics, rough organic performance. You need to know what you already have before deciding what to build.
Deliverable: Week 1 Baseline Report (current SoA, competitor recommendation frequency by question, full content inventory), exported from LBOX Report and saved as your permanent day-zero reference.
Ardent: the SEO Lead configured 28 questions across three clusters. Baseline SoA came back at 4%; competitors A and B were recommended in 11 of 28; Sources showed both competitor blogs as the primary cited domains. That gap became the north star.
VP Marketing note: SoA is your executive reporting metric for 90 days. Screenshot it on day one — the movement from day 1 to day 90 is the business case for everything that follows.
Week 2 — Question mapping & prioritization
Not all questions are equal: some are dominated by entrenched third-party sources; others are mid-tail questions where your authority gives a real path to a recommendation quickly. Week two separates them before you invest.
LBOX workflow: open Topics for topic-level performance and gaps, then Query Fanout for the follow-on questions the engines generate — often lower-competition entry points your initial set misses. Promote the best into the tracked set.
SEO Lead: build the Question Priority Matrix — score each question on citation difficulty (per Sources), business value (does it map to a buying decision or product line?), and content feasibility. Use Prompt demand to size weekly question volume. Flag "quick wins" where no source dominates and a well-structured piece could earn a recommendation within 30 days.
Content Lead: flag questions where existing content could be updated rather than replaced — faster than building new, and prioritized where the gap is small.
Deliverable: Question Priority Matrix — Quick Wins (weeks 5–6), Core Targets (by day 60), Stretch Goals (Phase 3+).
Ardent: 7 of 28 were Quick Wins; three existing posts were flagged for structural updates rather than replacement.
Week 3 — Content architecture & briefs
AEO content is architecturally different: the goal is to be the source an engine extracts and recommends, built around self-contained, extractable answers.
LBOX workflow: before any brief, open Sources and study the pages currently cited for your Quick Wins — the pages you must outperform. Every brief enforces three principles: the 40–60 word direct-answer rule (the paragraph the engine extracts; self-contained or it won't be cited), H2/H3 as extraction architecture (mirror follow-on questions from Query Fanout — "What does it cost?" beats "Pricing overview"), and evidence density (specific data points and cited sources get extracted; generic claims don't).
Content Lead: build briefs for the first wave of Quick Wins (5–7), each specifying target question, opening answer, H2/H3 from Query Fanout, evidence requirements; flag existing pages that can be structurally updated.
Brand Manager: review briefs for brand-voice alignment before production, and brief the writers on why the structure exists before they draft.
Deliverable: brief package (5–7) + list of pages flagged for structural update.
Ardent: the brief for "how to track team tasks without a spreadsheet" specified a 52-word opening answer, four H2 sections mirroring Query Fanout, a comparison table, and two cited studies — engineered to beat every currently cited page.
Week 4 — Phase 1 review & production planning
Focus: validate the strategy with internal stakeholders and lock the plan.
LBOX workflow: pull the 30-day report as the backbone of the internal review. Showing your SoA next to a competitor's on a shared screen creates more urgency than a deck.
VP Marketing / Head of Content: review and approve the Priority Matrix and brief package before production (changes after start are expensive); confirm Phase 2 resourcing — who writes, reviews, approves, and the SLA per step (48-hour review SLA is standard); set the reporting cadence — biweekly working reviews plus a monthly executive summary from the LBOX report.
Content Lead: confirm the workflow and writer assignments; establish the review guide — what reviewers check (accuracy, voice, missing context) and what they do NOT change (the opening answer, H2/H3, evidence requirements).
Deliverable: signed-off Phase 1 summary, approved briefs, confirmed Phase 2 plan with named owners and SLAs.
Ardent: the VP reviewed Ardent's 4% SoA against Competitor A's 31%, approved the plan, and set a biweekly cadence with the Content and SEO Leads.
Phase 2 · Production & Technical Rollout (Days 31–60)
Objective: produce and publish AEO-optimized content, ship the technical layer, and run the first SoA check against day zero.
Week 5 — First-wave production
Focus: write and internally review the Quick Win pieces (the 5–7 most likely to earn recommendations in the window).
LBOX workflow: before assigning writers, return to Sources once more and confirm the cited pages haven't shifted since week three — a brief built on week-three data may need a minor update.
Content Lead: manage the workflow and enforce brief adherence; flag drift early — the most common is a writer softening the opening answer into a brand narrative. Push back immediately.
Writer: draft to the brief — self-contained opening answer, question-mirroring H2/H3, evidence density, internal links; each piece with at least one comparison table or structured list, one callout with a specific data point, and a closing section answering a follow-on question.
Brand Manager: review for accuracy and voice, not structure; if a structural element feels off-brand, raise it with the Content Lead before changing it.
Deliverable: reviewed first drafts, ready for publication.
Ardent: five pieces in week five; one section that needed the previous paragraph to stand was rewritten to be self-contained before publication.
Week 6 — Publication & indexing
LBOX workflow: submit each published URL for indexing, then add the live URLs to tracked pages so LBOX monitors them for recommendation events — page-level, not just domain-level.
SEO Lead: submit all URLs for indexing right after publication; add them to tracked pages with dates noted; verify nothing is blocked from indexing.
Content Lead: manage final approval and publication on a 48-hour SLA — delays compress Phase 3.
A critical note on brand review: brand and legal reviews often target the opening answer — shortening, softening, or replacing it with a brand narrative. This is the single most damaging editorial change in AEO; that paragraph is the extraction target. When it happens, open Sources, pull a currently cited competitor page, and show its opening paragraph beside the brief. The comparison persuades better than any explanation.
Deliverable: all Quick Wins published, added to tracked pages, indexing requested.
Ardent: the Brand Manager's request to replace an opening answer with a brand narrative was resolved with the Sources comparison; the original structure was preserved.
Week 7 — Technical audit, schema & AEO review
Well-structured content is necessary but not sufficient — schema tells engines what a page is; crawl issues can stop it being processed at all.
LBOX workflow: run the AEO Audit (Site Health) on the new pages — it flags crawlability issues, bot-blocking, and render/extraction barriers that would prevent a recommendation even from a perfect page.
| Schema type | When to apply | AEO benefit |
|---|---|---|
| FAQPage | Any Q&A section | Increases FAQ extraction |
| HowTo | Step-by-step process pages | Maps to "how to" question patterns |
| Article | All editorial content | Signals content type and authorship |
| Product | Product & comparison pages | Enables structured feature extraction |
SEO Lead: run the audit on all Phase 2 pages and resolve crawlability issues within 72 hours; audit and add/correct schema; verify canonicals.
Deliverable: audit results, schema confirmed, indexing/crawlability report.
Ardent: three of five pages had no schema; the audit flagged one render issue blocking extraction — fixed, with FAQPage added to two pages and Article to all five within 48 hours.
Week 8 — Core Target production & first SoA check
By week eight the Quick Wins have been live ~two weeks — enough for a first check.
LBOX workflow: open Answers & Citations, filter to the ~14 days since publication, and look for new recommendations; check SoA against the baseline. Open Sentiment — if you're named but unfavorably framed, note it for Phase 3.
SEO Lead: build the first SoA movement report (which questions now recommend you, on which engines, and the move from baseline); begin Core Target briefs.
Content Lead: run the biweekly check-in and present the data, even if modest. If zero recommendations after two weeks, escalate to a content audit and read the actual answers — the text usually reveals why a page wasn't cited.
Deliverable: first SoA movement report + Core Target briefs (5–8).
Ardent: the week-eight check showed the first two recommendations (Perplexity and Google AI Overviews); SoA moved 4% → 11%. The VP called them "the most tangible results we've seen from any content investment in two years."
Phase 3 · Optimization & Scale (Days 61–90)
Objective: analyze the data at scale, fix what isn't working, pursue displacement, and build the roadmap for sustained growth beyond day 90.
Week 9 — Full SoA audit & gap analysis
Enough data now to draw conclusions. Use four views in sequence: Answers & Citations (read the actual answers where you're still absent — the text reveals why), Sources (which competitor pages gained/lost frequency — your displacement intelligence), Topics (a whole cluster underperforming is authority-level, not structural), Sentiment (unfavorable framing needs a different fix than a zero).
SEO Lead: run the full audit across all questions and engines; build the Gap Analysis Report (expected vs. actual, difference-in-differences vs. control); flag underperformers (live 3+ weeks, zero recommendations).
Content Lead: diagnose underperformers from the answer text and recommend specific remediation.
Deliverable: full SoA audit + gap analysis.
Ardent: recommendations on 4 of 5 Quick Wins and 2 of 6 Core Targets; the one underperformer's cited competitors all included a price comparison it lacked — diagnosis confirmed.
Week 10 — Remediation & structural updates
Remediation is the normal process of AEO, not failure. For each underperformer, use Sources to compare against the pages that are cited. Actions in priority order:
- Rewrite the opening answer to be fully self-contained (most common fix).
- Add/restructure the evidence layer (specific, cited data).
- Expand H2/H3 to capture missed follow-on questions (updated Query Fanout).
- Add/correct schema if a re-run AEO Audit reveals gaps.
- Build internal links from high-authority pages.
Re-submit for indexing and update tracked pages with the remediation date — a clean before/after for the report.
Content Lead: submit remediation with specific instructions drawn from the answer text; "make it better" produces vague results — name what the cited page has that yours doesn't.
Brand Manager: approve remediation within 24 hours; these are targeted structural fixes, not rewrites.
Deliverable: remediated pages re-published; tracked pages updated with dates.
Ardent: the underperformer's new opening added the price context every cited competitor included: "The best workflow tools for operations managers in 2026 range from $8 to $24 per user per month and are purpose-built for cross-functional task visibility, not general project tracking." Within ten days it earned a recommendation in ChatGPT.
Week 11 — Competitive displacement & stretch goals
By week eleven the Quick Win and Core Target content is performing or remediated — room for more competitive territory.
LBOX workflow: in Sources, filter for questions where a named competitor is cited, sort by frequency; open each cited page and examine its structure against the week-three principles. Use Topics to find adjacent clusters generating competitor recommendations not yet in your set, and add the best.
SEO Lead: identify the 3–5 highest-value questions where a competitor is cited and you have a credible authority claim; build displacement briefs designed to be demonstrably more comprehensive, evidence-dense, and structurally optimized than the cited page.
Content Lead: begin production; set realistic timelines — week-eleven displacement pieces may not earn recommendations until month four or five. Use the SoA trend to show the trajectory.
Deliverable: displacement brief package (3–5) + competitor recommendation-share analysis from Sources.
Ardent: a competitor's cited 900-word overview (no table, no schema, generic opening) was targeted with a 2,200-word guide, a 55-word opening answer, a six-column table, HowTo schema, and three cited studies — the best available answer to that question on the internet.
Week 12 — 90-day report & Q2 roadmap
The 90-day report is both a performance document and a planning asset.
LBOX workflow: generate the final-month report, then build the full 90-day narrative from the week-one baseline plus the current dashboard: SoA day 0 vs. 90; Share of Voice vs. competitors; total recommendation events by engine; competitor share change from Sources; sentiment trend. If the team runs a BI tool, use the LBOX report export / API to pull the data in (confirm the export target for your setup).
| Section | Content | LBOX source |
|---|---|---|
| Executive summary | SoA day 0 vs. 90; top-line wins | Live View overview |
| Movement by question | Per-question: recommendations, engines, dates | Answers & Citations |
| Content performance | Which pages earned recommendations and why | Sources + Answers |
| Competitive position | Share of Voice vs. competitors at day 90 | Visibility + Sources |
| Sentiment | How engines frame you in cited answers | Sentiment |
| Remediation results | Before/after on underperformers | Tracked pages + dates |
| Q2 roadmap | Stretch goals, displacement, new clusters | Topics + Query Fanout |
VP Marketing / Head of Content: present to leadership — every claim traceable to a specific view; build the Q2 roadmap with specific scope (new questions per month, displacement priorities, a month-six SoA target).
SEO Lead: export the full Live View data for the report; update the subject with the Q2 question set so it's ready to run on day 91.
Deliverable: 90-day performance report + Q2 content roadmap with targets and SoA projections.
Ardent: by day 90 SoA reached 29%, up from 4% — 8 recommendation events across 28 questions (4 Quick Win, 3 Core Target, 1 remediated). Competitor A had lost 2 (pages not updated in 14 months). The Q2 roadmap targeted 12 new questions per quarter and a projected 55%+ SoA by month nine.
The complete 90-day deliverable map
| Week | Phase | Deliverable | Owner | LBOX surface |
|---|---|---|---|---|
| 1 | Baseline | Baseline SoA audit + subject setup | SEO Lead | AI Visibility scan, Answers, Sources |
| 2 | Baseline | Question Priority Matrix (3-tier) | SEO Lead | Topics, Query Fanout, Prompt demand |
| 3 | Baseline | Content brief package (5–7) | Content Lead | Sources, Query Fanout |
| 4 | Baseline | Phase 1 summary + production plan | VP Marketing | 30-day Report |
| 5 | Production | First-wave drafts (5–7) | Content Lead / Writers | Sources |
| 6 | Production | Published Quick Wins + indexing | SEO Lead | Tracked pages |
| 7 | Production | AEO Audit + schema report | SEO Lead | AEO Audit |
| 8 | Production | First SoA movement report + wave-2 briefs | SEO / Content Lead | Answers & Citations |
| 9 | Optimization | Full SoA audit + gap analysis | SEO / Content Lead | Answers, Sources, Topics, Sentiment |
| 10 | Optimization | Remediated pages (re-published) | Content Lead | Sources, AEO Audit |
| 11 | Optimization | Competitive displacement briefs | SEO / Content Lead | Sources, Topics |
| 12 | Optimization | 90-day report + Q2 roadmap | VP Marketing / SEO Lead | Full Live View + export |
LBOX monitoring cadence
- Weekly: Answers & Citations, Share of Answer, Share of Voice vs. competitors.
- Bi-weekly: Sources review for new competitor recommendations; internal working review.
- Monthly: full 30-day report shared with VP Marketing.
- Day 90: full Live View export for the performance report and Q2 planning.
Seven rules for in-house AEO teams
1 · Assign one owner before day one. AEO without a single named owner becomes everyone's job, which means no one's. The Content or SEO Lead owns the model end to end. Committees don't run AEO; people do.
2 · Treat LBOX as the operating system, not a reporting tool. Every decision traces to a view: what to target (Topics, Query Fanout), how to structure (Sources), whether it's working (Answers & Citations, Share of Answer), what to fix (answer text, AEO Audit), what to build next (Sources, Topics gaps). A decision not grounded in a view is a guess, and guesses are expensive.
3 · Start with 10–15 priority questions, not 50. In-house teams over-scope. A smaller set produces clear winners, clear underperformers, and a fast learning loop. Expand in Q2 after you understand what the first wave taught you.
4 · Protect the opening answer. It is the extraction target — the most important 40–60 words on the page. Every reviewer will want to soften it; resist consistently, and use the Sources comparison to close the argument.
5 · Review live answers, not just scores. SoA tells you whether you're winning; the answer text tells you why. Read the answers weekly — they reveal which data point triggered a recommendation and what your page is missing.
6 · Plan for remediation from week one. Some pages won't earn a recommendation first time — that's the process working. Build remediation into the Phase 3 schedule as a normal step, not an emergency.
7 · Tie every question to a business category. Each tracked question should map to a product line, use case, persona, or positioning goal. Deprioritize questions that don't; Prompt demand helps size the business value before you invest.
The compounding effect: the first 30 days produce the baseline, the next 30 the first recommendations, the final 30 the data that makes the Q2 roadmap easy to justify. The Share of Answer trend line is the visual proof — show it to leadership at every check-in.
Phase-gate checklists
Phase 1 exit (Day 30): subject configured with 10–30 tracked questions + competitors · baseline SoA saved as the day-zero benchmark · Question Priority Matrix finalized (3-tier) · Prompt demand reviewed for all Quick Wins · brief package approved by VP Marketing (min. 5, each from Sources analysis) · pages flagged for update identified · workflow confirmed · Phase 1 summary presented and plan signed off.
Phase 2 exit (Day 60): all Quick Wins published and tracked · AEO Audit passed, crawlability resolved within 72 hours · schema on all pages · first SoA movement report delivered · Core Target briefs approved and in production · biweekly check-in complete with SoA progress shared.
Phase 3 exit (Day 90): full SoA audit complete (all questions, all engines, vs. baseline, difference-in-differences vs. control) · underperformers diagnosed from answer text, remediated, re-published · displacement briefs delivered · 90-day report presented · Q2 roadmap delivered · subject updated with the Q2 set, ready on day 91.
Red flags — escalate to VP Marketing when
- Zero recommendations at week 8 — read the actual answer text before concluding; remediate if it reveals a structural gap, otherwise call a strategy review.
- AEO Audit failures unresolved within 72 hours — a technical blocker, not a content problem.
- Internal stakeholders requesting structural changes to opening answers, H2/H3, or schema — teach with the Answers view and Sources before approving.
- A competitor's Share of Answer growing faster than yours — revisit the Question Priority Matrix and shift resources between tiers.
- Content production delays exceeding five business days — late content means late recommendations and a compressed Phase 3.
Final note
The 90-day model is not a guarantee — results depend on domain authority, content quality, question competition, and internal approval speed. What it provides is a repeatable, auditable process that gives an in-house team the best possible chance of measurable Share-of-Answer growth in a defined timeframe.
LBOX is the infrastructure that makes the process auditable: every claim in every internal report traces to a specific view, and every decision is grounded in data the team can act on. That transparency is what converts a 90-day experiment into a sustained operating model. Configure your subject, run Phase 1 before you produce a single piece of content, and let the data tell you what to build next.