Trust and transparency
ISPbills editorial standards
How we research, write, review and update technical guides, product claims, customer evidence and software comparisons.
Useful evidence before search volume
We publish when the material helps an ISP evaluate, configure or operate a real workflow—not simply to create another page for a keyword.
Technical guides
Guides should identify prerequisites, supported scope, operational risks, verification steps and the current documentation path.
Product statements
Capability claims must reflect the current product. Device, firmware, provider and country-dependent behavior is qualified where relevant.
Comparisons
Comparisons are vendor-authored. We link official public sources, show the review date, distinguish unknowns and recommend direct validation.
Customer evidence
Named facts are attributed to the customer or an available record. We do not publish modeled performance gains as measured customer outcomes.
AI assistance
Automation may assist research or editing, but publication requires human review for accuracy, usefulness, unsupported claims and duplicated material.
Corrections
Material changes should update the visible content and modification date. Readers can report an error through the contact or support channel.
A repeatable check before publication.
Each substantial guide is checked for a clear audience and search intent, original operational value, readable structure, relevant internal links, crawlable references and consistency with current product documentation.
Comparison pages receive an additional source review. Customer pages receive an evidence-boundary review so product imagery, customer-supplied facts and measured outcomes are not confused.
See something that needs updating?
Send the page URL, disputed statement and supporting source. The team will review the correction against current product and public evidence.