What’s new in pSEO Guard
This changelog covers changes you can see or act on. Internal refactors, test maintenance and development bookkeeping stay out of the way.
Last updated
August 2026 — Controlled WordPress publishing is available
Reviewed Projects can now connect to WordPress and move through Dry Run, Draft Deployment, verification, explicit Publish, retry and rollback without losing the page-level decision trail.
- Use a dedicated WordPress Application Password and run the zero-write Connection Test before Save.
- Draft and Publish Jobs preserve stable WordPress object IDs for updates.
- Partial failures remain visible by page; retry failed only does not repeat successful writes.
- Verification and rollback keep remote mismatches explicit instead of treating an uncertain write as success.
August 2026 — Plan, audit and check before publishing
pSEO Guard now connects the three steps that matter before a large page set goes live: build or import the plan, review its quality, then check it against pages that already exist.
- Audit page plans with Ready, Review and Blocked decisions instead of a single score.
- See when content checks could not run or could not compare every page, rather than treating missing evidence as a pass.
- Build a Page Matrix from structured inputs and export the full page plan with its source data.
- Check planned URLs, titles and body content against an existing public site before publishing.
- Open a dedicated Rule Reference from audit findings to understand why an issue appeared and how to fix it.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.