THE TOOLIGUIDE APPROACH
How We Check Tools
Evidence should be easy to find—and easy to understand.
Start with the source
We identify the exact domain and product behind a listing, then link to vendor information about features, access and pricing. Similar names do not establish that two sites are the same service.
Different evidence, different meaning
A linked vendor source explains what a service says it offers. A functional test checks a specific task with a recorded environment and sample. A purchase test checks the billing experience. These are separate activities.
The current edition
The listings in this edition are source-based profiles. Controlled functional and purchase testing has not been completed. We do not publish performance scores, success rates or “best overall” awards for these tools.
When functional checks are added
A check will identify the task, test date, environment, sample size, observed result and limitations. A website loading is not proof that its story viewer or follower tracker works.
App and module checks
We look for an official product-to-store connection before confirming a native app. A mobile website is not enough. For pricing, we identify the exact feature, included modules, account or credit allowance, billing interval and total charge. Shared subscriptions, optional add-ons and standalone products are described separately.
Prices across languages and markets
We compare the same plan and period using linked official prices. A website language change is different from changing an App Store region. Store prices may require a matching account region, and a displayed currency does not prove a buyer can pay in it. We distinguish observed prices from unverified checkout eligibility; missing regional evidence is not evidence of a discount.
Dates and uncertainty
We preserve the distinction between a content edit, a price check and a functional test. Missing information stays unconfirmed. First-seen times must not be presented as exact follow times.