Tools
SEO Checker
Run a free SEO checker on any page: title, meta description, headings, canonical and indexability settings, robots.txt and sitemap, speed and security signals in one pass. A score out of 100 and a prioritized to-do list; free, no sign-up.
After the analysis, the fixes that raise the score the most are listed here.
- 90-100Good
- 70-89Fair
- 0-69Weak
How to use the SEO Checker
- 1Enter the page URL
Type the address of the page you want to check. You can skip https://, the tool adds it; besides the home page, try the inner pages you want to rank.
- 2Add a focus keyword
In the optional field, enter the search the page targets. The tool then looks for it in the title, H1, meta description, URL and first 100 words, and works out its density.
- 3Start the analysis
Press Analyze. The tool downloads the page from our server, then checks robots.txt and the sitemap; the result usually arrives within a few seconds.
- 4Read the score and the to-do list
At the top you see a score out of 100 and the number of errors, warnings and passed checks. The priority to-do list puts the fix that adds the most points first.
- 5Drill into the tabs
The Meta, Content, Technical and Social tabs show what each check found and how to fix it. Copy report gives you the whole result as plain text for your team.
How does the SEO checker calculate the score?
Each check carries a weight based on how much it affects whether the page can be found. The tool divides the points earned by the total weight and caps the score when the page cannot be indexed.
Passed = full weight; Warning and Info = half the weight; Error = 0Points earned ÷ total weight × 100, rounded to a whole number105 on an HTTPS page, 102 on an HTTP page; a focus keyword adds 13If the status code is not 200, the page has noindex or robots.txt blocks Googlebot, the score is at most 4990 to 100 Good, 70 to 89 Fair, 0 to 69 Weak0.8 s or less Passed, 0.8 to 1.8 s Warning, over 1.8 s ErrorAn unreadable robots.txt or a sitemap that could not be checked stays out of the score. I measure response time from our server, and because it includes redirects and the HTML download, it can come out slightly higher than the real TTFB.
Example score calculations
These rows are example scenarios on an HTTPS page; every check not mentioned counts as passed, and the numbers follow the tool's formula.
| Example situation | Weight lost | Calculation | Score | Badge |
|---|---|---|---|---|
| Only the meta description is missing (warning) | 6 × 0.5 = 3 | (105 - 3) ÷ 105 × 100 = 97.1 | 97 | Good |
| No title (error); no description and no canonical (warnings) | 8 + 3 + 3 = 14 | (105 - 14) ÷ 105 × 100 = 86.7 | 87 | Fair |
| Response 2.1 s and no viewport (errors); H1, sitemap and alt text missing (warnings) | 6 + 6 + 3 + 1.5 + 2 = 18.5 | (105 - 18.5) ÷ 105 × 100 = 82.4 | 82 | Fair |
| The page has noindex (critical error), everything else passes | 10 | (105 - 10) ÷ 105 × 100 = 90.5; critical cap 49 | 49 | Weak |
| Keyword analysis: phrase missing from title and description (warnings) | 2 + 1 = 3 | (118 - 3) ÷ 118 × 100 = 97.46 | 97 | Good |
The fourth row shows why the cap exists: without it, a page that cannot be indexed would look Good with 90 points.
Checks, weights and thresholds
The checks that affect the score and the result the tool gives in each case:
| Check | Weight | Passed | Warning or Info | Error |
|---|---|---|---|---|
| HTTP status code | 10 | 200 | - | Any code other than 200 |
| noindex (meta robots, X-Robots-Tag) | 10 | No noindex | - | noindex present |
| robots.txt | 10 | No block for Googlebot, or no file | File returns 5xx or 429 | Googlebot blocked from this URL |
| Title | 8 | 30 to 60 characters, one tag | Short, long or several tags | Missing |
| HTTPS | 6 | HTTPS with a valid certificate | - | HTTP or a certificate that fails verification |
| Meta description | 6 | 70 to 160 characters | Missing, short, long or several | - |
| Canonical | 6 | Self-referencing absolute URL | Missing, relative, another URL or conflicting | - |
| Viewport | 6 | Includes width=device-width | No width=device-width | No tag |
| H1 | 6 | One H1 | None or several | - |
| Server response time | 6 | 0.8 s or less | 0.8 to 1.8 s | Over 1.8 s |
| Word count | 5 | 300 or more | Under 300 | - |
| Image alt text | 4 | Every image has alt | Images without an alt attribute | - |
| Page language (lang) | 3 | Set | Missing | - |
| Compression, sitemap, mixed content | 3 each | gzip or Brotli; sitemap found; no http:// resources | Each one that is missing | - |
| Open Graph, structured data | 3 each | og:title and og:image present; JSON-LD or microdata present | Missing (Info when there is no structured data) | - |
| Heading order, HTML size | 2 each | No skipped levels; HTML up to 1 MB | Skipped levels (Info); HTML over 1 MB | - |
Rows with weight 0 (hreflang, HSTS, favicon, link counts, text to HTML ratio, og:description and others) appear in the report but do not change the score. The thresholds are not Google rules; they are practical limits I use for warnings.
What is an SEO checker and what does this one measure?
An SEO checker is an audit tool that looks at a web page the way a search engine does and lists its technical and on-page gaps. This one checks a single URL: it downloads the HTML, reads robots.txt and the sitemap on the same domain, and then groups more than 30 checks into four tabs.
- Meta: title, meta description, canonical, lang, viewport, character set and hreflang.
- Content: H1 and heading order, word count, image alt text, links and an optional focus keyword.
- Technical: status code, redirects, noindex, robots.txt, HTTPS, response time, compression, HTML size, sitemap and structured data.
- Social: Open Graph and Twitter card tags.
I run this kind of scan on the first day of every new project in my SEO consulting work. The reason is simple: lost rankings rarely have an exotic cause. A forgotten noindex, a wrong canonical or one blocking robots.txt line is often enough. The tool turns the findings into a score out of 100 and sorts the fixes by impact.
What does the SEO checker score tell you?
The score is a weighted average of the checks. The three checks that can keep a page out of the index entirely weigh the most: status code, noindex and a robots.txt block, 10 each. Next, the title carries 8; meta description, canonical, viewport, H1, HTTPS and response time carry 6 each. Smaller signals sit between 2 and 5.
A passed check earns its full weight, a warning half, an error nothing. However, I added one more rule: if the page cannot be indexed, the score stays at 49 or below, no matter how polished everything else is. That way a noindex page never looks Good just because its title is nice.
Keep one thing in mind when you read the score: 100 points do not mean the page will rank first. The tool measures the technical and on-page foundation; content quality, competitors and backlinks sit outside this measurement. Still, if the foundation is cracked, nothing you build on top of it pays off fully. So treat the score as a health check, not a ranking forecast.
Which title and meta description lengths are right?
Google publishes no character limit for titles. The Google Search Central documentation says there is no limit on how long a title element can be, but the title link in results gets truncated to fit the device width. That is why the ranges in the tool, 30 to 60 characters for titles and 70 to 160 for descriptions, are practical limits that lower the risk of truncation, not rules.
- Put the topic first and the brand last; if Google cuts the title, the brand goes and the topic stays.
- Do not repeat the same word in a title; Google cites that as an example of keyword stuffing.
- Write a description for each page that describes only that page.
In practice, the Google preview in the report gives you a rough idea of how the title and description will look. For pixel-based measurement, also try the SERP preview tool; the edit link carries your texts over. I explain how to write strong ones step by step in my guide to meta titles and descriptions.
Why might your page not be indexed?
If the Technical tab shows a red row, start there first. The three most common technical reasons a page does not appear on Google are also the heaviest checks in the tool:
- Status code: Google does not index a page that returns 404, 410 or 5xx. If there are redirects, the tool shows the final URL and every step of the chain.
- noindex: The tool reads both the meta robots tag and the X-Robots-Tag header. A noindex left over from a staging site is the error I meet most often on new sites.
- robots.txt: The tool picks the group that applies to Googlebot and applies the longest matching rule; on a tie, Allow wins.
There is a subtle point here: Google cannot see a noindex on a page you block in robots.txt, because it never crawls that page. So if you want a page out of the index, use noindex, not a robots.txt block. To edit the file, try the robots.txt generator. For the definitive indexing status, use URL Inspection in Search Console; the tool shows you where to look.
How does the SEO checker catch canonical and redirect problems?
A canonical tag tells Google which URL you prefer when the same content lives at several addresses. The tool reads every canonical declaration on the page plus the HTTP Link header, then separates four cases: no canonical, a relative URL, a canonical pointing to another URL, or several conflicting URLs.
Google supports relative URLs but notes that they can cause problems in the long run, so it recommends absolute ones. A canonical that points elsewhere is sometimes intentional; for example, a filtered category page may point to the main category. Still, if you see it on a product or service page, that page is most likely not in the index.
For redirects, the tool follows the chain step by step, up to 5 redirects. A single redirect is fine; however, a chain of two or more strains both crawling and speed. For the full chain, use the redirect checker. If you have just moved your site, my website migration SEO checklist will help as well.
How should you read the speed and security signals?
The tool compares server response time with the TTFB thresholds from web.dev: 0.8 seconds or less is good, over 1.8 seconds is poor. I take the measurement from our server, not your browser, and it includes redirects and the HTML download. As a result, the figure can be slightly higher than the real TTFB, and your visitors' location changes it too.
- Compression: if the HTML does not arrive with gzip or Brotli, the transfer size grows for no reason.
- HTML size: Googlebot crawls the first 2 MB of an HTML file; the tool warns above 1 MB.
- HTTPS and mixed content: if an HTTPS page loads images or scripts over http://, browsers may block them.
- HSTS: it does not change the score, but I recommend it once HTTPS is permanent.
That said, this tool is not enough to see full page speed, meaning the weight of images and scripts. For that, I recommend a Lighthouse performance test.
In what order should you fix the issues?
The priority to-do list shows how many points each fix adds and puts the biggest gain first. In client work I follow a similar order:
- Remove anything that blocks indexing: status code, noindex and robots.txt.
- Rewrite the title, meta description and H1 around the page's real topic.
- Turn the canonical into a self-referencing absolute URL.
- Add supporting signals such as viewport, lang, alt text and structured data.
- Improve server speed and compression on the hosting side.
Then run the analysis again after each fix; you see the score move right away. You can also scan a competitor's page with the same tool and compare titles, descriptions and structured data. For an assessment that goes beyond one page and covers site structure and crawl budget, take a look at my technical SEO guide.
Common SEO check mistakes
- ✕MistakeTreating the score as a ranking forecast✓Do this insteadThe score measures the technical and on-page foundation. Content quality, competitors and links need a separate review.
- ✕MistakeChecking only the home page✓Do this insteadAnalyze the category, product and service pages that bring traffic and sales one by one; problems usually hide on inner pages.
- ✕MistakeRewriting a title that works just because of a length warning✓Do this insteadLook at the click-through rate in Search Console before you touch a title that performs well; character count alone is not the measure.
- ✕MistakeUsing robots.txt to remove a page from the index✓Do this insteadUse noindex and let Google crawl the page; Google cannot see a noindex on a page you block.
- ✕MistakeForcing the keyword into every field✓Do this insteadUsing the phrase naturally in the title, H1 and first paragraph is enough. More repetitions do not bring rankings; they send a spam signal.
Frequently Asked Questions
A higher score is not the same as higher rankings.
Once the technical base is fixed, the real work starts: the right keywords, content and link strategy. Let's review your site together.
Related Articles
Blog
How to Write a Meta Title and Description: Examples That Raise Click-Through RateRead article →
What Is Technical SEO? 10 Technical SEO Tips You Can Apply to Your WebsiteRead article →
What Is Google Search Console and How Do You Use It? A Beginner's GuideRead article →
Technical SEO After AI: What Changed in Search Engines and What You Should DoRead article →

