landing-experience-checker

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: landing-experience-checker
slug: aaron-landing-experience-checker
displayName: "Landing Experience Checker · 落地页体验预检"
summary: "落地页体验预检/广告落地页一致性检查"
description: 'Use when the user asks to "pre-launch check the landing page", "run a Quality-Score preflight", or "verify ad-to-page message match before launch"; produces an ad↔page continuity report — message-match gaps, above-the-fold check, page-speed read, form-friction count, mobile-render flags — as a pass/fix punch list. Not for redesigning or rewriting the page — use landing-optimizer; not for scoring the account or the RQS — use ad-account-auditor. 落地页体验预检/广告落地页一致性检查'
version: "19.2.0"
license: Apache-2.0
compatibility: "Claude Code and compatible agent-skill hosts"
homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
when_to_use: "Use before a paid campaign goes live to preflight the destination page against the ads: message-match continuity, above-the-fold offer/CTA presence, page-load speed, form-field friction, and mobile rendering. Also when the user asks why an ad's Quality Score or landing-page-experience rating is likely to be low."
argument-hint: "<destination URL> [ad copy/headlines] [goal: dr|prospecting]"
metadata: {"author": "aaron-he-zhu", "version": "19.2.0", "discipline": "ad", "phase": "orchestrate", "geo-relevance": "low", "hermes": {"tags": ["marketing", "ad", "orchestrate"], "category": "ad"}, "openclaw": {"emoji": "🎯", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
---

# Landing Experience Checker

Preflights the destination page against the ads before launch — ad↔page message-match continuity, above-the-fold offer/CTA presence, page-load speed, form-field friction, and mobile rendering — and returns a pass/fix punch list. This works the ROAS **O (Offer)** lever from the post-click side: it is the Quality-Score / landing-page-experience relevance check that stands between finished creative and a go-live decision. It **checks only** — it does not rewrite or redesign the page (that is `landing-optimizer`) and it does not compute the RQS or run vetoes (that is `ad-account-auditor`).

## Quick Start

```
Preflight [destination URL] against these headlines: [paste] — flag message-match gaps before we launch
```

```
Run a Quality-Score landing preflight on [URL]: above-the-fold offer, speed, form friction, mobile
```

```
Ads point at [URL] but the landing-page-experience rating is "below average" — tell me which lever is failing
```

## Skill Contract

**Expected output**: an ad↔page continuity punch list — each of the five checks (message-match, above-the-fold, speed, form friction, mobile) marked Pass / Partial / Fix with the specific gap and the one lever to hand off, plus the standard handoff summary for `memory/ad/landing-experience-checker/`.

- **Reads**: the destination URL (or its pasted copy), the ad headlines/hooks that point at it, the promised offer/claim, ROAS profile (`direct-response|prospecting|incremental-profit`), and any `~~page speed` (PageSpeed/CrUX) read the user can run; accepted offer wording from the claims projection owned by [offer-claims-registry](../../../protocol/offer-claims-registry/SKILL.md), when present, to check the page still honors the live offer.
- **Writes**: a user-facing continuity report (the five-check punch list) and a reusable handoff summary.
- **Promotes**: confirmed message-match breaks and any page-experience blocker to `memory/hot-cache.md` and `memory/open-loops.md`; propose durable page-fix items as pending-decision, never as approved decisions.
- **Done when**: all five checks are run and marked Pass / Partial / Fix, every Fix names the specific gap (not "improve the page"), and each failing check routes to the one sibling that owns the repair.
- **Primary next skill**: [ad-account-auditor](../../activate/ad-account-auditor/SKILL.md) — the ROAS gate that scores the account and runs the launch go/no-go once the page is preflighted.

### Handoff Summary