Messages when connecting WordPress
| Message | What to do |
|---|---|
| "SAR Intelligence cannot reach that address" | Enter the site's public address. Check the site is up and opens from outside, without a password or a maintenance page. |
| "That address redirects…" | Enter the address the site ends up on, with or without www and with https, as the message shows. |
| "That address did not answer like a WordPress site" | Check the address. If WordPress lives in a subfolder, include the folder. |
| "The SAR Intelligence plugin is not active on that site" | Install and activate the plugin, then try again. |
| "Application passwords are turned off on that site" | The site needs HTTPS, and a security plugin may have switched them off. See the next section. |
| "The site's host blocked SAR Intelligence" | Copy the ready request SAR shows and send it to your host's support. See below. |
| "That site is already connected" | The site is already in the organization's Sites. No second connection is needed. |
| "You did not approve SAR Intelligence on WordPress" | Start again and approve on WordPress's screen. |
| "That WordPress approval could not be used" | It expired, was used already or came from another site. Start again without a long pause. |
| "The SAR Intelligence plugin did not accept the connection" | Update the plugin and approve as an administrator, not as a user who cannot edit posts. |
Application passwords and security plugins
SAR connects with a WordPress application password. In wp-admin, open Tools → SAR Intelligence and choose Check the connection: it names the setting that blocks it.
- HTTPS: WordPress only offers application passwords over HTTPS. Turn on HTTPS at your host first.
- Wordfence: switch off "Disable WordPress application passwords" in Wordfence → Firewall → All Firewall Options → Brute Force Protection.
- Solid Security: allow application passwords for the user that connects SAR in Solid Security → Settings → Two-Factor, with REST API write access.
- Solid Security, REST API restricted: SAR's own routes still work, but reading WordPress's own content through SAR may be refused.
- Really Simple Security: switch off "Disable application passwords" in Really Simple Security → Settings → Hardening.
- All-In-One Security: switch off "Disable application password" in WP Security → User Security → Additional settings.
- Another security plugin: allow application passwords, at least for administrators.
REST API, headers and hosting
- The check was refused: a security plugin or firewall rule (such as Wordfence or Cloudflare) blocks the REST API. Allow the route
/wp-json/sar-intelligence/. - The site could not reach its own REST API: a firewall, maintenance mode or the server's address settings may be in the way. SAR may still work from outside, so try connecting.
- The host removes the Authorization header, but the fallback arrives: nothing needs changing; SAR uses its own header instead.
- The fallback does not arrive either: ask your host to pass the Authorization header to PHP.
When the host blocks SAR before WordPress answers, nothing on the site can fix it. SAR shows a ready Request to your host: it asks them to allow GET and POST requests to /wp-json/sar-intelligence/v1/, with the Authorization and X-Sar-* headers, and to let the Authorization header reach PHP. Choose Copy, send it to their support, and try again once they reply.
A source stopped working
- WordPress: in Connections, choose Check access. If it keeps failing, check the site is up and the plugin is active. If someone disconnected SAR in wp-admin, connect the site again with Add a site.
- Google, "Needs attention": Google access was removed from the account or expired. Choose Reconnect.
- Google, nothing was connected: the reading box was unticked on Google's screen. Choose Connect again and keep it ticked.
- Google, changes were not allowed: the edit box was unticked. The source stays connected and read-only; choose Allow changes again with both boxes ticked.
- Google says it has not verified the app: choose Advanced, then Go to SAR Intelligence.
- SEO data: if the provider no longer accepts the key, enter a new one under Limits and key.
In ChatGPT or Claude
- A source is missing: in Connections, a Google source with no property chosen shows "Choose a property" and reads nothing. In ChatGPT, also refresh the app's actions in its settings.
- It sees the wrong business: each connection sees one organization. Add a second connector for the other organization.
- A page says the app is not recognised: remove SAR Intelligence from the AI app and add it again.
- It cannot change something: the source is read-only, or your role is Analyst or Member. Ask an owner or admin.
- It says the day's limit was reached: it resets at midnight UTC. See Usage and limits.
Still stuck?
Write to us from the support page. Include your site's address, the message you saw and the results of the connection check. Never send a password: we do not need one.