Use cases
First determine the job the site does, then choose the inspection path.
Which entry points are seen? Does search demand match the product, specifications, and purchase information?
Do existing articles answer readers' questions? Improve existing answers first, then decide whether to add new ones.
AISEO Site does not read order, inventory, or conversion data. Search data provides clues; the final step still requires your pages and business evidence.
A shop, a knowledge site and a multilingual client site need different acceptance evidence, even when they read the same search report.
On a narrow screen, scroll the table sideways to read the verification column.
| What you observe | What to do | What to retain or verify |
|---|---|---|
| A buyer cannot decide between products | Check real specifications, constraints, variant links and purchase handoff. | A useful output is a supported selection or a clear missing specification. |
| A reader cannot troubleshoot a problem | Write the matching branch, steps and expected observation for one existing article. | A useful output is a checked result or a named unresolved test. |
| A client needs a report across languages | Bind permitted sites, map real equivalents and share selected evidence through scoped roles. | Missing language versions remain missing; a report is not proof of current Google reads. |
Write the acceptance question before opening the tool: “Can this buyer select the correct variant?” gives a clearer task than “improve SEO”.