The questions people actually ask.

Enter a domain. We crawl your pages the way Googlebot and AI crawlers do, run all 129 checks, and show the full scorecard, every pass, fail, and unmeasured item. No signup, no card, and the results aren't held hostage behind a paywall.

Because a crawl costs money and the free tier is a lead magnet rather than a product. The result always reports how many pages it covered against how many it found, so the score is explicitly a claim about that slice rather than about your whole site.

One real crawl per domain per day. A repeat request inside that window returns the scan that already ran rather than crawling again, which also stops the endpoint being used to point repeated traffic at somebody else’s site.

The score, grade, category breakdown and the number of findings are free and always visible, that is the diagnosis. The findings themselves are what an address buys. A shared scorecard link never unlocks them, whoever opens it.

Thirty days. A shared scorecard is a snapshot, not a permanent free product.

It means the check could not run: the crawler could not reach the page, a resource timed out, or a third-party source was unavailable. It is not counted as a pass. The industry default is to quietly round it up, which is how tools report 95/100 for sites with real problems.

Usually because they counted what they could not check as fine. Compare the coverage figures rather than the scores: a 94 at 40% coverage and a 71 at 95% coverage are not describing the same thing.

The SEO checks cover what search engines rank: metadata, structure, speed, internal linking. The 16 GEO checks cover what AI answer engines cite: whether your content is structured so ChatGPT, Claude, Perplexity, and AI Overviews can lift it and attribute it to you.

For some checks, yes, and those are labelled Model wherever they appear so you can weigh them accordingly. Most of the rubric is deterministic rules and graph analysis over your crawled site. A model judgement is never silently presented as a fact.

The loop stops and waits for you twice: once before any fix is generated (you approve the ranked plan) and once before anything ships (you approve the delivery). Nothing touches your site without those two clicks from you.

Three delivery modes. With code access, you get a pull request, a proposed change you approve. With CMS access, we apply changes through your platform's own editor, listed for your approval first. With neither, you get a copy-paste patch file with exact instructions for each change.

Every change is build-verified before you ever see it, and shipped changes are re-measured on the next scan. If a fix doesn't move its check from fail to pass, it gets flagged, and anything delivered as a PR is one click to revert.

That a build ran against the change before you saw it. It applies to the modes where we hold or mirror a repository, and to nothing else. A change written into a hosted CMS is preview-verified, and a patch you apply yourself is advisory. Those labels are never blurred.

The free scorecard, which needs no access at all. The connected delivery modes (pull requests, CMS drafts) are the model the product is designed around and are not connectors you can authorise today. The integrations pages mark the status of each one.

We store the crawl results and the fixes we generate for you, that's it. We don't resell crawl data, don't train models on your content, and don't keep repository or CMS access beyond the scopes you grant. Revoke access any time and the data goes with it.

It identifies itself as CrawldBot and the user agent links to a page explaining what it does and how to block it. It never crawls under a browser user agent.

Disallow CrawldBot in your robots.txt and it stops on the next scheduled run. Competitor monitoring is capped at 12 pages per site, one request at a time, once a week, and robots.txt is obeyed.

No, and we do not resell crawl data. Repository or CMS access is never kept beyond the scopes you grant, and revoking it takes the data with it.