Review SEO and conversion visibility before publishing — procedure

Use this guide to review whether a page or site is discoverable in search and measurable through GA4 events, subscription tracking, checkout tracking, and conversion-funnel visibility.

Publishing visibility workflow

Workflow summary

Review search discoverability and conversion-measurement visibility before or after publishing a website page, guide, article, prompt page, pricing page, subscription flow, or checkout path

Expected result
What the workflow should produce
Produce a two-part visibility review: SEO discoverability findings plus GA4 and funnel visibility findings, with exact fixes and NOT VERIFIED items.
Best for
When this workflow fits
New pages, changed page templates, updated site hierarchy, pricing pages, subscription flows, checkout paths, gated-content flows, content hubs, prompt pages, guide pages, and article pages.

Purpose

This guide explains how to review whether a page or site is visible in two different ways: search visibility and measurement visibility. Search visibility checks whether search engines can discover, index, and understand the page. Measurement visibility checks whether the site owner can measure user actions, subscription intent, checkout steps, and conversion outcomes. Use this workflow before publishing new pages, after changing site structure, or when GA4 reports do not show expected page, click, sign-up, subscription, or checkout activity.

When to use this

Use this section to decide whether this workflow is the right fit before you configure prompts, policies, or reference material.

Use case
A new or updated page needs search visibility
Use this when publishing or changing a page that should be discoverable through search, internal navigation, topic pages, guides, prompts, or articles.
Use case
A conversion path must be measurable
Use this when signup, subscription, checkout, purchase, lead, download, share, copy, or CTA interactions need to appear in analytics.
Use case
Traffic or conversion visibility is unclear
Use this when GA4, Search Console, or on-site behavior does not clearly show whether users can find and complete the intended action.

Do not use this when

Use this section to prevent the workflow from being applied to the wrong source type, risk level, or implementation context.

Wrong scope
You need a ranking guarantee
Do not use this workflow to guarantee ranking, traffic, impressions, indexing, conversions, or revenue. It can identify readiness and evidence gaps only.
Missing evidence
No page, flow, metadata, or tracking material is available
Do not infer indexing status, GA4 collection status, checkout performance, or conversion performance without supplied evidence.
Use a different workflow
The task is only factual source verification
Use the public-source verification workflow when the goal is only to answer a current factual question with citations.
Open web-source workflow

Workflow controls

What this workflow controls

Use this section to understand which parts of the AI workflow are controlled by this guide before you configure prompts, files, or verification steps.

Instruction layer
Visibility-review boundary
Defines the stable rule that SEO discoverability and analytics measurement are separate checks with different evidence sources.
Do not merge SEO readiness and GA4 measurement into one undifferentiated checklist.
Reference layer
Page, site, and analytics evidence
Defines the page content, templates, metadata, sitemap, robots.txt, canonical URLs, internal links, GA4 events, GTM tags, gtag calls, dataLayer pushes, DebugView evidence, network logs, and funnel steps used as evidence.
The workflow must not invent live indexing, ranking, GA4 collection, checkout, or conversion data.
Runtime prompt layer
Current page, flow, and review goal
Defines the current page or flow under review, the publishing context, the business goal, and the exact visibility concern.
Run the SEO prompt for search visibility and the GA4 prompt for measurement visibility.
Verification layer
Evidence-separated output
Checks that every finding is supported by supplied material, live evidence, or cited official documentation.
Unsupported claims must be marked NOT VERIFIED.

Workflow placement

Where to configure this workflow

Place each part of the workflow in the correct layer before you run it. Keep stable rules out of one-off prompts, keep source material in the reference layer, and keep the current task in the runtime prompt.

Instruction layer
Stable visibility-review rule
Put the rule that SEO and GA4 are separate review layers in the instruction layer when this workflow is reused.
Examples: ChatGPT Project Instructions · GPT Instructions · Claude Project Instructions · Gem Instructions
Reference layer
Site and measurement evidence
Put page files, layouts, metadata, sitemap, robots.txt, analytics code, GA4 event lists, GTM configuration notes, and funnel steps in the reference layer.
Examples: ChatGPT project files or GPT Knowledge · Claude Project Knowledge · Gemini Gem Knowledge files · Repository files
Runtime prompt layer
Current review request
Put the active page, flow, question, target audience, search intent, business goal, and tracking concern in the runtime prompt.
Examples: Current chat message · Task-specific prompt · One-time user request
Verification layer
Final visibility check
Check that SEO findings and GA4 findings are separated, evidence-backed, and not overstated.
Examples: Verification checklist · Evidence gate · Confidence note

Platform mapping

Open the full platform mapping when you need tool-specific setup

Use this guide for the workflow-specific placement. Use the reference pages for the full ChatGPT, Claude, Gemini, and API setup mapping.

ChatGPT Projects, GPTs, Skills, files/sources, Custom Instructions, Memory, and runtime prompts. Open mapping → Claude Projects, Project Instructions, Project Knowledge, Skills, Claude Code surfaces, and runtime chat input. Open mapping → Gemini Gems, Gem instructions, Knowledge files, Memory, Connected Apps, AI Studio, Gemini API, Files API, File Search, and Vertex AI. Open mapping → API / internal systems System/developer instructions, retrieval, tools, orchestration, approvals, validation, evals, logging, and application state. Open mapping →

Workflow assets

Required workflow assets

Open the prompts, policies, and reference pages needed to run this workflow correctly.

Required prompt
SEO discoverability audit
Checks indexing signals, metadata, heading hierarchy, internal linking, sitemap/canonical evidence, and search-discoverability gaps.
Type: Workflow prompt
Belongs in: Runtime prompt layer
Use when: The task is to review whether a page or site can be discovered, indexed, understood, and internally connected.
Do not use when: The primary task is GA4 event tracking, checkout measurement, subscription measurement, or conversion reporting.
Open prompt
Required prompt
GA4 and funnel visibility audit
Checks whether meaningful user actions and conversion paths are measurable through GA4 events and useful event parameters.
Type: Workflow prompt
Belongs in: Runtime prompt layer
Use when: The task is to review event tracking, signup, subscription, checkout, purchase, lead, or conversion visibility.
Do not use when: The primary task is indexing, metadata, sitemap coverage, or internal linking.
Open prompt
Required reference
Prompt layers and policy mapping
Explains where stable instructions, source material, runtime prompts, and verification gates belong.
Type: Configuration reference
Use when: Use when configuring this workflow in ChatGPT, Claude, Gemini, or an internal AI system.
Open reference

Implementation procedure

Step-by-step implementation procedure

Follow the workflow in order. Each step explains what to do, where it belongs, which asset to use, and what to check before continuing.

  1. Step 1 · Reference layer
    Collect page and SEO evidence
    Prepare the page URL or content, title, meta description, headings, internal links, canonical URL, sitemap evidence, robots.txt evidence, structured-data block, and intended search intent.
    What to do: Separate supplied page evidence from live evidence and mark anything not supplied as missing.
    Check before continuing: The page, metadata, internal-link context, and search-intent context are available or explicitly marked missing.
  2. Step 2 · Runtime prompt layer
    Run the SEO discoverability audit
    Use the SEO prompt to identify indexing blockers, metadata gaps, heading hierarchy problems, internal-linking gaps, sitemap/canonical issues, and structured-data notes.
    What to do: Ask for exact remediation actions and NOT VERIFIED items.
    Use this asset: SEO discoverability audit
    Check before continuing: The output separates confirmed SEO findings from missing evidence.
    Open prompt
  3. Step 3 · Reference layer
    Collect analytics and funnel evidence
    Prepare the page flow, CTA list, sign-up flow, subscription flow, checkout steps, GA4 event names, GTM tags, gtag calls, dataLayer pushes, DebugView evidence, network logs, or GA4 export rows when available.
    What to do: Separate implementation evidence from reporting evidence.
    Check before continuing: The business-critical actions and available tracking evidence are explicit.
  4. Step 4 · Runtime prompt layer
    Run the GA4 and funnel visibility audit
    Use the GA4 prompt to map visible user actions to GA4 recommended events where possible and identify missing event coverage, parameter gaps, and conversion/key-event candidates.
    What to do: Ask for an event table and exact implementation notes.
    Use this asset: GA4 and funnel visibility audit
    Check before continuing: The output separates observed tracking from missing tracking and NOT VERIFIED claims.
    Open prompt
  5. Step 5 · Verification layer
    Keep search visibility separate from measurement visibility
    Review the final output and confirm that SEO issues are not treated as GA4 issues, and GA4 measurement gaps are not treated as indexing issues.
    What to do: Prioritize fixes by blocker severity and evidence quality.
    Check before continuing: The final action list has separate SEO fixes, GA4 fixes, and missing-evidence items.

Verification checklist

Use this checklist before accepting the output, publishing it, or using it as evidence for a downstream workflow.

Boundary
SEO and GA4 findings are separated
The output does not merge indexing, metadata, and internal linking with event tracking, subscription measurement, or checkout visibility.
Evidence
Findings are supported
Each finding is supported by supplied material, live evidence, or cited official documentation.
No simulation
No ranking or analytics results are invented
The output does not invent indexing status, ranking, traffic, conversions, event receipt, checkout completion, or revenue.
Actionability
Fixes are concrete
The output gives exact metadata, linking, hierarchy, event, parameter, or funnel fixes where evidence supports them.

Common mistakes

Use this section to avoid configuration errors, prompt-layer drift, source-boundary mistakes, and weak verification behavior.

Mistake
Using one prompt for SEO and GA4 without boundaries
This hides the fact that search visibility and measurement visibility have different evidence requirements and failure modes.
Mistake
Treating missing GA4 events as an SEO issue
GA4 event gaps affect measurement, not indexing or ranking.
Mistake
Claiming a page is indexed without evidence
Indexing status requires Search Console, live search evidence, or another explicit source.
Mistake
Inventing event collection status
GA4 collection status requires implementation evidence, DebugView evidence, network logs, or GA4 export data.

Workflow connections

Related resources

Use these resources when you need the related guide, prompt, policy, reference page, or background article that supports this workflow.

Related prompts

Open these when you need the managed prompt page, reusable prompt component, or protected execution prompt behind the workflow.

Related reference

Open these when you need configuration details, terminology, diagrams, or platform placement guidance.