Make the page hierarchy explicit in the plan
A page family is easier to review when its hub and child relationships are present in the same page plan. pSEO Guard uses parent_url to surface hierarchy gaps before publishing.
Last updated
What parent_url means
parent_url is optional. When supplied, it identifies the planned parent or hub for that row. It can be an absolute URL or a site-relative path, just like the main URL field.
The parent should appear in the submitted page set
The audit checks the hierarchy inside the page plan you supplied. If parent_url is valid but the matching parent URL is not present in that set, the row receives a Review finding rather than being treated as complete.
- Invalid parent URL → Review
- Valid parent missing from the current page set → Review
- No parent_url supplied → no hierarchy claim is inferred
Do not confuse hierarchy with canonicalization
A parent URL describes page structure. A canonical describes consolidation. Pointing a child page at its hub as canonical is a different decision and should only be done intentionally.
Use Existing Site Guard for live-site evidence
The CSV hierarchy check does not prove that a parent exists on the live site. If the plan will be added to an existing site, run Existing Site Guard separately to compare the proposed set with pages the scanner can retrieve.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.