MotionexaLABS
Record · SpecimenDemonstration file

A finished audit, page by page.

This is a specimen audit for a fictional early-stage SaaS — "a session-replay tool for small product teams." Category, prompts and structure are exactly what clients receive; the data is a demonstration set, marked as such on every page. Your audit looks like this, with your numbers.

Page 01· Share-of-answer scorecard

The number everything hangs on.

Forty-two prompts, five engines, 210 logged answers. The scorecard reduces them to one honest figure per engine: how often you appear at all, and how high in the answer when you do.

In this specimen, the subject appears in 3 of 42 prompts (7% share of answer) while the category leader appears in 31 (74%). That gap — not a keyword ranking — is what the engagement exists to close.

Scorecard · specimen dataRun 01
EnginePrompts citedShare
ChatGPT1 / 422%
Perplexity2 / 425%
Gemini0 / 420%
Claude0 / 420%
AI Overviews0 / 420%
Blended share of answer: 7% · category leader: 74%
Page 02· The prompt log

Every prompt, on the record.

The log groups prompts into four clusters. A sample of each — in the real document, every row links to the full captured answer and screenshot.

Cluster A · Shortlists
  • "best session replay tools 2026"absent ×5
  • "session replay for startups"absent ×4
  • "affordable hotjar-style tools"cited ×1
Cluster B · Displacement
  • "[leader] alternatives"absent ×5
  • "[leader] vs [rival]"absent ×5
  • "cheaper than [leader]"absent ×5
Cluster C · Use case
  • "watch user rage clicks tool"cited ×2
  • "replay + privacy for EU users"absent ×5
Cluster D · Reputation
  • "is [subject] legit?"thin answer
  • "[subject] pricing"outdated
Page 03· Source map

Where the answers come from.

Across the 210 answers, the engines leaned on 61 distinct URLs. Ranked by how many answers each fed, the top of the map decides the work:

  • Review platform, category pagefed 38 answers · subject absent
  • "Best tools" listicle (updated 2026)fed 31 · subject absent
  • Community thread, "what do you use?"fed 19 · subject absent
  • Leader's own comparison pagesfed 17 · hostile framing
  • Subject's websitefed 2 · nothing quotable

The diagnosis memo translates this: the subject isn't being skipped by accident — it's absent from every source the engines trust, and its own site gives them nothing extractable to quote.

Page 04· Fix worksheet, top of the stack

Ranked fixes, with owners and dates.

Fix worksheet · specimen, first 6 of 23 linesRanked by impact ÷ effort
FixWhyEffort
Create review-platform profile + first 10 honest reviewsfeeds the #1 source2 wks
Publish "[subject] vs [leader]" comparison page with current pricingquotable, owns displacement prompts1 wk
Fix Organization/Product schema + entity disambiguationengines mis-resolve the name2 days
Add llms.txt + verify AI crawler accessthree crawlers currently blocked1 day
Pitch inclusion in the 2026 listicle (it updates quarterly)feeds the #2 sourceoutreach
Answer the community thread honestly, with disclosurefeeds the #3 source1 hr
Full worksheet: 23 lines · 9 client-side · 14 we can run in a Sprint
Page 05· What the re-run shows

The delta is the report.

Sprint engagements re-run the identical prompt log monthly. The specimen below shows the format: same prompts, same engines, movement stated plainly, every figure re-checkable in a chat window.

We don't promise a specific delta — engines are probabilistic and categories differ. We promise the measurement will be honest, and the founding-client terms on the rate card put teeth behind run 01.

Delta report · specimen formatRun 01 → 04
MeasureRun 01Run 04
Blended share of answer7%illustrative ↑
Engines citing ≥1 prompt2 / 5illustrative ↑
Reputation prompts answered correctly0 / 6illustrative ↑
Specimen format — your report carries your verified numbers