S

SEO Audit

Raw vs rendered, not a score

Docs
← Back to audit

How to Use This Tool

About this tool

This tool compares a page's raw HTML against what a crawler can actually read, then builds a list of actionable findings — not a single score. Search ranking depends on many other factors (content relevance, backlinks, domain authority, and more) that can't be measured from one URL, so this tool focuses on technical hygiene instead of promising a search position.

How to use it

  1. 1.Enter the URL of the page you want to check, then click Analyze.
  2. 2.Pick which user-agent to crawl as: Googlebot or Generic bot (full explanation below).
  3. 3.On success, you'll see a summary of findings by severity, the raw facts found (title, description, canonical, etc), and a full list of findings with why each matters and how to fix it.
  4. 4.If the page couldn't be fetched or was blocked, a single explanation banner appears instead of a findings list — see "When you see a banner" below.

Googlebot vs Generic bot

Googlebot

Mimics Googlebot: sends Googlebot's own User-Agent header, and is matched against the site's Googlebot-specific robots.txt group (if one exists). This answers "can Google crawl this page?" — the question most people actually want answered.

Generic bot

Uses this tool's own bot identity, matched against the generic group (User-agent: *) in robots.txt. This answers "what can a generic crawler, with no special treatment, see?" — useful when a site's robots.txt treats Googlebot differently from everyone else.

Results can differ by user-agent, since robots.txt can have different rules per user-agent. Important note: many large sites verify Googlebot's identity via reverse DNS / Google's real IP ranges, not just the User-Agent header — so even with Googlebot selected, a site like LinkedIn can still reject the request. That isn't a bug; that's their security working as designed.

When you see a banner instead of a findings list

This tool deliberately doesn't guess when a page couldn't be fetched. Rather than report "title not found" when the page was never actually read, it shows a single banner explaining why content checks were skipped entirely — not treated as failed, just never checked.

robots.txt disallows it
The site's robots.txt disallows this path for the user-agent you selected. The tool didn't proceed with fetching the page, out of respect for that rule. Try switching user-agent — results can differ if the site has separate rule groups per user-agent.
Server blocked it (anti-bot)
The server responded with a status commonly used to reject automated requests (e.g. 403, 429, or LinkedIn's own 999), not the real page. This usually means the site has an anti-scraping system, not that the page has an SEO problem.
Other HTTP error
The page responded with a non-2xx status that isn't an anti-bot signal (e.g. 404 or 500). Worth checking directly whether the page is genuinely broken.
Too many redirects
The URL redirected repeatedly without ever reaching a final page. There may be a redirect loop worth fixing.
Timeout / connection failed
The server didn't respond in a reasonable time, or the connection failed (e.g. an SSL error or connection refused).
Domain not found
The domain name couldn't be resolved. Double-check the URL is correct and the domain is still active.

Audit limits

To prevent abuse, the number of audits per IP address is limited over a given time window. If you hit the limit, you'll see a message asking you to try again later.