get_page_intelligence
readSite Analysis & Monitoring
Get every available metric for a single page in one call.
Connected surface
This tool and the Website dashboard page are two surfaces over the same data. The dashboard is where you view and curate it;
get_page_intelligence is how your AI can pull one page's full story while deciding what to do with it. How surfaces connect →Parameters
| Parameter | Type | Description | |
|---|---|---|---|
| url_path | string | optional | Page path (e.g. "/", "/blog/my-post") or full URL. Defaults to the homepage. |
| url | string | optional | Alias for url_path: the full page URL, e.g. "https://example.com/pricing". |
| path | string | optional | Alias for url_path. |
| url_id | string | optional | Rampify URL id from another tool's output; skips the path lookup. |
| domain | string | optional | Site domain (optional override) |
| project_id | string | optional | Project UUID (optional override) |
| period | enum("7d" | "30d" | "90d" | "all") | optional | Time window for traffic / conversions / AI-visibility data (default 30d). GSC search performance always uses the standardized lag-adjusted 28-day window so its impressions/clicks reconcile with get_search_performance and suggest_next_action. Free-plan projects see the last 30 days; when a longer period was asked for, the response includes history_limit with what to tell the user. |
| include | string[] | optional | Sections to return: meta, summary, performance, traffic, conversions, ai_visibility, seo_health, content, feature_specs, campaigns, history. Unknown names are ignored (and listed in ignored_include). Default: all sections. |
Related tools
crawl_sitewriteCrawl the site; records URLs with metadata, detects SEO issues, and files feature specs to resolve themscan_pagewriteAudit one page's SEO and keyword usage; runs against the live URL or content you provideget_issuesreadGet all SEO issues with health scoreget_search_performancereadSite-wide Google Search performance: top pages, queries, and ranking/CTR opportunities