What the owner's connected sources counted either side of a receipt's anchor day: Search Console clicks and impressions, Business Profile actions, verified crawler fetches from the site's own log, beacon arrivals, enquiries through the form and anything posted to /api/outcome. One named source per series, per-day means compared, a missing day never zero, a thin window reported as thin. A coincidence in time, stated as one: it never claims the fix caused the movement (licence for the domain, or owner)

get/api/outcomes

Request

  • Base URL: https://crawlcheck.io
  • URL: https://crawlcheck.io/api/outcomes
  • Auth: one of:
    • API key in header x-crawlcheck-key
    • HTTP bearer

Query parameters

receiptstring

A receipt id (rc1:…). Or give domain= for the domain's newest receipt

domainstring
daysinteger

The window either side of the anchor day

fresh'1'

Recompute instead of the six-hour cache

Response

crawlcheck-fix-outcomes

okboolean
kind'crawlcheck-fix-outcomes' required
vunknown required
generated_atstring
cachedboolean
connectedinteger required
usableinteger required
summarystring
readingstring
not_proofstring required
how_to_citestring

Changes

No recorded changes to this operation across all 1 revision of this API.