I'm getting "We could not reach the WordPress crawler plugin endpoints" when connecting WordPress. How do I fix it?
Updated June 30, 2026 · Reviewed by [email protected]
This error (internally called `plugin_unreachable`) means Trakkr's backend couldn't reach your WordPress site's crawler-plugin REST endpoints, almost always because something at the edge is blocking the request before it reaches WordPress.
The most common cause is Cloudflare (or another WAF) issuing a bot challenge because the request looks unidentified. Trakkr's WordPress connector identifies itself with its own user agent (`Trakkr WordPress Connector/1.0`), so make sure your WAF or security plugin explicitly allows that user agent through to the REST API path, rather than challenging all unrecognized bot traffic. If you're using a caching or compression plugin, also confirm it isn't rewriting or stripping response encoding on those endpoints.
Related questions
- Can I install crawler tracking on a site that isn't Cloudflare, Vercel, Netlify, or WordPress (like Wix, Framer, or a custom PHP site)?
- Connecting my Vercel-hosted site to crawler tracking keeps failing. What's going on?
- Crawler tracking shows visits from some AI bots (like Meta or Mistral) but not others (like ChatGPT or Perplexity), even though I know those engines have visited. Is tracking broken?
- I got a robots.txt or crawler-blocking alert from Trakkr that I think is wrong. How do I check it myself?
- Why does Trakkr say my site is blocking AI crawlers when I can see GPTBot traffic getting through in my own logs?