Skip to main content Skip to page footer

Audit module

Since versions 14.5.0/13.17.0/12.23.0 the AI Suite backend module has an area of its own for audits, headed “SEO & accessibility audit”. What gets checked is always a publicly reachable page URL, either a page from the page tree or a freely entered external URL. The analysis itself runs through the AutoDudes audit infrastructure.

Where do I find the function?

There are two ways:

  • Through the backend module: open the AI Suite backend module (section “Web”) and switch to the audit area.
  • 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)”.

Permission

The area is only shown if the backend user group holds the permission “Enable SEO and accessibility audits” (enable_audit), see Permission Management.

Extension settings

The extension settings of the AI Suite have a subsection of their own for the accessibility audit, with two options:

  • WCAG standard (auditWcagStandard): WCAG 2 Level A, Level AA and Level AAA are available. Level AA is preset. The value controls the HTML_CodeSniffer run. The axe run used in addition checks against its own rule set and is independent of it.
  • Default text model for audits (auditDefaultTextModel): a model identifier, for example Anthropic. If a model is set here, the model selection in the audit form is skipped. If the field stays empty, editors choose per run themselves.

Also new in these versions is the setting System domain (aiSuiteSystemDomain) in the license section. It holds the domain this installation is licensed for and is needed for CLI and cron runs, where no HTTP host is available. If you leave the field empty, the domain is derived from the site configuration.

The extension settings have been resorted into categories and subcategories with this release, see Configuration.

Storage of the results

Audit results are stored in the new table tx_aisuite_audit_result, each with page, language, audit type, focus keyword used and timestamp. If you open a page that has already been checked, the stored result is shown with the note “Cached result from” and the date, instead of starting a new run. Results are kept separately per language.

The table is created during the database compare. So run the database compare after the update, otherwise the module has no storage.

Credit consumption

Audits consume credits from your AI Suite allowance. When auditing a whole page tree, the AI Suite calculates a cost estimate before the start and shows the number of pages, the price per page and the total, currently 3 credits per page for SEO and for accessibility. If the balance is not enough for all pages, you are offered to check only the affordable part. Individual extra actions are labelled on the button, for instance “Find keyword candidates (2 credits)” or “Generate answers as text (1 credit)”. The consumption then also shows up in the statistics.