Report
The technical area of the report tells you whether your site is readable by AI assistants and what to fix so they name you: it starts from an analysis of your pages and ends with a list of actions ranked by priority, each with an owner.
For an AI assistant to cite you, it first has to be able to read and understand your pages. The technical part checks that the site can be reached and interpreted: how many pages are indexable, in which language, and whether the elements that signal the brand's identity (starting with titles) are present and clear. The typical outcome is that the site reads fine, but the signals that tie the pages to the brand name are missing.
Not all actions are equal, so the report ranks them on three levels: «to fix» are the problems that block or hamper reading and should be solved first; «to improve» are the aspects that strengthen your presence but are not urgent; «OK» is what already works. This scale tells you where to start without having to interpret the list yourself.
Every technical action names the owner who takes care of it, for example the developer for changes to the pages' code. Naming the owner is what makes the report operational: it is not just a diagnosis, but a list of assigned tasks, ready to enter the team's workflow.
Because readability and recognisability are different things. An assistant can reach the pages yet fail to link them to the brand name if the right signals are missing, starting with titles. The report separates the two levels and tells you what to fix.
No. That is exactly what the priority scale is for: start with what is «to fix», then move on to what is «to improve». Items already «OK» need no action.
The report assigns an owner to every item, usually the developer for changes to the site. The owner is shown next to the action so it can be acted on straight away.