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

# Run an AI SEO Site Audit

> Generate a comprehensive SEO report with actionable fixes

Hiveku's AI-powered site audit crawls your site and flags SEO issues across technical, performance, content, and mobile categories — each with a plain-language explanation and a suggested fix.

## Where to Find It

In your project, go to **Marketing > SEO > Tools > Site Audit**.

## Four Audit Categories

| Category            | What it checks                                                                         |
| ------------------- | -------------------------------------------------------------------------------------- |
| **Technical**       | Crawlability, indexing, broken links, redirects, robots.txt, sitemap                   |
| **Performance**     | Core Web Vitals, load speed, image sizes, JavaScript bloat                             |
| **Content Quality** | Title tags, meta descriptions, H1/H2 structure, word count, keyword usage, readability |
| **Mobile SEO**      | Mobile-friendliness, viewport, touch targets, responsive design                        |

You can run one category or all four at once. Running all four takes longer but gives you a complete picture.

## Run an Audit

<Steps>
  <Step title="Open Site Audit">
    Go to **Marketing > SEO > Tools > Site Audit**.
  </Step>

  <Step title="Pick a category">
    Choose Technical, Performance, Content Quality, Mobile, or **Run All**.
  </Step>

  <Step title="Enter the URL">
    Paste the URL you want to audit — usually your live site's home page. The audit follows internal links, so you only need to give it a starting point.
  </Step>

  <Step title="Click Run Audit">
    The audit crawls and analyzes your site. Most audits finish in 30–60 seconds; larger sites can take a few minutes.
  </Step>

  <Step title="Review the report">
    Results show an issue list, each with severity, affected URL, and a recommendation.
  </Step>
</Steps>

## Reading the Report

Each issue has three parts:

* **Severity** — `critical`, `warning`, or `notice`
* **Affected URL(s)** — where the issue was found
* **Recommendation** — a plain-language explanation and a suggested fix

Click any issue to open an AI-generated remediation guide with code examples specific to your stack.

<Tip>
  Prioritize critical issues first, then warnings. Notices are informational — sometimes worth fixing, sometimes not, depending on context. Don't try to zero out every issue on your first pass.
</Tip>

### Severity Levels

| Severity     | When to fix                                                                                       |
| ------------ | ------------------------------------------------------------------------------------------------- |
| **Critical** | Now — these directly block indexing or rankings (broken robots.txt, no title tags, server errors) |
| **Warning**  | This sprint — real issues that hurt you but aren't immediately fatal                              |
| **Notice**   | When you have time — often informational or edge cases                                            |

## Fix Issues with AI Chat

The audit integrates with your project's AI assistant. Once you've run an audit, you can just ask:

```
Fix the technical SEO issues from my last audit.
```

The AI reads the report, applies the fixes (updates `robots.txt`, adds missing meta tags, fixes redirects), and reports back what it changed. You review and deploy.

For bigger issues (JavaScript bloat, Core Web Vitals), the AI may propose changes that need your review — it won't silently rewrite your frontend architecture.

## Schedule Recurring Audits

Catch regressions automatically by scheduling audits.

<Steps>
  <Step title="Click Schedule on the audit tool">
    On the Site Audit page, click **Schedule**.
  </Step>

  <Step title="Pick a frequency">
    Weekly or monthly are the common cadences. Daily is rarely necessary and eats into your AI credits.
  </Step>

  <Step title="Choose which categories">
    You can schedule all four or a single category. A weekly technical audit plus a monthly content audit is a common pattern.
  </Step>

  <Step title="Set recipients">
    The summary can email you, your team, or a Slack channel.
  </Step>
</Steps>

See the [SEO reference](/marketing/seo) for integration details and crawl configuration.

## Verify a Fix

<Steps>
  <Step title="Run an audit">
    Note the issues it finds.
  </Step>

  <Step title="Apply a fix">
    Use AI chat or edit manually.
  </Step>

  <Step title="Deploy">
    Push the changes live — SEO audits run against your deployed site, not the editor.
  </Step>

  <Step title="Re-run the audit">
    The fixed issue should no longer appear. If it's still flagged, click into the issue details — the AI will explain what's still wrong.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Audit hangs or times out">
    Your site may be blocking the crawler. Check `robots.txt` — if you have broad disallow rules, add an explicit allow for the audit User-Agent during the audit window, or temporarily relax rules. Rate-limiting middleware (Cloudflare challenge, aggressive WAF) can also block crawls.
  </Accordion>

  <Accordion title="Too many false positives">
    Some issues are informational and may not apply to your case. Prioritize criticals and warnings. You can dismiss individual notices so they don't clutter future reports.
  </Accordion>

  <Accordion title="Report comes back empty">
    The crawler couldn't load any pages. Most common causes: the URL returns 404 (typo?), the site requires authentication (audit needs public access), or the site is client-rendered with no initial HTML (some audits can't follow JavaScript-only navigation — deploy with server rendering).
  </Accordion>

  <Accordion title="Core Web Vitals scores lower than PageSpeed Insights">
    Hiveku's performance audit uses a synthetic lab environment — real-user metrics from Google's Chrome UX Report can differ. Use both: the audit for quick iteration, PageSpeed Insights or Search Console for real-world validation.
  </Accordion>

  <Accordion title="AI chat didn't fix an issue">
    Some fixes require product decisions — rewriting a page title to target a specific keyword, for instance. The AI flags those and asks you. Check the AI thread for pending questions.
  </Accordion>
</AccordionGroup>

## What's Next?

<CardGroup cols={2}>
  <Card title="SEO Setup" icon="magnifying-glass" href="/how-tos/seo">
    Configure sitemaps, meta tags, and structured data
  </Card>

  <Card title="Connect Google Search Console" icon="google" href="/how-tos/connect-gsc">
    Verify real-world indexing and rankings
  </Card>
</CardGroup>