Skip to main content
itzseo
Sign inSign up
Technical Audits

Audit any page. Know exactly what to fix first.

ItzSEO audits one URL at a time: 27 on-page checks, Core Web Vitals from PageSpeed Insights on mobile and desktop, JSON-LD detection, a deterministic 0–100 score, and — on paid plans — Claude's plain-English explanation, fix steps, effort and impact for every issue. Mark issues resolved, download the report as CSV, re-run to see what is left. 3 audits a month on Free, 30 on Starter, 150 on Growth, 500 on Agency, 2,000 on Scale.

Start free Try the free single-page audit →
What is checked

27 checks per page, in about a minute.

On-page essentials

Title and meta description length, canonical link, robots and noindex, one H1, heading structure, word count, image alt text, html lang, HTML size.

Core Web Vitals, mobile and desktop

LCP, CLS, INP and the Lighthouse performance score from Google PageSpeed Insights, measured separately for each device. Lab data; thresholds flagged.

Structured data

Every JSON-LD block found, the @type values it declares (including @graph), and any block that is not valid JSON.

Social and AI signals

Open Graph title, description and image, Twitter card, and whether the site publishes an llms.txt for AI assistants.

Claude explains and prioritises

Why each issue matters, one to four fix steps, effort from 15 minutes to 4+ hours, impact high to low — sorted biggest wins first. Paid plans.

Deterministic score

A fixed weight per severity, so the same page gets the same number twice and the trend across audits means something.

CSV export and issue status

Download every issue with its fix steps. Mark issues resolved or ignored; open ones stay on top.

Queued, not blocking

Audits run in a background queue that is picked up every minute. Queue several pages and come back.

How it works

From URL to fix list.

  1. STEP 1

    Paste a URL

    Any public page. Private and internal addresses are refused. Queuing the same URL twice returns the audit already running.

  2. STEP 2

    Fetch and check

    The server-rendered HTML is fetched (up to 2 MB) and the on-page checks run. PageSpeed Insights measures mobile and desktop.

  3. STEP 3

    Claude prioritises

    On paid plans, every issue gets an explanation, fix steps, effort and impact. The score is computed from the issues, not by Claude.

  4. STEP 4

    Fix, tick off, re-run

    Work through the list, mark issues resolved, download the CSV for a client, and re-run the page to confirm.

Plans

Audits per month.

Free
3
no Claude guidance
Starter
30
Growth
150
Agency
500
Scale
2,000

One audit is one URL. Claude explanations, effort and impact ratings are on paid plans; the Free plan gets the same checks with standard descriptions.

Compared

Technical Audits vs a desktop crawler.

 ItzSEOScreaming Frog / Sitebulb
ScopeOne URL per audit, queued in the cloudWhole-site crawl from your machine
JavaScript renderingNo — server HTML onlyYes (Chromium)
Core Web VitalsPageSpeed Insights, mobile + desktopPageSpeed / CrUX integration
Fix guidanceClaude: explanation, steps, effort, impact per issueIssue lists and documentation
SchemaJSON-LD detection and validityFull structured-data validation
ExportCSV per audit; issue status trackingCSV, Excel, Sheets, reports
Bundled withRank tracking, keywords, content, AI search visibility, CRM — one subscriptionSold alone, licence per machine
FAQ

Technical Audits questions.

Does ItzSEO run technical SEO audits?
Yes — one page at a time. Paste any public URL and ItzSEO fetches it, runs 27 on-page checks (title and description length, canonical, robots and noindex, H1 structure, word count, image alt text, JSON-LD presence and validity, Open Graph and Twitter tags, html lang, page size, llms.txt), pulls Core Web Vitals from Google PageSpeed Insights for mobile and desktop, and has Claude explain and prioritise what it found. Audits per month: Free 3, Starter 30, Growth 150, Agency 500, Scale 2,000.
Is it a full-site crawl?
No. Each audit covers one URL. To audit several pages, queue them one by one; each is its own report with its own history. A site-wide crawler is not part of the product today.
Does it render JavaScript?
No. The audit reads the HTML the server returns, the same way Googlebot's first pass does. Content that only appears after client-side rendering is not seen. There is no headless browser involved.
Where do Core Web Vitals come from?
Google PageSpeed Insights, run twice per audit — once with the mobile strategy, once with desktop. These are lab measurements (Lighthouse). Field data from real users (CrUX) is not included, and INP is reported only when Lighthouse measures it, never substituted with another metric.
How is the score calculated?
From the issues found, with a fixed weight per severity (critical 25, high 12, medium 6, low 2, subtracted from 100). The same page audited twice on the same day gets the same score, so the trend across audits is real. Claude writes the explanations and the fix steps; it does not set the score.
What does Claude add?
On paid plans, every issue found gets a plain-English explanation of why it matters, one to four concrete fix steps, an effort estimate (15 minutes to 4+ hours) and an impact rating, sorted biggest wins first. Claude is told to explain only the issues the checker found, never to invent any. On the Free plan the same issues are listed with standard descriptions.
Does it validate schema markup?
It detects every JSON-LD block, reports the @type values it declares (including inside @graph) and flags blocks that are not valid JSON. It does not validate fields against the schema.org vocabulary or against Google's rich-result requirements — use Google's Rich Results Test for that.
Can I export or share the report?
Each audit downloads as a CSV with one row per issue (category, severity, impact, effort, status, explanation, fix steps). Issues can be marked resolved or ignored so a re-run shows what is left. There is no PDF export, and no push to Linear, Jira or GitHub.
How long does an audit take?
Audits run in a background queue picked up every minute. A typical run finishes in one to two minutes: the fetch, two PageSpeed measurements and the Claude pass. The page updates itself while you wait; you can leave and come back.
Can I try it without signing up?
Yes — the free tool at /tools/free-seo-audit runs a similar set of on-page checks on a single URL without an account. The signed-in version adds PageSpeed, Claude guidance, history, issue status and CSV export.

Try Technical Audits on your own workspace.

14-day trial. No credit card required.

Start free trial See pricing