Skip to main content Skip to page footer

Audits of a page

From versions 14.5.0/13.17.0/12.23.0 onwards you can have the AI Suite check individual pages. An audit tells you what is amiss on a page technically, in terms of content or in terms of accessibility, and offers an AI solution for some of the findings straight away. What gets checked is the published page, that is, what visitors and search engines see.

The six kinds of audit

How to have findings fixed directly is described under Fix with AI (fix wizard).

1. Where do I find the function?

You reach the input mask as follows:

  • Through the backend module: open the AI Suite backend module and switch to the area “SEO & accessibility audit”.
  • Through the context menu: select the page you want in the page tree, open the context menu with a right-click, choose “AI Suite” and there “Audit page (SEO / accessibility)”.

2. Structure of the input mask

The mask is structured as follows:

  • Type of audit: the six kinds of analysis available, see below.
  • Page to audit: the page from the page tree. By default the page selected in the page tree is preset.
  • External URL (optional): alternatively any publicly reachable address, including one outside this TYPO3 installation.
  • Language: checks the page in this language. Results are stored separately per language.
  • Search market: the market whose search data the SEO analyses use. It is preset from the language of the selected page.
  • Focus keyword (optional): the keyword the rating revolves around. For the topic cluster analysis it is mandatory.

“Run audit” starts the check. The SEO audit takes up to a minute because of the Lighthouse values, the accessibility scan usually only seconds.

3. Reading the results

At the top sits the audit score from 0 to 100, calculated from the findings. Below it follow the findings, grouped into errors, warnings and notices. Every finding carries a classification of how it can be fixed:

  • Fixable with AI Suite (one click): can be fixed directly in the backend.
  • AI explains, editor implements: the AI supplies the suggestion, you carry it out.
  • Hand over to your developer or agency: an intervention in the template or the configuration.
  • Information only: no action needed, context only.

With “Export as CSV” you download the list of findings, for instance to pass it on to development. If you open a page that has already been checked, you see the stored result with its date. A new run only starts when you trigger it.

4. Auditing a whole page tree

Instead of going page by page you can also have a subtree checked. To do so, choose the depth (only this page, this page and its direct subpages, or the whole subtree) and have the cost estimate calculated. You see the number of pages, the price and the available balance before the first page is checked.

During the run you see which page is currently being checked. The run can be stopped and resumed later. Pages already checked stay stored, even if the balance runs out in between. At the end you get the distribution of the scores across green, orange and red.