Verifying the Integration

Once the routing rule is live, verification is simply watching real traffic arrive. Search engine bots visit most sites many times per hour, so the first requests normally appear in the dashboard within minutes to a few hours of the integration going live.

What to check

• Bot requests appear. The dashboard's Overview and bot analytics report every request EdgeComet serves - which bot, which URL, status code, cache state, and response time. An empty report after a day means bot traffic is not reaching EdgeComet: recheck the routing step on the integration page.
• Bots receive the rendered page. Each logged request carries an SEO snapshot of the page as served - title, meta description, canonical, headings, structured data, word count, indexability. Open a recent request for one of your key pages and confirm the values are what you expect a bot to see.
• Status codes are healthy. A burst of 4xx or 5xx responses right after integration usually means EdgeComet cannot reach your origin - revisit the allow-list step.

What a healthy first day looks like

Requests from multiple bots (Googlebot variants, Bingbot, and typically several AI crawlers) across an increasing share of your URLs, mostly 200 responses, and cache hits climbing as the cache warms. Reports build from the traffic EdgeComet serves, so sections fill progressively: high-traffic pages show up first, the long tail follows as bots reach it.

Next: connect Google Search Console to add the search-performance side.