An audit is only useful if the issues get fixed. Each issue comes with how serious it is, how much fixing it should help, roughly how long it takes, and the steps to fix it.

By the end you can

Prioritise issues by severity, impact and effort
Mark an issue fixed or ignored
Export the issues as a CSV file

Screens used

Project, Audits, one audit

Before you start

A finished audit (see Audit a page).

Steps

1
Open the audit
On: Project, Audits
Open Audits in the project and open a finished audit.
You should see: A list of issues under the page snapshot, or "No issues found".
2
Read one issue
On: Audit page
Each issue has a severity label (critical, high, medium or low), an impact label and an effort estimate, then a short explanation and numbered fix steps.
You should see: You can say which issue is most serious.
3
Choose what to fix first
On: Audit page
Start with critical and high issues that have high impact and low effort. Leave low-severity issues with high effort for later.
You should see: A short list of the first issues to fix.
4
Mark an issue fixed
On: Audit page
After the fix is live on the website, press Mark as fixed on the issue.
You should see: The issue shows as Resolved.
5
Ignore an issue that does not apply
On: Audit page
If an issue is not relevant to this page, press Ignore to hide it from the open list. Reopen brings back an issue you resolved or ignored by mistake.
You should see: The issue leaves the open list.
6
Export for the developer or client
On: Audit page
Press Download CSV to get the issues as a spreadsheet.
You should see: A CSV file downloads.

Tips

After fixing, go back to Audits and use Re-run audit to confirm the score improved.
Marking as fixed does not change the website. It only records that the work was done.

Troubleshooting

The score did not change after you fixed the issues.: Marking an issue as fixed does not check the page again. Go back to Audits and re-run the audit.
The same issue comes back after every audit.: The fix was made on one page but the cause is in a shared part, such as the header or a template. Fix it there.

One row per shot, in the same order as the guide. Estimated length 2:13, recorded signed in as Owner. Use made-up data only. How to record

0:00Title card

Say: Work through the issues an audit found. Read each issue's severity, impact and effort, follow the fix steps, and mark issues fixed or ignored.

Hold until you see: Lesson title on screen for three seconds.

0:18Step 1: Open the audit (Project, Audits)

Say: Open Audits in the project and open a finished audit.

Hold until you see: A list of issues under the page snapshot, or "No issues found".

0:31Step 2: Read one issue (Audit page)

Say: Each issue has a severity label (critical, high, medium or low), an impact label and an effort estimate, then a short explanation and numbered fix steps.

Hold until you see: You can say which issue is most serious.

0:50Step 3: Choose what to fix first (Audit page)

Say: Start with critical and high issues that have high impact and low effort. Leave low-severity issues with high effort for later.

Hold until you see: A short list of the first issues to fix.

1:07Step 4: Mark an issue fixed (Audit page)

Say: After the fix is live on the website, press Mark as fixed on the issue.

Hold until you see: The issue shows as Resolved.

1:22Step 5: Ignore an issue that does not apply (Audit page)

Say: If an issue is not relevant to this page, press Ignore to hide it from the open list. Reopen brings back an issue you resolved or ignored by mistake.

Hold until you see: The issue leaves the open list.

1:43Step 6: Export for the developer or client (Audit page)

Say: Press Download CSV to get the issues as a spreadsheet.

Hold until you see: A CSV file downloads.

1:56End card

Say: That is work through the issues an audit found. The written steps are on this lesson's page in the ItzSEO course.

Hold until you see: End card with the lesson link.

0 of 8 checked

Step 1: Open the auditYou should see: A list of issues under the page snapshot, or "No issues found".
Step 2: Read one issueYou should see: You can say which issue is most serious.
Step 3: Choose what to fix firstYou should see: A short list of the first issues to fix.
Step 4: Mark an issue fixedYou should see: The issue shows as Resolved.
Step 5: Ignore an issue that does not applyYou should see: The issue leaves the open list.
Step 6: Export for the developer or clientYou should see: A CSV file downloads.
Problem case: The score did not change after you fixed the issues.You should see: Marking an issue as fixed does not check the page again. Go back to Audits and re-run the audit.
Problem case: The same issue comes back after every audit.You should see: The fix was made on one page but the cause is in a shared part, such as the header or a template. Fix it there.

By the end you can

Screens used

Before you start

Steps

Open the audit

Read one issue

Choose what to fix first

Mark an issue fixed

Ignore an issue that does not apply

Export for the developer or client

Tips

Troubleshooting

Related lessons