Skip to content
srSiteRune
Start free

For SEOs and engineers

Technical SEO Audit Tool

A technical SEO audit is the origin's contract with crawlers: what they are allowed to fetch, which URL is canonical, and whether the HTML they get is the page you think you shipped.

https://

No card. Three guest scans, then an account.

Technical surface we actually measure

  • Final status after redirects, plus the redirect chain we followed (cap 6 hops)
  • HTTPS vs HTTP on the final URL
  • Canonical tag present, empty, or pointing at a different host/scheme
  • robots.txt rules, including Disallow: / and missing Sitemap:
  • XML sitemap body we could fetch — we do not validate every <loc> in a 50k file
  • Duplicate or missing titles/descriptions on walked URLs
  • Indexability: noindex on home vs interiors, thin HTML, JS-only heroes
  • Structured data: JSON-LD types and parse failures
  • HTTP cache and compression as crawl-budget / TTFB signals — not as CWV
  • Rendering: we score the first HTML. If the hero is a client island, seo-thin fires. We do not execute Chrome.

Examples an SEO lead will recognize

Canonical to the apex, request was www (or the reverse)

We report the href we saw. We do not rewrite your CDN. Fix trailing slash and host in one place — Next metadata.alternates.canonical, Yoast, or theme.liquid.

Sitemap 200s with a 2xx HTML login wall

Shopify password pages and staging plugins do this. The finding is 'sitemap not usable', not a green check because the URL exists.

Two H1s and a title of 12 characters on /docs

The homepage can be a 90. The template family is the work. That is why we walk interiors.

Crawl approach

  1. Polite GET with SiteRune/1.0. If a WAF 403s the crawler UA and serves HTML to a Chrome UA, we flag the split — Googlebot often sees the 403.
  2. Same-origin only. No private IPs. Skip obvious admin, cart, checkout, wp-login.
  3. Prefer URLs listed in llms.txt, then nav, then sitemap locs.

What we will not pretend to do

  • No JS rendering, no log-file crawl budget, no hreflang matrix across 40 locales unless those URLs are in the walk.
  • No 'index bloat' estimate for faceted navigation we did not fetch.
  • Performance numbers are this vantage point's TTFB, not CrUX.

Questions

Do you render JavaScript?

No. We fetch HTML. If critical copy is client-only, that is a finding. For runtime INP/LCP, use Lighthouse or PageSpeed Insights after you ship.

Can you crawl my whole site?

Not on purpose. Caps exist so this stays a brief, not a 50,000-row CSV. Use Screaming Frog or Sitebulb for the estate; use SiteRune for the punch list and files.

Scan a live URL

Same engine as the rest of SiteRune. Guest scans stay free.

https://