Skip to the content

Free crawlability check

Free SEO Checker

Find the technical problems that keep a page out of search results. The checker reads the page the way a search crawler does and lists what to fix first, with the evidence behind every verdict.

Check a page

Enter a public address. The checker runs 26 crawlability, on-page and structured data checks.

Runs 26 checks. A bare domain works, https:// is added for you.

Why use the SEO Checker

Evidence, not opinions

Every verdict shows what was observed: the status code, the tag, the rule in robots.txt. You can check the reasoning instead of trusting a score.

Ordered by impact

Critical problems such as a noindex tag or a blocking robots.txt come first, because nothing else matters until they are fixed.

A fix for every issue

Each failing check links to its documentation with the cause, the fix and the references from Google and the standards.

No signup

No account, no email and no API key. Run the check, read the result, share the link with whoever has to fix it.

When to use the SEO Checker

Before a launch

Catch a forgotten noindex tag or a staging robots.txt before the site goes live.

After a migration

Confirm that redirects are short, canonicals point at the new urls and the sitemap lists them.

When traffic drops

Rule out the technical causes first: a page that answers 404, a canonical that points elsewhere, a blocked path.

Client onboarding

Hand a new client a clear list of technical issues on the first call, with the evidence attached.

Content review

Check that a new article has one H1, a sized title, a description and valid structured data.

Weekly hygiene

Pair the checker with a monitor and hear about regressions as soon as a deploy causes them.

Understanding SEO

What technical SEO covers

Technical SEO is everything that decides whether a search engine can reach a page, read it and understand it: the status code, the redirects, robots.txt, the sitemap, the canonical link, the indexing directives, the title and the structured data.

It does not decide whether a page ranks. Ranking depends on relevance, quality and links, which no checker can measure. Technical problems can keep a good page out of the results entirely, which is why they come first.

How the checker works

  1. 1robots.txt first. The checker reads robots.txt and refuses to continue if the site asks AbackAuditBot to stay away.
  2. 2The page. It fetches the address, follows up to five redirects and parses the HTML that a crawler receives.
  3. 3Site files. It reads the sitemap and tries the host variants with and without www.
  4. 4The verdicts. Each check passes, warns or fails with the evidence it saw, weighted by how much a failure costs.

Reading the score

A pass earns a full point, a warning half a point and a failure none. Critical checks weigh five times as much as low ones. A failing critical check caps the whole score at 59, because a site that tells search engines not to index it does not deserve a good score for tidy meta tags.

Use the score to track one site over time. Do not compare it across very different sites as if it were a league table.

Privacy, safety and limits

The check runs on Aback servers as AbackAuditBot. It sends ordinary GET and HEAD requests, never a cookie, a password or a form, and it never changes anything on the site.

The result is stored as a report that anyone with its link can open, and it is deleted after 30 days. Do not check addresses that carry secrets in the path or the query string.

Related tools and guides

Indexability CheckerA page can be blocked from the index in four places: the status code, a noindex directive, robots.txt and the canonical link. Check all four at once and see exactly which one is the problem.Meta Tag CheckerSee the title and description a search engine reads, how the result could look, and whether the canonical, robots, viewport and language tags are set correctly.Robots.txt CheckerCheck that robots.txt is published, parses cleanly and does not block the pages you want found. See at a glance which search engines and AI crawlers the rules allow.Sitemap CheckerCheck that your sitemap exists, parses as valid XML, is declared in robots.txt and lists urls that actually work. A broken sitemap wastes the crawl budget you give it.Structured Data CheckerStructured data tells search engines and AI assistants what a page is: an article, a product, an organisation, a set of questions. Check that your JSON-LD parses and carries the properties each type needs.Redirect CheckerFollow every redirect of an address, hop by hop. Find chains that slow crawlers down, loops that break pages, and host variants that split your signals across duplicates.Canonical CheckerThe canonical link tells search engines which url is the real one when several show the same content. Check that it exists, that it is absolute and that it points at a working page.AI Search Readiness CheckerGenerative engine optimization starts with access. Check that AI assistants can crawl your pages, receive the real content rather than a block page, and read it without running JavaScript.Guide: The technical SEO checklistA practical technical SEO checklist in the order that matters. Crawling, indexing, on-page signals, structured data, speed, AI search and security, with a way to check each item.Guide: Why your page is not on GoogleA step by step diagnosis for pages that do not appear in Google search. Status codes, robots.txt, noindex, canonical links, rendering, quality and how to ask Google to look again.

Frequently asked questions

Is this SEO checker free?

Yes. Every check is free with no account and no API key. The free tier allows ten audits an hour from one address, which is plenty for checking your own pages.

Will it tell me why my page does not rank?

It tells you whether technical problems keep the page out of the index or make it hard to understand. Ranking itself depends on relevance, quality and links, which no technical checker can measure honestly.

Does it crawl my whole site?

The checker looks at the address you enter plus the site files such as robots.txt and the sitemap. A full audit in standard mode samples up to 25 pages, and the Pro deep mode samples up to 100.

Why does the checker refuse my site?

If robots.txt disallows AbackAuditBot for the address, the check stops before reading a single page. Sites that sit behind a login or a bot challenge also cannot be checked.

How is this different from Google Search Console?

Search Console reports what Google actually did with your pages. This checker reports what any crawler would see right now, including pages Google has not visited yet. Use both.

Can I check a page on a staging server?

Only if it is publicly reachable and robots.txt does not block AbackAuditBot. Private addresses and internal networks are refused for safety.

How often can I run it?

Ten new checks an hour per client address, and a shared limit per site so that no site is crawled too often. A Pro license raises the limits sixfold.

Can I get this result as JSON?

Yes. Every result is a report with a JSON, Markdown and CSV export, and the same checks are available through the REST API and the MCP server.

↑ ↓ to move↵ to openesc to close