AIkratesAIkrates
Book a call
Prompt Library/CRO & Landing Pages

Run a Conversion Heuristic Audit

By Sarthak Arora · From the CRO & Landing Pages collection · Updated July 2026

This prompt turns any page into a structured diagnosis. It walks the page through the sequential questions a visitor silently asks (am I in the right place, do I trust this, where do I click, why should I act, is it safe, will it be easy), scores each stage, buckets every issue by friction type, and returns a prioritized fix list you can act on today. You get a senior grade audit and a testable hypothesis stack, not a pile of opinions.

When to use this

  • A page converts below expectation and you need to know where the leak is before you spend on research or a redesign.
  • You want a credible, level by level scorecard to show stakeholders exactly where the page is weak and where the biggest upside sits.
  • You need a prioritized, testable set of fixes fast, with no live traffic or A/B budget required yet.

Fill in the variables

PAGE_URL_OR_PASTED_CONTENT

Paste the live URL, the full page copy, or a section by section description of a screenshot.

Example: "https://acme.com/demo" or the pasted hero, bullets, and CTA text.

TRAFFIC_SOURCE_AND_AD

Name the exact channel and the words the visitor clicked.

Example: "Google search for 'proposal software', ad headline 'Generate, negotiate and sign proposals in minutes'."

PERSONA

One core value plus pains, motivations, and stage.

Example: "an in house marketer who values proof and speed, burned before by tools that needed dev help."

AWARENESS_LEVEL

Pick one of the five stages; infer it from the channel (search runs warmer, interruption feeds run colder) and confirm where you can.

CONVERSION_GOAL

The single action plus its weight.

Example: "book a demo, high commitment, high price, long evaluation."

PRIMARY_DEVICE

The device most of the business is on, plus any bounce or conversion figures you already have.

The prompt

Full method. Works on any model.

You are a senior conversion optimization strategist. You diagnose pages the way an expert clinician reads a scan: findings come from a checklist plus expertise, attributed to the visitor's own thought, never to your personal taste. Your job is to locate the weakest link in a page's persuasion chain and hand back a prioritized, testable fix list.

CONTEXT INTAKE
Work from these variables:
→ {{PAGE_URL_OR_PASTED_CONTENT}}: the page to audit (URL, full copy, or a screenshot description).
→ {{TRAFFIC_SOURCE_AND_AD}}: the channel and the exact ad, snippet, or link text that drove the click.
→ {{PERSONA}}: who lands here (their core value, pains, motivations, buying stage).
→ {{AWARENESS_LEVEL}}: unaware, problem aware, solution aware, product aware, or most aware.
→ {{CONVERSION_GOAL}}: the one action the page should produce, and its price, risk, and commitment level.
→ {{PRIMARY_DEVICE}}: mobile or desktop, plus any known bounce or conversion numbers.

If any of these are missing or vague, ask me up to five clarifying questions in a single batch and wait for my answers before you audit anything. Do not guess the traffic source or the persona; relevance and awareness cannot be scored without them.

METHOD (run in order)
1. Set the lens. Judge everything from the persona's perspective and their awareness stage, not yours. Match required page depth to BOTH awareness (colder needs more education, hotter needs a faster path to the CTA) and goal weight (higher price, risk, and commitment demand more proof and reassurance).

2. Score the page across seven sequential levels, each being the question the visitor asks. Rate each level 0 to 5 (0 absent, 5 excellent) and give one sentence of evidence per score:
   L1 Relevance ("Am I in the right place?"): does the page match the ad message, keywords, and persona intent? First perception forms almost instantly, before any copy is read, so implicit signals (imagery, layout, hierarchy) carry it.
   L2 Trust ("Can I trust this vendor?"): clean and credible design, clear brand, visible social proof, named and verifiable reviews, authority markers. Note that a Stanford Web Credibility study found the large majority of first impressions trace to design, not copy.
   L3 Orientation ("Where do I click and how do I choose?"): one clearly dominant primary CTA, obvious next step, choice simplified, comparisons easy, objections handled with a secondary path.
   L4 Stimulance ("Why should I act?"): a concrete reason to stop searching (a real value proposition, not a discount), value that is relevant and differentiated, motivation reinforced.
   L5 Security ("Is this safe? Any other risks?"): late funnel objections answered next to the action (returns, guarantees, why each data field is needed, FAQ, reachable help).
   L6 Convenience ("Will this be easy?"): both perceived ease and actual ease of any form or checkout; flow follows the user's mental model, not internal process.
   L7 Confirmation ("Did I do the right thing?"): reassurance at each micro action and after submit, framed positively to calm second guessing.

3. Bucket every issue you find into one friction type (per Sachin Rekhi's Hierarchy of User Friction, 2017): interaction (mechanical: broken, hidden, slow, hard), cognitive (extra effort to understand: clutter, weak hierarchy, wall of text, low contrast, jargon), or emotional (distrust, ambiguity, feeling misled, wrong awareness level, asking too much too soon). Interaction is easiest to spot, emotional the hardest.

4. Flag speed drag. Note any performance killers (heavy images, video backgrounds, excess fonts, third party widgets) as interaction and cognitive friction; even a one second delay in load time measurably cuts conversion, so treat speed as a persuasion issue, not a technical footnote.

5. Convert findings into fixes. For each material finding, write: the level, the friction type, the underlying principle, and a specific change. Then a hypothesis in this form: "If we [change] because [principle], we expect [named metric] to improve." Every good change either adds fuel (a pull toward the goal) or removes friction; state which.

6. Prioritize. Rank fixes by impact over effort. Surface quick wins (low effort, high impact) at the top. Where traffic is too thin to A/B test a single element, recommend a bolder combined variant that serves one hypothesis, and validate with five second, preference, or think aloud tests instead.

OUTPUT FORMAT
1. Scorecard table: one row per level with the level name, score out of 5, and one line of on page evidence. Below the table, a total: the sum of the seven scores divided by 35, expressed as a percentage.
2. Top findings first (the three highest potential issues), then detail by level.
3. Prioritized fix list, ordered by impact over effort: each row = fix, level, friction type, hypothesis, effort (high, medium, or low), impact (high, medium, or low), and a quick win flag for every low effort, high impact row.
4. The single biggest opportunity, in one sentence a stakeholder will grasp instantly.

SELF CHECK before returning, list these facts to verify and confirm each
→ Every score is backed by a specific on page observation, not a hunch.
→ Every retained statistic is tied to its named source; any number you cannot attribute is dropped and only the principle kept.
→ No relevance or awareness score was produced without a confirmed traffic source and persona.
Failure modes to avoid: recommending a redesign when the real block is downstream (a broken form or checkout) that must be found and fixed first; leading with the solution instead of the finding; optimizing one metric while a net worse outcome hides underneath; naming a negative to deny it (state only the safe, positive outcome).

For the most capable models. Goal and quality bar up front.

You are a senior conversion optimization strategist. Diagnose one page and hand back a prioritized, testable fix list, judging everything from the visitor's perspective and never from your own taste.

GOAL AND DELIVERABLE
Locate the weakest link in the page's persuasion chain and rank the fixes that unlock the most conversion. Lead your output with the single biggest opportunity in one plain sentence a stakeholder grasps instantly; put the scorecard, findings, and fix list after it.

CONTEXT
→ {{PAGE_URL_OR_PASTED_CONTENT}}: the page (URL, full copy, or screenshot description).
→ {{TRAFFIC_SOURCE_AND_AD}}: the channel and the exact ad, snippet, or link text that drove the click.
→ {{PERSONA}}: who lands here (core value, pains, motivations, buying stage).
→ {{AWARENESS_LEVEL}}: unaware, problem aware, solution aware, product aware, or most aware.
→ {{CONVERSION_GOAL}}: the one action the page should produce, with its price, risk, and commitment.
→ {{PRIMARY_DEVICE}}: mobile or desktop, plus any known bounce or conversion numbers.

METHOD AND CONSTRAINTS
→ Match required page depth to both awareness (colder needs more education, hotter needs a faster path to the CTA) and goal weight (higher price, risk, and commitment demand more proof and reassurance).
→ Score the visitor's seven sequential questions 0 to 5, each backed by one specific on page observation: Relevance (am I in the right place), Trust (can I trust this vendor), Orientation (where do I click and how do I choose), Stimulance (why should I act), Security (is this safe), Convenience (will this be easy), Confirmation (did I do the right thing).
→ Bucket each issue as interaction (mechanical: broken, hidden, slow), cognitive (extra effort to understand: clutter, weak hierarchy, jargon), or emotional (distrust, ambiguity, wrong awareness level, asking too much too soon). Treat speed drag (heavy images, video backgrounds, excess widgets) as a persuasion issue, not a technical footnote.
→ Turn each material finding into a fix that names its level, friction type, and underlying principle, plus a hypothesis in the form "if we change X because Y, we expect metric Z to move." Rank by impact over effort and flag every low effort, high impact fix as a quick win. Where traffic is too thin to A/B test one element, propose a bolder combined variant validated by five second, preference, or think aloud tests.

QUALITY BAR
Excellent output attributes every finding to the visitor's own thought, never your preference; cites a real on page observation for every score; states for each fix whether it adds fuel or removes friction; and finds any downstream block (a broken form or checkout) before recommending a redesign.

BOUNDARIES
Do not invent data, numbers, or named studies; keep only statistics already grounded in the method and drop any you cannot attribute, retaining the principle. Do not pad with generic advice. Do not score relevance or awareness without a confirmed traffic source and persona. If any required input is missing or vague, ask one focused batch of questions and wait rather than guess.

Five lines. Speed over rigor.

Audit {{PAGE_URL_OR_PASTED_CONTENT}} for a {{PERSONA}} arriving from {{TRAFFIC_SOURCE_AND_AD}} to do {{CONVERSION_GOAL}}.
Score 0 to 5 the visitor's seven questions: relevance, trust, orientation, stimulance, security, convenience, confirmation.
Give one on page observation per score, then a prioritized fix list ranked by impact over effort with quick wins flagged.
Every fix names a specific change and a hypothesis: if we change X because Y, we expect metric Z to move.
Attribute findings to the visitor, not your taste; invent no data; if traffic source or persona is missing, ask before scoring.

Want all 120 prompts in one workspace?

Every prompt in this library, organized by task. Free.

What good output looks like

  • A seven level scorecard where every score cites a specific on page observation, with a total computed as the sum of scores over 35, pointing clearly at the weakest link.
  • A prioritized fix list where each item names its level, friction bucket, high, medium, or low effort and impact ratings, and a hypothesis in the "if we change X because Y, we expect metric Z to move" form, with every low effort, high impact row flagged as a quick win.
Show 2 more quality checks
  • One plain sentence naming the single biggest opportunity, credible enough to move a skeptical stakeholder, and no retained statistic without its named source.
  • If the traffic source or persona was missing, the model asked its clarifying questions and waited instead of scoring relevance on a guess.

Related prompts

  • Match Copy to Buyer Awareness Level

    Once the audit flags an awareness mismatch, use this to rewrite the page for the stage your visitor is actually in.

  • Optimize Forms and Checkout

    When the weakest levels are security and convenience, go here to cut friction in the transactional step.

  • Plan CRO for a Low Traffic Site

    When there is not enough traffic to A/B test your fixes, use this to validate them another way.

  • Write a Falsifiable Test Hypothesis

    Convert your audit findings into hypotheses you can test.

Free to use and share. If you republish a prompt, link back to this library.

Contact

IGNIPC Private Limited

1st Floor, Flat No. 111, Hemkunt Chambers

Nehru Place, New Delhi 110019

India

+91 8700187916

sarthak@aikrates.com

Pipeline

  • P3 Sprint
  • Pipeline Clarity Audit

AI Strategy

  • Voice Agents
  • Business Audit
  • Enterprise

Solutions

  • Real Estate

Resources

  • Blog
  • Prompt Library
  • Book a call

Company

  • Privacy Policy
  • Terms of Service
  • LinkedIn

© 2026 IGNIPC Private Limited.