Skip to content
Publishing Principles

Every useful claim needs a source or a boundary

Service copy can influence a purchase, so it should be held to a stricter standard than promotional filler. Our process separates search demand, product truth, editorial judgment and rendered-page verification.

Last reviewed July 2026

  • Product truth before prose
  • Search research with intent review
  • AI assistance disclosed
  • Corrections applied at the source

01Search research is a map, not the answer

Keyword and SERP research helps identify customer language, comparisons and unanswered questions. Competitor repetition does not turn a claim into a fact. We use search data to shape coverage, then verify each commercial statement independently.

02Product truth controls commercial claims

Prices, quantities, caps, variations, currencies, expected starts and eligible delivery modes must come from the current service catalogue or checkout path. A page fails review when its persuasive copy conflicts with those sources.

03Evidence and qualification

Operational statements should be supported by code, provider configuration, order records or a documented policy. Estimates are labelled as estimates. Outcomes controlled by Instagram, TikTok, payment networks or customer changes are not presented as guaranteed.

04How AI is used

AI may assist research synthesis, drafting, structural editing and localization. It is not treated as a source. Prices, legal terms, technical behavior, links and market claims still require human or operator review against the relevant evidence.

05Localization is editorial work

Turkish and Arabic pages can change section order, examples and search phrasing to fit the market while preserving the same product facts. Arabic review also covers right-to-left rendering and mixed-direction numbers and URLs.

06Links, schema and rendered checks

A source file can look correct while the public page has a stale database override, broken link, duplicate schema or wrong canonical. Release checks therefore inspect both content structure and the rendered route in every locale.

07Corrections

Report a factual, pricing, translation or accessibility issue through Reach Us with the page URL and statement. When confirmed, the correction should be made in the controlling source and propagated to affected pages rather than hidden in an isolated exception.

Found something that does not match reality?

Send the URL and the exact claim so it can be checked against its source.

Report a correction