landing-page-intel
Extract competitor and customer intelligence from any company's landing page HTML. Discovers tech stack, analytics tools, ad pixels, customer logos, SEO metadata, CTAs, hidden elements, and more. No API keys required.
Best use case
landing-page-intel is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Extract competitor and customer intelligence from any company's landing page HTML. Discovers tech stack, analytics tools, ad pixels, customer logos, SEO metadata, CTAs, hidden elements, and more. No API keys required.
Teams using landing-page-intel should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/landing-page-intel/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How landing-page-intel Compares
| Feature / Agent | landing-page-intel | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Extract competitor and customer intelligence from any company's landing page HTML. Discovers tech stack, analytics tools, ad pixels, customer logos, SEO metadata, CTAs, hidden elements, and more. No API keys required.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Landing Page Intel Extract GTM-relevant intelligence from any company's landing page by scraping its HTML source. ## Quick Start Only dependency is `pip install requests`. No API key needed. ```bash # Basic scan of a single URL python3 skills/landing-page-intel/scripts/scrape_landing_page.py \ --url "https://example.com" # Scan multiple pages of the same site python3 skills/landing-page-intel/scripts/scrape_landing_page.py \ --url "https://example.com" --pages "/,/pricing,/about" # Output as summary table instead of JSON python3 skills/landing-page-intel/scripts/scrape_landing_page.py \ --url "https://example.com" --output summary # Save full report to file python3 skills/landing-page-intel/scripts/scrape_landing_page.py \ --url "https://example.com" --output json > report.json ``` ## What It Extracts | Category | Details | |----------|---------| | **Tech Stack** | Analytics (GA4, Mixpanel, Amplitude, PostHog, Heap), marketing automation (HubSpot, Marketo, Pardot), chat widgets (Intercom, Drift, Crisp, Zendesk), A/B testing (Optimizely, VWO, LaunchDarkly), session recording (Hotjar, FullStory, LogRocket), CDPs (Segment, Clearbit, 6sense) | | **Ad Pixels** | Meta Pixel, Google Ads, LinkedIn Insight Tag, TikTok pixel, Twitter pixel | | **Customer Logos** | Image URLs from "trusted by" / logo carousel sections, grouped by directory | | **SEO Metadata** | Title, meta description, Open Graph tags, Twitter Cards, canonical URL, structured data (JSON-LD), hreflang tags | | **CTAs & Sales Motion** | All CTA button text and links — reveals PLG vs sales-led motion | | **Social Proof** | Testimonials, customer counts, case study links, badge images | | **Integrations** | Links to integration/partner pages, embedded third-party widgets | | **Hidden Elements** | Content in `display:none`, `hidden`, or HTML comments that may reveal upcoming features | | **Infrastructure** | CMS platform (Webflow, WordPress, Next.js, etc.), detected from HTML signatures | ## CLI Reference | Flag | Default | Description | |------|---------|-------------| | `--url` | *required* | Target website URL | | `--pages` | `/` | Comma-separated paths to scan (e.g., `/,/pricing,/about`) | | `--output` | `json` | Output format: `json` or `summary` | | `--timeout` | `15` | Request timeout in seconds | ## GTM Use Cases - **Competitive intel**: See what tools competitors use, how they position, who their customers are - **Prospect research**: Before a sales call, scan a prospect's site to understand their stack and maturity - **Market mapping**: Scan multiple competitors to compare positioning, customer segments, and GTM motions - **Customer discovery**: Extract competitor customer logos as potential prospects for your own product ## Cost Free. No API keys required. Uses only HTTP requests to fetch public HTML.
Related Skills
ad-creative-intelligence
Scrape competitor ads from Meta and Google ad libraries, cluster by hook/angle/format, and surface new creative directions your team hasn't tested. Chains meta-ad-scraper and google-ad-scraper. Use when a marketing team wants to understand the competitive ad landscape before launching a campaign, or wants fresh creative inspiration from what's already working in the market.
review-intelligence-digest
Scrape G2, Capterra, and Trustpilot reviews for your product and competitors, then extract recurring themes, objections, proof points, and exact customer language for use in messaging. Chains review-site-scraper with LLM analysis. Produces a weekly or monthly digest that feeds directly into copywriting, positioning, and sales enablement. Use when a marketing team needs to ground messaging in real customer language.
competitor-intel
Competitor intelligence system. Research competitors across web, Reddit, Twitter/X, LinkedIn, and blogs. Build deep competitor profiles, monitor content and positioning changes, track what gets traction, and identify competitive gaps. Covers data collection, content tracking, and strategy analysis. Pure research skill — uses web search, web fetch, and optionally Apify for social scraping. No scripts required.
competitor-ad-intelligence
Scrape competitor ads from Meta Ad Library and Google Ads Transparency Center, analyze creative patterns (hooks, formats, CTAs), reverse-engineer landing page funnels, and produce a strategic teardown with vulnerability analysis and counter-play recommendations. Use when you need to understand the competitive ad landscape, find new creative directions, or identify weaknesses in a competitor's paid strategy.
competitive-pricing-intel
Monitor competitor pricing pages via live web scrape and Web Archive snapshots. Track plan changes, tier restructuring, new pricing models, and feature gating shifts. Produces a pricing comparison matrix and flags when a competitor changes packaging. Use when a product marketing team needs to stay current on competitive pricing or when preparing for a pricing change of their own.
ad-to-landing-page-auditor
Analyze the message match between your ads and landing pages. Checks if the promise in the ad copy carries through to the landing page headline, body, and CTA. Flags disconnects that kill conversion rates. Works with Google, Meta, and LinkedIn ads.
orthogonal-extract-webpage-data
Extract structured data from web pages using AI
orthogonal-company-intel
Full company intelligence report - overview, team, funding, products, news
competitor-monitoring-system
Set up and run ongoing competitive intelligence monitoring for a client. Tracks competitor content, ads, reviews, social, and product moves.
client-packet-engine
Batch client packet generator. Takes company names/URLs, runs intelligence + strategy generation, presents strategies for human selection, executes selected strategies in pitch-packet mode (no live campaigns or paid enrichment), and packages into local delivery packets.
client-package-notion
Package all work done for a client into a shareable Notion page with subpages and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured Notion workspace the client can browse. Lead list CSVs are uploaded to Google Sheets and linked from the Notion pages. Use when you want to deliver work to a client in a polished, navigable format.
client-package-local
Package all work done for a client into a local filesystem delivery package with .md files and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured directory with dated deliverables. Lead lists are uploaded to Google Sheets and linked from the markdown files. Use when you want to deliver work to a client in a polished, navigable format without requiring Notion.