Pages

Pages contains the project’s discovered page inventory. It is scoped to the project’s effective blog-path prefix. Discovery combines page content, Google Search Console evidence, configured thresholds, exclusions, cooldowns, and active Experiment state to identify Opportunities.

Pages has two views. Search Console contains the performance chart and range-aligned inventory. Insights leads with contradictions that merit attention: strong search traffic with weak engagement, stable visibility with falling CTR, valuable pages with low search exposure, and important pages with little observed continuation. Ordinary weak pages are not badged simply for being weak. Use Needs attention to filter the inventory to active findings.

Below those findings, Search movement shows which visible Pages changed average Search Console position and clicks. It is a diagnostic, not a literal rank history: page-level position is an impression-weighted average across queries. Focusing a movement cohort narrows the chart and inventory to the movers currently drawn on the board.

The shared range supports 24 hours, 7 days, 28 days, 3 months, the available 480-day history, and an inclusive custom start/end date. Daily ranges compare with the immediately preceding equal-length period. Insights use clicks and impressions for attribution; CTR and position remain supporting context.

Each row is identified by its full Search Console URL, not only its path. Domain properties can include an apex domain and several subdomains with the same path, so Pages keeps their metrics, keywords, status, and Experiment history separate. The table shows the path as its main label, the hostname beneath it, and the exact URL on hover.

When GA4 is available, Pages shows revenue for properties that report it; otherwise it shows conversions. Conversions is the aggregate number of all events marked as key events in the selected GA4 property for sessions that started on that page. GA4 remains a separately labelled 28-day enrichment; changing the Search Console range does not change revenue or conversions.

SERPclimber queues the first discovery automatically when a new project has a usable Google Search Console property or matching site-managed project history. Use Run discovery to retry or refresh the inventory later. If neither source is available, connect and select Google Search Console before retrying.

Opportunity requests are scoped to one project by default and use that project’s effective blog-path prefix. Stale inventory and Pages outside the configured prefix can be inspected, but they are not recommended or automatically selected for an Experiment. Cross-project reports must be requested explicitly and identify the project for every row.

General site-wide page questions use Search Console directly instead of the project Pages inventory. Those results contain URLs known to Search Console for the requested period, not necessarily every URL in the publishing system. A request for Pages outside the blog path applies the project’s effective prefix on the server.

Pages can be filtered using the same product states shown in the app: Opportunities, Testing, Drafting, Drafted, Cooldown, Discovered, and Excluded. Projects with pages on multiple hostnames also show a hostname multi-select filter. A hostname selection applies to the Search Console chart, page inventory, and Search movement. Project findings remain stable 28-day checks rather than changing when the visible chart range changes.

Eligibility and selection

A Page is not selected from traffic alone. Its current explanation can include:

• Position-band and impressions-per-day thresholds.
• Primary-keyword choice and its supporting evidence.
• Opportunity score components and data freshness.
• Existing Drafts, generation jobs, or running Experiments.
• Manual exclusions, prior decisions, cooldowns, and overrides.
• The actor and audit history behind a selection or exclusion.

Ask Chat “Why was this Page selected?” or “Why is this Page ineligible?” for the live rules, effective settings, history, and valid next actions.

Starting an Experiment

Starting an Experiment on an Opportunity immediately queues Draft generation. The Page moves through Drafting and Drafted without a separate enrollment step. Review the chosen primary keyword and any warnings first. A manual start can be allowed outside normal automated traffic or position thresholds, but its confirmation explains the higher-ranking or low-evidence risk. Pages outside the configured blog path cannot be drafted for Experiments.

Starting an Experiment does not publish content. The resulting Draft remains available for review unless Autopilot is allowed to publish it.

Excluding and restoring Pages

You can exclude one Page or a server-resolved set, such as every path containing a slug fragment. Bulk confirmations show the frozen match count before execution. Restoring a Page makes it available to current eligibility rules; it does not guarantee that it becomes an Opportunity immediately.

Existing Drafts or active Experiments can block an exclusion or require an explicit decision. If a bulk request partly fails, retrying creates a new plan for failed IDs only.