Developer contact email is verified
Why it matters
Chrome Web Store requires a monitored developer contact so users and the review team can report issues, abuse, and policy violations. An invalid or placeholder email (like dev@example.com) means user complaints go nowhere — the store's dispute escalation process routes through developer contact, and unresponsive developers are flagged for suspension. A real contact email is also how Chrome notifies you of impending policy violations before they become removals, making it a practical early-warning mechanism.
Severity rationale
Info because a missing or placeholder contact email blocks user feedback and policy violation notifications but does not directly affect extension functionality or immediate submission.
Remediation
Add a real, monitored contact email to your README and store listing. Avoid @example.com or role addresses you don't check daily.
{
"homepage_url": "https://yoursite.com"
}
In README.md:
## Support
For bug reports or questions: support@yourdomain.com
We respond within 2 business days.
Use an address on a domain you own, not a Gmail alias — it signals legitimacy to reviewers. Set up email forwarding if needed so support requests reach you regardless of which inbox you monitor.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Chrome Web Store Readiness Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- external · chrome-cws-developer-contact — Chrome Web Store — Developer Contact Information Requirement
Taxons
History
- 2026-04-18·v1.0.0·Initial import from extension-store-readiness·automated