Before and after a change: equal windows around a site event, on verified Googlebot

Pick a site event and a window either side; see verified Googlebot's requests, pages, crawl purpose buckets, status classes, bytes and timings before and after, with the change on the per-day rate, and track whether a URL pattern is going to zero since the change.

You changed robots.txt, fixed a redirect chain or moved hosts. The question is always the same: what did Googlebot do differently afterwards? Until now that meant two exports and a spreadsheet.

What changed

  • Before and after a site event on SEO Overview: choose a site event (or add one from the timeline) and 7, 14 or 28 days either side. Equal UTC windows on verified Googlebot fetches: requests, pages fetched, the crawl purpose buckets (pages, render resources, 304 rechecks, redirects, refused, errors), status classes, bytes and mean time where the feed measures them. Changes are on the per-day rate, so an after window that is still running compares fairly, and the panel says when it is cut short.
  • Is this pattern going to zero? Type a URL pattern as the URL-patterns report spells it (/search?q={val}) and track it across the two windows: to zero, falling, rising or flat, for verified Googlebot only.
  • GET /public/v1/websites/{id}/seo/event-compare (event_id or at, days, bot, pattern); MCP get_event_compare (1.28.0); CLI seo event-compare (2.8.0); definitions event_compare and pattern_trend.

See before and after a site event in the help.

← Figures you can quote: data as of, final, one window per page, and robots.txt by dayBots are classed by what they do: ads crawlers, SEO tools and Applebot as search →
← All changelog entries