Skip to main content
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

CategoryWhat it checks
TechnicalCrawlability, indexing, broken links, redirects, robots.txt, sitemap
PerformanceCore Web Vitals, load speed, image sizes, JavaScript bloat
Content QualityTitle tags, meta descriptions, H1/H2 structure, word count, keyword usage, readability
Mobile SEOMobile-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

1

Open Site Audit

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

Pick a category

Choose Technical, Performance, Content Quality, Mobile, or Run All.
3

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

Click Run Audit

The audit crawls and analyzes your site. Most audits finish in 30–60 seconds; larger sites can take a few minutes.
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

SeverityWhen to fix
CriticalNow — these directly block indexing or rankings (broken robots.txt, no title tags, server errors)
WarningThis sprint — real issues that hurt you but aren’t immediately fatal
NoticeWhen 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.
1

Click Schedule on the audit tool

On the Site Audit page, click Schedule.
2

Pick a frequency

Weekly or monthly are the common cadences. Daily is rarely necessary and eats into your AI credits.
3

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

Set recipients

The summary can email you, your team, or a Slack channel.
See the SEO reference for integration details and crawl configuration.

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

​
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