WordPress site won't connect or sync
Fix API key errors, and sites whose host or firewall blocks SEObolt.
The app talks to your site through the SEObolt plugin's REST API, at /wp-json/seobolt/v1/. Most problems are a wrong API key, or a host firewall blocking requests from the app.
Messages when connecting
| Message | Fix |
|---|---|
| Invalid API key | Copy the API key again from the SEObolt plugin's settings in WordPress. It's a key for that site, not your license key. |
| SEObolt plugin not found or API not enabled | Make sure the SEObolt Pro plugin is installed and active, and that the site's REST API isn't disabled by another plugin. |
| Could not connect to site | The app couldn't reach the site. Check the Site URL, including https://. If it's right, your host is probably blocking the app; see below. |
| This site is already connected | It's already on the WordPress Sites page. |
If your host or firewall blocks the app
Managed firewalls such as Cloudflare's bot protection, Sucuri or a host's ModSecurity often block requests from cloud servers. You can still connect the site: the app saves it and waits for the plugin to send its data.
- Connect the site as usual. If the test fails, the app keeps the site and shows a message about pushing from WordPress.
- In WordPress, open SEObolt β API & Integrations β API Keys and select Push now. This needs plugin version 2.4.147 or later.
The plugin then sends your page list to the app. The site can keep a pending_push status on the WordPress Sites page even after a successful push.
Pushing sends your page list only. 404s and redirects still need the app to reach your site, so if you need those, allow requests to /wp-json/seobolt/v1/ in your firewall.
Note: SEObolt runs on cloud servers without a fixed IP address, so allowing a single IP won't work reliably. Allow the path instead, or lower the firewall's bot-protection level for it.
Allowing SEObolt in Cloudflare
Every request the app makes to the plugin identifies itself with the user agent SEObolt/1.0 (+https://seobolt.io) and your plugin API key.
- In Cloudflare, open Security β WAF β Custom rules and create a rule.
- Match URI Path starts with
/wp-json/seobolt/. You can also require User Agent containsSEObolt/1.0. - Set the action to Skip and tick the protections to skip, including All Super Bot Fight Mode rules if your plan has them.
The free Bot Fight Mode can't be skipped by a rule. If it's on, turn it off for the site or use Push now in the plugin, as above.
Sync says "Please wait"
You can sync a WordPress site once a minute.
Pages missing from Bulk Editor
Bulk Editor finds your pages from a recent plugin push (in the last 48 hours), then the plugin, then your public sitemap. "No sitemap found" means all three were blocked or missing; use Push now in the plugin. If the site shows pending_push, Bulk Editor may still say "No sitemap found", but pages sent with Push now are already listed.
Last updated 2026-10-28