Resolve the context first
A guide begins with manufacturer, model family, region, software or firmware version, app version and test date. If a required field is unresolved, the record remains a non-indexed research state.
Grade the evidence
Home Product Support uses four evidence grades. The interface shows the highest grade supporting the answer, while the underlying ledger records the source span and review date.
- Grade A: official standard, manufacturer record or direct reproducible test
- Grade B: qualified review or several credible technical sources
- Grade C: one retailer, forum report or moderated observation—lead only
- Grade D: unverified or generated assertion—never a published fact
Test risk, rollback and expected state
Every step records what should happen, how to reverse it and what settings or data could be lost. A destructive action cannot lead the sequence and cannot publish without a backup or credential warning.
Review, publish and retire
Records pass factual, editorial, accessibility, link, schema and rendering checks. Software releases create stale-content alerts. Replaced instructions keep a visible change record and redirect only when the new answer covers the old intent.
Indexability gate for model pages
A named current or installed-base product hub can be indexed when it identifies the family, exact model pattern, platform variation, first-party support source and relevant diagnostic paths. Shared model-by-symptom routes remain useful for on-site diagnosis but are marked noindex and excluded from XML sitemaps until their instructions and evidence are independently distinct.
Scaled structure without doorway pages
Templates enforce required fields and consistent navigation; they do not license manufacturer-name swaps. Search-submitted answers must own a distinct query intent, direct answer, scope, fault boundary, instructions, risks and evidence. Exact error codes are kept in a separate manufacturer-and-product ledger so a similar code cannot be inferred across platforms.