Know what WordPress will allow before the first write
Preflight separates a reachable WordPress site from a connection that can safely create and verify Draft Pages. It is read-only and records the capabilities used by later Jobs.
Last updated
Identity and health
pSEO Guard confirms that the URL is a public HTTPS WordPress origin and that the REST API responds on the same site.
- Private networks, embedded credentials, unsupported ports and the pSEO Guard Worker host are refused.
- Every read-only redirect is checked again and must stay on the connected origin.
- Requests time out after 8 seconds and JSON responses are capped at 1 MiB.
Authentication
Preflight calls the authenticated users endpoint with edit context. A rejected or expired Application Password produces a blocked result and does not change the saved Destination.
- The test must identify the intended WordPress user.
- The test never returns the Application Password.
- A successful HTTP response is not enough if the required capabilities are missing.
Required Page permissions
The connection can be saved only when Pages supports create and update and the user can write title, content, slug and status.
- Parent is optional; a plan that needs parent-child pages cannot proceed unless parent is writable.
- Publish permission is recorded separately and enforced again before a Publish Job.
- Posts and custom post types may be reported by WordPress, but this release writes only standard Pages.
Read-only means no content writes
Preflight uses GET and OPTIONS only. It does not create a test Page, update an existing Page or publish a hidden fixture.
- wroteContent remains false.
- A blocked test leaves any previously saved Destination intact.
- Save is a separate action after the result is visible.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.