Feature Badge Rejection for Extension Without Clear Reason
Yixian Wang
Hi,
I am seeking help regarding my extension SwiftApply – AI Job Application Autofill (ID: gdpkgfdddmdlkebdhpofaignhdnoflgd).
I recently self-nominated it for the Featured badge, but the request was rejected with a very general reason:
"It doesn’t meet our compliance best practices."
I have carefully reviewed the documentation links provided (General best practices, Developer policies, etc.), but I still have no idea what specific compliance issue applies to my extension.
A few points to clarify my setup:
-
Manifest V3 is used.
-
A Privacy Policy is provided.
-
Only required permissions (cookies, storage) are requested, with clear explanation at submission.
-
Images are clear and the listing is complete.
-
The extension is functional and fully accessible: it has a free plan with all core functionality available (with usage limits) and no login wall.
I also looked into the possibility found in this group that mentioned content scripts running on all_urls might be an issue.
This is necessary because many job application forms are dynamically loaded inside iframes (e.g., Greenhouse).
Because of CORS restrictions, I rely on postMessage to communicate between iframe and top window — a practice I understand to be compliant. And i believe this is the only way to handle it, because only top frame is responsible for rendering ui, and it does not have access to iframes elements.
Despite trying to explain this to support via email, the response was just a standard reply stating they don't offer 1:1 support.
Can someone help me understand what exactly is considered non-compliant in my case?
I am happy to make any necessary adjustments if I can get more specific feedback.
Thanks so much for your help!
Best regards,
Yixian Wang