agentleFS
HainrixzHainrixz/claude-ads/skills/ads-landing/SKILL.md

ads-landing

Skill102 starsChanged 6 months agoMITView on GitHub

Landing page quality assessment for paid advertising campaigns. Evaluates message match, page speed, mobile experience, trust signals, form optimization, and conversion rate potential. Use when user says landing page, post-click experience, landing page audit, conversion rate, or landing page optimization.

9 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ads-apple.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • chriswesttSkill

    ads-apple

    Apple Ads (formerly Apple Search Ads) deep analysis for mobile app advertisers. Evaluates campaign structure, bid health, Custom Product Pages (CPPs), MMP attribution, budget pacing, TAP coverage (Today/Search/Product Pages), Maximize Conversions bidding, and goal CPA benchmarks by country. Use when user says Apple Ads, Apple Search Ads, ASA, App Store ads, Apple ads, Search Ads, or is advertising a mobile app on iOS.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 4 are common, 0 are distinctive, and 2 are very specific to this project.

  • 4

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ads/references/benchmarks.md for conversion rate benchmarks

    line 13
  2. Very specific:

    Read ads/references/conversion-tracking.md for pixel/tag verification

    line 14
  3. Common:

    Keyword match: search keyword appears naturally in page content

    line 28
  4. Common:

    No lazy loading for below-fold content

    line 55
  5. Common:

    No interstitials or popups blocking content on load

    line 70
  6. Common:

    Use multi-step forms for 5+ fields (progressive disclosure)

    line 100

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Portions Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) - see LICENSE for original authors · tododeia.com · id er-fd4fa55b -->

Landing Page Quality for Ad Campaigns

Process

  1. Collect landing page URLs from active ad campaigns
  2. Read ads/references/benchmarks.md for conversion rate benchmarks
  3. Read ads/references/conversion-tracking.md for pixel/tag verification
  4. Assess each landing page for ad-specific quality factors
  5. Score landing pages and identify improvement opportunities
  6. Generate recommendations prioritized by conversion impact

Message Match Assessment

The #1 landing page issue in ad campaigns: does the page match the ad?

What to Check

  • Headline match: landing page H1 reflects ad copy headline/keyword
  • Offer match: promoted offer (price, discount, trial) is visible above fold
  • CTA match: landing page CTA matches ad's promised action
  • Visual match: consistent imagery between ad creative and page
  • Keyword match: search keyword appears naturally in page content

Message Match Scoring

LevelDescriptionScore
Exact matchHeadline, offer, CTA all align perfectly100%
Partial matchHeadline matches but offer/CTA differs60%
Weak matchGeneric page, loosely related to ad30%
MismatchPage content doesn't reflect ad promise0%

Page Speed Assessment

Slow pages kill conversion rates. For every 1s delay, CVR drops ~7%.

Thresholds (Ad Landing Pages)

MetricPassWarningFail
LCP<2.5s2.5-4.0s>4.0s
INP<200ms200-500ms>500ms
CLS<0.10.1-0.25>0.25
Time to Interactive<3.0s3.0-5.0s>5.0s
Page weight<2MB2-5MB>5MB

Common Speed Issues in Ad Pages

  • Hero images not compressed (use WebP/AVIF)
  • Too many third-party scripts (chat widgets, analytics, heatmaps)
  • Render-blocking CSS/JS above fold
  • No lazy loading for below-fold content
  • Font files not preloaded

Mobile Experience

75%+ of ad clicks come from mobile. Mobile experience is critical.

Mobile Checklist

  • Tap targets: ≥48x48px with ≥8px spacing
  • Font size: ≥16px body text (no pinch-to-zoom needed)
  • Form fields: properly sized, keyboard type matches input (email, phone, number)
  • CTA button: full-width on mobile, visible without scrolling
  • No horizontal scroll
  • Images responsive and properly sized
  • Phone number clickable (tel: link)
  • No interstitials or popups blocking content on load

Trust Signals

Above-the-Fold Trust Elements

  • Company logo visible
  • Social proof (customer count, reviews, ratings)
  • Security badges (SSL, payment security, guarantees)
  • Recognizable client logos (B2B)
  • Star ratings or testimonial snippet

Below-the-Fold Trust Elements

  • Full testimonials with names, photos, companies
  • Case study highlights with specific metrics
  • Certifications, awards, accreditations
  • Privacy policy link
  • Physical address/phone number (local service businesses)

Form Optimization

Form Length Impact on CVR

FieldsExpected CVR ImpactUse Case
1-3 fieldsHighest CVRTop-of-funnel, free offer
4-5 fieldsModerate CVRMid-funnel, qualified leads
6-8 fieldsLower CVRBottom-funnel, sales-ready
9+ fieldsLowest CVROnly for high-value offers

Form Best Practices

  • Pre-fill fields where possible (UTM data, known info)
  • Use multi-step forms for 5+ fields (progressive disclosure)
  • Show progress indicator on multi-step forms
  • Inline validation (don't wait until submit to show errors)
  • Error messages are clear and helpful
  • Submit button text is specific ("Get My Free Quote" not "Submit")
  • Thank you page has clear next steps

Landing Page Health Score Algorithm

Landing Page Health Score = (Message Match x 0.25) + (Page Speed x 0.25) + (Mobile x 0.20) + (Trust x 0.15) + (Form x 0.15)

Each component is scored 0-100, then weighted. Final score maps to grade: A (90-100), B (75-89), C (60-74), D (40-59), F (<40).

Consent Banner Impact

Flag if any of the following are true:

  • Consent banner covers the primary CTA on load
  • Consent banner delays form interaction by >1 second
  • Consent banner pushes critical content (headline, offer, CTA) below the fold
  • Banner cannot be dismissed on mobile without scrolling

Consent Mode V2: Verify Consent Mode V2 implementation for EU/EEA traffic to ensure tracking data quality. Without Consent Mode V2, conversion modeling is degraded and remarketing audiences shrink significantly.

Quick Wins

PriorityFixExpected Impact
1Move primary CTA above the fold on all devices+15-25% CVR
2Reduce form fields to essential only (name, email, one qualifier)+10-20% CVR
3Add trust badges near CTA (security, guarantee, reviews)+5-15% CVR
4Optimize hero image (WebP/AVIF, <200KB, proper dimensions)-1-2s load time
5Fix mobile tap targets (>=48x48px with >=8px spacing)+5-10% mobile CVR

Ad-Specific Landing Page Elements

UTM Parameter Handling

  • UTM parameters captured and stored (for attribution)
  • Click IDs preserved: gclid (Google), fbclid (Meta), ttclid (TikTok), msclkid (Microsoft)
  • Parameters passed to form submissions or CRM

Dynamic Content

  • Dynamic keyword insertion in headline (Google Ads feature)
  • Location-specific content for geo-targeted campaigns
  • Audience-specific messaging (different pages for different segments)
  • A/B testing active on key elements (headline, CTA, hero image)

Conversion Tracking

  • Thank you page/event fires correctly for all platforms
  • Form submission triggers conversion event
  • Phone call tracking configured (if applicable)
  • Chat/live agent triggers tracked as micro-conversions

Landing Page Quality by Platform

PlatformKey RequirementNotes
GoogleQS component: landing page experienceDirectly affects ad rank and CPC
MetaPage load speed criticalSlow pages = Meta penalizes delivery
LinkedInProfessional, B2B appropriateMatch LinkedIn's professional context
TikTokMobile-first mandatory95%+ TikTok traffic is mobile
MicrosoftDesktop-optimized matters moreHigher desktop % than other platforms

Output

Landing Page Assessment

Landing Page Health

Message Match:    ████████░░  XX/100
Page Speed:       ██████████  XX/100
Mobile:           ███████░░░  XX/100
Trust Signals:    █████░░░░░  XX/100
Form Quality:     ████████░░  XX/100

Deliverables

  • LANDING-PAGE-REPORT.md: Per-page assessment with scores
  • Message match analysis per ad-to-page combination
  • Page speed improvement priorities
  • Mobile experience fixes
  • Form optimization recommendations
  • Quick Wins sorted by conversion impact

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.