Free SEO check
Enter a page’s address and we check it against what Google and Bing say matters, from whether it can be found to how fast it loads for real visitors. Every finding links to the search engine’s own documentation. No score, no sign-up.
How the check works
You give us the address of a page. We fetch it once, with the site’s robots.txt and the few files the page points to, such as its canonical address and its favicon, and read what a search engine reads. Then we compare what we find with what Google and Bing say in their own documentation, and link every finding to the page it comes from.
Each stage gets a verdict in words: Blocked, Needs attention or Looks fine, or Not checked when the check couldn’t get that far. There is no score out of 100, because search engines don’t use one.
Speed comes from Google PageSpeed Insights, which reports how fast the page loads for real visitors. It takes a little longer, so it arrives after the rest. The check is free and asks for nothing but the address. If you want help with what it finds, you can request a call back under the results.
What it looks at, stage by stage
The stages follow the order a search engine works in: it has to reach a page before it can index it, and index it before it can show it.
Reach
Whether the page answers, and with what. We follow redirects one at a time, up to five, note whether the page uses HTTPS and whether the plain http:// address leads to it, and time the server’s first answer. Google doesn’t index a page that answers with an error (Google on HTTP status codes), and a redirect that loops never reaches a page.
Index
Whether search engines may crawl and index the page. We read robots.txt the way Google does: the group of rules meant for Googlebot, and in it the longest rule that matches (Google’s robots.txt rules). We look for noindex in the page and in its headers (Google on noindex), check the canonical address the page names (Google on canonical URLs) and look for a sitemap.
We also count the words the HTML carries before any script runs. Google runs JavaScript before it indexes a page (Google on JavaScript), but Bing warns that content it can’t render reliably may not be indexed (Bing Webmaster Guidelines), and tests have found that most AI crawlers don’t run scripts at all.
How it shows in results
What a search result is built from: the title, which Google starts from in most cases (Google on title links), the meta description, which it uses when it describes the page better than the page’s own text (Google on snippets), the favicon (Google on favicons) and, on a home page, the site name (Google on site names). We draw how the result might look, as a guide only: Google often shows a different title or description.
Content and structure
Whether the page has a main heading and real heading elements, whether its images have alt text (Google on images), whether it declares its language and fits a phone’s screen (Google on mobile-first indexing), and whether its links are ones search engines can follow (Google on crawlable links).
Structured data
Which schema.org types the page marks up, whether each JSON-LD block can be read, and which of the types Google can turn into a rich result (Google’s list). We don’t check every property ourselves: Google’s Rich Results Test does that, and the report links to it for your page.
Speed
Real visitors’ Core Web Vitals on phones over the last 28 days, from the Chrome UX Report: how fast the main content shows, how quickly the page responds and how much it jumps about, for the page or, with too few visits, the whole site. Google says its ranking systems use these (Google on Core Web Vitals). Lighthouse’s lab test is there to help find causes, not as a score.
What other checkers flag, and why we don’t
Many SEO tools report problems that Google says don’t matter: more or fewer than one H1, headings out of order, titles over 60 characters, descriptions of the wrong length, too few words, a low text-to-code ratio, a missing keywords tag and unminified code (Google’s SEO Starter Guide, Google’s office hours). The report shows what your page has for each, with what Google said, but counts none of it against you.
What the check leaves out
A check of one page can’t see everything. It doesn’t look at:
- The rest of your site. We check one page at a time, so problems elsewhere, such as broken links or the same title on many pages, don’t show.
- The page after its scripts run. We read the HTML as the server sends it, and Google, which runs scripts, may see more than we do.
- Rankings, traffic and links from other sites. Search Console shows what Google sees for your site; we don’t guess.
- Whether the content helps the people it’s for. That matters most, and no tool can judge it for you (Google on helpful content).
Request a call back
Leave your number and we’ll ring you back the same working day. Prefer email? Add your address and we’ll write back instead.