> ## Documentation Index
> Fetch the complete documentation index at: https://faii.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Re-running Audits

> How to re-run Technical Audits after making fixes - verify improvements, track progress, and maintain your technical health over time.

<Info>
  **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.
</Info>

## 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

| Plan         |          Recommended Schedule          |
| ------------ | :------------------------------------: |
| Starter      |      Monthly (plan limit: 1/month)     |
| Professional | Bi-weekly or after significant changes |
| Enterprise   |       Weekly or after any changes      |

### 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

<Note>
  Running a new audit doesn't delete previous results. All audit history is preserved for comparison.
</Note>

## Comparing Audits

### Side-by-side comparison

After a new audit completes, view the comparison:

| Metric          | Previous |  Current | Change |
| --------------- | :------: | :------: | :----: |
| Overall grade   | B- (72%) | B+ (82%) |  +10%  |
| Critical issues |     3    |     0    |   -3   |
| Warnings        |    12    |     5    |   -7   |
| Info items      |    20    |    18    |   -2   |

### Category comparison

| Category          | Previous | Current |
| ----------------- | :------: | :-----: |
| Crawlability      |    C+    |    A-   |
| Content Structure |     B    |    B+   |
| Schema            |     C    |    B    |
| Performance       |    B+    |    B+   |
| Security          |     A    |    A    |

### 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

| Fix Made           | How to Verify                              |
| ------------------ | ------------------------------------------ |
| Updated robots.txt | Crawlability: no "AI bots blocked" warning |
| Added schema       | Schema: relevant schema now detected       |
| Fixed broken links | Crawlability: 404 count reduced            |
| Added HTTPS        | Security: HTTPS check passes               |
| Fixed headings     | Content Structure: hierarchy valid         |

## Handling Recurring Issues

### Issues that keep coming back

| Cause                         | Solution                                 |
| ----------------------------- | ---------------------------------------- |
| CMS auto-generating bad pages | Configure CMS settings properly          |
| Plugin conflicts              | Identify and resolve conflicting plugins |
| Team members creating issues  | Document standards; train team           |
| Third-party integrations      | Review integration settings              |

### 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

| Plan         | Audit History Retained |
| ------------ | :--------------------: |
| Starter      |      Last 6 audits     |
| Professional |     Last 12 audits     |
| Enterprise   |        Unlimited       |

## 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

## Related Articles

<CardGroup cols={2}>
  <Card title="What Is Technical Audit" icon="stethoscope" href="/docs/technical-audit/what-is-technical-audit">
    Audit overview
  </Card>

  <Card title="Fixing Issues" icon="wrench" href="/docs/technical-audit/fixing-issues">
    How to resolve findings
  </Card>
</CardGroup>