Skip to main content
itzseo
Powered by Claude

Prioritized fixes.
Plain English. Zero noise.

Most audit tools drop 200 issues on your dashboard and wish you luck. ItzSEO runs the full crawl, measures Core Web Vitals, validates schema — then Claude prioritizes every issue by impact and effort and explains the fix.

The 200-issue dump

Most audit tools list problems. They don't rank them.

You crawl a 142-page site. The tool returns 47 issues. Five are critical, fifteen are noise, and the rest sit in between. Without a priority, your team picks the easy ones and the critical ones stay broken.

What ItzSEO does

Crawl. Measure. Validate. Prioritize.

Full-site Playwright crawl

Real browser. Render-aware. Picks up JavaScript-rendered content. Bounded by tier (Free 25 pages, Starter 250, Growth 1,000, Agency 1,000, Scale 5,000).

Core Web Vitals

LCP, INP, CLS from both lab (Playwright) and field (CrUX). Per-page scoring. Mobile + desktop separately. Threshold-flagged.

Schema validation

Every JSON-LD block validated against schema.org. Invalid fields flagged with the line number. Suggested fix included.

Claude prioritization

Every issue scored by impact × effort. Critical = LCP > 4s on guide pages (high impact, hours of effort). Med = broken 404 links (medium impact, minutes). Surfaces what to fix first.

Plain-English fix steps

No “optimize TTFB.” You get ‘Your hosting's TTFB is 1.2s. Most likely cause: cold cache on dynamic queries. Fix: add Cloudflare full-page caching for /guides/*.’

Export anywhere

Linear, Jira, GitHub Issues — one click per issue. Or assign inline to a teammate. Or export the full audit as a CSV/PDF for client reports.

Severity levels

4 buckets. Claude-assigned.

CRITMissing canonical on paginated pages24 pages1h
CRITLCP > 4s on guide pages18 pages3h
HIGHMissing Article schema42 pages2h
MEDBroken internal links (404)7 pages30m
LOWMissing alt text on decorative images56 images1h
Exports

Issues go where your team already works.

One click per issue. Linear, Jira, or assign inline to a teammate via /projects/[id]/tasks. Or bulk-export as CSV for a client report. White-label PDF on Agency tier.

FAQ

Technical Audits questions.

How long does a full-site audit take?
Bounded crawl: ~5 minutes for 100 pages, ~30 minutes for 1,000 pages. Background job — you don't have to keep the tab open. Email notification when complete. Larger sites should run audits weekly via the cron schedule rather than on-demand.
Does the crawler respect robots.txt?
Yes. We honor robots.txt by default + a 1-second crawl-delay between requests. Override only available on Agency+ if you confirm you own the domain (rare — useful for staging sites where you want to crawl despite a noindex).
What's the page limit?
Free: 25 pages. Starter: 250. Growth: 1,000. Agency: 1,000 (with 5 sites). Scale: 5,000 across all sites. Beyond Scale, contact us.
Do you check for JavaScript SEO issues?
Yes. Playwright renders the page in a real Chromium browser, so we catch JS-rendered content, lazy-loaded images, hydration mismatches, and CSR-only content. This is the main reason we're slower than crawler-only tools like Screaming Frog — accurate render matters more than speed.
Can I run an audit before signing up?
Single-page free at /tools/free-seo-audit (no signup). For multi-page audits, you need a Starter tier or higher. Free plan includes one Basic audit per workspace.
How is Claude prioritization different from rule-based severity?
Rule-based: ‘missing canonical = HIGH’. Claude: ‘missing canonical on a 24-page guide series with high traffic = CRIT, missing canonical on a stagnant tag page with 0 traffic = LOW.’ Context-aware. Same issue type, different priority based on impact.

Stop dumping issues. Start fixing them.

14-day trial. Or audit a single page free.