Reachability · document 02

GEO Dashboard

In the workspace: /geo/

Availability

Included on Pro and Advanced

This document is open to every reader on every plan. Availability tells you what a plan includes; it does not decide what you may read.

What it is for

Answer engines read the web with crawlers of their own, and they are not the crawlers the industry has spent a decade optimising for. Two separate questions decide whether your work can reach a generated answer: whether those agents can retrieve the page at all, and whether the page, once retrieved, can be quoted without being rewritten. This dashboard answers both side by side, because a site routinely passes one and fails the other.

How to use it

Select a project. Both halves of the dashboard read the same project, so the two findings always describe one site.
Open the access section first. If an answer engine cannot retrieve the page, nothing in the readiness section can help yet.
Then open the content readiness section, which examines whether a retrieved page states its facts in a form that can be cited.
Note the date on each finding. Both are dated observations, and a later run is only meaningful against an earlier one.

Reading the result

Access and readiness are reported as two findings with two dates, and they are never merged into a single score. A composite number would hide which half failed, and which half failed is the only part that tells you what to change. Read them as a sequence: reachable and quotable, reachable but not quotable, or not reachable at all.

What it cannot tell you

It reports what your own server and markup declare to those agents today. It makes no prediction about whether any particular answer will cite you: no audit can, and a product that claimed otherwise would be selling a forecast as a fact. Treat a clean result as a removed obstacle, not as a placement.

What it keeps

The dated finding, so that a later run can be compared against it. The page content itself is not retained.