Landing-page structure + ad→lander congruence audit. 600-ad TrendTrack sample, 11 live Alevia PDPs and 9 redirects resolved, 4 live Dawn destinations fetched the same evening.
Alevia runs no advertorial layer at all. The morning read's "shared bridge /amla/33" was wrong — every short link is a vanity 301 straight to a numbered PDP. Their whole 3.6k-ad machine lands direct on product pages.
The real system: one template, one price, ~4 ingredient SKUs — and a numbered PDP clone per condition lane whose mechanism block, FAQ objection, timelines, survey stats and reviews are all re-skinned to continue the exact sentence the ad's reveal started. Congruence is mechanism-level, not topic-level.
Dawn matches them at the avatar level (2 skinned PDPs, real beat continuity) and stops there: 8+ angles pour into 2 skins. Their condition axis is our angle axis — that's the transferable machine.
Numbers are arbitrary (/pom/11 ≠ pomegranate-11). The alias exists because alevia.com/amla/33 inside a first-person story reads like a shared community link, not a store URL — and it gives per-lane click routing with a clean surface, no visible UTM.
H1, price, buy box never change. The product is a commodity vessel; the lander is a condition-mechanism skin. What actually swaps per numbered clone:
| Slot | pomegranate-22 · kidney | amla-74 · blood pressure |
|---|---|---|
| Meta description | "protein stops leaking, the foam disappears, numbers finally…" | "repair the damaged lining inside your blood vessels…" |
| FAQ objection | "different from cranberry, kidney detox teas…?" | "different from Beetroot, Garlic, or Magnesium?" |
| Advertorial H2 | "The Reason Your Kidney Numbers Keep Dropping Is Not What You Were Told" | "The Reason Why Your Blood Pressure Keeps Climbing Is Not What You Were Told" |
| Mechanism section | "Defend the filters from the core" | "Support your vessels from the core" |
| Decline timeline | "How Kidney Damage Progresses Over Time" | "How Blood Pressure Damage Progresses Over Time" |
| Recovery timeline | "What To Expect As Your Filters Recover" | "What to Expect as Your Vessel Wall Gets Stronger" |
| Survey-stat quotes | "My eGFR stopped dropping for the first time in years" | "My cuff numbers came down without medication" |
| Ingredient story | pomegranate "The Fruit of Life", punicalagins | amla "The Nurse", emblicanins |
Keyword density confirms total skin discipline: amla-28 = 45× nerve · amla-88 = 35× cholesterol · amla-74 = 21× blood pressure · pomegranate-47 = 13× blood sugar + A1C · pomegranate-22 = 15× kidney + 6× dialysis. Cross-condition bleed: 1–4 stray mentions.
Fixed skeleton on every variant: buy box + accordion (Description / Results / 90-Day Guarantee / Shipping) → testimonial band → FAQ → advertorial block below the buy box: "The Reason…" → mechanism → decline timeline → recovery timeline → Real Stories → comparison table → survey stats → Verified Reviews. The ad did the selling; the lander closes and kills objections, with depth for scrollers. Generalist fallbacks ("Why Feeling 'Off' Is Not a Willpower Problem") catch mixed-lane traffic with the softest claims.
| Lander | Ads | Copies | Max days | Dominant sources | Congruence |
|---|---|---|---|---|---|
| amla-192011 generalist | 120 | 58 | 127 | Wellness Insider, Arthritis, Cholesterol, BP Journal | catch-all for multi-lane + brand checklist evergreens |
| pomegranate-22 kidney | 95 | 31 | 64 | Julie Anderson, Laura Peterson, Clinic, Jessica | ALL persona-page kidney-dialysis stories |
| pomegranate generalist | 77 | 46 | 77 | Blood Sugar Journal, Wellness Insider, Arthritis | new-ingredient incubation + mixed lanes |
| amla-88 cholesterol | 59 | 19 | 100 | Wellness Journal (video), 2× Cholesterol pages | cholesterol lane + video traffic |
| pomegranate-56 blood pressure | 49 | 18 | 64 | BP Journal 39/49 | hard lane-locked |
| pomegranate-47 blood sugar | 48 | 24 | 70 | Blood Sugar Journal 36/48 | hard lane-locked |
| amla-11 soft generalist | 37 | 30 | 43 | Nerve, Arthritis, BP, Cholesterol (spread) | typed-link / compliance target |
| amla-74 blood pressure | 28 | 8 | 113 | Wellness Journal + persona BP stories | oldest pair: 113d copy ↔ 113d lander |
| amla-28 nerve | 26 | 5 | 118 | Wellness Journal + Nerve Community | nerve lane + video |
| garlic detox | 21 | 7 | 77 | Detox Support Community 19/21 | newest lane, own skin from day one |
The Nurse Teresa BP ad's reveal — "the inner wall of your vessels… can't relax on their own" — is continued verbatim by amla-74's meta description: "repair the damaged lining inside your blood vessels so they relax on their own." The lander picks up the ad's sentence mid-thought. Same on kidney (ad's foam imagery → "the foam disappears") and blood sugar (Metformin rants → "how fast food becomes sugar"). The failed-solution stack the ad genericizes is the same list the lander FAQ names and kills.
113-day-old copy runs on a 113-day-old lander; new lanes (garlic/detox, pomegranate/kidney) launched with their own skin from day one. The lander is part of the tested cell — kept or killed with the copy, never a shared endpoint.
Community page, persona page, clinic page and video page all pour into the same lander when the condition matches — kidney stories from four different pages → pomegranate-22. The lander axis is the condition; the page axis is trust-register.
template_suffixExactly the U/Z/V pinning mechanism already proven on 4 stores (pending P2 lander_builder.py cleantt mode industrializes it). Swap per variant, mirroring the measured Alevia slot set: headline block, mechanism lead, failed-stack FAQ item, 3–4 survey stats, review pick, meta description. Buy box, price, guarantee untouched.
Lane-B wrong-label / treatment-gap (current winner's mechanism verbatim) · lane-A stakes / school-consequences · lane-A witness (pairs with the dad-POV pilot). Every new-angle pilot launches with its lander variant — tested as one cell, kept or killed as one cell.
/w/<n> → variant URL, one per lander, used in primary text per the winner skeleton. Shopify native URL redirects — zero infra.
"Could the lander's first advertorial H2 be the next sentence of the ad's reveal?" That is the entire Alevia trick as one audit question.
Built 8-12, unpublished — already follows this doctrine for lane C. Goes live when lane C pilots launch.
Fake survey-percentage widgets (animated counters claiming "% saw real improvement" — fabricated-stats exposure we don't need) · the soft-lander/hard-lander typed-vs-CTA split (their compliance cloak; our claim book doesn't require it) · 13-lander sprawl at our 2-page scale.
All insight + query endpoints now return insufficient_credits (pool 0). The morning 600-ad pull consumed most of the monthly pool; evening probes (~145 rows) burned the remainder, and one 40-ad re-pull was lost to an overwrite before the credit error surfaced (fully redundant with the on-disk 600). Everything in this report runs off disk data + live page fetches, which are free. Next TrendTrack read: check credit state first — the tracker list appears free, row-returning endpoints are metered.
The "shared bridge /amla/33" claim in both morning docs (native-anatomy §links, application-recs §2 funnel analog) has been patched in place with the resolved-redirect evidence. The §2 "test one shared story-bridge per lane" recommendation was built on that false premise — Alevia's evidence now argues for angle-matched PDP variants instead.