The state of the run.

A run goes through the same stages in the same order every time. This is what they are, and what each one is bounded by:

• The run reads the domain’s robots.txt and its sitemap, so that it knows which pages the site says it has.
• It reads the site’s pages, one copy each, up to the number of pages the run was sold. A page that will not load is recorded with the status it returned rather than dropped, because a page in a sitemap that answers with an error is itself a finding.
• It reads the figures for the property you connected, where you connected one. This is the slow step on a large property, and section 2 is about it.
• It runs the catalogue of checks over what it read. Every check reports a value and a result, and a check that could not run reports that rather than a zero.
• It writes the document, in which every sentence has to point at a check result that exists. A sentence whose citation cannot be resolved is not published.
• It sends one email carrying the link to the document. That link is the document; there is no account to sign in to and no password.

The indexation census, which asks a search engine what it has done with each of your pages, is capped by that service at 2,000 inspections per property per day. When that constraint applies, a site whose sitemap lists more pages than that cannot be censused in one day, and the run finishes on a later day rather than reporting a number it did not measure.

Where it applies, the waiting screen will say so in those terms and give the day the census finishes, rather than a countdown that runs out. It is the only staged limit in the product, and it belongs to the service being read rather than to the run.

Until both exist, no run is being accepted and nobody is being charged for one.

A run fails in one of four places: the crawl, the property read, the writing, or the census limit in section 2. Which one failed is named on the screen you are left with, along with what it means for the document and whether anything is expected of you.

There is no support queue and no telephone number, and that is a deliberate part of the product rather than an omission. A failure that needs you to do something says what; a failure that does not is retried or reported without you. The one thing a failure never produces is a document that looks finished.

The contact route is in the footer below. It answers questions about a run and requests about data; it is not a support desk and it does not answer on a schedule.