Getting started: your first reading in a few minutes
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.
Create an account
Sign up with an email address and a password, or continue with Google. A confirmation link arrives by email, and the panel waits for it before letting you through. No card is asked for: the Solo plan is free for good, with one site, five hundred pages per reading and four readings a month.
If you typed your address into the field on the home page, it travels with you into the sign-up and into the first site you add, so nobody types their own domain twice.
Add your site
Adding a site asks two things and nothing else. Everything about how the site is read lives in its settings afterwards, with defaults that suit most sites.
- Website URL: the address of the home page. The reading starts there and follows the site’s own links and sitemap.
- What kind of site it is: Ecommerce, Content or blog, SaaS, Local business, Directory or marketplace, or Something else. The preset weights the plan: a directory is judged on crawl budget and duplication, a store on its product pages. You can change it later.
- Start the audit. The screen shows pages found, pages read and an estimate, and you can close the tab; the reading carries on in the background.
What a reading is
A reading is our word for a crawl and everything written from it. It moves through a few phases you can watch: discovering pages, reading the site, checking links and images, measuring Core Web Vitals, finding technical issues, writing the action plan, and summarising for the AI chat.
A small site takes minutes. A large one takes longer, because the reader fetches one page at a time per site and slows itself down when the server pushes back. Every plan has a monthly allowance of readings and a cap on pages per reading; the site’s settings show both.
Once it is done, the reading is the unit everything else is built on. The plan, the issues, the chat and the reports all come from the latest reading, and a second reading is what turns them into a comparison.
If the reading looks too small
A site that answers our reader with "forbidden" reads as a tiny, healthy site. The overview says so when it happens, with the number of pages a firewall refused, and lists the addresses we read from. Ask whoever runs the firewall to allow those addresses. The reader identifies as an ordinary browser, so allow by address rather than by user agent.
The other usual reasons are honest ones: robots.txt keeps the reader out of part of the site, the plan’s page cap was reached, or the default filters skipped login, cart, sort and filter URLs on purpose. The crawl settings say which, and each can be changed.
Where to look first
Three screens carry the first week.
- Site overview: the SEO score with its verdict, what we would do this week, the time it takes, and how many pages were read of how many were found.
- Action plan: the leaks worth your time, capped at five bundles, each saying what to do, where, roughly how long, and who can do it. The next help page is about working with it.
- AI Chat: ask why a page dropped, what to fix first, or for a developer brief. It answers from this site’s latest reading, not from general advice.
The plans, in one paragraph
Solo is free: one site, five hundred pages per reading, four readings a month, readings only when you ask. Studio adds three sites, five thousand pages, thirty readings, weekly scheduled readings, change detection, alerts and PDF reports. Business adds ten sites, twenty-five thousand pages, daily readings, three seats, Slack and the SEOLift and Citability modules. Agency adds fifty sites, a hundred thousand pages, ten seats, unbranded reports, API access and Log Intelligence.
The pricing page lists every limit. When you reach one, the panel says which and what the next plan changes, and nothing is lost while you decide.