I test AI tools and report what happened, so the details matter. A wrong price, a misread benchmark or a feature that works differently than I described can send you to the wrong tool. When I get something wrong, I fix it where you can see it and say what changed.
What counts as an error
I treat these as errors and correct them:
- a wrong fact, number, date or price
- a feature, limit or setting described incorrectly
- a quote or claim attributed to the wrong person or company
- a test result reported differently from what the tool actually returned
- a link that points to the wrong source or doesn’t support the sentence it’s attached to
AI tools also change after I publish. A new model, a price change or a removed feature can make an accurate article out of date. I handle that as an update, explained further down this page.
How to report an error
Use the contact page and include:
- the link to the article
- the sentence or section you think is wrong
- a source, a screenshot of your own result, or a short explanation of what you found
A source helps most. I can check a documentation page or a study much faster than a description of one. Please don’t send passwords, private documents or personal data.
What I do with your report
I read every correction request and check the point against the original source. When the error is about a test result, I run the test again with the same prompt and settings, as long as the tool still allows it.
If the article is wrong, I correct it. If I still think the article is right, I’ll tell you why and point you to the source I’m relying on.
How corrections appear in an article
Typos, formatting problems and broken links get fixed without a note, because they don’t change what the article tells you.
A correction that changes a fact, a number, a test result or a conclusion gets a dated note at the end of the article. The note says what the article said before and what it says now, so anyone who read the earlier version knows what changed. For example:
Correction, [date]: An earlier version of this article listed the wrong monthly price for the Pro plan. The pricing table now shows the price from the official pricing page, checked on [date].
If a correction changes my verdict, I also add a note at the top of the article, so nobody acts on the old recommendation. I don’t quietly rewrite or delete an article to hide a mistake.
Updates and retests
Prices, plans, models and features change often in this field. When I update an article for that reason, the “Updated” date under the headline changes and the article says what was updated.
When I run my tests again, the “Last tested” date changes too, and I note how the new results compare with the old ones.
Requests from companies
Companies whose tools I cover can report errors the same way as anyone else, and I correct factual mistakes no matter who points them out. A test result, a score or a verdict stays as it is when a company asks me to change it. If a vendor thinks a test was unfair, I’m happy to look at it again, and the article will say if anything changes.
You can read more about how I work in the Editorial Policy, and about where my information comes from on the Data Sources page.