Free website SEO checker

Signals This Website Checker Tests

The checker reads the page response and a same-host robots.txt/sitemap location when reachable. It reports observed values and basic conditions without producing an opaque SEO score.

How to read the live technical check

This tool fetches one public URL and reports specific signals from the response it receives at that moment. A result is an observation, not an overall SEO score. Start with the exact URL you want to assess: the homepage, a service page, a city page and a blog article can have different metadata, directives and response behavior.

HTTP response and HTTPS: the response status tells you whether the requested URL was served, redirected or unavailable to this scan. A successful HTTPS fetch confirms the connection used for that request; it does not prove every asset on the page uses HTTPS or that the site has no security issue. If a page redirects, inspect its destination and ensure the final destination is the intended canonical URL.

Title, description and canonical: these values are read from the fetched HTML. A missing title or description may make the page harder to interpret in search results, but a present tag is not a ranking guarantee. A canonical tag communicates a preferred URL; it does not force a search engine to choose that version. Compare it with the page URL, internal links and sitemap entry.

Headings and images: the tool counts H1/H2 elements and identifies basic heading-level skips. It does not judge whether the headings answer the user’s question. For images, it reports whether alt attributes exist; it cannot determine whether the text accurately describes each image. Review the actual page and write concise descriptive alternatives for informative images. Decorative images should not carry redundant text.

Robots, sitemap and viewport: the scanner checks the page’s robots directives, a same-host robots.txt response, a discoverable sitemap location and whether a viewport tag appears. A sitemap helps crawlers discover URLs but does not guarantee that they will crawl or index them. A viewport tag is only a technical hint; it does not prove the mobile layout is usable.

What the checker cannot prove

This is not a Google Search Console integration. It cannot report whether Google has indexed the page, which canonical Google selected, why a URL is excluded, what keywords it ranks for or how many impressions it receives. It does not inspect Google Analytics, backlink databases, competitor rankings, Core Web Vitals, page speed from real users, accessibility, conversion tracking or a fully rendered browser experience.

It also does not crawl your whole website. One scan covers the submitted URL and limited same-host discovery checks. It will not identify every broken internal link, duplicate page, blocked resource, redirect chain, orphan page, structured-data error or performance issue on a large site. A clean result means only that the listed checks did not detect a problem in that fetch.

For Google-specific indexing evidence, verify that you control the correct Search Console property and inspect the exact URL. Review the selected canonical, crawl date, fetch result and indexing status shown by Google. Do not request re-indexing repeatedly as a substitute for fixing a technical or content problem; a request is not a guarantee of inclusion.

Official guidance: Search Console URL Inspection, robots.txt basics and Google’s sitemap guidance.

A practical way to use the results

1. Run the check on the exact public URL and note the date and response.
2. Compare the canonical, robots directives and sitemap URL with the page you intend search engines to use.
3. Inspect the page in a browser at mobile and desktop widths; the checker does not perform that visual test.
4. Fix issues in the template, content-management system or server configuration that generates the response.
5. Run the check again and confirm that the observed signal changed as expected.
6. For Google coverage, review the URL in Search Console and follow Google’s reported crawl and indexing details.

If you are responsible for a site with many URLs, use a crawl that can export the affected page list and group issues by template. Fixing one shared template may correct several pages, while a page-specific canonical or robots directive may need an individual change. Keep a record of each old and new URL when changing a site structure.

Results are returned to the browser and audit reports are not saved by this checker. The public URL is fetched server-side, so only submit a website you are authorized to assess. Local network addresses and non-standard ports are blocked, and the current browser session is limited to five scans per hour.

Website SEO Checker: Frequently Asked Questions