How it works

What happens in those four minutes

One pass, both Google and the answer engines. Nothing installed.

  1. 0s

    Paste your store URL

    No app to install, no theme edit, no developer, no API token. The crawl reads the public storefront — the same pages a shopper or a search engine sees.

  2. ~1 min

    The crawl maps the storefront

    Templates are detected, every reachable page is queued, and each one is fetched the way a modern crawler sees it — including what survives with JavaScript switched off.

  3. ~2 min

    41 checks run on every page

    Titles, meta, heading order, structured data and Core Web Vitals, scored per page rather than averaged into one site-wide number that names nobody.

  4. ~3 min

    The GEO score folds them into 8 axes

    Direct-answer blocks, claim specificity, parseable structure and machine access become one score out of a hundred — a measure of how quotable the page is.

  5. ~4 min

    Prompts go out to 4 answer engines

    ChatGPT, Perplexity, Gemini and Google AI Overviews are asked what a real shopper would ask. Every cited domain is recorded — yours and everybody else’s.

  6. Done

    Findings come back ranked

    Sorted by expected lift first and effort second, grouped by template so one fix covers the whole set. Where the fix is copy, Aidvio drafts it and waits for your approval.

Step 04, in detail

How 41 checks become one number

Named axes, not a black box

Each of the 41 checks belongs to exactly one of 8 axes. The axis scores are what you act on; the composite is only there for the trend line.

A page at 64 with freshness at 41 has a dated-content problem, not a structured-data problem — and the score says so.

Content structure71Crawlability78Authority62Structured data52Semantic clarity69Format66Freshness41Prompt alignment5864out of 10041 checks8 axes, weighted by the checks each holds
Safety

Aidvio only reads your store. Nothing is written without your approval.

The crawl is rate-limited and read-only — it costs your storefront roughly what one shopper session does. A drafted rewrite is shown against a diff of the live page and stays in the queue until you approve it. There is no setting that turns that off.

The audit is the first day, not the whole job

every turn41 checks · 8 axes · 4 enginesCrawlNo installFindings~4 minutesApprovalOnly what you approveRe-crawl1, 3 or 7 days

The first crawl is day one. The loop is every day after it — and it only closes through the approval step.

See your citation gap.

A read-only scan of up to 250 products. No card, no install, and a finished score in about four minutes.