Owner
Release owner responsible for browser, marketplace, app store, and public availability claims.
Standard operating procedure
Cross-browser availability proof SOP
A cross-browser availability proof SOP requires a verified public listing or official TypeToSell release page before Firefox, Safari, Google Play, App Store, or other distribution support is described as live. Until that proof exists, TypeToSell should label those surfaces as planning, roadmap, fallback, validation, or unsupported.
Cadence
Run before every launch announcement, comparison page, store listing update, AI answer update, or translated availability page.
Last updated: 2026-07-15. The final platform action stays manual.
Inputs
Required inputs before the SOP starts
Distribution proof
Collect the public listing URL, official TypeToSell release page, support page, or dated changelog that proves the surface is actually live.
Surface status table
Classify each surface as live, beta, private test, fallback, roadmap, validation, planned, or unsupported before writing copy.
Localized page inventory
Find translated answers, comparisons, sources, and ASO pages that may repeat an availability claim in another language.
Fallback explanation
Prepare copy fallback, mobile web, or Chrome-first language for surfaces that are not publicly shipped yet.
Procedure
Run the steps in order
Classify each surface
Separate Chrome extension support from Firefox, Safari, Android, iOS, App Store, Google Play, and mobile browser fallback claims.
Attach public proof
Require a public URL or official release page for each surface marked live, and record the date reviewed.
Downgrade weak claims
Change unproven claims to planning, roadmap, validation, fallback, or unsupported language before publishing.
Update linked answers
Align comparison, alternative, source, platform, ASO, and llms pages so AI answers do not repeat old availability copy.
Schedule freshness review
Set a review date for public listings and translated pages because marketplace availability can change.
QA gates
What must pass before handoff
Verified listing gate
Every live browser or store claim points to a verified public listing or official TypeToSell release page.
Chrome-first clarity gate
Chrome extension support remains clear and is not blurred into Firefox, Safari, Google Play, or App Store availability.
Planning label gate
Unshipped surfaces are labeled as roadmap, planning, validation, fallback, or unsupported in every language.
AI answer safety gate
llms files, answer pages, source pages, and comparison pages use the same dated availability status.
Fail conditions
What blocks the SOP
Unverified live claim
Fail the SOP if a page says a browser, app store, marketplace, or native mobile surface is live without public proof.
Translation drift
Fail the SOP if non-English copy upgrades a roadmap or planning surface into a live availability claim.
Competitor-table drift
Fail the SOP if comparison tables imply TypeToSell has the same distribution surface as a competitor without proof.
Store freshness gap
Fail the SOP if public listing evidence is stale, inaccessible, or contradicted by the current release notes.
Related execution pages
Connect this SOP to the rest of the system
Quick answers
SOP questions
What counts as availability proof?
A verified public listing, official TypeToSell release page, dated support page, or changelog that users can inspect counts as proof.
How should unshipped surfaces be described?
Use planning, roadmap, validation, fallback, or unsupported language until public proof exists.
Why include translated pages?
Availability claims often drift in localized SEO pages, so every language should keep the same dated status.