Help & Guides

Step-by-step guides for every tool, recipe, and setting

Getting StartedYour site, at the top of each project

Your site, at the top of each project

Your own site comes first

Every project opens with one card about your own website. Its figures are for the last 30 days, and every number is shown with what it is out of. Subjects with a page on your site - the subjects the pages we published on your site answer. Two pages on one subject count once. Asked about by an AI engine - of those subjects, how many a visibility run asked about in the last 30 days. Of those, had their page cited in an answer - of the subjects asked about, how many had their page cited by an answer given in the last 30 days. A page first cited months ago and cited again in those 30 days counts: we read the answers given in the window, not only the first time a page was cited. Not asked yet - the rest, with the first of them named. A subject nobody asked about is not a page that failed. It is a page nobody has checked yet, and the card says so rather than counting it as a miss. Only visibility runs count as asking: a tracked prompt's answers are not read for citations of your pages, so counting them would put answers in "of those" that could never be counted as cited.

Measure them

Publishing a subject normally puts it on your site's watchlist, as long as the watchlist has room. Even so, many subjects go a month without being asked - the card shows how many. A subject is left out when the watchlist is full, when it has no topic of its own, or when a run's questions run out before it: runs take a watchlist's topics in turn. Measure them lists the subjects named on the card, each with its own Measure button. Measure adds that subject to the questions your visibility runs ask for this site - the same as Measure now on the card of topics your open gaps are about - when the watchlist has room. If it has none, if the subject was retired from your topics, or if it is on the list already, the card says so under the subject and nothing is changed. What your runs ask is asked on your own AI keys: subjects join the watchlist on their own up to its cap, and anything beyond that is your choice. While your account is read-only, nothing new can be measured, so the card offers no Measure button.

How far your pages have got

Each page sits at exactly one step - the furthest it has reached since it went live - so the steps add up to the number of pages: - Not fetched yet - nothing has come for it. - Turned away by your site - crawlers came and every fetch with a known status was refused. Shown only when it happens. - Fetched, but by no search crawler or assistant - only by crawlers our list does not class, such as Applebot or Amazonbot, alone or with AI training crawlers. Shown only when it happens. - Fetched only by AI training crawlers - GPTBot, ClaudeBot, and other companies' training crawlers, and nothing else. They gather pages a future model may learn from; they feed no search index and no answer given today, so a page only they have taken is not yet on its way to being found. - Fetched by search crawlers - Googlebot and Bingbot, whose indexes AI Overviews, AI Mode and Copilot draw on, and the answer engines' own: OAI-SearchBot, Claude-SearchBot and PerplexityBot. - Fetched by an assistant for a question - ChatGPT-User, Claude-User or Perplexity-User, fetching the page because somebody asked something. - Cited in an answer at any time - an answer we measured cited it, in the last 30 days or before. These steps are counted over every night we hold, not only the last 30 days: "fetched" means fetched at any time, and "cited" means cited at any time. That is why the cited step can be larger than the "of those" figure above it, which counts only the last 30 days. The card names the crawlers that came, from your site's own log.

When fetches are not visible

We read who fetched your pages from your own site's Cloudflare zone and nowhere else, by the same rule as the AI crawlers card on this project's Settings tab. The card says the fetches are not visible - instead of counting your pages as not fetched - when the zone is not connected, when your plan does not include reading it (Growth and above), or before its first nightly read. We cannot see, which is not the same as nobody coming. If Cloudflare refuses our last read, or the project is archived, the card still shows the nights we hold, gives the date of the last one, and counts a page published after it as not visible. If we started watching your site within the last 30 days, the card says so: "not fetched yet" then means not since that day. A cited page still shows as cited: a citation comes from the answer, not from your site's log. A page at another address than your site, such as a subdomain the zone does not cover, is not visible either.

Evidence pieces elsewhere

Below your own site are the evidence pieces we published elsewhere for you - Google Docs, Sheets and decks, YouTube videos, cloud pages, Blogger posts: how many there are, how many were cited in the last 30 days, and how many of the visibility-run answers that cited them named you. Both come from the same answers: a piece counts as cited when an answer given in those 30 days listed it as a source, or when our citation records first saw it cited in them - which is how a Google AI Overview's citations are found. "Mostly in answers that already named you" appears only when more than half of those answers did. It means the pieces were used in answers that knew you anyway. When fewer did, the card gives the count instead. When some pieces were cited only by an AI Overview, the card says its count covers the visibility-run answers, because those are the only answers whose naming we read.