google_ads_landing_page_analyze
Extract structured content from a landing page—title, meta description, headings, CTAs, features, prices, and JSON-LD—for ad-copy alignment and keyword analysis. Fetches via HTTP(S) with security protections.
Instructions
Fetch a landing page over HTTP(S) and extract structured content for ad-copy alignment. Returns title, meta_description, h1_texts, h2_texts, main_text (truncated to 1500 chars), cta_texts, features (list-item snippets, capped at 30), prices (JP yen patterns), brand_name, industry_hints, og_title, og_description, and structured_data (up to 5 JSON-LD blocks). On fetch or parse failure, returns the same shape with an error field set instead of raising. Side effect: issues one outbound HTTP GET to the URL with a 15s timeout, a 500KB body cap, up to 5 redirects, and a 'MarketingAgent/1.0' User-Agent; SSRF-protected against localhost, private / link-local / reserved IP ranges, and cloud metadata endpoints (redirect targets are re-validated). The Google Ads customer context is unused by the analysis itself — passing customer_id only scopes credential routing. Use this for ad-copy vs. LP message-match and keyword-extraction workflows. For Google's indexing/coverage view of the same URL use search_console_url_inspection_inspect; for a batched workflow that combines LP analysis with existing ads, search terms, and keyword suggestions use google_ads_creative_research.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | No | Google Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted. | |
| url | Yes | Absolute landing page URL to fetch (http:// or https:// scheme only, e.g. 'https://example.com/lp/offer'). Private-range, loopback, and cloud-metadata hosts are rejected. |