Home / Editorial policy
Editorial policy
How guides are researched, tested, dated and corrected, and what we refuse to do.
The governing principle
A troubleshooting guide is only worth publishing if it changes the outcome for the person reading it. Everything below exists to serve that one test. If a section of a guide would not change what a stuck reader does next, it does not go in, however good it might be for search.
How a guide gets written
- Start from a real failure state. We identify the specific thing the reader is looking at: the exact error text, the screen it appears on, the point in the flow where it appears. Guides are organised by symptom, not by feature.
- Separate the causes. One error message routinely has several unrelated causes. We work out which ones actually produce it before writing a single step, because a guide that mixes causes gives every reader mostly-irrelevant instructions.
- Walk the fix on the live interface. Steps are performed on the provider's current interface, not copied from documentation. Where the documented behaviour and the observed behaviour differ, we describe what actually happens and say that it differs.
- Write the failure branches. We cover what to do when the main fix does not work, because for a meaningful share of readers it will not.
- Review before publishing. Every guide is read by a second person against this policy before it goes live.
Verification and sources
Where a claim comes from a provider's official documentation, we link that documentation directly in a sources block at the end of the guide, with a note on what it supports. External links open in a new tab and are marked so search engines do not treat them as endorsements.
We do not cite other troubleshooting blogs as sources. If a fix cannot be traced to official documentation or verified by performing it, it does not appear.
Dates and freshness
Every guide displays the date it was last reviewed. This is not decoration. Provider interfaces change without notice, and a step-by-step guide can become wrong without a single word being edited.
A guide is re-checked when we become aware that the interface it describes has changed, when a reader reports that a step no longer matches, and on a routine review cycle regardless. When a guide is revised, the review date is updated. When the change is substantive rather than cosmetic, we say what changed.
Saying what we cannot do
Some account problems cannot be solved by the account holder. Recovery can fail permanently. Some lockouts require information the reader no longer has. Some accounts are closed and gone.
Where that is the case, we say so directly and explain what the remaining options are, including when the realistic option is to start a new account. We consider padding such a guide with steps that will not work to be a failure of the guide, not a hedge.
Use of AI tools
We use software tooling in research, drafting and quality checks. No guide is published on the basis of generated text alone. The substance of every guide (what the error means, which causes produce it, and whether the steps actually work) is established by a person performing and verifying the process, and every guide is reviewed by a person before publication. Accountability for what is published rests with the editorial team, not with a tool.
Advertising and editorial independence
The site carries advertising. Advertisers have no input into what we cover, what we conclude, or how a guide is written, and are not shown guides ahead of publication.
We do not publish sponsored troubleshooting guides, paid placements inside guides, or affiliate-driven recommendations dressed as fixes. If we ever publish anything commercially sponsored, it will be labelled unambiguously as such on the page itself.
Corrections
We would rather be corrected than be wrong. If a step does not match what you see, if an instruction fails, or if something here is simply incorrect, tell us through the contact page and include what you were looking at.
Verified errors are fixed promptly and the review date is updated. Corrections that materially change the advice are noted on the page rather than quietly edited away.