> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# inspect_site

> Server-side fetch + static analysis of a customer page — pixel installation, scripts, forms, iframes.

Crawls a URL on a connected domain and reports what's actually on the page: whether the Cometly pixel is installed (and matches THIS space's uid), every other ad/analytics/marketing script, forms (native + 3rd-party widgets like HubSpot / Typeform / Calendly), iframes, framework / page-builder fingerprints.

## When to use

* The user is troubleshooting tracking, attribution, conversion events, or forms.
* You want to ground recommendations in "what's actually on this landing page" rather than assumptions.
* During the Ask AI "Troubleshoot setup" guided flow.

## Limitations — important

This is a server-side HTTP fetch + static analysis. It can confirm a script TAG is on the page, NOT that the script actually fires in a real browser. Pair with [`verify_pixel_events`](/mcp/tools/verify-pixel-events) to confirm events are actually arriving from real user traffic.

The diagnostic matrix:

* Pixel tag missing → install issue.
* Pixel tag present + 0 recent events → ad-blocker, CSP, wrong-uid, or page never visited.
* Pixel tag present + recent events → working.

## Domain scope

For safety, this tool only accepts URLs whose host matches one of THIS space's allowed domains. Off-domain URLs return `[authorization_error]` with the allowed domain list.

## Parameters

| Parameter | Type   | Required | Description                                               |
| --------- | ------ | -------- | --------------------------------------------------------- |
| `url`     | string | Yes      | Absolute HTTPS URL on one of the space's allowed domains. |

## Output

Structured JSON with `pixel`, `scripts`, `forms`, `iframes`, `frameworks`, `meta_tags` blocks. Lead with the most decision-relevant facts in your response (pixel presence + uid match), then summarize the rest.
