Indexing & crawlability
HTTPS and the http→https redirect, www consistency, redirect chains, robots.txt rules, noindex directives, the canonical tag and the XML sitemap. If any of these is wrong, nothing else on the page matters.
Enter a URL and get a graded SEO audit in seconds: indexing, titles and headings, structured data, social previews, mobile readiness, speed and security, then Google Lighthouse scores with Core Web Vitals. Every check shows the value it was judged on.
What it checks
Search engines rank pages they can crawl, understand, and trust. The checks map to those three questions, weighted by how much each one actually moves the answer.
HTTPS and the http→https redirect, www consistency, redirect chains, robots.txt rules, noindex directives, the canonical tag and the XML sitemap. If any of these is wrong, nothing else on the page matters.
Title and meta description length against what search results display, a single H1, heading order, visible word count, the declared language and image alt coverage — the signals that say what the page is about.
Open Graph and Twitter card completeness, so shared links carry a real preview, plus JSON-LD structured data — the machine-readable layer that rich results and AI answer engines read.
The viewport tag Google's mobile-first index requires, server response time, document weight, text compression, render-blocking scripts in the head and mixed content.
HSTS and the same security-header grade as our tech stack checker. Not direct ranking factors, but Lighthouse best-practice items and trust signals for visitors.
Google's own performance, accessibility, best-practice and SEO scores from a real mobile render, plus field data from Chrome users where the site has enough traffic.
What it cannot see
Want to know what a site is built on, not just how it ranks? Try the website tech stack checker, or browse our directory of AI build tools.
FAQ
Around thirty checks across eight areas, all from what the site publishes: whether the homepage returns 200 over HTTPS and how http:// and www variants redirect; robots.txt, noindex directives, the canonical tag and the XML sitemap; the title, meta description, H1 and heading order, visible word count, language and image alt text; internal and external links; Open Graph and Twitter card tags; JSON-LD structured data and favicon; the mobile viewport; server response time, document size, compression, render-blocking scripts and mixed content; and HSTS plus the security-header grade. A Google Lighthouse run then adds performance, accessibility, best-practice and SEO scores with Core Web Vitals.
No, and no free single-fetch tool honestly can. Rankings depend on the query, the searcher's location and device, and hundreds of pages of competition. What this tool measures is everything on your side that ranking depends on: whether search engines can crawl and index the page, whether it says clearly what it is about, whether it is fast and mobile-ready, and whether it carries the structured data that rich results and AI answer engines read. Fix those and rankings follow; ignore them and no amount of content will.
Every check carries a weight from 1 to 3 according to how much it matters — noindex, HTTPS, the viewport tag and the title carry 3; nice-to-haves like the favicon carry 1. A pass scores full weight, a warning half, a failure zero, and informational checks carry none. The score is the weighted percentage, graded A (90+), B (75+), C (60+), D (40+) or F. It is deliberately strict: a B means the basics are in place, an A means there is nothing obvious left to fix from the outside.
Because Google is actually loading the page. PageSpeed Insights spins up a simulated mobile device, loads the homepage with JavaScript running, records a performance trace and audits the rendered result. That takes ten to forty seconds, so it runs after the rest of the report and fills in when ready. If the site has enough Chrome traffic, the section also shows field data — the Core Web Vitals real visitors experienced over the last 28 days, which is what Google's ranking systems use.
The on-page checks read the HTML the server sends and do not execute JavaScript. A site that renders its content client-side — many React, Vue and Angular builds do — sends a nearly empty document and fills it in the browser. Google does render JavaScript, but later and with a budget, so server-rendered or pre-rendered content still indexes faster and more reliably. The Lighthouse section, which does run JavaScript, will show whether the rendered page is healthy.
Yes. The tool makes the same requests any browser or search engine crawler makes: the homepage, robots.txt, the sitemap and the http:// and www variants of the address, once each. It reads only public responses, sends no unusual traffic, and never attempts to log in, probe for vulnerabilities or crawl beyond those few URLs. Checking a competitor's homepage is ordinary competitive research; the results are things they already publish to everyone.
Technical SEO, Core Web Vitals, structured data for AI answer engines, and the engineering to ship the fixes — one team, no hand-offs. The first audit is free.
No commitment. No sales pitch. Straight answers.