Configure what matters

Conversion pages

Conversion pages are the paths where your business outcomes happen — signups, pricing views, demo requests, free-trial starts. Mark them and SignalGuide treats problems there as P0. Skip them and a bounce-rate spike on your pricing page looks the same as one on a glossary post.

What counts as a conversion page

Anything where a visitor taking an action matters to you:

  • Pricing page (/plans/, /pricing)
  • Signup or registration (/signup, /register)
  • Demo or contact form (/lp/demo-call/, /contact)
  • Free-trial start (/free-trial)
  • Any landing page you run paid traffic to

You don't need every page. Five well-chosen paths are more useful than thirty. The analysis engine weights every red flag against your conversion page list — more paths means more checks, but the highest value comes from the pages most tied to revenue.

How to mark a page as a conversion page

Open Settings and find the Conversion pages section. Enter the exact path (leading slash required) and an optional label. The label appears in briefings instead of the raw path — “Pricing page” reads better than “/plans/” in a P0 alert.

The save hits POST /{site_id}/conversion-pages in api/routes/site_config.py. Each entry is stored as a ConversionPage row linked to your site.

To remove one, click the delete icon. The request hits DELETE /{site_id}/conversion-pages/{page_id}.

Exact path, not a pattern
Conversion pages use exact-path matching, not the wildcard patterns that clusters use. Enter /plans/ if that is the exact path GA4 reports, including the trailing slash. Check your GA4 property if you're unsure which variant gets the traffic.

How conversion pages affect priority scoring

The red-flag detector in api/services/analysis.py applies different priority levels based on whether the affected page is a conversion page:

  • P0 — bounce rate above 60% on a conversion page with more than 20 views; traffic drop of more than 20% on a conversion page; near-zero traffic on a page that previously had more than 50 views.
  • P1 — the same anomalies on a high-traffic non-conversion page (top decile by views for your site).
  • P2 — same anomalies on lower-traffic pages, or CTR gaps on non-conversion pages.

Vanity pages that match a vanity filter pattern are skipped entirely in red-flag detection — unless they are also marked as a conversion page, in which case they are still checked. Conversion status beats vanity suppression.

Source-funnel analysis

Conversion pages also drive the source-funnel analysis. During each run, the engine calls pull_ga4_source_funnels() (in api/services/ga4.py), which pulls GA4 sessions by sessionDefaultChannelGroup and counts how many sessions also landed on one of your conversion paths. The result is a per-channel conversion rate.

This is what surfaces insights like “Organic search converts at 4.1% but Direct is at 0.8%” — actionable because you know exactly which pages the analysis considers high-intent.

The MCP tool get_conversion_pages(site_id) returns your configured conversion pages merged with their current snapshot metrics and per-channel conversion rates, so you can ask an AI assistant about conversion performance directly.

Conversion pages and indexation checks

When the analysis engine runs crawlability checks, conversion pages are checked first — before GA4 top pages or GSC top pages. The logic in api/services/analysis.py builds an ordered priority list with conversion paths at the front. If one of your conversion pages shows an indexation problem, it surfaces as a high-priority finding before anything else.

No conversion pages configured
Without conversion pages, the analysis engine can still detect traffic anomalies — but it has no way to distinguish a bounce on your pricing page from a bounce on a how-to blog post. P0 findings will be rarer and less targeted.

Related: Content clusters and Vanity filters.