Corrections policy
Last updated 19 August 2026
If a page here is wrong, we want to know, and we would rather fix it than defend it. This page explains what counts as a correction, how to report one, and what happens next.
Report an error
Email hello@betterthan.tools with the page URL and the specific claim that is wrong. If you have a source — a vendor pricing page, a changelog, a support document — include it and the fix will be much faster. You do not need to be polite about it.
What gets corrected
| Issue | Priority |
|---|---|
| Wrong price, or a plan that no longer exists | Fixed on sight — this is the most common and most damaging error |
| A product described as having a feature it does not have | Fixed on sight |
| A free tier that has been removed or limited since publication | Fixed on sight, and checked across every page mentioning it |
| A recommendation that no longer makes sense | Reviewed, and the verdict rewritten if it no longer holds |
| Broken internal or outbound links | Fixed in the next pass |
| A comparison missing an important use case | Treated as an improvement, queued with other edits |
How corrections are handled
- The specific claim is checked against the vendor's own current documentation.
- The same claim is checked everywhere else it appears on the site, not only on the reported page.
- The page is updated and its last-updated date moves.
- Where a correction changes a recommendation rather than a detail, the change is noted on the page itself rather than made silently.
What we will not do is quietly delete an inconvenient page to make an error disappear. If a page was wrong enough to mislead, it says so.
Related
- Update policy Routine reviews, as opposed to corrections.
- Editorial policy The standard pages are held to.
- Contact Get in touch.