Drop your extension .zip into CWS Submission Copilot and get a full pre-submit report: policy code violations, unused permissions, remote code, keyword stuffing, and missing files. All analyzed right in your browser. Nothing uploaded.
Full scan, report, and per-finding fix guidance free forever. Pro adds batch, history, and the listing optimizer.
The Chrome Web Store rejects extensions with opaque policy codes like "Blue Argon" or "Purple Potassium." Three rejections costs you three weeks and, since 2025, you only get one appeal per submission. CWS Submission Copilot names those codes, explains exactly what triggered each one, and tells you how to fix it before you ever submit.
Run your normal build and zip your extension. No special export needed.
Open the Copilot popup and drop your .zip (or .crx). Everything unzips and analyzes in your browser.
Critical findings appear at the top. Each one shows the policy code, the cause, and the exact fix. Patch and rescan until you get a green light.
Full manifest, source, and listing-text analysis with an overall readiness score and a breakdown by severity: blocker, warning, or info.
Every permission is checked against what your code actually uses. Unused or overly broad permissions (Purple Potassium) flagged immediately.
Finds CDN script tags, eval calls, and other patterns that trigger Blue Argon rejections. The most common silent killer of extensions.
Scans your title, description, and keywords for Yellow Argon (keyword stuffing) and Red Nickel (promotional words) before you paste them into the CWS dashboard.
Every finding links to the relevant CWS policy, shows the exact file and line, and tells you precisely what to change.
Export the full scan as plain text or Markdown. Paste into your team chat or ticket tracker with one click.
Guided remediation flow with before/after code snippets, so even complex fixes take minutes not hours.
Rewrites your title and description to maximize keyword relevance without triggering Yellow Argon or Red Nickel.
Track readiness scores across versions, and scan an entire folder of extension builds in one pass.
CWS rejection emails use internal codenames. Most developers never know what they mean. Copilot does.
CDN script tags, external JS imports, and eval-like patterns. The single most common reason for rejection in 2024-2025.
Permissions declared in manifest.json that the code never uses, or broad host patterns like <all_urls> where a narrower match would do.
Repeating the same keyword too many times in your title or description triggers this rejection automatically. Copilot counts keyword density and flags violations before you publish.
Words like "best," "free," "#1," "guaranteed," and similar promotional phrases are disallowed in CWS titles and descriptions.
Icons, referenced scripts, or content scripts listed in the manifest that are absent from the .zip. Copilot cross-checks every declared file against what is actually present.
The full scan and all per-finding guidance are free, forever. Pro adds the power tools.
Never. Your .zip is unzipped and analyzed entirely inside your browser tab. No file, no line of code, and no manifest value ever leaves your machine.
No. CWS Submission Copilot is a readiness signal, not a guarantee. It catches the most common automated and policy-based rejection patterns, but CWS reviewers can still reject for reasons outside the tool's scope. The goal is to remove the avoidable blockers before you submit.
Since 2025, the Chrome Web Store allows only one appeal per submission. If your appeal is denied, the rejection stands and you must create a new submission (and restart the review queue). Fixing every blocker before your first submission eliminates the risk of wasting that single appeal.
Yes. You can paste your title, description, and keywords directly into the listing checker even before you have a build ready.
Yes. CWS Submission Copilot supports both MV2 and MV3. Several Blue Argon and Purple Potassium patterns are MV3-specific, so newer extensions benefit the most.
Standard .zip is the primary format. .crx files are also supported. This is the same .zip you would normally upload to the CWS Developer Dashboard.