Spoke
Analyst-style comparative content
Comparison questions are among the most valuable a buyer asks and among the most common an AI engine is given. The format decides whether you can be quoted — a table in HTML can be, the same table as an image cannot.
That machine-readable tables are extractable and images are not follows from how parsing works. That comparative content is disproportionately cited is practitioner observation, not a published finding.
"X versus Y" is a question with a buyer behind it. Somebody asking it has stopped wondering whether to solve the problem and started working out how. Those questions were always commercially valuable in search, and they are exactly the shape of question people now bring to an assistant.
The opportunity is that most organizations will not write honest comparative content, because honest comparison means conceding that something else is better in some circumstance. That reluctance is why the field is open.
Why should comparison tables be HTML rather than images?
Because a machine can read one and not the other. A real table exposes its headers, rows and relationships, so a passage can be extracted and attributed. An image of a table is an opaque rectangle, and a PDF is at best awkwardly parsed — both throw away the structure that made the content quotable.
This is the cheapest mistake to avoid on this list, and designers make it constantly because a rendered image looks tidier.
What makes a comparison trustworthy
Criteria stated first. Before any verdict, say what you are judging on and why those criteria. A reader who disagrees with your criteria can then discount the conclusion intelligently rather than just distrusting you.
Concessions. If the honest answer is that a competitor is better for small teams, write that. A comparison where you win every row tells the reader nothing except that you wrote it.
Scope limits. Say what you did not evaluate. "We did not test the enterprise tier" is a sentence that makes everything around it more believable.
A date. Product comparisons rot faster than almost any other content. An undated comparison is a liability.
The structural pattern that works
Lead with a one-paragraph direct answer naming who each option suits. Then the table. Then a short section per option explaining the trade-off in prose, because a table cannot carry nuance. Then the limits of the evaluation.
That order matters. An engine extracting from this page can take the opening paragraph as a complete answer, or a table row as a specific fact, and be correct either way.
A note on comparing yourself
If you sell one of the things being compared, say so above the comparison, not beneath it. Content that reads as authoritative and unbiased is content a system is more likely to reach for — and undisclosed interest, once noticed, discredits everything else on the page.
The procurement section of this site applies the same standard to the people who publish it, which is the only way the standard means anything.
More in GEO & entities
How AI engines retrieve
Retrieval is what lets a model quote something you published this morning. Understanding it tells you which levers exist — and which widely repeated tactics are aimed at nothing at all.
What Google documents
Google published a guide to showing up in its AI features, and a big chunk of it is a list of popular tactics it says you don't need. That makes it the most useful source in this field, and the most uncomfortable one.
Training vs retrieval
One of these you can change this afternoon. The other changes when somebody else trains a model. Knowing which is which tells you where effort is worth spending and where it is wasted.
Platform matrix
One row per engine, each with its own last-verified date and a link to the platform's own documentation. Where a row could not be verified, it says so instead of being filled in from memory.
Entity consistency
The highest-value work in getting quoted by AI is also the dullest. Describe your company the same way everywhere, give it one stable identifier, and stop handing machines reasons to hedge about who you are.