01 / layout
AI Reco Report · Snapshot · Illustrative layout
Subject (example only)
Linear.app
Category used for this layout: issue tracking and project management for software teams. Competitors shown as labels only — not findings.
- Product URL
- https://linear.app
- Category
- Issue tracker for software teams
- Competitors named in prompts
- Jira · Asana · Height (prompt inputs, not results)
- Engines
- ChatGPT · Perplexity · Gemini · Claude · Google AI Overviews
- Prompts
- 20 buyer questions × 5 engines = 100 captures
- SLA
- PDF delivered within 24 hours of a cleared order
A real cover carries the run date, the operator initials, and a one-line method note (“logged-in browser users, same-day, same prompt text”). Those fields stay blank on this page so this cannot be mistaken for a finished report.
02 / layout
Contents
What is in a finished PDF.
Page numbers below are typical, not a promise. Length follows how talkative the engines were that day.
- 01Cover and method1
- 02How to read the tables2
- 03Mention / no-mention / wrong-fact matrix (20 × 5)3–5
- 04Who was recommended instead6
- 05Quote sheets — screenshot + verbatim sentence7–9
- 06Wrong-fact log10
- 07Five-item fix list11
- 08Appendix — every prompt, in full12+
03 / layout
Section 03 · Mention matrix
Did the engine name the subject?
Each cell in a real report is one of three marks: mentioned, not mentioned, or mentioned with a wrong fact. The grid below is empty. It does not describe Linear, Jira, Asana, Height, or anyone else.
| Prompt (short label) |
ChatGPT |
Perplexity |
Gemini |
Claude |
AI Overviews |
| Best issue tracker for software teams |
— |
— |
— |
— |
— |
| Best project tool for a 20-person eng team |
— |
— |
— |
— |
— |
| Linear vs Jira for startups |
— |
— |
— |
— |
— |
| Linear vs Asana |
— |
— |
— |
— |
— |
| Alternatives to Jira |
— |
— |
— |
— |
— |
| How much does Linear cost |
— |
— |
— |
— |
— |
| Who should use Linear |
— |
— |
— |
— |
— |
| … 13 more prompts in a real PDF |
— |
— |
— |
— |
— |
Mentioned Subject named, fact-check clean
Wrong fact Named, but a concrete claim was off
Not mentioned Subject absent from the answer
— Placeholder. Not a finding.
06 / layout
Section 04 · Displacement
Who was recommended instead.
When a prompt asks for a pick (“best X for Y”), a real report lists the name the engine led with. The rows below show the shape of that table. The “winner” cells are empty. Filling them would be a claim about Linear we are not making.
| Prompt |
Engine |
Name the engine led with |
Subject in the answer? |
| Best issue tracker for software teams |
ChatGPT |
name reserved |
— |
| Best issue tracker for software teams |
Perplexity |
name reserved |
— |
| Best project tool for a 20-person eng team |
Gemini |
name reserved |
— |
| Alternatives to Jira |
Claude |
name reserved |
— |
| Who should use Linear vs a spreadsheet |
AI Overviews |
name reserved |
— |
A finished page continues for all 20 prompts × any engine that made a pick. We do not invent a “share of voice.”
07 / layout
Section 05 · Quote sheet
Screenshot plus the sentence we will quote.
A real page pairs a browser capture with one verbatim sentence. The boxes below are empty. There is no Linear quote on this site, invented or otherwise.
ChatGPT
status reserved
Prompt 04 · Linear vs Jira for startups
Screenshot placeholder.
A real report pastes the browser window here — URL bar, model name, full answer. Nothing in this box is a capture.
“ ”
Verbatim quote reserved · we do not write one for this layout
Perplexity
status reserved
Prompt 09 · How much does Linear cost
Screenshot placeholder.
Citations, if the engine showed them, appear in the real capture. We do not reconstruct them here.
“ ”
Verbatim quote reserved · we do not write one for this layout
Every one of the 100 answers gets this treatment in the working file. The customer PDF prints the decisive ones and points the rest to the appendix.
10 / layout
Section 06 · Wrong-fact log
Concrete claims that were off.
We only log a wrong fact when a specific, checkable statement fails — a price, a plan name, a platform, a founding year. Tone and taste are not wrong facts. The rows below show columns only.
| Engine |
Prompt |
Claim (verbatim) |
What is true |
Source we checked |
| engine |
prompt # |
No claim written for this layout |
Correction reserved |
linear.app/pricing, or equivalent |
| engine |
prompt # |
No claim written for this layout |
Correction reserved |
Docs or changelog page |
If an engine got every checkable claim right, this page is short. We do not pad it.
11 / layout
Section 07 · Five fixes
The list we always write.
Every snapshot ends with five actions. The categories are fixed so a founder knows what kind of work is coming. The sentences under them, in a real PDF, are written from that run’s quotes. The sentences here are category descriptions — not advice about Linear.
01
Schema
Structured data on the marketing site and docs so engines that read the open web can see product, price, and organization as data, not only as prose.
SoftwareApplication
FAQPage
Organization
02
FAQ
A public page that answers the buyer questions we actually ran — pricing, who should use it, how it differs from the three named rivals — in the same nouns the prompts used.
On-site FAQSame nouns as the prompts
03
Listicle citations
The comparison and “best X” pages that engines already cite. A real report names the URLs that showed up in Perplexity and AI Overviews that day. This layout names none.
Third-party listsURLs reserved
04
Pricing-page clarity
Plan names, seats, and “from” prices written so a model that quotes the page cannot invent a number. Tied, in a real report, to whatever the wrong-fact log caught.
Plan namesPublic “from” price
05
llms.txt
A short, crawlable file at the site root that states product, category, and what the product is not — in the voice we want quoted.
/llms.txtPlain text
12 / layout
Section 08 · Appendix
Every prompt, in full.
A skeptical PM should be able to paste any line back into an engine. Placeholders below use the Linear example subject so you can see the texture. The live library lives in PROMPTS.md.
| # |
Family |
Prompt as run (example subject) |
| 01 |
Best X for Y |
What is the best issue tracker for software teams in 2026? |
| 04 |
X vs Z |
Linear vs Jira for a startup engineering team. Which should I pick and why? |
| 08 |
Alternatives |
What are the best alternatives to Jira for software teams? |
| 12 |
Pricing |
How much does Linear cost? What is on the free plan versus paid? |
| 16 |
Who should use |
Who should use Linear, and who should pick something else? |
| — |
15 more |
Printed in full in a real appendix. See PROMPTS.md for the reusable library with {{product}} placeholders. |