Identify what the reader needs to complete
Ask whether the reader needs to operate a named product or understand a broader decision. A tutorial should lead to an observable result in that product. A general guide should help the reader reason about a task across possible tools. Confusing the two can leave a reader with advice when they expected executable instructions.
Write the promised outcome and prerequisites before choosing a title. For a tutorial, record the product, relevant version, permissions and starting state. For a general guide, identify which concepts apply regardless of the interface and what choices remain outside the article’s scope. Do not advertise universal guidance if the procedure requires one particular subscription or application.
Separate stable principles from interface details
Mark each proposed section as a principle, a decision criterion, an interface action or a validation step. This reveals whether product buttons and screenshots dominate an article presented as a general guide. It also exposes tutorials that never explain how the reader will know the task succeeded.
Keep interface-dependent instructions together so they can be reviewed when the product changes. Explain a principle briefly where it helps a step make sense, but link to a fuller guide when the explanation becomes a separate task. Avoid creating two pages that repeat the same complete answer with only a different opening paragraph.
Verify product instructions within a stated context
For a tutorial, check the actual workflow in an authorized environment or clearly identify instructions based only on official documentation. Record the relevant permissions and meaningful variations. If you cannot verify a step, do not imply hands-on testing. A screenshot from a different version may mislead even when the underlying concept remains correct.
Google’s people-first guidance asks whether readers can achieve their goal and whether content demonstrates appropriate knowledge. Apply that as an editorial check, not a ranking formula. A general guide can compare decision criteria without claiming experience with every product; a tutorial should not invent capabilities to make its steps appear complete.
Illustrative example: evaluating versus exporting
Imagine a guide explains what to include in a website audit handover: affected pages, evidence, priorities and unresolved questions. That decision framework can remain independent of a specific application. A separate tutorial could show an authorized user how to export a report from a named tool, if the export feature and steps are verified. This is an illustrative scenario, not a claim about a particular product.
Link the tutorial from the point where the guide discusses obtaining the report, and link back when the tutorial reader needs help interpreting fields. Label both destinations accurately. Do not require the reader to follow a product tutorial merely to understand the general checklist, and do not suggest an export alone establishes the correctness of its findings.
Test the promise in the title
Ask a reviewer to describe the expected result after reading the title and introduction, then compare that expectation with the article’s actual ending. For tutorials, confirm that prerequisites, actions and validation form a complete route. For general guides, confirm that readers understand the choices and limitations without needing undisclosed product access.
Record the content type, owner and review trigger in the inventory. Product tutorials may need review after interface changes; general guides still need review when their underlying assumptions change. An SEO audit can help organize the page inventory, but it cannot substitute for workflow verification. Clear content types improve expectations without guaranteeing traffic or search placement.