POLICY / PUBLICATION STANDARD
How UtilityForge decides what can be published, described, indexed, and corrected.
A product claim must be supported by the implementation shown on the page. Local tools name their browser processing. Live-data tools name a provider and freshness state. API directory records require source provenance and verification evidence before becoming indexable.
Planned work is labelled planned, unverified work is not called verified, and a failed or rate-limited provider is not represented as a current result.
Each indexable local tool must have working inputs and outputs, an original description, a method or formula, a concrete example, limitations, FAQs, related tools, and a source/processing declaration. The quality gate rejects pages that lack those elements.
UtilityForge does not publish doorway pages, duplicate tool routes, keyword-stuffed copy, fabricated customer reviews, invented live values, or generic filler presented as expertise.
Source, method, and copy corrections are reviewed against the relevant route and evidence. A correction that changes public meaning should update the page’s review information and, where material, the changelog.
Editorial standards last reviewed: 27 August 2026.