Publish reviewed drafts safely
A successful Draft write is not permission to publish. pSEO Guard keeps content creation, remote verification and human Publish approval as separate steps.
Last updated
Create or update Drafts
Confirming the Dry Run starts a durable Draft Job. Every outgoing request fixes status to Draft, and every page result is saved separately.
- Create claims the page before sending the request so an unknown network outcome cannot be retried into a duplicate.
- Update reads the bound WordPress ID first and proceeds only when the remote Page is still Draft.
- A partial Job preserves successful and failed rows instead of rolling back the entire batch.
Review the per-page record
Job completed means no work remains; it does not mean every page succeeded. Read the success, failed, skipped, mismatch and verification counts before moving on.
- Remote mismatch is deliberately not an automatic retry.
- A normal failed update can be retried after its cause is fixed.
- Refreshing the browser does not erase the durable Job record.
Verify before Publish
Run Verify after the Draft Job. Only a Draft whose WordPress ID, status, title, content, slug, parent and current same-origin link match may become selectable for Publish.
Publish requires a deliberate selection
Nothing is selected by default. Choose the verified Drafts, review the confirmation, then approve Publish as a separate Job.
- Publish permission must have been recorded by Preflight.
- The Page is read again immediately before the status change.
- The final public pathname must match the confirmed manifest.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.