--- name: build-a-high-converting-ecommerce-landing-page description: >- Plans and validates a dedicated, navigation-free ecommerce landing page for paid campaigns - promo pushes, seasonal offers, single-product or bundle drops aimed at cold Display/YouTube/Demand Gen traffic. It settles the LP-vs-product-page question first, defines the offer and messaging angle by traffic temperature, lays out a proof-early persuasion structure, and wires post-launch monitoring through gads_get_shopping_performance, gads_get_geo_performance, and ga4_run_report, with gads_generate_rsa_copy keeping ad and page promises identical. The page build itself is human work. Do not use it for Shopping/PLA destinations - those visitors expect a normal product page (build-a-high-converting-product-page) - nor for lead-gen/SaaS pages (build-a-high-converting-landing-page), nor when the leak is after add-to-cart (optimize-cart-and-checkout-flow). --- # Build a Dedicated Ecommerce Landing Page ## Purpose Creates a single-purpose ecommerce page with no site navigation, built to convert paid traffic on one offer. Unlike a product page, everything a visitor needs to decide lives on this one page, exits are removed, and the structure runs proof-early: the product visual already says what is for sale, so the page's first job is convincing the visitor it works. ## When to run - A promotion or seasonal sale needs a focused destination separate from the catalog. - A single-product or bundle campaign targets cold traffic on Display, YouTube, or Demand Gen. - You want to test messaging independently of the live product page. - The standard product page underconverts for paid traffic and a more persuasive alternative is worth trying. ## When NOT to run - Traffic comes from Shopping PLAs or product-feed placements - those clicks expect a product page with navigation; a stripped page confuses them → build-a-high-converting-product-page. - The destination is for lead-gen or SaaS conversion → build-a-high-converting-landing-page. - Add-to-cart is fine but purchases stall → optimize-cart-and-checkout-flow. - The offer (price, promo mechanics, guarantee) is not yet decided - that is a business decision that precedes this skill. - The existing product page already converts well for paid traffic - no dedicated page needed. ## Prerequisites - Finalized offer: product/bundle contents, current and comparison price, shipping terms, guarantee, and a genuine urgency driver if one exists. - Product assets: images/video, specs, and a curated set of 5-10 strong customer reviews (photos help). - Campaign context: traffic source, audience temperature, and the ad concept that will run. - GA4 ecommerce events (add_to_cart, purchase) implemented and verifiable. ## Procedure 1. **Confirm the destination decision.** Walk the gate in the decision rules. If the traffic profile says product page, stop here and switch skills - this is the cheapest mistake to avoid. 2. **Pull performance context.** If the product already sells, use `gads_get_shopping_performance` to see its current CVR/ROAS baseline and `gads_get_geo_performance` for regional skews worth reflecting in shipping or urgency copy. 3. **Write the offer sheet.** One document: what exactly is sold, current price, original price and savings, shipping terms, guarantee wording, and the legitimate buy-now reason. Every element gets a home on the page; anything missing here becomes a hole in the page later. 4. **Choose the messaging angle by traffic temperature** (decision rules below) - offer-led for warm and retargeting traffic, benefit-led for mid-intent search, transformation-led with the full persuasion arc for cold audiences. 5. **Outline the page in proof-early order:** (a) product-forward hero with visible price and a short positioning line plus the buy CTA; (b) customer evidence - aggregate ratings, curated reviews, user photos; (c) outcome-framed benefits tied back to the evidence; (d) specs, comparisons, and what-is-included details; (e) purchase reassurance - guarantee detail, shipping clarity, sizing help, FAQ; (f) a genuine act-now trigger; (g) closing recap with price, CTA, express-pay buttons, and a final risk-removal line. 6. **Draft copy.** Visitor-first and specific: name the saving in currency, the durability in numbers, the delivery in dates. Place a CTA after the hero, after the evidence block, and at the close - three minimum. The model can draft copy; sign-off is a HUMAN STEP. 7. **Align the ads.** Use `gads_generate_rsa_copy` seeded with the page's exact promise so ad and hero say the same thing. If ads are then created or edited via VigilDog tools, consult `gads_policy_guardrail` before the session's first Google Ads write, preview with validate_only, and apply only after explicit user approval. 8. **HUMAN STEP (outside VigilDog):** build the page. Strip all header/footer navigation and outbound links; alternate image and text blocks; give CTAs the highest-contrast color on the page; design at a small mobile viewport first. 9. **HUMAN STEP (outside VigilDog):** configure the checkout path - straight to checkout for a fixed product/bundle, or add-to-cart-then-checkout when the visitor picks a variant on the page. Fewest possible steps between CTA click and payment. 10. **HUMAN STEP (outside VigilDog):** pre-launch test on a real phone: read the whole page, complete a test purchase, confirm page-view/add-to-cart/purchase events fire, confirm there is no clickable route off the page, confirm sub-3-second load. 11. **Launch and monitor.** Point the campaign at the page. For the first two weeks, track CVR and revenue through `gads_get_shopping_performance` (or campaign-level pulls) and bounce, time on page, add-to-cart and purchase events through `ga4_run_report` filtered to the page path. 12. **Route follow-ups.** High bounce → recheck ad-to-hero message match. Long time-on-page but low conversion → strengthen evidence and objection blocks. Strong add-to-cart but weak purchase → optimize-cart-and-checkout-flow. Stable baseline → run-a-landing-page-a-b-test on the hero or offer framing. ## Decision rules - **Dedicated LP vs product page:** promotion/seasonal push, cold-channel traffic, or independent message testing → dedicated LP. PLA/feed traffic, variant browsing, or an already-strong product page → product page. - **Angle by source:** branded search → lead with price/offer, light persuasion. Generic product search → lead with benefits, heavy proof. Display/YouTube cold → lead with the problem or transformation, full sequence. Retargeting → lead with urgency and the remaining objections. - **Structure:** price visible without scrolling; evidence before benefit claims; minimum three CTAs; zero navigation elements. - **Urgency:** only real constraints - a countdown that resets on refresh permanently burns trust. - **Speed floor:** under 3 seconds on mobile before spend flows. ## Common failure modes - **Sending Shopping traffic to the stripped page.** PLA clicks expect a product page; bounce spikes and the test reads as a page failure when it was a routing failure. - **Fake scarcity.** Reset timers and permanent "only 2 left" labels get screenshotted and destroy the brand's credibility beyond this campaign. - **Navigation leaks.** One clickable logo in the header quietly drains a percentage of buyers back into the catalog; audit every clickable element. - **Ad-page promise drift.** The ad says 50% off, the hero says "premium quality" - the visitor assumes the deal is gone. Repeat the ad's promise verbatim in the hero. - **Launching without a test purchase.** A broken variant selector or failing payment step can burn days of cold-traffic budget before anyone notices. ## Related skills - **Before:** create-an-irresistible-offer (offer mechanics), set-up-google-ads-conversion-tracking (purchase tracking). - **After:** optimize-cart-and-checkout-flow (post-click funnel), run-a-landing-page-a-b-test (message testing), monitor-landing-page-performance (recurring watch). - **Siblings:** build-a-high-converting-product-page (PLA/organic destination), build-a-high-converting-landing-page (lead-gen/SaaS).