Skip to main content
WordPress connects to FixAEO in two separate ways, for two different jobs. The plugin captures AI crawler traffic on your server, where a JavaScript tag can’t reach. The publishing connection lets you push Improve recommendations into WordPress as draft posts. They’re independent — set up either, or both.

​
The Agent Analytics plugin

Bots like GPTBot and ClaudeBot never run JavaScript, so a browser tag never records them. This plugin runs inside PHP on every request, spots the AI-looking ones, and forwards them to your agent analytics dashboard.
1

Download the plugin

Open Crawl insights under Agent analytics, choose WordPress in the platform picker, and download the .zip. Your site ID is shown on the same panel.
2

Upload and activate

In WordPress go to Plugins → Add New → Upload Plugin, upload the zip, then activate it.
3

Enter your credentials

Open Settings → FixAEO Agent Analytics. Paste your API key and site ID, then save. Create the API key in your FixAEO account settings.
4

Send a test hit

The settings page has a test button. It confirms the key, the site ID, and your plan in one round trip.
Requires WordPress 5.5 or later and PHP 7.4 or later. Server-side ingestion needs a paid plan — see Plans and limits.

​
How does it avoid slowing your site down?

Capture is one small database write, and it happens during PHP shutdown after the page has already been sent to the visitor. Nothing blocks a request. Uploads run separately: a background job fires every five minutes, batches up to 2,000 buffered rows, and posts them to FixAEO. Non-AI requests do almost nothing. Every step swallows its own errors. A bad key or an unreachable endpoint can’t break your site, and the buffer is pruned as it drains, so it stays small even when delivery is failing.

​
What leaves your server

For AI-looking requests only: the user agent, request path, referer, visitor IP, HTTP status, request method, and a timestamp. Behind a CDN, with the proxy setting on, it also sends the visitor’s country. No post content and no customer data.
The plugin sees requests that reach PHP. If a full-page cache — Varnish, an nginx cache, or a CDN — serves a page before WordPress runs, that hit isn’t counted. On a heavily cached site, use an edge connector instead. The setup panel lists the options.
The settings page also has a “Behind a proxy / CDN” toggle for correct visitor IPs, plus an enable switch. A status panel shows what’s captured, what’s pending, and when the last send happened. Deleting the plugin removes the buffer table, the settings, and the scheduled job. Deactivating keeps your settings and just stops the job.

​
The publishing connection

Separately, you can connect a WordPress site so FixAEO can publish content recommendations to it. Open Integrations in the app and add a site using a WordPress Application Password. That’s built into WordPress 5.6 and later, so no plugin is needed. Once connected, Improve gets a “Publish to WordPress” action. Recommendations always land as drafts, never live posts. You review and publish from the WordPress editor yourself. Connections bind to the current brand, so a multi-brand account keeps its sites separate. You can re-validate a connection at any time, or disconnect it — after which publishing needs a fresh connection.