Editorial policy

A practical standard for deciding which iPhone Duo questions deserve a page and how claims are presented.

Verification note: This policy is the operating standard for the site’s content system and is designed to prevent thin, duplicated, or overconfident troubleshooting pages.

Quick answer

The short version

A topic needs a distinct intent, a score of at least 13 out of 21, and at least one evidence condition: an official source, two independent sources, or a repeated question with a safe reproducible solution.

Source hierarchy

  • Official Apple product pages, technical specifications, support documentation, or government sources where relevant.
  • Primary technical data or release documentation.
  • Independent tests and documented walkthroughs.
  • Several consistent user reports as supporting context.
  • A single comment is only a demand signal, never proof of a precise fix.

Topic score: 0–21

DimensionPointsQuestion
Demand0–5Is there a distinct, recurring search or user need?
SERP weakness0–5Can we be clearer, safer, newer, or more specific than current results?
Urgency0–4Does the reader need a safe answer now?
Evidence quality0–4Can the claim be verified without guessing?
Cluster potential0–3Will the page strengthen a hub and related guides?
Publication threshold
Publish at 13/21 or higher, plus at least one evidence condition: an official source; two independent sources; or a repeated question with a safe, reproducible solution.

Page and update rules

  • One stable URL should solve one independent search intent and close variants, not every spelling of a keyword.
  • Answer the query early, use original tables or decision trees, and keep FAQs limited to visible questions answered on the page.
  • Update a page when a fact, procedure, product state, or materially useful evidence changes; never change a date only to look fresh.
  • Link hubs to child pages and child pages back to the hub and relevant siblings. Remove or merge overlap instead of creating keyword variants.

Prohibited practices

  • Invented tests, reviews, authorship credentials, user reports, search volumes, or official status.
  • Copied competitor wording, structure, tables, screenshots, or walkthrough order.
  • Mass-produced pages with no independent intent or evidence.
  • Purchased links, fabricated citations, hidden text, doorway pages, misleading schema, or fake urgency.
Evidence boundary

Confirmed

  • The site uses the 0–21 score and 13/21 threshold requested for its operating system.
  • The policy defines fact hierarchy, updates, linking, schema, and prohibited practices.
Needs context

Provisional

  • Scores are editorial prioritization signals, not professional search-volume measurements.
Questions covered here

FAQ

Does a high score guarantee traffic?

No. The score prioritizes useful, supportable work; rankings, indexing, competition, and demand remain uncertain.

Editorial responsibility

Maya Bennett

Independent technology editor for iPhone Duo Help. The byline means this page was checked against its cited sources and its uncertainty is stated; it does not claim Apple employment, repair credentials, or personal testing.

Read the verification method →