What pSEO Guard writes to WordPress

Supported object

pSEO Guard writes standard WordPress Pages through /wp-json/wp/v2/pages. It stores the WordPress numeric ID as the durable identity for later updates.

• Create a Page as Draft.
• Update the same Page by ID.
• Verify the saved Page with edit context.
• Publish an explicitly selected verified Draft.
• Return a published Page to Draft.

Supported fields

Every write can include title, content, slug and status. Parent is included when the plan declares a hierarchy and Preflight confirms that WordPress accepts it.

• title — the Page title.
• content — the Page body sent to the WordPress block-compatible REST field.
• slug — the final path segment.
• status — Draft for ordinary writes; Publish only after explicit approval.
• parent — the already-created WordPress parent Page ID.

Not supported in this release

Do not assume that a field exposed by a plugin is part of the publishing contract.

• Posts or custom post types.
• ACF fields, custom meta and theme-specific options.
• Yoast, Rank Math or other SEO plugin fields.
• Featured images, menus, taxonomies and reusable blocks.
• Permanent delete, redirect creation or automatic canonical changes.

Hierarchy rule

Parent Pages are processed before children. A child resolves the parent’s WordPress ID at write time; if the parent has not succeeded, the child fails visibly instead of being created at the wrong level.