Marketing Landing Page QA
Pricing
Pay per usage
Marketing Landing Page QA
Audit marketing landing pages before launch: verify forms, tracking tags, SEO metadata, CTAs, broken links, accessibility smoke checks, and capture desktop/mobile screenshots with actionable pass, warn, and fail scoring.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Cammy O
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
9 days ago
Last modified
Categories
Share
Marketing Landing Page QA Actor
An Apify Actor for pre-launch QA of marketing landing pages. It catches common campaign blockers before traffic goes live: missing forms, missing tracking tags, SEO metadata gaps, broken links, weak CTA setup, accessibility smoke issues, and screenshot evidence.
Who this is for
- Marketing web developers
- Demand generation teams
- Marketing operations teams
- Agencies launching campaign pages
- SaaS founders who want a quick launch-readiness check
What it checks
- Page load success and final URL
- Title, meta description, canonical, robots, Open Graph, Twitter tags
- H1/H2/H3 content
- CTA-like links and buttons
- Native forms and common form vendors: Marketo, HubSpot, Pardot, Eloqua, Salesforce, Typeform
- Marketing tags: GTM, GA, Adobe, LinkedIn, Meta, Demandbase, 6sense, Drift, Qualified, Intercom
- Bounded broken-link checks
- Accessibility smoke checks: missing image alt text, unlabeled fields, empty buttons/links, heading issues
- Desktop and mobile screenshots stored in the Apify key-value store
What it does not do
- It does not submit forms.
- It does not log in.
- It does not perform a full Lighthouse or WCAG audit.
- It does not guarantee pixel events fired; it detects script/page presence.
Example input
{"urls": ["https://example.com/campaign"],"expectedFormProvider": "marketo","expectedTracking": ["gtm", "linkedin"],"checkBrokenLinks": true,"maxLinksToCheck": 30,"takeScreenshots": true,"timeoutSecs": 30}
Local development
npm installnpm run buildnpm testnpm run lintnpm start
npm start runs the compiled JavaScript from dist/. Use npm run dev only for quick non-Playwright development; Playwright page.evaluate() functions should be exercised through the compiled build to avoid live-transpiler helper leakage.
For local Actor input, create storage/key_value_stores/default/INPUT.json with the example input.
Output
The Actor pushes one dataset item per audited URL with:
status:pass,warn, orfailscore: 0-100blockers,warnings,noticesmetadata,forms,tracking,ctas,links,accessibility- screenshot keys in the default key-value store
Privacy and ethics
This Actor audits public landing pages and does not submit lead forms or collect leads. Use it for pages you own, pages you are authorized to test, or public competitive analysis consistent with applicable terms and law.