Skip to content

mbfinotti/advertising-skills / skills/paid-landing-page-audit

paid-landing-page-audit

Verified

Audit a landing page receiving paid traffic against post-click conversion best practice and return a prioritised fix list - message match to the ad, above-the-fold clarity, form friction, trust, speed, mobile, policy risk - with every finding labelled by evidence class and no statistical claims on thin data. Use whenever the user says their ads get clicks but no conversions, asks why a landing page isn't converting, or mentions post-click experience, message match, conversion friction, form friction, or CPA rising after the click - even if they never say 'landing page audit'. Covers B2B and B2C on any platform. Audit only. Do NOT use for pre-click account problems - use mbfinotti/advertising-skills@ad-account-diagnostic instead.

FileKindSize
SKILL.mdskill md24.8 KB
evals/evals.jsonconfig37.4 KB
references/evidence-and-benchmarks.mdmarkdown11.2 KB
references/page-checks.mdmarkdown10.9 KB
references/report-template.mdmarkdown5.9 KB

evals/evals.json

View on GitHub
{
  "skill_name": "paid-landing-page-audit",
  "evals": [
    {
      "id": 1,
      "prompt": "I run growth at Loftbeam, a B2B scheduling SaaS. Our Meta demo campaign's CPA went from $52 to $96 over five weeks, so I want a full audit of our landing page. Extra context in case it helps: CTR went from 1.7% to 0.8% over those same five weeks, frequency climbed from 2.2 to 5.9, we haven't touched targeting, the offer, or the page since March, and the demo-booked event fires once and deduplicates correctly (verified last week). Here's the page: headline 'Scheduling that runs itself', subhead about calendar sync, one 'Book a demo' CTA, three customer logos, a 5-field form. Give me the ranked list of page fixes.",
      "expected_output": "A refusal to blame the page: the declining CTR and climbing frequency are named as an upstream creative-fatigue signal, the page verdict is withheld, the request is handed off to a creative-fatigue diagnosis, and no ranked page fix list is produced.",
      "files": [],
      "expectations": [
        "The response identifies the CTR decline (1.7% to 0.8%) and the frequency climb (2.2 to 5.9) as pre-click, ad-side evidence rather than evidence about the landing page.",
        "The response names creative fatigue (or ad wear-out / audience saturation) as the likely cause of the CPA rise.",
        "The response states that the evidence does not support a page-fault verdict, or explicitly declines to conclude the page is the problem.",
        "The response does not deliver a ranked landing-page fix list.",
        "The response recommends a creative-fatigue (or ad-side) diagnosis as the next step before any page work.",
        "The response explains that a CPA rise alone cannot distinguish a page problem from an ad problem.",
        "The response states the specific upstream signal that triggered the refusal (falling CTR and/or rising frequency), not just a generic 'check the ads first'.",
        "The response does not attribute the $52-to-$96 CPA change to any element of the described page.",
        "The response does not recommend a page redesign or rebuild.",
        "The upstream verdict appears before any commentary on the page's content.",
        "The response does not present criticisms of the pasted page elements as the explanation for the performance decline.",
        "No specific percentage conversion lift is promised anywhere in the response."
      ]
    },
    {
      "id": 2,
      "prompt": "We're Kelpwise, selling compliance software to mid-market fintechs. Landing page for our Google Ads campaign, last 30 days: 640 sessions, 9 conversions. Mobile converts at 1.1% and desktop at 1.9%, so clearly mobile is the problem, right? I want you to audit the page copy below, confirm which device to prioritize based on those rates, and set up an A/B test on the headline so we can prove the fix works before rolling it out. Target CPA is $120 and we're at $210. Page copy: headline 'Compliance, simplified', subhead 'Audit-ready in weeks, not months', CTA 'Get a demo', a 7-field form asking name, work email, phone, company, role, company size, and current tooling, two anonymous quotes ('Great product!' — Customer), no pricing mentioned.",
      "expected_output": "An audit that declares the data below the volume floor, refuses the mobile-vs-desktop read and the A/B test recommendation, and ranks fixes by first-principles friction and established research instead, with evidence-class labels and the standard report sections.",
      "files": [],
      "expectations": [
        "The response states that 640 sessions / 9 conversions sits below the volume threshold (around 1,000 sessions or 30 conversions) at which conversion data becomes readable.",
        "The response refuses to conclude mobile converts worse than desktop from the 1.1% vs 1.9% split, calling the comparison noise or statistically unreadable at this volume.",
        "The response declines to recommend an A/B test as the validation path at this conversion volume (below roughly 100 conversions per month).",
        "The response recommends shipping well-evidenced friction removals and monitoring, rather than testing, as the path forward.",
        "The fix ranking is explicitly grounded in first-principles friction and established research rather than in this page's own conversion numbers.",
        "The response still delivers an audit rather than refusing the task because the data is thin.",
        "The response notes that the volume thresholds are practitioner heuristics and that a proper sample-size calculation would supersede them.",
        "No specific percentage conversion lift is promised anywhere in the response.",
        "Findings derived from the pasted copy are labelled as opinion (or explicitly distinguished from data-backed observations).",
        "The report includes a section listing what could not be checked from pasted copy alone (e.g. rendering, load speed, layout, analytics funnel) and what that means for the findings.",
        "The report includes a section naming things that were checked and are fine, not only faults.",
        "The fix list contains at most seven items.",
        "The anonymous unattributed quotes are flagged as a trust weakness (attributable name, role, specific result required)."
      ]
    },
    {
      "id": 3,
      "prompt": "I'm head of demand gen at Ferrovine, an enterprise data-governance platform, deals around $80k ACV. Our paid LinkedIn campaign lands on a demo request page with an 8-field form. My CMO read that Baymard found the average checkout has 11.3 form fields when about 8 is achievable, and that every form field costs roughly 11% of conversions, so she wants us down to 3 fields (name, email, company) to boost fills. Meanwhile our SDR team keeps complaining that over half of current MQLs are students and consultants with no budget. Last month: 2,400 sessions, 85 form fills. Audit the form and tell us what to change to hit our pipeline number.",
      "expected_output": "An audit that rejects the Baymard checkout data and the per-field percentage as inapplicable, identifies lead quality as the bottleneck, legitimately considers adding qualifying friction judged against pipeline with lag acknowledged, and refuses an A/B test as the validation path at this volume.",
      "files": [],
      "expectations": [
        "The response rejects applying Baymard's checkout figures to this B2B lead form, stating they are B2C ecommerce checkout data.",
        "The response rejects the ~11% per-field figure, stating that published per-field numbers disagree in size and shape and no trustworthy universal percentage exists.",
        "The response states the defensible claim as direction only: every field costs conversion and the cost is non-linear.",
        "The response identifies lead quality, not fill volume, as the current bottleneck, using the SDR complaint about unqualified MQLs.",
        "The response treats adding or keeping a qualifying field as a legitimate recommendation in this situation, not as an error.",
        "The recommendation is judged against pipeline (MQL to SQL to closed-won or equivalent), not against form-fill rate.",
        "The response acknowledges a long lag (on the order of 30-180 days) before the change's true pipeline effect is visible.",
        "The response does not endorse cutting the form to 3 fields to maximize fills.",
        "The response explicitly counters the assumption that a shorter form is always better, noting shorter B2B forms can degrade lead quality or revenue.",
        "The response evaluates fields by whether each is needed now versus collectible after the conversion.",
        "The response does not prescribe an A/B test as the validation path given roughly 85 conversions per month.",
        "The proposed validation is shipping plus monitoring downstream lead-quality or pipeline movement over time.",
        "No specific percentage conversion or fill-rate lift is promised anywhere in the response.",
        "Form findings carry an evidence-class label (opinion vs observation) or an equivalent explicit distinction."
      ]
    },
    {
      "id": 4,
      "prompt": "Marketing manager at Plumecart, a DTC skincare brand. Our paid social landing page needs more punch, so here's the plan I want your help executing: (1) add a countdown timer that restarts for each visitor, for urgency; (2) we drafted three customer testimonials in-house since real customers are slow to reply — tell me where on the page they should go; (3) make the CTA button red, red converts better; (4) our CEO read that people have 8-second attention spans so we're cutting nearly all body copy; (5) give me the percentage lift we should expect from all this so I can put it in the launch deck. Page does about 22,000 paid sessions and 450 orders a month.",
      "expected_output": "A response that refuses the resetting countdown and fabricated testimonials as FTC-exposure findings against a page, debunks the red-button rule and the 8-second attention span with the correct evidence, refuses the lift number citing experiment win-rate data, and offers legitimate alternatives.",
      "files": [],
      "expectations": [
        "The response refuses to add the resetting countdown timer, treating manufactured urgency as a finding against a page rather than a fix for one.",
        "The response identifies fake urgency or fake scarcity as an FTC and/or ad-platform-policy exposure, not merely a bad practice.",
        "The response refuses to place the in-house-written testimonials.",
        "The response states that fabricated testimonials or reviews are an FTC enforcement target (or illegal under the fake-review rule).",
        "The response offers the legitimate alternative: real, attributable testimonials carrying a real name, role, and specific result.",
        "The response rejects the claim that red buttons convert better, stating no universal winning button colour exists.",
        "The response redirects the button question to contrast and prominence against surroundings rather than hue.",
        "The response rejects the 8-second attention span figure as unsupported (broken or untraceable citation).",
        "The response cites the verified alternative: visual first impressions form in about 50ms (Lindgaard), and/or that about 57% of viewing time lands above the fold.",
        "The response does not endorse cutting nearly all body copy, tying page length instead to offer complexity and traffic temperature.",
        "The response refuses to provide a percentage lift figure for the launch deck.",
        "The refusal is justified with experiment win-rate evidence: only roughly 10-33% of experiments (or about 12% in Optimizely's corpus) improve their target metric.",
        "The response offers a test-and-measure framing (changes judged by a named metric) in place of a promised number.",
        "The response allows genuine urgency (a real deadline or real stock limit) as acceptable when true."
      ]
    },
    {
      "id": 5,
      "prompt": "I manage paid acquisition for Grainhollow, an online course platform. We already know the issues on our paid search landing page, I just need the priority order — cheapest quick wins first please. The issues: (a) countdown timer that resets on every page load (been there a year, the previous manager said it converts well), (b) 'guaranteed to double your salary' claim in the hero, (c) mobile LCP 5.2s in field data, and mobile is 74% of our spend, (d) the headline doesn't mention the course the ad promotes, (e) testimonials buried in the footer, (f) a 14-field signup form, (g) hero video autoplays with sound. Constraint: I can edit copy and images in the CMS myself, but there is no dev team and no agency — nobody can touch code, page speed, or the form stack.",
      "expected_output": "A prioritised list where the two compliance removals lead regardless of ratio, ordering is by efficiency rather than cheapest-first, the speed fix is deleted and named under a ruled-out section because there is no route to engineering, and every fix carries the required labels.",
      "files": [],
      "expectations": [
        "The countdown-timer removal and the 'double your salary' claim removal lead the list, ahead of every conversion fix.",
        "The resetting countdown is treated as a removal despite the claim that it 'converts well', because the exposure stands every day it remains.",
        "The unsubstantiated salary-doubling guarantee is flagged as an FTC and/or ad-platform policy exposure.",
        "The response does not adopt cheapest-first as the sort key, and states the ranking principle used instead: funnel step unblocked per unit of effort.",
        "The speed fix (5.2s mobile LCP) is deleted from the ranked list because there is no route to engineering at all.",
        "The deleted speed work is named in a dedicated ruled-out section together with the constraint that removed it, not parked at the bottom of the ranked list or dropped silently.",
        "Message match (making the headline confirm the promoted course) sits at or near the top of the shippable fixes.",
        "Moving the footer testimonials to the point of friction is presented as an hour-scale, high-ratio fix.",
        "The ranked fix list contains at most seven items.",
        "Each ranked fix carries a severity and an effort bracket, and not every fix is marked critical.",
        "Effort is expressed as time and coordination (hours, days, weeks), never as a currency amount.",
        "No specific percentage conversion lift is promised anywhere in the response.",
        "The form recommendation is scoped against the no-dev constraint (CMS-editable changes, or fields assessed as needed-now versus collectible-later) rather than assuming a rebuild.",
        "Findings are evaluated mobile-first, since 74% of spend lands on mobile."
      ]
    },
    {
      "id": 6,
      "prompt": "We're Veldscript, a legal-tech SaaS. Google Ads traffic goes to a landing page with dynamic headline swapping keyed off utm_term — built by a contractor who left. I open the page and it looks great to me. Last month's numbers: Google Ads reports 412 conversions, GA4 shows 236 for the same page, so I've been reporting the average, 324, to leadership as the real number. That gives conversion rate = 324 / 41,000 sessions, about 0.8%. One more detail: clicks route through go.veldscript.com, a tracking redirect, before reaching the page. Can you audit the page? I'll paste the live URL and our top ad.",
      "expected_output": "An audit that tests the page with the real ad parameters instead of the bare URL, checks click-ID survival through the redirect, rejects the averaged conversion count as mixing incomparable measures, and refuses the conversion-rate math built on it.",
      "files": [],
      "expectations": [
        "The response instructs loading the page with the campaign's real ad parameters (actual utm_term values), not the bare URL the user opened.",
        "The response names the silent failure mode: the generic fallback variant can serve while the page still 'works', so nobody notices.",
        "The response requires verifying that the personalised headline variant actually renders for the campaign's real terms.",
        "The response flags the go.veldscript.com redirect as a place where the click ID (gclid) can be stripped, and requires verifying it survives through to the landing page.",
        "The response explains that stripped click IDs break the platform's ability to attribute and optimise.",
        "The response rejects the averaged figure of 324, stating platform-reported and on-site conversion counts must never be mixed in one calculation.",
        "The response explains the 412-vs-236 divergence via attribution-window and view-through differences: two different measures of different things.",
        "The response does not validate the 0.8% conversion-rate calculation built on the blended count.",
        "The response requires stating which of the two counts every subsequent observation uses (or picking one consistently).",
        "The message-match check covers the visual axis (does the hero echo the ad's creative), not only the headline wording.",
        "The response requests or uses the analytics funnel segmented by device and traffic source.",
        "No specific percentage conversion lift is promised anywhere in the response.",
        "The report reserves a place for inputs not yet received or checks not yet possible (e.g. session recordings, rendered check pending the URL), rather than treating the audit as complete without them."
      ]
    },
    {
      "id": 7,
      "prompt": "Full audit request for Marrowfield Goods, a DTC cookware brand. Meta cold prospecting drives /copper-set. The ad: video of a chef searing a steak in our copper pan, primary text 'The 5-piece copper set — 35% off this week', CTA 'Shop the set'. The landing page: headline 'Cookware, reimagined', hero is a moodboard collage of textures (no product visible), price appears only after clicking through to a separate product page, CTA button says 'Explore our collections'. Shipping cost first appears at the payment step. 28-day data: 46,000 sessions, 380 purchases, CPA $58 against a $35 target, 81% of sessions and spend on mobile. No session recordings or heatmaps are set up. Give me the full audit report.",
      "expected_output": "A complete report in the audit's shape: verdict paragraph first, a ranked fix list of at most seven led by the message-match failures (verbal, visual, offer, CTA), Baymard-backed shipping-cost finding, full labelling per fix, non-empty not-a-problem and could-not-check sections, and re-check predictions, with no lift promises.",
      "files": [],
      "expectations": [
        "The report opens with a one-paragraph verdict before any fix list.",
        "The report notes that upstream signals (CTR trend, frequency, tracking deduplication) were not supplied, and treats them as unchecked rather than silently assuming the page is the problem.",
        "The verbal message-match failure is identified: 'Cookware, reimagined' does not confirm the ad's '5-piece copper set — 35% off' promise.",
        "The visual message-match failure is identified: the moodboard hero does not echo the ad's chef-and-pan creative, and the fix reuses the ad's key visual.",
        "The offer-match failure is identified: the 35% offer and price are absent from the landing page, flagged as a policy-side bait-and-switch risk as well as a conversion leak.",
        "The CTA mismatch is identified: 'Explore our collections' does not carry the ad's 'Shop the set' action.",
        "The late-revealed shipping cost is flagged, citing late-revealed extra costs as the top stated abandonment reason in B2C checkout research (Baymard).",
        "The fix list contains at most seven items, with message-match fixes at or near the top.",
        "Each fix names the funnel step it unblocks and carries an evidence-class label, a source tier, a severity, and an effort bracket.",
        "Not every finding is marked critical.",
        "A not-a-problem section is present and non-empty.",
        "A could-not-check section is present and lists the absent session recordings/heatmaps with what that absence means for the findings.",
        "A re-check section gives, per fix, the funnel step expected to move, the direction, and a date or cadence for judging it.",
        "No specific percentage conversion lift is promised anywhere in the report.",
        "Findings are verified or scoped mobile-first, since 81% of sessions and spend are mobile."
      ]
    },
    {
      "id": 8,
      "prompt": "Growth PM at Quartzelle, B2C subscription meal kits. Our paid search landing page converts at 3.9%. Unbounce's benchmark report says the median page does 6.6% and paid search pages do 10.9%, so I've set the team target: get to 10.9%. Second: Lighthouse scores the page 68/100 on performance, so I want a speed sprint next month; for reference CrUX field data shows LCP 2.1s, INP 140ms, CLS 0.04 on mobile at p75. Traffic is 78% mobile sessions but 70% of revenue closes on desktop. CPA is $92 against a $40 target. The team's first proposed fix: change the button text from 'Submit' to 'Get my box'. Thoughts? Please also audit the page copy I pasted below: headline 'Dinner, solved', three benefit bullets, one photo of a delivered box, CTA 'Submit', FAQ accordion, no price shown before checkout.",
      "expected_output": "An audit that demotes the Unbounce medians to context, kills the speed sprint because field Core Web Vitals pass, weights devices by revenue rather than sessions, screens out the button tweak as too small for a 2.3x CPA gap while promoting offer-level work, and flags the missing ad as a blind spot.",
      "files": [],
      "expectations": [
        "The response rejects treating the Unbounce 6.6% / 10.9% medians as a target, presenting them as context only.",
        "The rejection names the caveat: a vendor dataset, self-selected, with conversion definitions varying by page type.",
        "The response rejects the speed sprint because the field Core Web Vitals already pass the 'good' thresholds.",
        "The response distinguishes lab data (Lighthouse) from field data (CrUX), treating field data as the deciding evidence.",
        "Speed is filed under the not-a-problem section, with the point that speed work on a passing page steals priority from message and offer work.",
        "Any Core Web Vitals thresholds cited match LCP 2.5s or less, INP 200ms or less, CLS 0.1 or less, at the 75th percentile.",
        "The response weights devices by where the money is: it notes desktop carries 70% of revenue and scopes fixes to both devices rather than mobile-only.",
        "The response screens out the 'Submit' to 'Get my box' button tweak as too small to plausibly close a 2.3x CPA gap, and says so explicitly.",
        "Given the CPA gap is a multiple of target, the response promotes offer and value-proposition-level work rather than settling for copy tweaks.",
        "The hidden price (no price before checkout) is flagged as an offer-clarity or trust finding.",
        "The response identifies that the actual ad was never supplied, and either requests it or marks the message-match check as blind or unverifiable without it.",
        "The response still audits the pasted copy rather than stopping at meta-commentary.",
        "No specific percentage conversion lift or forecast of reaching 10.9% is given anywhere in the response."
      ]
    },
    {
      "id": 9,
      "prompt": "Our CRO lead at Bindlegrove, a B2B webinar platform, wants more rigor. Landing page takes paid LinkedIn traffic; copy pasted below. Four asks: (1) compute the page's MECLABS score using C = 4m + 3v + 2(i-f) - 2a — ratings: motivation 7/10, value 6/10, incentive 4/10, friction 6/10, anxiety 5/10 — we'll track the score quarterly; (2) prioritize our backlog of 12 candidate fixes with ICE scores; (3) our founder loves the $300M button story — one word change made $300 million — so headline word tweaks go to the top of the backlog; (4) the signup is 4 clicks from the page and an exec wants everything within 3 clicks. Page copy: headline 'Webinars your prospects actually attend', demo CTA, one G2 badge, a 6-field form.",
      "expected_output": "A response that refuses to compute a MECLABS number (thought tool, not an equation), swaps ICE for evidence-weighted PXL-shaped scoring, corrects the $300M button retelling to the forced-registration friction lesson, rejects the 3-click rule in favour of information scent, and prioritises by efficiency.",
      "files": [],
      "expectations": [
        "The response refuses to compute a numeric MECLABS score, stating the heuristic is a thought tool, not an equation to solve.",
        "The response explains the coefficients express a thinking sequence (motivation first, then value, then incentive net of friction, then anxiety), not literal multipliers.",
        "The response notes motivation is largely pre-existing and external: a page refers to it and cannot create it.",
        "The response declines ICE as the prioritisation scheme, naming its weakness: the proposer guesses two of the three inputs and scores their own idea.",
        "The response recommends or applies evidence-weighted, mostly-binary scoring in the shape of PXL instead.",
        "At least two PXL-style binary questions appear (above the fold, noticeable within five seconds, on the paid entry path, backed by this page's data, backed by established research).",
        "The response corrects the $300M button retelling: the verified lesson is removing forced-registration friction discovered through user research, not a headline or button word change.",
        "The response notes the $300M case is a single anecdote, not a transferable lift template.",
        "Headline word tweaks are not placed at the top of the backlog on the strength of the anecdote.",
        "The response rejects the 3-click rule as having no supporting evidence.",
        "The 4-click signup path is judged by information scent per step rather than by click count.",
        "No specific percentage conversion lift is promised anywhere in the response.",
        "The prioritisation ranks by funnel step unblocked per unit of effort, with effort bracketed as time and coordination rather than a currency amount."
      ]
    }
  ],
  "trigger_queries": [
    { "query": "My Google Ads get tons of clicks but almost nobody converts once they hit the page", "should_trigger": true },
    { "query": "Can you audit the landing page for our Meta prospecting campaign?", "should_trigger": true },
    { "query": "Why isn't my landing page converting? Traffic from paid search looks healthy", "should_trigger": true },
    { "query": "CPA doubled but CTR is stable — I think something's wrong after the click", "should_trigger": true },
    { "query": "Run a post-click experience review on our demo booking page", "should_trigger": true },
    { "query": "Does my landing page actually match my ad? The headline feels off", "should_trigger": true },
    { "query": "Check message match between our search ads and the page they point to", "should_trigger": true },
    { "query": "Our form completion rate on paid traffic is terrible — where's the friction?", "should_trigger": true },
    { "query": "People click the ad, land, and bounce within seconds. What's broken?", "should_trigger": true },
    { "query": "Audit this page — it takes traffic from TikTok ads and converts under 1%", "should_trigger": true },
    { "query": "The ads perform fine, the page doesn't. Help me find the leaks", "should_trigger": true },
    { "query": "Need a conversion audit on the page behind our LinkedIn lead gen campaign", "should_trigger": true },
    { "query": "We send $30k a month of paid social to this URL and get almost no signups — tear it down", "should_trigger": true },
    { "query": "Landing page conversion rate dropped after our redesign, paid traffic only", "should_trigger": true },
    { "query": "My clicks are expensive and wasted — the page must be leaking somewhere", "should_trigger": true },
    { "query": "Is my hero section killing conversions from our YouTube ads?", "should_trigger": true },
    { "query": "review the post-click funnel for our google ads, from landing to lead", "should_trigger": true },
    { "query": "Our PPC agency claims the page is the problem — verify that for me", "should_trigger": true },
    { "query": "What's wrong with this signup page? All its traffic comes from paid ads", "should_trigger": true },
    { "query": "The demo page gets 5k paid visits a month and 12 bookings. Diagnose it", "should_trigger": true },
    { "query": "Check whether our landing page experience is dragging down our Google Quality Score", "should_trigger": true },
    { "query": "Mobile visitors from Instagram ads never reach the form — why?", "should_trigger": true },
    { "query": "Audit our Black Friday promo page before we put more spend behind it", "should_trigger": true },
    { "query": "Give me a prioritized fix list for the page our search campaigns land on", "should_trigger": true },
    { "query": "A consultant said we have message match issues — can you check the whole click path?", "should_trigger": true },
    { "query": "Ad clicks are up, conversions flat. Is the page or the offer the problem?", "should_trigger": true },
    { "query": "Why do people abandon our checkout right after clicking a retargeting ad?", "should_trigger": true },
    { "query": "Our lead form has 11 fields — is that why paid conversions are so low?", "should_trigger": true },
    { "query": "The client's page converts organic fine but paid traffic tanks — figure out why", "should_trigger": true },
    { "query": "Assess conversion friction on the page behind our Microsoft Ads campaigns", "should_trigger": true },
    { "query": "I need an audit of our free-trial page: paid traffic in, hardly any trials out", "should_trigger": true },
    { "query": "Look at this landing page and tell me what to fix first — we buy about 8k clicks a month to it", "should_trigger": true },
    { "query": "Ads got approved, clicks are cheap, but the page isn't doing its job", "should_trigger": true },
    { "query": "We're paying $6 a click and the page converts at 0.4%. Where do I start?", "should_trigger": true },
    { "query": "The page our promo ads point at feels off — full teardown please", "should_trigger": true },
    { "query": "Evaluate whether our landing page justifies the ad spend we're sending to it", "should_trigger": true },
    { "query": "Conversion on our paid landing pages is way below our email pages — audit the paid ones", "should_trigger": true },
    { "query": "Do a heuristic review of our SaaS trial page — traffic is 90% paid search", "should_trigger": true },
    { "query": "My boss wants to know why the campaign page isn't converting before we kill the campaign", "should_trigger": true },
    { "query": "Check our destination page for anything that could get our Google ads disapproved, plus general conversion issues", "should_trigger": true },
    { "query": "The visual in our ad and the page hero don't match at all — how bad is that, and what else is wrong?", "should_trigger": true },
    { "query": "Post-click audit for our webinar registration page, all traffic paid", "should_trigger": true },
    { "query": "Users click 'get 30% off' in the ad and land on a page that never mentions a discount — audit it", "should_trigger": true },
    { "query": "Something between the click and the thank-you page is eating our conversions", "should_trigger": true },
    { "query": "We doubled spend, conversions didn't move. The account looks clean — check the page", "should_trigger": true },
    { "query": "Score my landing page against conversion best practices — it runs on paid traffic only", "should_trigger": true },
    { "query": "Need to know if page speed is why paid mobile visitors don't convert", "should_trigger": true },
    { "query": "Our CRO consultant left mid-project — pick up the audit of our paid landing page", "should_trigger": true },
    { "query": "The dynamic headline swap on our page might not be working for ad traffic — investigate", "should_trigger": true },
    { "query": "why does nobody fill out the form after clicking our ads", "should_trigger": true },
    { "query": "Spent all week on the ad. Turns out the page might be the real problem — take a look", "should_trigger": true },
    { "query": "Give the landing page a once-over before Monday's campaign launch", "should_trigger": true },
    { "query": "Everything after the click is a black box — audit landing to conversion for our paid traffic", "should_trigger": true },
    { "query": "Clicks convert on desktop but mobile paid traffic does nothing — audit the page experience", "should_trigger": true },
    { "query": "Is our landing page experience wasting our ad budget?", "should_trigger": true },
    { "query": "Why did our CPA go up across the whole ad account? Targeting and pages haven't changed", "should_trigger": false },
    { "query": "Our ads used to work great and now they don't — run a full account diagnostic", "should_trigger": false },
    { "query": "CTR has been sliding for three weeks and frequency hit 6 — is our creative worn out?", "should_trigger": false },
    { "query": "How often should we refresh ad creative before it fatigues?", "should_trigger": false },
    { "query": "Conversions aren't showing up in Ads Manager — I think our pixel is broken", "should_trigger": false },
    { "query": "Pre-launch check: make sure our conversion events fire once and deduplicate", "should_trigger": false },
    { "query": "Meta claims 300 conversions but the CRM shows 170 — which number is real?", "should_trigger": false },
    { "query": "Why don't our Google Ads conversion numbers match GA4?", "should_trigger": false },
    { "query": "Write me five headline variants for our responsive search ads", "should_trigger": false },
    { "query": "Our ads all sound the same — generate fresh angles to test", "should_trigger": false },
    { "query": "Draft a creative brief my designer can execute for the spring campaign", "should_trigger": false },
    { "query": "Design an A/B test for three new ad concepts with budget per cell", "should_trigger": false },
    { "query": "Which of these five video hooks deserves test budget?", "should_trigger": false },
    { "query": "Write a UGC script a creator can film for our supplement brand", "should_trigger": false },
    { "query": "Build a negative keyword list from our search terms report", "should_trigger": false },
    { "query": "We're paying for junk clicks on irrelevant queries — block them", "should_trigger": false },
    { "query": "Should we switch from manual CPC to target CPA bidding?", "should_trigger": false },
    { "query": "Is my campaign on pace to spend the monthly budget or are we underspending?", "should_trigger": false },
    { "query": "How should I split $50k a month between Google and Meta?", "should_trigger": false },
    { "query": "Which ad platform should a B2B SaaS start advertising on?", "should_trigger": false },
    { "query": "Our campaign is crushing it — how fast can we scale the budget?", "should_trigger": false },
    { "query": "What's the maximum CAC we can afford given our margins?", "should_trigger": false },
    { "query": "Is a 3.2 ROAS good for an ecommerce store our size?", "should_trigger": false },
    { "query": "Design our retargeting stages, recency windows, and frequency caps", "should_trigger": false },
    { "query": "Turn our ICP into audience tiers for Meta prospecting", "should_trigger": false },
    { "query": "Which customers should seed our lookalike audience?", "should_trigger": false },
    { "query": "Map the buying committee we should target for enterprise deals", "should_trigger": false },
    { "query": "We have 40 campaigns all stuck in learning limited — should we consolidate?", "should_trigger": false },
    { "query": "Carousel or video — which ad format fits a consideration objective?", "should_trigger": false },
    { "query": "What ads are our competitors running right now?", "should_trigger": false },
    { "query": "How do I break into paid media as a career?", "should_trigger": false },
    { "query": "Write interview questions for hiring a media buyer", "should_trigger": false },
    { "query": "Which PPC newsletters and podcasts are worth following?", "should_trigger": false },
    { "query": "New client, brand-new ad account — where do we even start?", "should_trigger": false },
    { "query": "Plan a campaign that promotes our CEO's LinkedIn posts as ads", "should_trigger": false },
    { "query": "How do we get our product recommended inside ChatGPT answers?", "should_trigger": false },
    { "query": "Design a landing page for our new product launch", "should_trigger": false },
    { "query": "Write hero copy for our homepage redesign", "should_trigger": false },
    { "query": "Build me a high-converting landing page in Webflow", "should_trigger": false },
    { "query": "Audit my site's SEO — we've stopped ranking for our main keywords", "should_trigger": false },
    { "query": "Why did organic traffic to our blog drop last month?", "should_trigger": false },
    { "query": "Improve Core Web Vitals across the whole site", "should_trigger": false },
    { "query": "Run an accessibility audit on our web app", "should_trigger": false },
    { "query": "Review the landing page for our email newsletter campaign — all traffic comes from our list", "should_trigger": false },
    { "query": "Audit our pricing page — visitors arrive from organic search and word of mouth", "should_trigger": false },
    { "query": "Which A/B testing tool should we buy for the team?", "should_trigger": false },
    { "query": "Analyze the checkout funnel across the whole site, all channels blended", "should_trigger": false },
    { "query": "Set up heatmaps and session recordings on our site", "should_trigger": false },
    { "query": "Our ad got rejected for policy reasons — rewrite the ad copy so it passes review", "should_trigger": false },
    { "query": "Forecast the conversion lift we'd get from a site redesign", "should_trigger": false },
    { "query": "What's a good landing page conversion rate benchmark for SaaS?", "should_trigger": false },
    { "query": "Restructure our ad groups and keywords to raise Quality Score", "should_trigger": false },
    { "query": "Write the follow-up email sequence for leads after they convert", "should_trigger": false },
    { "query": "Our blog popup is annoying readers — should we remove it?", "should_trigger": false },
    { "query": "Compare Unbounce and Instapage for building landing pages", "should_trigger": false }
  ]
}
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall