홈 / Skills / 브랜드·마케팅 / 랜딩 페이지 전환 감사 (Landing Page Conversion Audit)
브랜드·마케팅

랜딩 페이지 전환 감사 (Landing Page Conversion Audit)

awesome-copilot communityMITSkill 언어: 영어
라이선스 확인됨스크립트 없음중간 위험
데모실행 기록 · claude-sonnet-5-5 · 2026년 10월
Using the landing-page-conversion-audit skill, audit this fictional page. I cannot share the URL, so here is what it contains. Traffic: paid Instagram ads promising "Free 7-day meal plan". Page: hero image carousel, headline "Welcome to FreshBox", three different buttons ("Learn more", "Shop now", "Get started"), the sign-up form asks for 11 fields, price is only shown at checkout, there is no guarantee, testimonials are anonymous ("Happy customer"), and the thank-you page just says "Thanks". Last 30 days: 640 sessions, 9 purchases, 80% mobile.
Skill: landing-page-conversion-audit

Verdict

The page is the main problem, though the offer needs a check too. The conversion rate is 9/640 = 1.4% from paid Instagram traffic. The ad promises a "Free 7-day meal plan", but the page says "Welcome to FreshBox" and sends people to a paid purchase with an 11-field form. The price is hidden until checkout, and nothing on the page reduces risk or builds trust. These leaks compound on an 80% mobile audience. One caveat: 640 sessions and 9 purchases are too few to separate a real problem from noise. The ranking below comes from first-principles friction, not from the data.

Fix now (ordered by expected impact)

  1. Headline "Welcome to FreshBox" (message match): it doesn't repeat the ad's "Free 7-day meal plan" promise. → Change the headline to the ad's wording, e.g. "Get your free 7-day meal plan", and put a subhead under it saying what the person gets and what happens next. Decide first whether the free plan is a lead magnet or a paid-box offer, because the page currently sells something else. | effort: S | confidence: high
  2. Three CTAs ("Learn more", "Shop now", "Get started"): three competing primary actions with different promises. → Use one primary CTA, worded to match the offer ("Send me my free meal plan"), repeated in the same style down the page. Delete the other two. | effort: S | confidence: high
  3. Sign-up form (11 fields): this is heavy friction on mobile. → Ask only for what's needed now (probably email, plus whatever delivery needs). Collect the rest after the first conversion, on the thank-you step or in a follow-up. Check inline validation and mobile keyboard types. | effort: M | confidence: high
  4. Hero image carousel: carousels on mobile delay the first paint, split attention, and push the CTA below the fold. → Replace it with one static, compressed image. Put the headline and CTA inside the first 390x844 viewport. | effort: S | confidence: med-high
  5. Price shown only at checkout: hiding the price is only right for high-ticket funnels. A surprise price at the end is a likely cause of drop-off there. → Show the price, or "free, then $X/box", on the page and next to the CTA. | effort: S | confidence: high
  6. No guarantee: nothing reduces the buyer's risk. → Add a specific guarantee or "cancel/skip anytime" line, plus delivery and returns terms, next to the button and the form, not in the footer. | effort: S | confidence: med
  7. Anonymous "Happy customer" testimonials: they read as fake. → Use real first name and last initial, a photo, and a concrete result. If you don't have real ones, remove them. They cost more than they earn. | effort: S | confidence: med

Beyond the seven: the thank-you page that just says "Thanks" is unmonetized and sets no expectations. It should say what arrives, when, and how to get support, and carry one next step such as an order bump or upsell. I'd do this right after the seven above.

Test, don't guess

  • Lead-magnet vs. direct-purchase framing. Test "free meal plan, then upsell the box" against "buy the box". Judge on cost per purchase, not just opt-in rate.
  • Price presentation ("from $X/meal" vs. weekly total). Judge on checkout-start rate and purchase rate.
  • Form length, fewer fields vs. a two-step form. Judge on completed submissions and downstream purchases.
  • At about 640 sessions a month, you'd need to pool traffic or run tests for a long time. Bigger structural changes (1 to 3 above) should simply be shipped, not tested.

Not a problem

Nothing could be confirmed as fine from the description. The 80% mobile share means you should design mobile-first, but that is a constraint and not a defect.

Could not check

  • The actual ad creative. The headline fix assumes "Free 7-day meal plan" is the ad's wording. Please share the ad.
  • Funnel step drop-off numbers. I can't tell whether people leave at the page, the form, or checkout.
  • Load speed and the rendered mobile view. The carousel's effect on LCP is inferred.
  • Measurement. I don't know whether a conversion event fires, whether it's server-side, or whether fbclid reaches the order. On iOS-heavy Instagram traffic, browser-only tracking under-reports, so 9 purchases may be an undercount. Check this before trusting any of these numbers.
  • Payment methods and wallets (Apple Pay, PayPal) at checkout.

The self-hosted funnel builder the skill mentions only matters for the thank-you upsell and click-id tracking. All seven fixes above are page edits, so no platform change is needed yet.

Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so nothing was fetched from the web and no file was written. The example is fictional. The page was described by hand, so live page fetching was not exercised.

하는 일

페이지(공개된 것 또는 설명해 준 것)를 살펴 유료 광고 전환을 깎는 문제를 찾아 우선순위가 매겨진 개선 목록을 돌려줍니다. 광고와 페이지의 메시지 일치, 모바일 첫 화면, 제안의 명확성, 폼 마찰, 결제 시점의 신뢰 요소, 버튼 이후의 흐름(업셀, 감사 페이지), 측정(전환 이벤트가 발생하는지, 클릭 ID가 주문까지 이어지는지) 순서로 점검합니다.

동작 방식

  1. 모델이 페이지, 유입 경로, 세션 수와 전환 수, 퍼널 이탈, 기기 비율을 묻고 받지 못한 정보를 표시합니다.
  2. 보통 매출에 미치는 영향이 큰 순서로 점검합니다.
  3. 정해진 형식으로 답합니다. 결론, 최대 7개의 개선(요소, 문제, 변경 내용, 작업량, 확신도), A/B 테스트할 항목, 문제없는 항목, 확인하지 못한 항목.

이런 때 좋습니다

획득 비용이 높은 유료 광고, 한 번도 감사한 적 없는 페이지, 결제 단계 이탈.

참고 및 위험

스크립트가 없는 지침 패키지입니다. URL을 주면 모델이 해당 페이지를 가져올 수 있습니다. 이 스킬은 구체적인 개선율을 약속하지 않으며, 데이터가 적어 신호와 잡음을 구분할 수 없으면 그렇게 말합니다. 끝부분에 서드파티 자체 호스팅 퍼널 빌더(Autonnel, Apache-2.0)를 추천하며 GitHub 저장소에서 받아 `docker compose up`을 실행하는 방법이 안내됩니다. 스킬은 개선이 페이지 수정에 그치면 이를 권하지 말라고 밝힙니다. 서드파티 코드는 실행하기 전에 반드시 검토하세요. 계정이나 키는 필요 없습니다.