On-Page SEO Audit Generator

About thirty checks, one weighted score, and a direct link to the tool that fixes whatever fails.

View the page source in your browser (Ctrl+U or ⌘+U) and paste the whole thing. Nothing is uploaded.

out of 100

0Passed
0Warnings
0Failed
0Critical

Fix these first

    Full audit

    Runs in your browser. The HTML you paste is parsed in this tab with the browser's own DOMParser, which builds an inert document — scripts in your markup never run and nothing is requested from the pages it references. That means you can safely audit a staging site, a client page behind a login, or an unpublished draft.

    What the on-Page SEO Audit Generator does

    This is the hub of our SEO tools. It runs about thirty on-page checks against a page's HTML, produces a weighted score, and links each failing check to the specific tool that fixes it.

    The checks are grouped the way you would work through them. Titles and meta covers the title tag and its pixel width, the meta description, canonical, robots directives, encoding, viewport and language. Headings checks the H1, the outline for skipped levels, and empty headings. Content looks at word count, average sentence length and whether the text is in real paragraphs. Keyword placement — enabled when you supply a target phrase — checks the title, H1, opening paragraph and subheadings, and flags density above 4%. Images covers alt attributes, declared dimensions and filenames. Links covers anchor text, broken and empty anchors, and internal linking. Structured data checks JSON-LD validity and the four core Open Graph tags.

    The score is weighted rather than a simple pass count. A missing viewport tag, a noindex on a page you want indexed, or a missing H1 count triple; a slightly short meta description counts once. Warnings score half. That means the number reflects how much is genuinely wrong rather than how many boxes are unticked, and the Fix these first panel orders failures by weight so you start where it matters.

    What this cannot check is anything requiring a request: server response codes, page speed, whether external links resolve, whether the page is actually indexed, or how it ranks. Those need a crawler or Search Console. This covers the on-page half, which is the half you control directly and can fix today.

    How to use it

    1. Open the page you want to audit and view its source, then paste the whole thing in.
    2. Add your target keyword to enable the placement checks.
    3. Work through Fix these first — those are the failures weighted as most damaging.
    4. Follow the tool link beside each item, fix it, then paste the updated HTML back in and watch the score move.

    A worked example

    A page scoring 68/100 reports:

    Fix these first
    ✗ Viewport                 Missing — the page will not be mobile-friendly.
    ✗ Exactly one H1           No H1 on the page.
    ✗ Alt text                 3 of 5 images have no alt attribute.
    ✗ No broken anchors        2 anchors with a missing, empty or placeholder href.
    
    Warnings
    ! Title fits in results    612px against a 580px budget — it will be truncated.
    ! Canonical tag            No canonical. Add a self-referencing one.
    ! Open Graph tags          Missing: og:image, og:url

    The order matters. Adding a viewport meta tag is one line and worth three points of weight, because without it the page fails mobile usability entirely. Trimming the title is worth one. Both are quick, but doing them in the wrong order means spending your afternoon on the smaller problem.

    Fix the four failures and the same page scores 88. That is the value of a weighted score over a checklist: it tells you not just what is wrong but what to do first.

    Frequently asked questions

    Why does it need pasted HTML rather than a URL?

    Browsers block cross-origin requests, so a page cannot fetch another site's HTML. A tool claiming to audit a URL from the browser is routing it through a server. Pasting keeps everything local and also lets you audit staging sites, pages behind a login and local builds.

    How is the score calculated?

    Each check carries a weight of 1 to 3 depending on how much it matters. A pass scores full weight, a warning half, a failure nothing. The total is expressed out of 100. A missing viewport or a noindex costs three times as much as a slightly short meta description.

    What does this audit not cover?

    Anything needing a network request: HTTP status codes, redirects, page speed, whether external links are alive, whether the page is indexed, and how it ranks. Use Search Console and a server-side crawler for those. This covers on-page factors, which is the part you control directly.

    Is a score of 100 the goal?

    No. Some checks will not apply to your page — a page with no images cannot pass the alt-text check meaningfully, and forcing a keyword into a subheading to gain a point makes the page worse. Use the score to find real problems, then stop.