Page plan
Definition
A page plan is the full pre-publish record of proposed pages and the information needed to review them before they go live. It connects page identity, intent, URLs, hierarchy, source evidence, rendered fields, and the decisions that determine which candidate pages should move forward.
Why page plan matters in programmatic SEO
The plan keeps the reason for a page attached to the page itself. Without that record, a generated URL can outlive the intent, source evidence, relationship, or eligibility rule that originally justified it, leaving future editors to reverse-engineer why the page exists.
A durable page plan also separates generation from publication. Rows can be kept, merged, excluded, or sent to review before a CMS import or static build makes them public. That distinction becomes increasingly important as the number of candidate pages grows.
A simple example
A page plan for location pages might record the intended search job, proposed URL, title, H1, canonical, parent URL, local availability, source record ID, body evidence, and a decision such as Keep, Review, or Exclude for every row.
If two rows share a target intent, one may be merged. If a service is unavailable in a city, that row can be excluded while retaining the reason. If the planned URL collides with an existing page, the plan can record the remediation before publication.
Common misconception
“A CMS import or exported CSV is the page plan. Those are delivery formats; the plan is the underlying decision model that should exist before them and remain understandable afterward.”
How pSEO Guard handles page plan
pSEO Guard audits planned rows before publishing and keeps findings tied to the specific proposed URLs. Rather than reducing a batch to one score, it records page-level reasons so reviewers know which rows are Ready, which need Review, and which findings should Block publication.
A page matrix can be one way to construct the plan, while the audit adds quality decisions and, when requested, existing-site evidence. Together they keep the page family reviewable before it becomes an operational maintenance problem.