Editorial Policy
What we publish, how we check it, and what happens when we get something wrong.
Last updated: 28 October 2026
How we choose topics
Topics come from real questions — problems we have hit ourselves, things readers ask about, and gaps where the existing answers are forum threads rather than explanations. We do not publish an article simply because a keyword tool reported a high search volume. If we cannot write something more useful than what already exists, we do not write it.
How we check things
- Product details — prices, plan limits, feature claims — are checked against the vendor’s own documentation or pricing page at the time of publication.
- Steps in a tutorial are written against the current version of the software, and we say which version or date they apply to where that matters.
- Where a claim is important, we link to the source so you can check it yourself.
- Where we are uncertain, the article says so. We would rather publish “we have not tested this” than imply we have.
What we will not do
- Invent test results, benchmarks or first-hand experience we did not have.
- Fabricate screenshots, quotes or reviews.
- Publish a positive review in exchange for payment.
- Pad an article to hit a word count.
- Guarantee outcomes — rankings, approval decisions, traffic numbers — that nobody can actually guarantee.
Use of AI tools
This site is about AI tools, so it would be strange not to say how we use them. [ replace this ] — replace this paragraph with your actual practice, and make sure it stays true. A clear, accurate statement here builds more trust than silence does. If AI assists with drafting or editing, say so and say what a human does before anything is published: checking every factual claim, running every step, and taking responsibility for the result.
Corrections
If we publish something wrong, we fix it. Substantive corrections — anything that changes the advice — are noted at the bottom of the article with the date, rather than edited away silently. Typos and broken links are simply fixed.
To report an error, use the contact page and tell us which article and what is wrong. These get handled before anything else.
Updates
Software changes constantly, and a guide that was accurate last year can be actively misleading today. We revise guides when the product changes and show the date on the page. If you find a guide that no longer matches reality, telling us is genuinely helpful.
Commercial content
Affiliate links are disclosed where they appear and explained in the affiliate disclosure. We also offer website services, which are mentioned on the homepage rather than inserted into tutorials. Editorial decisions are not made by whoever is paying — see about Codexs for how the whole thing is funded.
Codexs publishes plain-English guides to AI tools and everyday software for freelancers, creators and small teams.