Skip to main content
Quick Answer: After fixing audit issues, run a new audit to verify the fixes worked. Compare before and after grades to measure improvement. Regular re-runs catch new issues early.

​
What You’ll Learn

  • When to re-run an audit
  • How to compare audit results
  • Setting up regular audit schedules
  • Handling recurring issues

​
When to Re-run

​
After fixes

Run a new audit after:
  • Fixing Critical issues
  • Addressing a batch of Warnings
  • Adding schema markup
  • Making performance improvements
  • Completing a site migration

​
Regular schedule

​
Trigger events

Re-run after these events:
  • New WordPress theme installed
  • Major plugin updates
  • Content management system upgrade
  • SSL certificate changes
  • Hosting provider change
  • Large batch of new content published

​
Running a New Audit

  1. Go to Technical Audit in your dashboard
  2. Click Run New Audit
  3. Wait for the crawl to complete (typically 5-30 minutes depending on site size)
  4. View updated results and grade
Running a new audit doesn’t delete previous results. All audit history is preserved for comparison.

​
Comparing Audits

​
Side-by-side comparison

After a new audit completes, view the comparison:

​
Category comparison

​
Trend view

See your audit grade plotted over time:
  • Track improvement trajectory
  • Identify regression points
  • Correlate with site changes

​
Verifying Specific Fixes

​
Check individual issues

After fixing a specific issue:
  1. Run new audit
  2. Go to the relevant category
  3. Verify the specific issue no longer appears
  4. Check that the fix didn’t create new issues

​
Common verification

​
Handling Recurring Issues

​
Issues that keep coming back

​
Prevention

  • Set up audit alerts for grade drops
  • Establish content publishing standards
  • Create a technical SEO checklist for new pages
  • Review CMS settings after updates

​
Audit History

View all past audits:
  • Date and time of each audit
  • Grade achieved
  • Issue counts
  • Comparison to previous
  • Full detailed report for each

​
Retention

​
Tips

  • Don’t run audits too frequently - Give fixes time to propagate (wait at least a day after changes)
  • Fix and verify in batches - Fix 5-10 issues, then run an audit, rather than running after each fix
  • Watch for regressions - A lower grade after site changes means something broke
  • Celebrate improvements - Track your grade progression to show stakeholders progress
  • Set grade targets - Aim for B+ initially, then work toward A

What Is Technical Audit

Audit overview

Fixing Issues

How to resolve findings