Skip to main content
Hiveku’s AI-powered site audit crawls your site and flags SEO issues, each with a plain-language explanation and a suggested fix.

​
Where to Find It

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

​
What the Report Covers

Site Audit runs ONE crawl that covers everything. The issues in the report come back labeled by category - crawlability, indexability, performance, content, internal linking, mobile, and security - so the categories describe how the findings are grouped, not separate audits you choose between. The most common groups: The standalone Technical, Performance, Content, and Mobile audit tools under Marketing > SEO > Tools are separate tools, not modes of Site Audit - Site Audit has no category picker.

​
Run an Audit

1

Open Site Audit

Go to Marketing > SEO > Tools > Site Audit.
2

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.
3

Set the page budget

The default is 50 pages. Larger crawls cover more of the site and cost proportionally more research credit.
4

Click Run Audit

The audit crawls and analyzes your site - typically within a minute or two, up to about five minutes for a default 50-page crawl.
5

Review the report

Results show an issue list, each with severity, affected URL, and a recommendation.

​
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.
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.

​
Severity Levels

​
Fix Issues with AI Chat

The audit integrates with your project’s AI assistant. Once you’ve run an audit, you can just ask:
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.

​
Make it a cadence

There is no scheduler on the Site Audit tool - audits run when you run them. Two habits keep them useful: re-run after every deploy that touches templates or routing, and put the audit on a weekly agency cadence from Claude Code - the /hiveku:weekly pass reads the audit delta as part of its sweep. See SEO Delivery Tools for the agent-side audit surface and crawl details.

​
Verify a Fix

1

Run an audit

Note the issues it finds.
2

Apply a fix

Use AI chat or edit manually.
3

Deploy

Push the changes live — SEO audits run against your deployed site, not the editor.
4

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.

​
From Claude Code

The same audit is available to the agent rail: start a crawl, poll it to completion, then run crawl deep dives - redirect chains, duplicate content, non-indexable pages, internal links. See Site audits: one crawl, three calls for the tool surface and Run SEO from Claude Code for the commands that drive it.

​
Troubleshooting

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.
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.
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).
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.
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.

​
What’s Next?

SEO Setup

Configure sitemaps, meta tags, and structured data

Connect Google Search Console

Verify real-world indexing and rankings