Landing Page & Ad Message Match Auditor

Audit the landing pages behind your Meta, Google, LinkedIn or TikTok ads before you spend another dollar on traffic. The Actor fetches each page, checks it against 20 conversion and compliance rules, measures how well the page echoes your ad copy (message match) and returns a scored dataset plus a Markdown report you can forward to a client.

What it does

• Message match score: how many meaningful terms of your ad headline and primary text appear in the page title, H1 and opening copy. Low match = wasted clicks and lower Quality Score.
• Conversion readiness: H1 count, recognizable calls to action, lead form presence and length, trust signals (testimonials, guarantee, social proof), pricing, phone/email/address, chat and video.
• Tracking and compliance: GA4 / GTM / Clarity / Hotjar analytics, conversion pixels (Meta, Google Ads, TikTok, LinkedIn, Microsoft, Pinterest, Snap, X), consent manager presence, privacy policy link, HTTPS.
• Mobile and speed proxies: viewport meta, html lang, HTML weight, server response time, external and render-blocking scripts, images without alt.
• SEO basics and tech: title and meta description length, canonical, robots, Open Graph, structured data, hreflang, detected platform (WordPress, Shopify, Webflow, Next.js, HubSpot CMS and more).
• Report: REPORT (Markdown) in the key-value store with a summary table and one findings table per page, ready to paste into a client deck.

Input

Field	Type	Default	Description
urls	array of strings	required	Landing page URLs (max 500). One billable event per audited page.
adCopy	string	""	Ad headline + primary text used for the message match score.
pairs	array of {url, adCopy}	[]	Per-URL ad copy when every page has its own ad.
targetKeywords	array of strings	[]	Keywords that must appear on the page; reported found / missing.
maxItems	integer	100	Hard cap on audited pages per run.

Output

One dataset item per page with score (0–100), grade (A–F), messageMatch (score, matched and missing terms, H1/title echo), cta, forms, trust, tracking, mobile, speed, seo, tech, the full findings list (PASS / WARN / FAIL / INFO with a human message) and topFixes (three most important fixes). The overview dataset view shows the scoreboard. The key-value store contains REPORT (Markdown) and OUTPUT (run summary with the average score).

Example item (shortened):

{
  "finalUrl": "https://example.com/lp",
  "score": 88,
  "grade": "B",
  "messageMatch": { "score": 100, "matchedTerms": ["roof", "repair", "austin"], "missingTerms": [], "h1Match": true },
  "cta": { "count": 2, "texts": ["Get a free quote", "Call now"] },
  "tracking": { "hasAnalytics": true, "hasAdPixel": true, "consentManager": true },
  "topFixes": ["Meta description 32 chars", "No html lang attribute"]
}

Pricing and cost control

Pay per event: Landing page audited (page-audited) — one event per page that returned a response. Unreachable pages are still reported but produce a FAIL item; set maxItems to cap the number of pages (and therefore the cost) of a run. Typical run: 20 pages in under a minute at 256 MB.

Limitations and fair use

• The audit analyzes the HTML the server returns; content injected only by JavaScript (single-page apps) may be invisible, which is itself reported as low word count.
• Response time is measured from Apify's servers and is a proxy, not a Core Web Vitals lab result.
• Only publicly reachable pages; no logins, paywalls or CAPTCHA solving.
• Rules are heuristics tuned for lead-generation and e-commerce landing pages in English, Polish and German; scores compare pages against each other, not against a universal benchmark.

Example

Input: three landing pages plus the ad text "Start your free trial today. Build an online store in minutes with no coding." Output: three scored items and a report showing which page echoes the ad, which one has no conversion pixel and what to fix first. See examples/input.json and examples/output.json.

Use cases

• Agencies: pre-launch QA of every client landing page; monthly audit deliverable.
• Media buyers: diagnose low conversion rates and poor Quality Score caused by message mismatch.
• CRO teams: generate A/B hypotheses from the topFixes of each page.