Page intent
Definition
Page intent is the specific question, decision, or task a particular page is designed to satisfy for a visitor. It translates broad search demand into a page-level job, making it possible to decide whether a proposed URL has a distinct purpose or merely repeats another page.
Why page intent matters in programmatic SEO
A programmatic page family can contain thousands of technically unique rows without containing thousands of distinct page jobs. Page intent gives every row an explicit purpose that can be compared with its siblings, parents, and pages already live on the site.
That matters because URL, title, H1, and keyword uniqueness are structural signals, not proof of a different answer. Defining page intent early helps teams merge synonym targets, keep genuinely different tasks separate, and avoid creating child pages that add nothing beyond a stronger parent.
A simple example
A product comparison page for “X vs Y” may help a buyer choose between two products by comparing price, capabilities, constraints, and use cases. An “X + Y integration” page can involve the same products but answer a different task: whether they connect, how the connection works, and what setup is required.
The entities overlap, but the visitor job changes, so separate page intents can be justified. If two proposed pages both reduce to “help the user choose between X and Y,” changing the title wording does not create a second intent.
Common misconception
“A unique target keyword, title, or URL proves a unique page intent. Those fields can differ while the underlying visitor job remains the same.”
How pSEO Guard handles page intent
pSEO Guard keeps declared page targets beside each planned row so ownership conflicts remain visible during review. Overlap is treated as a signal that needs a decision, not as an automatic instruction to delete or canonicalize one page.
The broader audit also checks whether the planned structure supports the stated intent. Duplicate identifiers, missing evidence, near-duplicate bodies, weak parent relationships, or collisions with existing pages can all show that a supposedly distinct page job is not yet supported by the page plan.