Website SEO Checker

Enter a URL to score ten groups of on-page signals, read every finding with the reason behind it, and export the whole report as Markdown or JSON.

Ten scored groups covering everything from the title tag to the sitemap response.

Only the finished report travels back, so one audit costs a few kilobytes rather than a page.

  • Around forty checks in one report.
  • Heading outline and link issues listed.
  • Markdown and JSON export included.

How to run an on-page SEO audit

Enter the URL, read the scored sections, work down the findings, then export the report.

  1. 1

    Enter the page URL

    Audit the exact page you care about rather than only the home page, because titles, headings, canonical values, and structured data are all per page. Leave the robots and sitemap option on to confirm the URL is actually crawlable.

  2. 2

    Read the section scores

    Ten groups are scored separately, so a page can be strong on meta and weak on structured data without one hiding the other. The bar chart makes the weakest group obvious before you read a single individual finding.

  3. 3

    Work through the findings

    Filter to errors first, then warnings. Every row names the signal, states what was found, and explains the consequence, which is usually enough to turn a finding straight into a change without looking anything else up.

  4. 4

    Check the page details and export

    The details panel holds the full heading outline, every tag value, image statistics with the sources missing alt text, and the link issues. Export as Markdown for a ticket or JSON when the audit feeds a spreadsheet or a script.

Ten scored sections

Title and meta, indexability, headings, content, images, links, structured data, social tags, technical health, and crawlability each get their own score and weighting.

Full heading outline

Every heading is listed in document order and indented by level, so a missing H1 or a jump from H2 straight to H4 is visible rather than merely reported.

Image and link auditing

Missing alt attributes are listed with their sources, alongside counts for decorative alt text, absent dimensions, lazy loading, generic anchors, and unsafe new-tab links.

Indexability and crawlability

Robots meta, X-Robots-Tag, canonical, HTTP status, robots.txt rules for this exact path, and a live sitemap response are all resolved into one clear verdict.

Single request per audit

Images and outbound links are never downloaded, so a complete report costs one page fetch plus an optional robots.txt read and a headers-only sitemap check.

Markdown and JSON export

Copy the audit as Markdown for a ticket or a client email, download it as a file, or take the JSON when the findings feed a spreadsheet, a dashboard, or a script.

Website SEO Checker privacy and processing

These notes cover which server retrieves the page, how many requests one audit costs, how long a report stays cached, and what survives once the tab is closed.

One fetch, report returned

A Rune server retrieves the page once, optionally reads robots.txt and confirms a sitemap responds, then runs every check and returns only the finished report. The page HTML is never sent to your browser, which keeps a full audit down to a few kilobytes.

No stored audits

Reports live in the open tab and in a short shared fetch cache that expires on its own. No audited URL is written to an account, a profile, or a history list anyone can browse.

Website SEO Checker account access

Running an audit, reading every section, and exporting the report as Markdown or JSON all work without an account and without any sign-in step.

Before You Use Website SEO Checker

This is a single-page markup audit, which is a useful slice of SEO rather than the whole picture.

Scope

One page is audited per run, so a site-wide problem needs several representative templates checked.

Rankings also depend on links, authority, competition, and intent, none of which any markup audit can measure.

Rendering

The audit reads the server response, which is what crawlers see before any JavaScript runs.

Content injected on the client will show as missing here, and that gap is itself worth knowing about.

Judgement

Thresholds such as title length or word count are conventions, not rules any search engine publishes.

A deliberate short title on a strong page beats a padded one written only to satisfy a checker.

Access

Pages behind a login, a firewall, or aggressive bot protection cannot be retrieved for auditing.

A page that blocks this audit often blocks search crawlers too, which is worth investigating on its own.

Limits

Website SEO Checker reads one page per audit up to 1.5 MB of HTML, and it never downloads the images or outbound links it reports on, so every finding comes from markup already retrieved.

Audits are rate limited per address and each result is cached for thirty minutes, so checking the same URL again returns the earlier report without a second fetch.

Questions about Website SEO Checker

What does this audit actually cover?

Around forty checks across ten groups: title and meta tags, indexability directives, heading structure, content depth, image accessibility, link quality, structured data, social tags, technical health, and whether robots.txt and a sitemap allow the page to be found.

Why does the audit need a server request?

Browsers block reading another site's HTML across origins, which is a security rule no page can opt out of. One server request works around it, and because the analysis happens there too, only a small report travels back to you.

Does the checker download my images to test them?

No. Image findings come from the markup already retrieved, covering alt attributes, declared dimensions, lazy loading, and file format. Nothing about an image is fetched, which keeps one audit to a single page request.

What score should I be aiming for?

Treat the score as a summary rather than a target. Clearing every error and understanding each warning matters far more than the number, and a page with one deliberate warning can easily outrank a page scoring one hundred.

How many requests does one audit make?

One for the page itself, plus a robots.txt read and a headers-only sitemap check when that option is left on. Images and outbound links are judged from the markup already retrieved, so nothing else is ever downloaded.

Is the URL I audit stored anywhere?

A report is held in a short server cache so that repeating the same check is instant, and it clears itself after thirty minutes. Nothing is attached to an account, a profile, or a history list you or anyone else can browse.

4.7 (351 ratings)