Dry run
Definition
A dry run is a non-destructive rehearsal of a publishing operation that calculates what would be created, updated, skipped, or blocked without making the intended remote content changes.
Why dry run matters in programmatic SEO
A dry run helps separate planning errors from write-time errors before a large release touches the CMS. It can reveal which local pages map to existing remote objects, which pages would create new objects, which dependencies are unresolved, and whether the proposed release still matches the reviewed source and template version.
The useful property is zero unintended writes. A dry run should produce evidence about the planned operation, not quietly create test pages and call them temporary.
A simple example
A team prepares 200 approved location pages for WordPress. Before writing drafts, a dry run resolves each page against the intended destination and reports which rows will Create, Update, or Skip, along with any page that cannot safely proceed.
The team reviews unexpected updates, fixes unresolved parent relationships, and starts the Draft Job only after the manifest matches the intended release. The dry run reduces uncertainty without requiring disposable public URLs.
Common misconception
“A dry run means publishing a small test page or executing the real job and deleting the result afterward. A true dry run is non-destructive: it evaluates the operation and its dependencies without relying on cleanup to restore the previous state.”
How pSEO Guard handles dry run
pSEO Guard's connected WordPress workflow includes a zero-write Dry Run for reviewed Projects. It builds the deployment manifest, resolves Create / Update / Skip actions, checks destination identity and supported parent relationships, and shows the intended standard-Page write before the Draft Job begins.
Dry Run remains distinct from the browser audit. The audit decides whether a proposed page deserves to move forward; Dry Run reconciles that approved page artifact with the connected WordPress destination so the operator can review the actual release operation before any content write.