Why Do Clear Opinions With Reasoning Work Better Than Neutral Overviews in AI Answers?
Clear opinions with reasoning work better than neutral overviews because an assistant can write a neutral overview itself, but it cannot invent a well-argued judgement backed by evidence. Many questions people ask AI are decisions: which option, whether to do something, what to avoid. A page that says "choose X if..., choose Y if..., because..." maps directly onto the answer. A page that lists pros and cons without concluding gives the assistant nothing it did not already have. Tone is not the main reason, though. The research that coined "generative engine optimization" found that making text more persuasive and authoritative gave no significant gain. Adding sources, quotations and statistics raised visibility by 30 to 40%. What works is a position with its reasons and evidence attached.
What does the research actually show?
Aggarwal and colleagues tested nine ways of rewriting web content and measured how visible each rewrite became in AI-generated answers. Their findings, published at KDD 2024:
- Cite Sources, Quotation Addition and Statistics Addition performed best, improving visibility by roughly 30 to 40% on their main measure.
- An "Authoritative" rewrite, making the style more persuasive and confident, gave no significant improvement. The authors concluded that generative engines were "already somewhat robust" to such changes.
- Keyword stuffing did not help.
- The gains were largest for lower-ranked sources. Pages that were not top search results benefited most from adding evidence.
So the lesson is not "sound confident". It is "say something specific and show why it is true". A clear opinion with reasoning is one way of doing exactly that.
Why do reasoned positions fit AI answers so well?
- Decision questions need a verdict. "Should a 10-person agency use Pelmark or Quellwick?" wants a recommendation with conditions. A page that commits, with reasons, supplies it.
- Reasons are quotable. "Quellwick suits small sales teams because its pipeline view needs almost no setup, while Pelmark's strength is marketing automation, which a 10-person agency may not use yet" can be lifted into an answer intact.
- Neutral overviews are commodity content. The standard list of pros and cons exists on hundreds of pages, and the model has seen it many times. Your version adds nothing distinctive. Google's own guidance encourages non-commodity content.
- Conditional advice matches long prompts. People describe their situation to assistants. "If you have fewer than 20 users and no developer, choose X" matches that situation directly.
- Answers attribute views. Assistants often present positions as "According to [source]...". A page with a clear view is easier to attribute than one that says nothing in particular.
When decision-stage content leads to enquiries, it pays twice. That is covered in whether decision-stage pages drive inbound leads from AI answers.
Does confident language work better than hedging for AI content extraction?
Mostly not, according to the research above. Across all query types, a more persuasive and authoritative style gave no significant gain, although the authors found it did help on debate-style and history questions. Evidence helped far more and far more consistently. But heavy hedging does hurt, for a practical reason. It removes the claim an answer could extract.
Compare:
- Hedged: "Some businesses may find that certain CRM tools could potentially offer benefits depending on various factors."
- Precise: "For sales teams under 10 people, Quellwick is usually the faster setup: most teams we have onboarded were running their pipeline within a day. Larger teams that need marketing automation are better served by Pelmark."
The first contains no statement to quote. The second contains two, with a condition and a piece of evidence.
The fix is precision, not bravado:
- Replace vague qualifiers with conditions. Instead of "may not suit everyone", write "does not suit teams that need on-premise hosting".
- State uncertainty exactly where it exists: "we have tested this with teams up to 200 users; beyond that we have no data".
- Keep genuine caveats. Removing a real limitation to sound confident makes the page wrong, and answers will repeat the error.
How do you write a reasoned position?
- Answer the decision in the first sentence: "For most small agencies, we recommend Quellwick over Pelmark."
- State the conditions under which the answer changes: team size, budget, existing tools, regulatory needs.
- Give the reasons, one per point, each with evidence: a test, a figure, a customer example, a documented feature.
- Say who should choose differently, and why.
- Show your basis: what you tested, when, and any interest you have, such as selling one of the options.
- Date it, and update it when the facts change.
A useful template for comparison pages:
| Situation | Our recommendation | Main reason | Evidence |
|---|---|---|---|
| Under 10 users, sales-focused | Option A | Fastest setup, lowest cost | Setup time in our tests; list prices |
| 10 to 100 users, marketing and sales | Option B | Built-in marketing automation | Feature documentation |
| Regulated industry | Option C | EU data residency and audit logs | Security page; certifications |
When should you stay neutral?
- When the evidence genuinely does not favour one option. Say so, and explain what would tip the choice.
- On contested health, legal or financial questions, where a recommendation needs professional context. Explain the options and the factors, and point to qualified advice.
- When you have an interest you cannot disclose. A biased verdict presented as neutral misleads readers, and assistants may repeat it as if it were independent, which is exactly why an undisclosed interest is a problem.
Neutral does not mean empty. Even a balanced page can state the conditions under which each option is better.
Are there risks in taking a position?
- Being wrong in public. Opinions based on weak evidence get repeated and then challenged. Base positions on tests, data or clear experience.
- Conflicts of interest. If you sell one of the options, disclose it prominently. A fair verdict that sometimes recommends a competitor is more credible than one that always picks you.
- Going stale. A recommendation from two years ago may now be wrong. Review positions when products, prices or rules change.
- Contradicting yourself. Different pages recommending different things confuse answers. Keep one canonical view per question.
How consistency and clarity compare with sheer volume is covered in whether clarity and trust matter more than publishing volume for AI visibility.
What might an illustrative case look like?
Consider an illustrative IT consultancy with a long "Cloud backup options explained" page that described six services neutrally and concluded "the right choice depends on your needs". AI answers to "which cloud backup should a small law firm use?" never cited it. The firm rewrote the page. It opened with a recommendation for small law firms, a table of three situations with a pick for each, and reasons tied to its restore-time tests and each service's data residency terms. It also disclosed which services it resells. Within two months, answers began citing the page for law-firm and small-office questions, often quoting its restore-time figures.
What do people ask about opinions and AI answers?
Will AI answers repeat our opinion as fact?
Sometimes they attribute it, sometimes not. That is why the reasons and evidence matter: they keep the claim accurate when it travels.
Should every page take a position?
No. Reference pages, documentation and definitions should be accurate and neutral. Decision pages benefit most from a clear view.
Does a strong opinion hurt trust if it favours our product?
Only if it is unfair or undisclosed. Disclose your interest and say when a competitor is the better choice.
Is persuasive writing useless for AI?
Persuasive style alone showed no significant gain in research. Persuasive evidence is what counts.
Published by The Kovmere Team · updated Sep 29, 2026 · More resources