Skip to content

Check one page's status, indexability, SEO tags and bot visits ​

The Overview tab of EdgeComet Page Analysis shows the state of one page as bots received it: status code, index status, robots directives, canonical, title, meta description, headings, links and structured data. Below them, Bot Visits charts the bots that requested the page.

Every field comes from a copy EdgeComet served to bots, not from a separate fetch. A small count beside a field label means the field changed; click it to see the old values.

The tab's Search Performance and Recent changes cards are covered in Track SEO changes on one page against its Google traffic.

The Content card of Page Analysis for https://edgecomet.com/seo-alerts/. Title SEO Alerts for Website Changes & Performance | EdgeComet and the meta description each carry a lightning icon and a change count of 1. H1s (1) has a count of 2 and reads SEO alerts for real-time monitoring. H2s (13), with a count of 2, and H3s (30), with a count of 3, list their first six headings with Show all 13 and Show all 30

Which copy of the page the Overview tab describes ​

The Overview tab describes the newest copy of the page that EdgeComet rendered or fetched for a bot or for the pre-cache:

  • On a site EdgeComet renders: the newest rendered copy. A newer copy from the bypass dimension, which carries your server's raw HTML, does not replace it. On a JavaScript site that raw HTML is often an empty app shell.
  • On a cache-only site, or for a URL EdgeComet has never rendered: the newest copy of any kind, which is your server's HTML.

The change history reads the same copies, and the fields and their history always agree. Until a copy with SEO data exists, the tab shows "No data found for this URL" with "This URL has not been processed by EdgeComet yet. It will appear here once bots start visiting it."

Page Overview: can the page be indexed? ​

The Page Overview card answers whether the page can be indexed and when Google last fetched it:

  • Cached At: when EdgeComet stored the cached copy, with a badge: Cached, Cache expired, Not cached or Recaching....
  • Status Code: the status bots received. An error shows its type, and a redirect shows "Redirects to:" and the target.
  • Index Status: Indexable, Non-200, Blocked by robots, Canonical points elsewhere or Unknown. It is EdgeComet's reading of the copy it received, from the status code, robots directives and canonical. It is not a report of whether Google indexed the URL.
  • Meta Robots: the robots meta tag of the page.
  • Last Googlebot Visit: the most recent request from Googlebot, desktop or mobile, over all time and not only the period. Requests from fake bots are left out. A page Googlebot never requested reads "never".
  • Canonical: the canonical URL the page declares.
  • Hreflang (N): each language code with its URL.

The Page Overview card for https://edgecomet.com/ai-action-board/: Cached At Oct 18, 2026, 7:05 PM with a Cached badge, Status Code 200, Index Status Indexable, Meta Robots index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, Last Googlebot Visit Sep 30, 2026, 4:12 PM, Canonical https://edgecomet.com/ai-action-board/ and Hreflang (0) empty

A lightning icon titled Modified by Edge SEO marks Status Code, Meta Robots, Canonical, Title and Meta Description when an Edge SEO rule for the URL sets that field. The Edge SEO tab lists those rules.

Content: what do the title, description and headings say? ​

The Content card shows the Title, Meta Description, H1s, H2s and H3s of the page, each heading list with its count, such as H2s (13). A long list shows its first headings and Show all N. A field the page does not have reads "empty".

Change history for one field ​

Click the count beside a field label to open its Change history. Each entry is a date with the old value marked "-" and the new value marked "+". The oldest entry reads "first recorded" with the value EdgeComet saw first. For every change across the site, see the Change log.

Status Code, Index Status, Meta Robots, Canonical, Hreflang, Title, Meta Description, H1s, H2s and H3s show a change count. Structured data changes appear in Recent changes. To see every field's changes on one timeline, with the page's Google traffic, see Track SEO changes on one page against its Google traffic.

The Content card for /seo-alerts/ with the Change history of H1s open. Oct 7, 2026 replaces Real-time SEO alerts for rankings, and performance tracking with SEO alerts for real-time monitoring. Sep 4, 2026 replaces SEO Alerts for Rankings, Visibility, and Performance Tracking with Real-time SEO alerts for rankings, and performance tracking. Aug 27, 2026 reads first recorded, 1 entry

The Links & Resources card counts the page's links and images:

  • Links: Total, Internal, External and Nofollow.
  • Images: Total, Internal and External.
  • Structured Data: the schema.org types the page declares, such as BreadcrumbList, FAQPage or Organization. To check that the markup is valid, see Validate structured data across your site.

The Links & Resources card for /seo-alerts/: Links 79 total, 75 internal, 4 external, 0 nofollow; Images 53 total, 53 internal, 0 external. Structured Data lists Answer, BreadcrumbList, EntryPoint, FAQPage, ImageObject, ListItem, Organization, PropertyValueSpecification, Question, ReadAction, SearchAction, Service, WebPage and WebSite

Bot Visits: which bots request the page? ​

The Bot Visits card draws the page's requests over the period, one line per bot family: Googlebot Search, Bingbot Search, ChatGPT, Claude, Meta AI, Other and Fake Bots. A card per family gives its requests, its share of the page's requests and the change against the previous period.

View rows opens every request for the URL in Data Explorer > Bot log, and a family card opens that family's requests. With no requests in the period, the card reads "No bot visits recorded for this URL in the selected period".

The Bot Visits card for /seo-alerts/ over 90 days, one line per bot family by week. The family cards read Googlebot Search 20 (4.4%), Bingbot Search 3 (0.7%), ChatGPT 84 (18.5%), Claude 7 (1.5%), Meta AI 18 (4.0%), Other 314 (69.0%) and Fake Bots 9 (2.0%). ChatGPT peaks in mid-August and Meta AI in early October

Re-cache: store a new copy and see what changed ​

Re-cache renders or fetches a new copy of the page at high priority and shows what changed. Use it right after you publish a change, instead of waiting for the next bot:

  1. Publish the change on your site, or publish an Edge SEO rule.
  2. Open Page Analysis for the URL and click Re-cache. The button reads Sending..., then Added to queue, and Recaching... shows while EdgeComet stores the new copy.
  3. When the new copy is stored, every card reloads. On the Overview tab, the fields that changed are highlighted for a few seconds: Title, Meta Description, headings, Canonical, Meta Robots or Status Code.

When you publish an Edge SEO rule and open Page Analysis from it, the page shows Recaching... for the recache the publish started and reloads when the new copy is stored. To refresh many pages at once, see Recache, invalidate and flush cached pages.

What to do next ​

Where to find it ​

In the dashboard: Page Analysis > Overview for a URL. Open it from Search and ask (Cmd+K or Ctrl+K, type the URL, choose Analyze) or from the magnifier icon beside a URL in a report.

Related Articles