OctiAI

Categories

One‑Shot CRO Audit & Test Plan Template

A concise research prompt that turns funnel URLs, screenshots, benchmarks, and objections into a prioritized, ready-to-run CRO audit, 12 quick-win tests, and an 8-week roadmap.

What You'll Get

How to Use

Prep analytics and name assets clearly

Before running the prompt, export 2-4 baseline metrics (sessions, conversion rate, revenue per visitor) and label funnel assets with exact filenames (e.g., homepage_v2.png, checkout_heatmap_Jan.csv). This reduces assumptions and increases test confidence.

Works Best With

Works best with focused funnel assets and clear constraints

Prompt Template


## Goal
- Improve conversion performance for pages in the provided funnel while preserving or improving organic search alignment: rank for relevant queries, satisfy the user intent ({{search_intent}}), and convert visitors into validated leads or purchases for the target audience ({{audience}}) in {{region_language}}.

## Inputs
- Topic / keyword cluster: {{primary_keyword}}
- Audience / ICP: {{audience}}
- Positioning / core conversion promise: include in {{funnel_assets}} or state in {{constraints}}
- Funnel assets (URLs, screenshots, conversion benchmarks, analytics highlights, session recordings, common objections, proof): {{funnel_assets}}
- Internal links and important pages to protect/promote: include inside {{funnel_assets}}
- Constraints (tone, length, regulatory/compliance limits, A/B testing constraints, no redesign / copy-only): {{constraints}}
- If any keyword or analytics data is missing, infer intent and propose 2-3 reasonable measurement options and benchmarks.

## Prompt
You are a senior CRO consultant and conversion copywriter with 10+ years of B2B/B2C optimization experience. Using the inputs below, produce a single deliverable that contains: a short spec, a prioritized CRO audit (page-by-page), and a tactical 8-week prioritized test roadmap. Follow the exact output structure and formatting rules in "Output Format" below.

Inputs (use these exactly):
- Target keyword / topic: {{primary_keyword}}
- Search intent: {{search_intent}}
- Audience: {{audience}}
- Region / language: {{region_language}}
- Funnel assets & evidence: {{funnel_assets}}
- Constraints / compliance: {{constraints}}

Deliverables — produce each item explicitly and label them:
1. Brief / Spec (1-3 paragraphs)
   - One-paragraph objective tying conversion goal to the keyword/intent and target audience.
   - Pages analyzed (list URLs or page names).
   - Primary KPIs to measure (revenue/reach/lead rate / micro-conversions).
   - Key assumptions and required data to validate.

2. Prioritized CRO Audit (sectioned by page)
   - For each page: short summary (1 sentence), then a structured list of issues grouped as UX friction, copy friction, trust/proof gaps, technical/performance, and analytics/tracking gaps.
   - For every issue include: evidence from {{funnel_assets}} (quote the asset name or mark as "assumption" if not present), impact estimate (High/Med/Low), confidence score (1-5), and one-line recommended fix.

3. Hypotheses & Test Library
   - Produce exactly 12 quick-win tests suitable to start within 1-2 weeks. For each test include:
     - Test ID (T1…T12)
     - Page(s) targeted
     - Hypothesis (If we X, then Y because Z)
     - Required creative change (copy / element / asset / variant copy sample)
     - Measurement KPI (primary) — allow qualitative labels (uplift categories: +1-5%, +5-15%, +15%+)
     - Estimated implementation effort: Low / Med / High
     - Required analytics events or tags
     - Confidence (1-5)
   - Provide 3 sample variant copy snippets per A/B test for the highest-impact 3 tests.

4. Prioritized Roadmap (1-8 weeks)
   - Present as a weekly sprint plan (Week 1 → Week 8). Map each of the 12 tests into the 8-week timeline, sequencing by expected ROI / effort / risk.
   - Mark which tests should run concurrently and which require sequential learning.

5. Measurement & Reporting Plan
   - For each test: success criteria, minimum detectable effect, recommended sample size heuristic (if analytics data missing, give a conservative rule-of-thumb), primary dashboard metrics, and guardrail metrics to watch.
   - Provide 3 ready-made analytics queries or GA4/GA360/Segment pseudo-queries to pull baseline numbers from {{funnel_assets}}.

6. Implementation Checklist & Asset List
   - Exact assets required per test (copy, images, CTAs, UTM tags, experiment flags).
   - Roles & estimated time per role (copywriter, designer, developer, analyst).

7. SEO + On-page Authority Addenda (for each page analyzed)
   - H1/H2/H3 map proposal (headline stack).
   - Meta title and meta description suggestions (2 variants each).
   - Internal link targets to protect or create.
   - 6-8 FAQ items (user-intent aligned) and 2 suggested FAQ schema snippet outlines.

8. Schema Suggestions
   - For each page, recommend 1-2 JSON-LD schema types (e.g., Product, FAQPage, HowTo, WebPage) and a 3-5 field sample (no full JSON unless requested).

9. Facts vs Assumptions & Confidence Log
   - Separate explicit facts (pulled from {{funnel_assets}}) vs assumptions made.
   - For each assumption list how to validate it and its priority.

Output tone and rules:
- Use concise, actionable language. Prioritize clarity over prose.
- Return the brief/spec first, then audit, then tests, then roadmap, then measurement, then SEO addenda, then schema suggestions.
- Use bullets, numbered lists, and tables where useful.
- Provide inline copy examples in plain text (no markup formatting that would break A/B test imports).
- Label all deliverables clearly so engineers/analysts can act without follow-up.

Compliance and E-E-A-T:
- Do not invent statistics. If you must estimate, explicitly label as "estimate" with rationale and confidence (1-5).
- If legal, medical, or financial claims appear, flag them and provide safe cautious language.
- Cite the specific asset name from {{funnel_assets}} when referencing data; otherwise mark as assumption.

Formatting requirements (must follow exactly):
- Begin the response with a one-line Brief / Spec header.
- Use an H1 for each major section (e.g., # Prioritized CRO Audit).
- Use H2 for each page analyzed and H3 for issue groups (UX friction, Copy friction, Trust gaps, Technical, Tracking).
- Present the 12 tests as a table with columns: Test ID | Page | Hypothesis | Creative change | KPI | Effort | Confidence.
- Provide the roadmap as a weekly table (Week 1…Week 8) mapping tests by ID.
- End with a short "Next steps" checklist (3 items).

Quality checks (enforce before returning):
- All referenced data points must be traced to a named asset in {{funnel_assets}} or explicitly labeled assumption.
- The 12 tests must be actionable and have at least one measurable KPI each.
- The roadmap must cover Weeks 1-8 and include prioritization rationale.

Now produce the full deliverable following the structure and rules above.

## Output Format
- Enforce a clear structure: H1/H2/H3 map, scannable sections, bullets, and tables when useful.
- Use plain copy samples for test variants and meta text.
- Include internal link targets and FAQ items as bullet lists.
- Keep each page audit to a maximum of 1 A4 page worth of content (concise).

## Guardrails
- No invented statistics; separate facts vs assumptions.
- E-E-A-T: explicitly flag expertise limitations and advise conservative language for regulated claims.
- Align findings with the provided {{search_intent}} and {{primary_keyword}}; avoid tangents.
- When analytics are missing, propose 2 realistic baseline options and state the detection limits.
- All recommended tests must be runnable without full redesign unless {{constraints}} allows it.

## Examples
Keyword → 3-bullet content brief excerpt
- Example keyword: checkout abandonment
  - Brief: Objective is to reduce checkout abandonment by improving clarity of shipping/costs and reinforcing trust for the {{audience}}. Primary KPI: checkout completion rate.
  - Focus bullets: 1) Surface total price earlier (copy change), 2) Add a compact trust bar (proof placement), 3) Fix form usability (reduce required fields).
  - Quick-win test idea: Show total price earlier vs control — KPI: +checkout completion rate, Effort: Low.

Use this prompt exactly (with the provided placeholders) when you paste into the target model.

Variables

Usage Notes

Not for

Do not include

One‑Shot CRO Audit & Test Plan Template

Generate a single, structured deliverable (brief, page-by-page CRO audit, 12 quick-win A/B tests with hypotheses and creative variants, 8-week prioritized roadmap, measurement plan, and SEO addenda) from funnel assets and constraints.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Search Intent

Provide the key details needed for this variable.

Audience

Provide the key details needed for this variable.

Region Language

Provide the key details needed for this variable.

Primary Keyword

Provide the key details needed for this variable.

Funnel Assets

Provide the key details needed for this variable.

Constraints

Provide the key details needed for this variable.

Rules

Canonical Examples

Input: B2B SaaS: InboxFlow email automation for SMB marketers (US). Keyword: "email automation software for small business". Assets: LandingPage_URL, SignupFlow_Screenshots, GA4_Q1_export, UserInterviews_Mar2026, AdCreative_Feb. Constraints: copy-only, 500-char hero limit.

Loading result...

Failed to load output.


Brief / Spec
# Prioritized CRO Audit
## Homepage (LandingPage_URL)
### UX friction
- ...
# Hypotheses & Test Library
Table: T1-T12 ...

Why it works: This example demonstrates the prompt producing a full CRO spec and tactical test plan for a B2B SaaS funnel using provided assets and explicit constraints (copy-only, hero length). It shows how to convert asset evidence into prioritized audits, 12 concrete A/B tests with creative variants, an 8-week roadmap, measurement guidance, SEO addenda, and schema recommendations while marking assumptions where data is missing.

Input: DTC product: PosturePro ergonomic standing desk. Keyword: "best standing desk for home office". Audience: remote workers (US/EU). Assets: PDP_URL, Checkout_Analytics_Q4, Heatmaps_Oct2025, CustomerReviews_2025, Competitive_Landing_Screenshots. Constraints: avoid health claims; pricing page tests allowed.

Loading result...

Failed to load output.


Brief / Spec
# Prioritized CRO Audit
## PDP (PDP_URL)
### UX friction
- CTA below the fold... 
# Hypotheses & Test Library
Table: T1-T12 ...
# Next steps: instrument events, run T1, review Heatmaps_Oct2025

Why it works: This example shows the prompt applied to a DTC product PDP-to-checkout funnel: it converts product and review assets into a prioritized CRO audit, 12 tests (including PDP, cart, checkout), an 8-week roadmap, measurement queries, SEO addenda tailored to product pages, and schema suggestions while flagging health-claim guardrails.

Works Best With

Works best with focused funnel assets and clear constraints