Evidence before output
Our process is designed around primary search-engine documentation, reproducible checks, crawl and analytics evidence, and clearly attributed industry research. We do not present a copied archive page, a merchant description, or an AI-generated draft as completed research.
- Define the decision. We start with the problem a reader must solve, not a keyword variation.
- Check primary documentation. Search-engine and platform documentation outrank commentary when a factual rule is available.
- Check the workflow. Actions are tested against observable site behavior, tool output, or a reproducible example where possible.
- Separate fact from judgment. Confirmed needs, working hypotheses, and editorial actions are labelled by context.
- Review after meaningful changes. Pages are revisited when platforms, standards, or search behavior materially change.
Research, experience, and opinion
We distinguish direct observation from second-hand information. When we have not personally used or tested something, we say so through the wording and production notes. Editorial judgment is explained with criteria instead of being disguised as an objective fact.
Use of AI and automation
Automation may assist with source structure, transcription, structured comparisons, grammar, or an initial draft. It may not publish autonomously. A human editor checks claims, links, dates, relevance, and originality. The editor also checks whether the page adds value beyond its sources. Materially AI-assisted pages are marked in their production notes.
Updates
Pages are reviewed when source facts change, a reader reports a material issue, or the topic becomes stale. The visible updated date should reflect a meaningful change. That can be a change to the main content, evidence, structured data, or useful links, not an automatic date refresh.
How a topic becomes a page
The first question is whether the topic represents a distinct decision for the reader. Search demand can help reveal how people phrase the problem. But keyword variation alone is not enough reason to create another page. The intended page needs a clear role within the wider site. It should exist for more than matching a phrase.
How evidence is used
Primary documentation is the starting point when a platform or search engine publishes a direct rule. For work questions, crawl data, rendered output, analytics, and reproducible checks can show how a specific site behaves. Industry research can add context when it is clearly attributed and relevant to the conclusion.
Evidence is not treated as interchangeable. A product page, archived copy, or third-party summary may be useful as a lead. But it does not automatically carry the same weight as the original source or a direct technical observation.
How actions are formed
Research produces facts and observations; the action is the editorial step that connects them to a decision. That action should explain the criteria being used. Where several approaches could work, the page should describe the trade-off rather than presenting one option as a universal rule.
Quality checks before publication
A final review checks whether the page answers the intended question and whether important claims are supported. It also checks that uncertainty is visible and the language is original. Links and dates are checked in context. The editor also looks for unnecessary repetition, vague filler, and statements that sound more certain than the evidence allows.
Method in short
- Define the decision first.
- Check primary documentation.
- Check site behavior where possible.
- Separate fact from judgment.
- Review claims before publication.
- Revisit pages after meaningful changes.