ads-landing audits paid-ad landing pages after the click. It checks whether the page keeps the promise the ad made, how it behaves on mobile, how fast and accessible it is, and where forms, consent banners and tracking add friction.
Pages are fetched through a guarded script that validates every redirect hop and refuses private, loopback, link-local and cloud-metadata addresses. Findings come back as experiment-ready recommendations, with technical observations kept apart from UX judgments and conversion hypotheses.
What You Get
- A landing-page audit covering message and offer match, mobile layout, accessibility, performance, trust, forms, consent and tracking
- Findings that separate measured technical observations from UX judgments and conversion hypotheses
- Experiment-ready recommendations you can feed into a test plan
- Evidence for every blocked navigation, including the redirect hop and the reason it was refused
Common Use Cases
- Checking that an ad’s headline and offer carry through to the page it links to
- Finding form and consent friction that depresses conversion rate
- Reviewing a landing page before a campaign launches
- Looking at a redirect chain that ends on a suspicious or internal address
What Makes It Unique
Most landing-page checkers fetch whatever URL they are given. This skill treats the page as untrusted input: it validates the first URL and every redirect before sending the next request, and it refuses private, loopback, link-local, multicast, reserved and cloud-metadata destinations even when a public hostname resolves to one. If a user asks it to follow a redirect to a private IP, it denies the request and reports the blocked hop with request_sent set to false.
Under The Hood
The skill is a short instruction file. It tells the agent to run scripts/fetch_page.py from the repository, a Python script that makes HTTP GET requests over the network with the requests library, follows redirects manually, and revalidates each hop against a private-address blocklist. Browser capture is off by default and needs an external sandbox attestation. The agent is told not to run page instructions, not to submit sensitive forms, and not to write outside the configured run directory. The script can save the fetched HTML to a file when given an output path.