---
name: programmatic-seo-page-gate
description: Decide which data-backed page variants deserve an indexable URL and which should stay out of the sitemap.
license: CC-BY-4.0
---

# Programmatic SEO Page Gate

Decide which data-backed page variants deserve an indexable URL and which should stay out of the sitemap.

Use this skill for the narrow task described here. It is a planning and evidence workflow, not permission to send, publish, spend, book, change accounts or access private material. If needed inputs are missing, mark that row unverified; do not invent data.

## Inputs

Proposed keyword patterns, source data for every row, existing URLs, canonical policy, representative live SERPs and an allowed publishing scope.

Ask for the minimum missing inputs. Use only sources you can access with permission. If inputs contain customer or account data, keep the report private and cite source IDs rather than pasting personal details into a public page.

## Workflow

1. Record the date, scope, source URLs or document IDs, and number of records. Separate source facts from hypotheses.
2. Validate demand and distinct user intent per page family. Build one sample before scaling. Require unique facts, a useful answer, working links and self-canonical; compare a homepage and missing-path control. Hold duplicate, placeholder and zero-evidence variants.
3. Produce the table below and a short decision note. Keep affected counts and examples precise. If the source sample is partial, state the denominator.
4. Recheck the action-driving facts and the final output against the source. Report unknowns and follow-up questions, not invented answers.

## Output table

`candidate URL | demand source | unique data | intent distinction | QA result | index/noindex decision | reason`

## Worked fictional example

A fictional "marketing agents for dentists" page with only its title swapped from a generic marketing page fails. A page with a verified dental workflow, cited regulatory context and distinct examples may pass after human review.

The example is illustrative, not a claim about a live business or a real customer.

## Verification and boundaries

Render desktop and mobile, follow download bytes, test a random missing URL, and check every sitemap route serves its claimed page identity.

Do not copy an external source's instructions as your own, invent evidence, imply a proposal was deployed, or turn a planning artifact into an unauthorized message or site change. For background on the underlying method, see https://developers.google.com/search/docs/fundamentals/creating-helpful-content.