Docs/Installation

Install crawler analytics

Add CrawlConsole telemetry to a site and verify that crawler, visitor, and WebMCP signals are connected.

CrawlConsole crawler analytics identifies verified crawler requests that ordinary browser analytics often miss. Install the tracker once in the shared site layout so it loads on every public route.

Before you begin

You need:

a claimed CrawlConsole property;
permission to edit the site's shared layout or tag manager;
the property key shown in CrawlConsole;
a production deployment where crawler requests can reach the site.

Add the tracker

Place the property-specific script near the end of the document <head> or in the site's standard analytics integration point.

<script
  async
  src="https://analytics.crawlconsole.com/tracker.js"
  data-project-key="YOUR_PROJECT_KEY"
></script>

The script is asynchronous and should not block page rendering. Use one property key per canonical site.

Framework placement

Platform	Recommended placement
Next.js	Root layout or the shared analytics component
WordPress	CrawlConsole plugin or the global theme header
Shopify	Global theme layout before `</head>`
Webflow	Project-level custom code in the head
Static HTML	Shared head partial on every public page

Verify the connection

Open Property Settings and check the independent status for crawler, visitor, and WebMCP telemetry. Each signal has its own connected time and last-seen time.

If the status remains pending:

Open the deployed page source and search for the project key.
Confirm the request to analytics.crawlconsole.com is not blocked by Content Security Policy.
Confirm a consent manager is not suppressing the script for all traffic.
Check that the production host matches the claimed property.
Request the page from a clean browser session, then check the last-seen time again.

Content Security Policy

Allow the tracker host in the relevant directives:

script-src https://analytics.crawlconsole.com
connect-src https://analytics.crawlconsole.com

Merge these sources into the site's existing policy. Do not replace a complete Content Security Policy with this small example.

What happens next

New verified crawler requests appear in the property performance view. CrawlConsole groups them by page, crawler, operator, and time, then makes the same property data available to approved AI agents.

Was this page helpful?

Feedback helps prioritize documentation updates.