Real-browser technical audit

Audit every page the way Google renders it.

300+ checks in a real Chromium browser on mobile, tablet and desktop. Your Google data ranks every fix.

Crawls run on your machine. Free, always.Evidence screenshots, not guesswork

Download for Mac

$19/mo, or $14/mo billed yearly · 7 days free · No card required

Digispot AI · SEO SpiderLive crawl
Page Audit Report
/products/digispot-ai-seo-spider
86Page score
Desktop94
Tablet90
Mobile78
Crawlability96
Metadata88
Content79
Schema92
Core Web Vitals71
Links94
CriticalLCP 4.1s on mobile
WarningMeta description truncated (172 chars)
Warning3 images missing alt text
NoticeAdd FAQ schema for AEO eligibility
287 of 300+ checks passed · evidence screenshots captured

Mobile 78 · Tablet 90 · Desktop 94 — parity gaps surfaced per URL

How it works

Inside a real-browser technical SEO audit

Static crawlers read source HTML and miss the rendered page. Spider audits what Googlebot indexes.

Crawl

Render in a real browser

Every page runs its JavaScript in Chromium on mobile, tablet and desktop. SPAs, lazy content and client-side redirects included.

Check

300+ checks, 23 categories

Crawlability, schema and Core Web Vitals to AEO, llms.txt, local SEO and accessibility. Each with a fix.

Score

Scores you can defend

A weighted page score across nine categories, plus a site score for SSL, robots.txt, sitemap and llms.txt.

Prioritize

Ranked by traffic at risk

GSC and GA4 weight every issue. Your fix list starts with what costs clicks.

In the app

One URL, rendered on three devices

Every page is rendered and screenshotted on each device, then scored. Mobile-parity gaps can't hide behind a good desktop score.

Digispot AI · SEO SpiderRendered · 3 devices
Render parity
/products/category/running-shoes
Mobile78
Tablet90
Desktop94

Mobile parity gap: −16 vs desktop. Hero image pushes LCP to 4.1s and the theme hides the H1 below 640px — both invisible in a desktop-only audit.

3 screenshots captured
URLMobileTabletDesktopGap
/products/category/running-shoes789094−16
/pricing919293−2
/blog/technical-seo-guide868888−2
What you get

Checks that only exist after rendering

Rendering parity, cloaking, AEO readiness — the signals you can't audit from view-source.

Screenshot evidence per finding

Each page is captured as rendered, per device. Every issue you escalate ships with proof.

Cloaking detection, scored

Each page is fetched twice, plain HTTP and full render. The gap is scored 0–100 to catch hidden content.

AI-search readiness built in

A dedicated AEO category: AI-crawler access, llms.txt completeness, FAQ schema gaps, snippet structure.

Per-device score gaps

Mobile, tablet and desktop each get a score per URL. Parity gaps stop hiding in averages.

Audit-to-audit comparison

Each crawl diffs against the last: new issues, fixed issues, score deltas. Prove a release helped, or catch its regression.

One issue catalog, zero drift

Severity, impact and fix guidance are defined once. Reports, MCP tools and AI always agree.

In the app

One page, 300+ checks, 11 report tabs

Every page opens a tabbed report, scored 0–100 per category. Metadata to Core Web Vitals, schema, local SEO and AI search.

Per-page audit coverage
315 checks · 23 categories
Metadata

Titles, meta descriptions, canonicals, robots directives, indexability

Headings

H1–H6 hierarchy, structure, keyword usage

Content

Depth, readability, duplication, E-E-A-T signals, brand mentions

Links

Internal/external, broken links, anchors, orphans, crawl depth

Media

Alt text, dimensions, compression, modern formats, video SEO

Schema

JSON-LD validity, required props, rich-result eligibility

Social

Open Graph, Twitter/X cards, share images & dimensions

Performance

Core Web Vitals (LCP, INP, CLS), TTFB, render-blocking

AI Search / AEO

AI-crawler access, llms.txt, FAQ schema, snippet structure

Local SEO

LocalBusiness schema, NAP consistency, hours, geo-coordinates

Internationalization

hreflang tags, x-default, return links, language targeting

Technical

SSL/HTTPS, HSTS, mobile-friendliness, URL readability, a11y

Every check backed by a screenshot · scored 0–100 per category · covers Google Search & AI-answer-engine best practices

Run it from Claude or Cursor

Your agent reads the audit like a teammate

Findings, screenshots, diffs and quick wins. All queryable over MCP.

Claude·digispot-seo · MCP

What broke since the last deploy?

Used 2 toolscompare_auditsget_page_issues

Compared the last two audits: 3 new issues, 11 fixed, score +4. The new ones are all missing canonicals on /blog templates — one-line fix, want the diff?

Ask a follow-up…

Tools your agent gets

start_crawlget_crawl_summaryget_quick_winsget_page_reportcompare_audits

One-call workflow recipes

  • Quick Wins to Spreadsheetrun
  • AI SEO Page Reviewrun

Or just type /seo-audit — one of 9 packaged slash commands the Spider ships for Claude Code.

Run your first real-browser audit today

Crawl 10,000 pages on Starter, unlimited on Pro. See what HTML-only crawlers miss.

Download for Mac

$19/mo, or $14/mo billed yearly · 7 days free · No card required

Explore the full Digispot AI SEO Spider

Common questions

How is this different from Screaming Frog or Sitebulb?

Three ways. Rendering: every page runs its JavaScript in real Chromium on three devices, so you audit what Google indexes. Prioritization: GSC and GA4 rank every issue by traffic at risk. Action: an MCP server lets your AI agent read findings and fix them. Price helps too: $169/yr vs $279/yr, and crawling is free.

How many pages can I crawl, and what does a crawl cost?

Crawling is free, always. It runs on your machine, so nothing is metered. The Free plan crawls up to 100 pages, mobile only. Starter crawls 10,000 pages on mobile, tablet and desktop. Pro and Agency remove the page limit.

What does 'evidence-backed' actually mean?

Every page is screenshotted as rendered, per device, during the crawl. When the audit flags a layout shift, a hidden H1 or a mobile-parity gap, you and your client see the rendered page beside the finding.

Does it audit for AI search engines too?

Yes, as a first-class check category. The audit validates llms.txt (weighted into your site score), checks if robots.txt blocks AI crawlers like GPTBot or PerplexityBot, flags questions missing FAQ schema, and compares how LLM bots and Googlebot see each page.