A Competitor Claim Verification Log
Keep one row per competitor claim with five fields: the claim as written, the page it appears on, the source you verified it against, the date you checked, and how volatile it is. Then re-check on a schedule set by volatility rather than by calendar convenience — pricing quarterly, feature availability quarterly, positioning annually. The failure this prevents is specific and expensive: a competitor adds the capability you said they lack, your page keeps saying it, and an assistant quotes your page as the source. You are now the origin of a false statement about a named company, which is a different category of problem from being out of date.
Comparison content is the highest-maintenance content a site has and is almost never maintained. It is written at launch, it is accurate at launch, and nothing about the publishing process revisits it.
The log
| Field | Example | Why |
|---|---|---|
| Claim as written | "Does not offer a self-hosted option" | The exact words that could be quoted |
| Page | /compare/example | Where to fix it |
| Source | Their docs page, linked | Makes re-checking fast |
| Checked on | 2026-09-26 | The shelf life clock |
| Volatility | High / medium / low | Sets the re-check interval |
Volatility decides the schedule
Pricing and tier boundaries move fastest and deserve a quarterly pass. Feature availability moves nearly as fast, particularly anything a competitor is actively building. Company positioning and target market move slowly. Setting one review cadence for all three either wastes effort or misses the volatile claims, which are also the ones most likely to be wrong in your favour.
Negative claims age worst
"They do not support X" is true until the day they ship X, and nothing tells you. Positive claims about a competitor degrade gracefully — a feature they had usually still exists. Negative claims fail in the direction that flatters you, which is exactly the direction that damages credibility when it is caught. Flag every negative claim as high volatility regardless of the category.
When you find a stale claim
Fix the page, and consider saying so. A short note that a claim was corrected costs a line and is the difference between a page that maintains itself and a page that quietly revises history. It also gives a reader a reason to believe the remaining claims were checked, which is the entire value of the log.
Our own log
We maintain one for our comparison pages, and we have corrected claims on them after finding them stale. That is not a claim to be better at this than anyone; it is why the negative-claims section above is specific rather than theoretical.
FAQ
How often is realistic for a small team? — A quarterly pass over pricing and negative claims only. That is perhaps an hour per comparison page and it catches the claims that matter. Everything else can run annually.
Should we link to the competitor's source? — Yes, in the log at minimum, and often on the page. It makes re-checking fast, it makes the claim verifiable, and a comparison that cites the other side's own documentation is harder to dismiss.
What about claims from a competitor's marketing rather than docs? — Record which it was. A capability claimed in marketing copy and a capability documented in a reference guide are different levels of evidence, and quoting the first as established fact is how comparison pages become wrong in both directions.
Put this to work on your own website.
Fenn finds what your customers ask, drafts the articles and site fixes, and measures what ChatGPT, Claude, Gemini, Perplexity and Grok say about you — with every change waiting for your approval.