Every check, written down.
The complete list of what a reading looks at, with the threshold behind each one. Generated from the crawler itself, so it says exactly what the code does.
Where your crawl budget actually goes
Google’s own breakdown puts faceted navigation at 50% of reported over-crawling and action parameters at another 25%. These checks measure that space directly: how many URLs your filters generate, which links only perform an action, whether an unchanged page can answer with a cheap 304, and whether the tags Google needs sit inside the 2 MB it reads.
Read the crawl-budget checks →What to allow through the firewall
A firewall that answers our reader with 403 makes your site look like a tiny healthy one: nothing is read, so nothing is found. If your readings come back with a handful of pages and a refusal, these are the addresses the crawl leaves from.
The crawl reads robots.txt first and honours it, fetches one page at a time per site, and slows down on its own when a site pushes back. It reads as an ordinary browser, so allow it by address; a user-agent rule will not match it.
Modules
A reading shows what your site offers. Your server logs show what Googlebot actually took. Upload them and see which templates verified crawlers reach, which they skip, and where their budget is wasted. Visitors are never stored.
You already have the searches, the impressions and the positions. SEOLift joins them to the reading, tells you which pages are one change away from more traffic, names the change, forecasts the gain in clicks as a range, and then measures your edit against pages it left alone.
Every page of every reading is measured for whether an assistant may quote it at all, and how easily it can lift an answer out. The gates run on every plan. The score, the breakdown, the trend and the fix drafts come with the module.
Internal linking is thousands of bounded yes or no decisions: does this paragraph have a reader reason to link to that page, is the phrase already in the copy, which page. The module makes those decisions one paragraph at a time, places only what passes, and writes down what it refused.
Citability says whether a page can be quoted. This says whether one was, this week, on the questions a buyer actually asks. You name the prompts, the module asks them once a week, and keeps a count: named or not, cited or not, which page, and what changed since last week.
What each module does, on one page
Help
From an empty account to the first action plan: creating the account, adding a site, what a reading is and how long it takes, what to do if it comes back too small, and where to look first.
How the action plan is put together, what mark fixed, snooze and ignore do, how a fix is verified, and what the pages table, the changes view, the AI chat and the reports are for.
Connecting Google Search Console and Slack, inviting teammates and their roles, API keys, how plans and invoices work, refunds, and the languages the panel speaks.
Short answers to the questions that reach us most: page counts, firewalls, crawl load, why the score differs from another tool, where the AI gets its answers, what happens at a limit, and where to write.
For the person who manages your firewall or hosting: who is asking, why pages are fetched, how the reader behaves, and the addresses it reads from.
By category
Whether a page can be indexed at all: canonicals, noindex directives, soft 404s and the size limits Googlebot works within.
What crawlers can reach and how much of it is worth reaching — robots.txt, sitemaps, pagination and the parameter space your filters create.
Titles, descriptions, headings and the substance of the page itself — what a searcher sees before they click, and what they find after.
Broken links, redirect chains, orphan pages and how internal link equity moves around the site.
Server response time, payload weight, image sizes, Core Web Vitals and the HTTP caching that decides what a re-crawl costs.
Pages that say the same thing twice — by fingerprint, and by meaning.
Viewport, JavaScript rendering and the gap between the HTML you serve and the page a crawler finally sees.
Hreflang: return links, self-references, language codes and the pages they point at.
What a keyboard and a screen reader run into: labels, landmarks, tab order and link text.
Mixed content and the response headers a browser expects from a site served over HTTPS.