How we research, verify, and publish every guide on OmniGuide.
This page explains exactly how our content gets made — where facts come from, how we handle mistakes, and how we keep sponsorships from ever touching our recommendations.
Purpose of this policy
OmniGuide exists to give readers clear, usable answers to real questions. This policy sets out the standards every guide is held to before it gets published — and stays held to after, since a guide is only useful if it stays accurate.
We’re publishing this openly so you don’t have to take our trustworthiness on faith. If any guide falls short of what’s written here, tell us — see the contact section below.
Sourcing and research
Every factual claim on OmniGuide is checked against a primary or authoritative source before publication. In practice, that means we prioritize:
- Official documentation, government sources, or manufacturer information for factual and technical claims
- Original studies or data over second-hand summaries of them
- Recent sources over older ones, especially for anything price-, policy-, or version-related
We do not rely on other blogs or content farms as a primary source. If a claim can’t be verified against something authoritative, it doesn’t go in the guide — or it’s clearly flagged as our own opinion rather than fact.
Authorship and review
Every guide lists its author. [Describe your actual process here — for example: “Guides are written by our founding editor and reviewed by a second team member before publishing” or “All guides are written and fact-checked by the same person; we’re a small team and are transparent about that.”]
Why this matters: Google and AI search systems weight clear, honest authorship information heavily when deciding whether to trust and surface a page. Vague or missing authorship is one of the fastest ways to lose credibility — with readers and with algorithms.
Use of AI tools
[Be specific and honest here — for example: “We use AI tools to help draft and structure some guides. Every AI-assisted draft is fact-checked and edited by a human before publishing, and no guide is published without human review.” Adjust this to match your actual workflow.]
We disclose this because undisclosed AI-generated content — especially content that hasn’t been fact-checked — is a growing trust problem online. We’d rather be upfront about our process than pretend otherwise.
Corrections policy
If a guide contains an error — a factual mistake, an outdated step, or a broken link — we correct it as soon as we’re aware of it. Depending on the significance of the change:
- Minor corrections (typos, broken links, small clarifications) are fixed silently.
- Substantive corrections (a factual error, an outdated recommendation, a changed step) are fixed and the guide’s “last updated” date is refreshed to reflect it.
We don’t quietly delete guides that turn out to be wrong — we fix them, because a corrected guide is more useful than a missing one.
Affiliate and sponsorship disclosure
[State your actual policy clearly — for example: “Some guides on OmniGuide contain affiliate links. If you click one and make a purchase, we may earn a small commission at no extra cost to you. This never influences which products or services we recommend — our recommendations are based on independent research first, and affiliate relationships are added afterward, only where relevant.”]
Any sponsored content, if we ever publish it, will be clearly labeled as such at the top of the guide — never blended in as if it were independent editorial content.
Content freshness and updates
Facts, prices, steps, and screenshots go stale. [State your actual review cadence — for example: “We review our most-visited guides every 90 days and update anything that’s changed.” If you don’t have a fixed schedule yet, say so honestly: “We’re a young publication and are still formalizing a review schedule — for now, guides are updated whenever we become aware of outdated information.”]
Contact us
Spotted an error, an outdated step, or something that doesn’t match this policy? We want to know. Reach us at [your contact email] or through our contact page.
Curious what we’re building?
See this policy in action — browse the guides we’ve published so far.
Browse All Guides