Free Technical SEO Tools

Separate indexation signals from the index

A page can be blocked and still look fine in your browser. The indexability checker and the Google index checker read status, robots.txt, noindex, X-Robots-Tag, canonicals, and redirects on the URL you paste. They do not ask Google whether that URL is in the index. URL Inspection does. Use these tools to find a technical block, then confirm in Search Console.

Schema is the same split. The schema checker extracts JSON-LD and Microdata from the HTML, or validates JSON-LD you paste. Errors are the rows to fix first: invalid JSON, a missing @type, a missing @context. Warnings are recommended fields. Valid markup does not guarantee a rich result. Google's Rich Results Test is the eligibility check. This checker does not parse RDFa.

SSL and security headers are configuration, not content. The SSL checker reports issuer, expiry, days remaining, TLS version, and SAN names for the host. The security headers checker grades a short list of response headers and offers snippets you still have to install yourself. Neither tool changes your server. The mixed content checker lists http subresources on one HTTPS page: scripts and stylesheets browsers block, images and media they warn on, and plain http links that are not mixed content. It reads server HTML, not scripts that inject tags later.

Order for a URL that dropped out of results: status code, robots.txt, noindex and X-Robots-Tag, then canonical, then schema only if the URL is fetchable and indexable. A schema error on a noindexed URL is not the first ticket. HTTPS and security headers matter when the browser or the host is warning, not when the title tag is the thing you came to fix. Hreflang for a single URL lives with the on-page checker. This category is the block-or-allow layer.

Bulk checks exist because one URL is rarely the whole incident. The meta robots checker takes up to 50 URLs when you suspect a template stamped noindex across a section. The single-URL indexability checker is the place to read the full set of signals once you know which URL is the example. WordPress tools in this group read the public REST API. They do not need a plugin, and they only see what that API exposes to anonymous requests.