Supported WordPress versions
WordPress 6.0+, PHP 7.4+, REST enabled, HTTPS, self-hosted.
Requirements
| Requirement | Minimum | Why |
|---|---|---|
| WordPress | 6.0 or newer | Gutenberg block output and the REST endpoints Pressbotics writes to. |
| PHP | 7.4 or newer | Required by the companion plugin. |
| REST API | Enabled and reachable | Everything Pressbotics does goes through the WordPress REST API. |
| HTTPS | Required | Application Passwords are disabled by WordPress over plain HTTP. |
| Hosting | Self-hosted WordPress | You must be able to install plugins and create Application Passwords. |
WordPress.com
Lower WordPress.com plans do not let you install plugins and do not offer Application Passwords. Without either, there is no credential Pressbotics can use and no way to make SEO fields writable. A self-hosted WordPress installation is required. This is a platform limitation, not something a setting on our side can change.
Things hosts and plugins break
- Security plugins that disable the REST API for non-logged-in requests, or block Application Passwords outright.
- Firewalls and WAFs that reject requests from outside your country or from datacentre IP ranges.
- Sites that are not publicly routable. Local, private-network and internal addresses are refused by design.
- Aggressive caching in front of the REST API, which can make a successful write look like a failure.
What to check
Run site_health, or Refresh site info in the dashboard. It reports the detected WordPress version, whether the companion plugin is present, and whether SEO fields are writable — which is faster than guessing. If the probe cannot reach the site at all, the problem is network or hosting, not Pressbotics.