Use Audit to review your website pages, identify issues that may affect how AI platforms access and understand your content, and monitor how your audit performance changes over time.
What does an audit check?
Audit issues are grouped into two main areas:
Area | What it looks at |
Technical | How the page is built, delivered, linked, and accessed, including indexability, canonical tags, redirects, internal links, crawler access, blocking resources, and performance. |
Content | The content and structure of the page, including titles, meta descriptions, headings, word count, and structured data. |
Technical issues can make it harder for AI platforms to reach a page. Content issues can make it harder for them to understand and use it.
Important: The audit crawl does not run JavaScript. Content loaded only through JavaScript may therefore not be visible to the audit.
Track your website evolution
Website Evolution shows how your overall website audit score changes over time.
At least two completed full audits are needed before a trend can be shown.
The chart reflects audits run across the complete set of auditable pages. Auditing or re-auditing only selected pages does not update the overall Website Evolution trend.
Use this view to understand whether your website audit performance is improving or declining between full audit runs.
Review your website issues
The Issues summary shows the currently open issues identified for your brand. Issues from earlier audits remain included until they are resolved or dismissed.
Issues marked as Critical issue or High priority are considered to need immediate attention, helping you understand where to focus first.
Review your auditable pages
The pages table shows the website pages currently available for auditing.
For each page, you can review:
Issues — the number of issues currently associated with that page.
Technical — the page’s current Technical score.
AEO — the page’s current AEO score.
Last audit — when that page was last audited.
Use Search Page to find a specific page. Select a page to open its audit results in more detail.
Manage your sitemap
Select Edit Sitemap to review the sitemap sources connected to your brand and manage the pages included in future audits. From here, you can open Edit Auditable Pages or Change sitemap URL.
Manage auditable pages
Select Edit Auditable Pages to review the pages Yetify can include in the next audit.
From this view, you can:
use Search Page to find a page;
Upload CSV to add pages in bulk;
Add Pages manually;
select Refresh Pages to refresh the page list;
remove individual pages you no longer want to include.
The number shown at the top indicates how many pages will be covered in the next audit.
Change your sitemap URL
Select Change sitemap URL to update the sitemap sources Yetify uses to discover pages.
After updating the sitemap URL, select Update & Refresh.
Important: When the sitemap is updated and refreshed, pages that are no longer present in the sitemap are removed from the auditable page list.
Manual and automatic audits
Yetify runs automatic audits separately from the manual audits you start yourself. Automatic audits run for each brand on a rolling seven-day cycle and do not use your manual audit credits.
Manual audits are started when you select pages and choose Audit Pages. Each page checked uses one audit credit.
Your audit allowance depends on your plan:
Starter: 200 audits
Pro: 1,000 audits
Enterprise: custom limits
Tip: Use a manual audit when you want to check selected pages after making changes, without waiting for the next automatic audit.
Run a manual audit
Select the pages you want to audit and choose Audit Pages.
Before the audit starts, Yetify shows how the run affects your available allowance:
Used — audit credits already used.
This run — pages included in the current run.
Remaining — credits left after the run.
Each selected page uses one audit credit.
Review a page audit
Select a page from the Audit table to review its results in more detail.
The page detail view shows the page title, URL, page preview, when it was last audited, and its current Technical and AEO scores.
You can also select Audit Page to run a new manual audit for that page.
Understand Technical and AEO scores
Both Technical and AEO use a 0–100 scale, where a higher score is better.
Score | What it represents |
Technical | How well the page is built and performs, based on technical checks including page accessibility and performance. |
AEO | How well the page is prepared to be found, understood, and cited by AI answer engines. |
Technical focuses on whether the page works properly and can be reached. AEO focuses on whether the page provides the structure, metadata, content, and accessibility needed to work effectively as a source for AI platforms. Only genuine problems reduce the AEO score. Optional improvements do not.
If a page has not been measured, Yetify shows no score rather than treating it as 100. A measured page with no detected problems can score 100.
Review issues on a page
Under Issues on this page, you can review the issues identified for the selected page.
Issues are organised into two categories:
Technical — issues related to how the website is built, delivered, linked, or accessed. Examples include indexability, redirects, internal links, blocking resources, crawler access, and page performance.
Content — issues related to the information and structure on the page itself, such as titles, meta descriptions, headings, word count, and structured data.
For each issue, the table shows:
ID — the identifier used to track the same issue across audit results.
Issue — the problem Yetify identified.
Status — the current state of the issue.
Severity — the priority assigned to the issue.
Pages affected — how many pages are affected by that issue.
Issues that still require action can appear with the status Needs attention.
Use Search Issue and the available filters to find specific issues.
Manage an issue
Open the options menu next to an issue to access the available actions:
See Detail — open more information about the issue.
Re-run audit — audit the affected page again.
Go to page — open the affected website page.
Mark as fixed — manually indicate that you have addressed the issue.
Mark an issue as fixed
Selecting Mark as fixed changes the issue status, but does not automatically verify that the underlying problem has been resolved. No new crawl or page check is triggered. Verification requires the affected page to be audited again.
Re-run an audit
A re-run audits the whole affected page, not only the selected issue. Other open issues affecting the same page are checked during the same run.
Each page re-audited uses one manual audit credit. If the page passes the relevant check, the issue moves to Resolved. If the problem is still detected, it remains open. A resolved issue is not deleted, so its record remains available.