What the audit checks
Schema markup
Schema markup
Does each page have appropriate structured data? SurgeRank checks for
Article, FAQPage, HowTo, Organization, and Product schema where relevant. Pages without schema are harder for AI engines to categorise and less likely to be cited with attribution.Crawlability
Crawlability
Are AI crawlers blocked by your
robots.txt, noindex directives, or prohibitively slow load times? SurgeRank tests against the known user-agent strings used by major AI crawlers (including GPTBot, Google-Extended, and PerplexityBot) and flags any directive that prevents them from accessing your content.Content structure
Content structure
Are headings, paragraphs, and lists organised so an AI engine can extract discrete, attributable facts? The audit checks heading hierarchy, paragraph length, and whether key claims are surfaced early in sections rather than buried in long prose blocks.
Entity clarity
Entity clarity
Is your brand name, product name, and category consistent throughout the site? Inconsistent entity naming (for example, using “SurgeRank”, “Surge Rank”, and “SR” interchangeably) confuses AI engines and reduces citation confidence. The audit flags inconsistencies across your crawled pages.
Freshness signals
Freshness signals
Does your content clearly show when it was published and when it was last updated? AI engines weight freshness heavily for certain query types. The audit checks for visible publication dates,
datePublished and dateModified in schema, and Last-Modified HTTP headers.Internal linking
Internal linking
Do your most important pages receive strong internal links from the rest of the site? AI crawlers follow internal links to discover and re-crawl content. Pages that are poorly linked internally are crawled less frequently and cited less often. The audit identifies high-value pages with weak internal link profiles.
Running an audit
To start an audit, open the Audit tab and click Run audit. SurgeRank will crawl your site starting from your root domain. A full crawl typically completes within 15 minutes for sites under 1,000 pages; larger sites may take longer. You’ll receive an in-app notification and an optional email when the audit is complete. You can limit the crawl to a specific subdirectory (for example,/blog/ only) using the Crawl scope setting if you want faster results for a particular section of your site.
Reading audit results
Every issue the audit finds is assigned one of three priority levels:| Priority | Meaning |
|---|---|
| High | Directly blocks or significantly suppresses AI citations. Fix immediately. |
| Medium | Reduces citation frequency or quality. Fix in the current sprint. |
| Low | Minor signal improvements. Address when capacity allows. |
Fixing issues
Every finding in the audit results includes three things:- Plain-English description — what the issue is and why it matters for AI citations.
- Specific fix recommendation — exactly what to change, including which file, CMS setting, or page element to update.
- Code snippet (for schema issues) — a ready-to-use JSON-LD block you can paste directly into your CMS’s
<head>section or schema field.
robots.txt rule or HTTP header causing the block and provides a corrected version you can implement immediately.