Loading...
Check content for AI right inside WordPress today, with a browser extension and Developer API for building your own integration.
Check posts and pages for AI-generated content before you publish — right inside the block editor, Classic Editor, and Elementor.
Select any text on a page and check it for AI-generated content, without switching tabs.
We're in final testing ahead of submitting the extension to the Chrome Web Store and Microsoft Edge Add-ons. It isn't installable yet — there's no download link because neither listing exists yet. Check back here; this card will switch to a direct install link the moment that changes.
Building something that isn't WordPress? Every integration on this page, including the plugin above, is built on the same Developer API you can use directly.
Every integration connects with the ZeroGPT account you already manage — sign in directly, or use a Developer API key if you prefer.
Requests from any connected tool show up together in your API activity and usage stats.
The browser extension is next. We'll link to it here the moment it's approved.
Integrations, installation, and what each connection mode actually does.
It adds an AI-content check to your WordPress editor. Open any post or page, click "Check for AI content," and you get an AI-likelihood score without leaving the editor — no copying text in and out of a separate tool.
In your WordPress dashboard, go to Plugins → Add New, search for "ZeroGPT AI Content Detector," then install and activate it. You can also download it directly from the official listing linked above.
The block editor (Gutenberg), the Classic Editor, and Elementor. Other page builders, including WooCommerce's product editor, Divi, and WPBakery, are not supported yet.
Yes. Sign in with your ZeroGPT account from the plugin's setup screen — there's no key to create or paste. A Developer API key is only needed if you prefer that connection method instead.
Account Connect is the simpler path for most sites: sign in once and you're done. A Developer API key makes sense if you already manage API keys for other integrations, or want a key you can revoke independently of your login.
Account Connect checks count against the same detection allowance your ZeroGPT account uses on the website. Developer API key checks count against that key's Developer API character allowance instead, which needs Developer API access enabled on your plan.
No. Checking only happens when an editor clicks "Check for AI content" or "Recheck," or — only if you explicitly turn it on — when automatic checking is enabled and a draft meets a length threshold. Nothing is scanned on save or publish.
Only the plain text of the post or page you're actively checking, sent over HTTPS from your server when a check is requested. No other WordPress data — site settings, other users' content, visitor data — is ever sent.
The check fails and the plugin tells you so — it never retries automatically. If it's a rate limit, quota, timeout, or a temporary outage, you decide when to click "Recheck" again.
No. It's read-only with respect to your content — it reads the current draft to send for analysis and shows a result, but never writes anything back into the post.
Detection currently supports English text only.
Not yet. It's in final testing ahead of submission to the Chrome Web Store and Microsoft Edge Add-ons — this page will link directly to both listings the day it's approved.
The full Developer API documentation, including authentication, endpoints, and rate limits, is at Dashboard → Developer API. You can create and revoke keys from Dashboard → Developer API → API Keys.
No. Google's guidance is that AI-generated content isn't automatically against its Search guidelines — the concern is low-quality, mass-produced content. Treat any AI detector, including this one, as an editorial check before publishing, not an SEO requirement or a ranking guarantee.
Still have questions? Contact our support team