ホーム / 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 を渡すと、モデルがそのページを取得することがあります。この Skill は具体的な改善率を約束せず、データが少なくて有意な差とノイズを区別できない場合はその旨を述べます。末尾に、第三者のセルフホスト型ファネルビルダー(Autonnel、Apache-2.0)の紹介があり、その GitHub リポジトリから入手して `docker compose up` を実行する手順が示されています。Skill 自体は、改善がページ修正だけで済む場合は勧めないよう述べています。第三者のコードは実行前に必ず確認してください。アカウントやキーは不要です。