How tools are verified
We select tools with a clear user decision, an existing product page and sufficient first-party evidence. Researchers record each source with publisher, title, URL, access date and the exact fields it supports. Official product, pricing, documentation and help pages take priority. Unsupported fields remain null, empty or visibly pending.
Pricing, free access, platforms, major features, integrations, security, ownership, release availability, API access and affiliate status require claim-level evidence. Pricing is rechecked against the official page and is always shown with a check date and a warning that it may change.
How we test
Documentation reviewed means official materials were researched; it is not a product test. Hands-on tested requires a named tester, date, plan, device, browser, reproducible scenarios, evidence and limitations. We do not publish comparative speed or output-quality claims until the same protocol has been applied to every product.
Rating method
Ratings require a documented methodology version, comparable evidence and an editorial score stored in the dataset. A missing numeric score is displayed as not yet rated and never inferred from popularity or affiliate status.
How editorial judgments are formed
Best for maps verified capabilities to a specific audience and job. Not ideal for records a documented constraint or plan boundary. Pros and cons must follow from sourced product facts or a dated, labeled editorial observation. A verdict summarizes fit and limitations; it does not declare a universal winner.
The workflow is research → draft → fact_check → editorial_review → verified. A verified record moves to needs_update when evidence becomes stale, then returns to research. Draft-stage material is not indexed as an editorial review.
Verified, estimated and coming soon
- Verified means the structured facts were checked against official sources and the page was published from that record.
- Estimated is used only when a value can be safely represented as a range or a clearly labeled note.
- Coming soon means the page or section is not published yet and should not be shown as a claim.
How affiliate relationships work
Affiliate destinations are stored separately from official website URLs. A confirmed affiliate link does not change verification status, ranking or recommendations. Sponsored destinations are always labeled and use safe external-link attributes.
Scores
We do not display editorial scores unless a documented scoring methodology exists and the score was produced against that method. Until then, rating fields remain null and the interface says “Not yet rated.”
How often information is updated
Fast-changing AI pricing and features are normally reviewed every 30 days; stable business platforms every 60–90 days; editorial reviews every 90 days; affiliate destinations every 30 days. Corrections update the source, affected claims, verification date and public change history. Readers can report errors through the contact page.
Three evidence levels
- Verified product information: official URL, category, basic features, pricing source and last verified date.
- Editorial review: sources reviewed, claim links, pros/cons, best fit, limitations, reviewer and fact-check complete.
- Hands-on tested: Level 2 plus a complete test record and environment.
Scores remain absent until a published scoring rubric and comparable evidence exist. Popularity, affiliate status and vendor claims never create a score.
How to add a new tool
- Add or update the tool record in
data/tools.json. - Use the existing slug contract to publish the tool page at
/tools/{slug}.html. - Keep unknown facts empty instead of inventing claims.
- Run the validators, check links and publish only runtime files.