What Is an SEO Test? How to Test a Website's SEO Step by Step
An SEO test checks whether a search engine can reach your page, is allowed to index it, and can understand what it's about. That's the whole job. It is not a ranking prediction and it doesn't tell you what position you'll hold. It answers a narrower, more useful question: is anything on this page stopping it from competing at all?
People conflate two different things under "test my SEO." One is the technical page check, which is what this article covers and what SEOtest.app tools do. The other is rank tracking, watching your position for a keyword over time, which comes from Google Search Console, not from a test tool. Getting them mixed up is why someone runs a "test," sees a green score, and then panics that they still aren't on page one. The test passed. Ranking is a separate, slower game.
The fastest way to run a test is to paste your URL into the free SEO analyzer on the homepage, which checks most of what follows in one pass. But it helps to know what each check is actually looking for, so you can read the output instead of just chasing a number.
What an SEO test actually checks
A complete on-page SEO test covers six things. In roughly the order that matters:
Crawlability. Can a search engine bot fetch the page at all? A stray Disallow line in robots.txt, a server returning a 500 error, or a redirect loop all make a page uncrawlable. If a bot can't fetch it, nothing else matters.
Indexability. Even a crawlable page can carry a <meta name="robots" content="noindex"> tag or an X-Robots-Tag: noindex header that tells Google to keep it out of the index. This is the single most common "why isn't my new site showing up" cause we see: a noindex left on from the staging build.
On-page metadata. The <title> and meta description. These don't just affect ranking; the title is a real ranking factor and both control how your listing reads in search results, which drives your click-through rate.
Heading structure. Whether the page has one clear H1 and a sensible H2/H3 outline, so both readers and crawlers can follow the document's structure.
Structured data. Schema markup (JSON-LD) that makes the page eligible for rich results. Optional, but it changes how your listing looks.
Social tags. Open Graph and Twitter Card tags that control the preview when your link is shared. Not a Google ranking factor, but broken cards cost clicks.
Some tests also fold in performance (Core Web Vitals), which Google measures directly through PageSpeed Insights. We'll treat that as its own step because Google owns the authoritative tool for it.
A 10-minute SEO test sequence
Here's the order to run it. Each step names the specific check and what a pass looks like.
Minute 1-2: the whole-page pass
Paste your URL into the homepage analyzer. Read the summary. This flags the obvious failures (missing title, no H1, no meta description, missing OG tags) so you know where to dig. If everything's green here, the deeper steps are just confirmation.
Minute 3-4: can it be crawled and indexed?
Two checks. First, visit yoursite.com/robots.txt in the browser and confirm you don't see Disallow: / under User-agent: *. Run it through the robots.txt validator if the syntax looks off. Second, view the page source (Ctrl+U) and search for "noindex". If you find content="noindex" in a robots meta tag on a page you want indexed, that's your problem, full stop. Robots.txt and noindex do different jobs, and mixing them up is common enough that we wrote up robots.txt versus noindex.
Minute 5-6: metadata length and headings
Drop your title and meta description into the SEO Character Counter. A title over roughly 580 pixels (about 60 characters, but pixels are what Google truncates on) gets cut off in results. A description over about 155-160 characters gets clipped. Then run the page through the Heading Analyzer and confirm there's exactly one H1 and the levels don't skip.
Minute 7-8: redirects and structured data
If you're testing a URL that redirects (say the non-www to www version), run it through the Redirect Checker and confirm it's a single 301, not a chain of three hops. Then, if the page has schema, validate it. The Schema Markup Generator builds clean JSON-LD, and Google's own Rich Results Test confirms eligibility.
Minute 9-10: social preview
Run the page through the Open Graph Checker to confirm the scraper sees a title, description, and image. Then check how the card renders with the Social Media Preview. If the image is missing, it's usually because the og:image tag points to a relative URL or is injected client-side where scrapers can't read it.
Ten minutes, six categories, and you know whether the page is technically sound. For the version of this that walks a whole site rather than one page, see our free SEO audit walkthrough.
How to read the results without panicking
This is where people get it wrong. A test tool hands you a list of warnings, and the instinct is to fix all of them. Don't. Warnings are not equal.
Sort what you find into three buckets:
| Severity | Examples | Action |
| --- | --- | --- |
| Blocking | noindex on a live page, Disallow: /, 500 error, redirect loop | Fix today. The page can't rank until you do. |
| Real but not urgent | title truncated, no meta description, missing H1, thin content | Fix this week. These affect performance but the page still works. |
| Cosmetic | missing og:locale, no Twitter Card on a B2B page, "image alt could be more descriptive" | Fix if you're bored. Often not worth the time. |
The tools that give you a single "SEO score out of 100" flatten this distinction, which is why the score is less useful than the list underneath it. A page can score 78 with one blocking issue and a page can score 78 with fifteen cosmetic ones. The number's the same; the situations are opposite.
A concrete example of a warning to ignore: many tools flag "meta keywords tag missing." Google stopped using the meta keywords tag for ranking well over a decade ago. Adding it does nothing. If a tool marks its absence as a problem, that tells you something about the tool.
Where the score does help is tracking your own page over time. If you fix the blocking issues and the number climbs, good. Just don't compare your score to a competitor's, because you're both being graded by a formula neither of you controls.
Test versus rank tracking: don't confuse them
To close the loop on the thing people mix up. An SEO test tells you if a page is technically ready to compete. It says nothing about whether it will win. Winning depends on content quality, competition, links, and time, and the way you measure it is Google Search Console, which shows your real impressions, clicks, and average position for every query.
So the honest workflow is: run the test to clear technical blockers, publish good content, then watch Search Console over weeks to see if it ranks. A test you pass on Monday won't show ranking movement on Tuesday, and that's normal, not a failure. If you're doing this for a brand-new site, our guide on SEO for a new website sets realistic expectations for the first month.
Frequently Asked Questions
What is an SEO test in simple terms?
It's a check of whether a search engine can reach your page, is allowed to index it, and can understand what it's about. It looks at crawlability, indexability, your title and description, headings, structured data, and social tags. It does not predict your ranking; it confirms the page is technically able to compete.
How do I test my website's SEO for free?
Paste your URL into the free SEO analyzer for a one-screen summary, then run the specific checks: robots.txt and noindex for indexing, the character counter for metadata length, the heading analyzer for structure, and the Open Graph checker for social previews. For actual ranking data, use Google Search Console, which is also free.
Does passing an SEO test mean I'll rank on Google?
No. A test confirms your page has no technical blockers. Ranking depends on content quality, competition, backlinks, and time. Think of the test as clearing the page for takeoff, not guaranteeing it reaches the destination. Many pages pass every technical check and still take months to rank in a competitive niche.
How often should I test my SEO?
Test a page once when you publish it, and again whenever you make structural changes (new template, migration, redesign) or after a site move. Retesting an unchanged page daily tells you nothing. For ongoing monitoring, Search Console does the watching for you and flags indexing problems as they appear.
Why does my page pass the test but still not appear in Google?
Almost always because it hasn't been indexed yet, not because of a test failure. New pages can take days to weeks to get crawled and indexed. Check the URL Inspection tool in Search Console: it tells you whether Google has indexed the page and why not if it hasn't. A passed test plus an unindexed URL usually just means "wait, or request indexing."