Read WordPress back before trusting the result
The request that wrote a Page is not the proof. Verification requests the saved WordPress ID with edit context and compares what WordPress now returns.
Last updated
What is compared
Verification checks the object and content that determine whether the planned page is still the same remote Page.
- Numeric WordPress ID.
- Draft status.
- Title, content and slug.
- Parent WordPress ID when the plan has a parent.
- Expected content hash.
- A current HTTP(S) link on the connected origin.
Draft links can use ?page_id=N
WordPress may return a same-origin query link for a Draft even when pretty permalinks are enabled. That is acceptable during Draft verification because the Page is not public yet.
- The link must still come from the current readback and stay on the connected origin.
- The final planned pathname is enforced when Publish is attempted and after WordPress reports the Page as published.
When verification stops
A changed title, body, slug, parent, status, hash or origin becomes a visible mismatch. pSEO Guard does not overwrite a Page whose current identity or state cannot be proved.
- Fix the remote state or update the plan deliberately.
- Run Verify again after the cause is understood.
- Do not treat an old saved URL as proof for the current readback.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.