Editorial Methodology
How tools are built
Every ZeroUtil tool runs entirely in your browser. There are no uploads to a server unless explicitly noted (video and audio tools, where size makes browser-side processing impractical, send the file to our backend at api.zeroutil.com and the result is auto-deleted within 15 minutes). All other tools — text, dev, image, PDF, math, SEO, security — process your input on your machine and never see the network.
How guides are written
Informational guides on this site are produced through a six-stage pipeline: tool audit, competitive scrape, keyword research, draft, editorial review, and publish. The draft and review stages use Claude (Anthropic) under a flat-rate developer subscription. Every draft is keyed to a specific tool, includes a real captured output example, and rotates through multiple prompt-template variants to avoid structural sameness across the corpus. Every guide is reviewed by the editorial team before merging to the live site, soaks on a Cloudflare Pages preview branch for at least 48 hours, and ships with a 7-day window during which no advertising is rendered on the page. AI involvement is disclosed via the byline ("ZeroUtil Editorial Team") and on the editorial-guidelines page. No guide is published with a fabricated rating, a fake credential, or a named human author who did not write it.
Quality bar
- Minimum 800 words of substantive content before the first ad slot is rendered.
- At least one captured example output from the tool the guide is about.
- Source citations for every factual claim that is not a tool-specific observation.
- Strict separation between tool keywords (transactional intent) and guide keywords (informational intent) to prevent cannibalization.
Corrections
Found a factual error? Email us via the contact page. The editorial team reads every message and updates the guide with a visible Last reviewed datestamp on the next build. There is no comment system; corrections happen in the source file and are visible in the page's edit history.