The AIO track checks how discoverable your pages are in AI-powered search: the signals that let AI indexes and crawlers reach a page, understand what it is and place it, from structured data to accessible markup.
Each category is a group of related checks. Examples show the kind of thing that is tested, not a complete list.
A page that cannot be found cannot be used. These checks look at the signals that lead an index to your content.
Keep your sitemap complete, link to important pages, and declare one canonical URL per page.
Many crawlers and agents render pages like a phone. Pages that only work on wide screens are harder to read.
Add a viewport meta tag and test the layout at phone width.
Schema types tell an AI system whether a page is a product, a how-to, an article or part of a hierarchy.
Add JSON-LD for the type each page really is, and keep it identical to the visible content.
Labels on interactive elements help screen readers and AI agents understand a page.
Add aria-label attributes or associated label elements to every interactive control.
Alt text and captions give a machine the meaning of an image, which is needed for visual and product search.
Describe what each image shows, and wrap key images with a caption.
Scan a page or a whole site. Every scan runs the four core tracks, and the report lists each failed check with its fix.
Start a scan and open the AIO section of the report to see each check, its result and the fix.
How to start a scan→Straight answers about the AIO checks.
In the report in the app. Each check has its result, severity and fix. The public pages describe what each category covers.
From weighted checks. Every deduction ties to one check and one fix, and the four track scores combine into the overall score. How the score is built.
It makes your site easier to find, read and quote. Benchmarq measures readiness and does not promise rankings, citations or traffic.
Run a scan and see each check, its result and the fix.