Question 1

Why did my Chrome extension get rejected?

Accepted Answer

Chrome extensions are commonly rejected for overly broad permissions (like <all_urls>), inline scripts, missing privacy policies, MV2 APIs in MV3 extensions, or policy violations. CheckMyExtension detects all these before you submit.

Question 2

How do I validate my Chrome extension manifest?

Accepted Answer

Paste your manifest.json into CheckMyExtension and click Run Audit. The tool checks 80+ Chrome Web Store policy rules and shows exactly which lines cause violations, with AI-powered fix suggestions.

Question 3

Is CheckMyExtension free to use?

Accepted Answer

Yes. The free plan gives 3 audits per month with no credit card required. Pro plan ($9/month) gives 100 audits/month with AI features, all 5 browsers, and PDF reports.

Question 4

Does CheckMyExtension support Firefox and Edge extensions?

Accepted Answer

Yes. CheckMyExtension validates extensions against Chrome Web Store, Microsoft Edge Add-ons, Firefox AMO, Brave, and Safari policies — all in one tool.

Question 5

How do I migrate from Manifest V2 to Manifest V3?

Accepted Answer

CheckMyExtension includes a MV2 to MV3 migration tool that identifies deprecated APIs and suggests updated equivalents. Upload your extension ZIP and the AI engine highlights every change needed.

Question 6

My Chrome extension failed review — what should I do?

Accepted Answer

If your Chrome extension failed review, upload it to CheckMyExtension to find the exact violation. Common causes are: host_permissions using <all_urls>, remotely hosted code, missing privacy policy, inline scripts, or using MV2 background pages. The tool shows every failing rule with a fix suggestion.

Question 7

How do I check if my Chrome extension will pass review?

Accepted Answer

Use CheckMyExtension before submitting — paste your manifest.json or upload your extension ZIP. The AI runs 80+ policy checks against Chrome Web Store rules and gives a compliance score. A score above 90 means your extension is very likely to pass.

Question 8

Chrome extension not passing review — common reasons?

Accepted Answer

Top reasons Chrome extensions fail review: (1) Overly broad permissions like tabs or <all_urls>, (2) No privacy policy link in manifest, (3) Remotely hosted code or eval(), (4) Misleading description or name, (5) Missing host_permissions for declared functionality, (6) Still using Manifest V2. CheckMyExtension catches all of these automatically.

Question 9

How to check Chrome extension policy violations?

Accepted Answer

Go to checkmyextension.in, paste your manifest.json in the editor, and click Run Audit. The tool checks against all Chrome Web Store Developer Program Policies and highlights violations with severity levels: Critical, High, Medium, and Low.

Question 10

Chrome extension rejected — how long does re-review take?

Accepted Answer

Chrome re-review typically takes 1–3 business days. To avoid multiple rejection cycles, use CheckMyExtension to fix all violations before resubmitting. The tool shows the exact policy reference for each violation so you know exactly what to fix.

Question 11

How to validate manifest.json for Chrome extension?

Accepted Answer

CheckMyExtension provides a free online manifest.json validator with real-time linting. It checks manifest_version, required fields, permission scope, content_security_policy, and 80+ other rules against the latest Chrome Web Store policies.