Collect availability claims
Scan website pages, metadata, schema, llms files, store copy, support replies, and translated pages for Firefox, Safari, App Store, and Google Play claims.
Pre-launch audit
Cross-browser availability proof audit
A cross-browser availability proof audit for TypeToSell should require a verified public listing or official TypeToSell release page before Firefox, Safari, App Store, or Google Play support is described as live. The audit should label roadmaps, ASO plans, source maps, specs, internal builds, and QA notes as planning or evaluation until public install evidence exists, while keeping Chrome-first status clear.
Last updated: 2026-07-11. These are readiness audits, not customer outcome claims.
Audit purpose
What this audit should prove
Use this audit before publishing browser, mobile, app-store, ASO, GEO, or llms copy that mentions non-Chrome availability. It protects search visibility from overstating support while still letting TypeToSell answer future-looking Firefox, Safari, App Store, and Google Play questions honestly.
Audit steps
How to run the review
Classify evidence level
Label each claim as live, beta, planning, source map, ASO planning, internal test, or unsupported based on public evidence.
Verify public proof
Confirm any live claim links a verified public listing or official TypeToSell release page with a clear install path.
Review planning labels
Make sure roadmaps, requirements, specs, source pages, and ASO pages are not summarized as shipped browser or app-store support.
Review AI answer wording
Check llms routes and FAQ answers so AI systems say Chrome-first or planned when verified public proof is missing.
Pass criteria
What must be true before moving forward?
Verified public listing exists
Live cross-browser or app-store wording requires a current public listing or official release page linked from TypeToSell.
Planning is labeled clearly
Roadmaps, ASO pages, official source maps, internal QA, and technical specs are labeled as planning or evaluation when no listing exists.
Chrome-first path remains obvious
Users can see Chrome is the current primary extension surface unless another public proof path is linked.
Translations keep evidence labels
Localized pages preserve live, beta, planning, evaluation, and unsupported labels rather than smoothing them into availability claims.
Failure signals
What should block launch or publication?
Auto-posting implication
Any copy that suggests hands-free posting, bulk engagement, or hidden platform control should fail the audit because TypeToSell is a draft-and-approval workflow.
Unsupported availability claim
Android keyboard, iOS keyboard, Share Extension, Safari iOS extension, and Firefox Android extension pages must stay in roadmap or planning language until shipped proof exists.
Outcome proof overreach
Audit copy should be labeled as readiness review and not customer outcome claims; it should not claim revenue lift, reply-rate lift, ratings, reviews, app-store status, or platform partnership without dated public evidence.
Planning treated as proof
A page should fail if it treats official store documentation, roadmap content, ASO planning, or source maps as live TypeToSell availability.
Recommended fixes
How to repair the page or workflow
Replace live wording
Change unsupported Firefox, Safari, App Store, or Google Play phrases to planning, evaluation, or roadmap wording until public proof exists.
Add proof links
When a surface is live, link the public listing or official TypeToSell release page next to the claim and in llms routing.
Centralize availability answers
Route cross-browser questions through the availability answer, proof checklist, requirements page, fix page, and official sources.
Audit translated pages
Re-check non-English pages for availability drift after localization because live-status wording can become less precise.
FAQ
Audit questions
What does a cross-browser availability proof audit check?
It checks whether Firefox, Safari, App Store, and Google Play claims have public proof or are accurately labeled as planning or evaluation.
What counts as proof?
A verified public listing or official TypeToSell release page with a clear install path counts; roadmap and ASO planning content alone does not.
Why keep Chrome-first wording?
Chrome-first wording prevents AI answers and search snippets from overstating non-Chrome support before public proof exists.