There's no tag to install, no data warehouse to connect and no onboarding call standing between you and your first score. Here's exactly what happens, in order.
That's the whole setup. We crawl the site the way an AI engine's fetcher does — same user agents, same rendering constraints, same patience for slow servers. On a typical marketing site the first pass finishes in under two minutes.
Everything a model needs in order to find you, parse you and trust you. Signals roll up into four sub-scores and one composite number, and every failure is listed with the URLs that caused it.
You start with a prompt set seeded from your category and your competitors, then you edit it — the generic, brand-heavy prompt libraries other tools ship produce a flattering number nobody can act on. Each prompt runs repeatedly across the month, because answer engines are generative and a single reading is a sample, not a rank.
Issues sorted by impact against effort, each with the artefact that closes it: validated JSON-LD, a content brief written against the prompts you're losing, or a short checklist. Ship, re-scan, and the history shows whether it landed.
Four to eight weeks, honestly. Engines have to re-crawl your pages and the models have to start drawing on them. Some fixes register in days — a robots.txt rule that was blocking a fetcher, a broken canonical. Entity and schema work takes longer, because it depends on other sites catching up too. Anyone promising a jump in a fortnight is selling you something.
Free scan, no card, no sales call. Keep the report either way.