SEO checker
Can Google find, read and index your site?
What the SEO check covers58 scored checks in 8 groups and 20 suggestions, each with its source.
- Crawl access: robots.txt, status codes, redirects
- Indexing: noindex, canonicals, soft 404s
- Discovery: sitemaps, internal links, hreflang
- Understanding: titles, structured data, content in the server HTML
- Up to 25 pages sampled, every result with its evidence
SEO checker results, explained
- Strong (85 to 100)
- The homepage passes the Lighthouse-compatible SEO audits, or misses only minor ones. Google can fetch it, is allowed to index it and finds a title, a description and crawlable links.
- Ready with gaps (70 to 84)
- Indexing works, but one or two audits fail, often a missing meta description, link text such as click here or images without alt text. Fix them in the order shown.
- Important blockers (50 to 69)
- Something stops Google from understanding the homepage well, such as an invalid canonical, a robots.txt that does not parse or hreflang codes Google rejects.
- Likely to struggle (under 50)
- The homepage cannot be indexed as it stands. The usual causes are a noindex, a robots.txt Disallow or an error status. Clear that first; the other audits matter little until it is fixed.
- Beyond Lighthouse
- Sitemaps, redirects, soft 404s and the sampled deeper pages are listed apart. They never move the headline number but often explain why pages are missing from Google.
Common problems with SEO scans
A launch that kept its staging settings
The site went live with Disallow: / in robots.txt, a noindex in the shared layout or a canonical that still names the preview host. Search Console shows pages as excluded with no error on the site itself.
Fix: Remove the staging rule, deploy, then use URL Inspection in Search Console to request indexing of the homepage and key pages.
Content that only exists after JavaScript runs
The server HTML holds an empty root element and a script bundle. Google renders JavaScript later, but Bing, AI crawlers and link previews often read only the first response.
Fix: Render the main text, title and links on the server or at build time, and keep JavaScript for interaction.
Two or three versions of every URL
The same page answers on http and https, with and without www, with and without a trailing slash. Links and signals are split across copies.
Fix: Pick one host and one URL form, redirect the rest permanently in a single hop, and point canonicals and the sitemap at the chosen form.
Missing pages that answer 200
Any mistyped URL shows a friendly not found message with status 200, or redirects to the homepage. Google reports these as soft 404s and may crawl them as thin pages.
Fix: Return a real 404 or 410 status for URLs that do not exist, with a helpful page body.
A homepage head that fails the SEO audits, and one that passes
The noindex alone keeps the homepage out of Google whatever else the page does well. Descriptive link text tells Google and readers what the target page is about.
<head> <title>Home</title> <meta name="robots" content="noindex"> </head> <a href="/pricing">Click here</a>
<html lang="en"> <head> <title>Acme: invoicing for EU freelancers</title> <meta name="description" content="Send VAT-ready invoices in minutes and get paid by card or SEPA transfer."> <link rel="canonical" href="https://acme.example/"> </head> <a href="/pricing">See Acme pricing</a>
Questions about SEO scans
- Does a score of 100 mean my site will rank?
- No. The score says Google can crawl, index and read the homepage. Ranking depends on how useful the content is for a query, which no static scan can measure.
- Why is the headline score based on the homepage?
- It follows Lighthouse's SEO category, which audits one page. The deeper pages the scan samples are checked too and listed under Beyond Lighthouse.
- How is this different from Google Search Console?
- Search Console reports what Google actually crawled and indexed for a site you own. This checker tests any domain from the outside in about a minute, so it is useful before launch or for a site you cannot verify.