Resources / Guide

Publishing Review Guide

Get approved faster with accurate disclosures, tight permissions, and reviewer-friendly assets.

MV3 Permissions Privacy Labels Reviewer Q&A

Table of contents

Section snippets

Assets

  • Write benefit-first listing copy; avoid claims you can’t prove.
  • Provide alt text for screenshots. Keep captions factual.

Permissions

  • Justify each permission; prefer narrow host patterns.
  • Use optional permissions where possible.

Reviewer Q&A

  • Prepare short, factual replies; link evidence (logs, screenshots).
  • Answer exactly what was asked; avoid speculation.
Get Store-Ready See Pricing

Templates & checklists

Listing copy template

Benefit-first title & description with do/don’t examples.

Screenshot checklist

Shots that communicate outcomes, not just UI.

Reviewer reply template

Concise structure with evidence links and privacy notes.
Need MV3 migration? Talk to an Expert

Requirements & policy basics

Know which policies apply (user data, limited use, automation) and reference them in your listing.

Privacy disclosures & labels

Labels must reflect real data flows; keep retention and usage wording accurate.

Submission workflow (& re-submissions)

Submit with correct assets, reply quickly to reviews, include logs/screenshots when asked.

Post-approval updates & change control

Document changes, update disclosures, and note permission diffs in release notes.

Edge/Firefox differences

Copy updates to Edge Add-ons / Firefox AMO with small asset and manifest tweaks.

Common rejection reasons (and fixes)

  • Over-broad host permissions → narrow patterns, add optional permissions.
  • Privacy mismatch → align labels to actual data paths.
  • Unclear purpose → rewrite listing copy to emphasize user benefit.