On-page SEO audit
Enter a page and this tool reads its HTML, then reports on the title and meta tags, heading structure, image alt text, links, structured data, and whether robots.txt points to a sitemap. Each finding says what’s wrong in plain words.
It’s for makers who want a quick second opinion on a page before or after launch, without learning a full SEO suite. It audits one page at a time, so start with the page you most want people to find.
Free with a ShipScroll account.
How to use the On-Page SEO Audit
- Enter the address of the page, not just your domain, if it’s an inner page you care about.
- Press Audit page and wait a few seconds.
- Fix red items first: they can keep a page out of results or leave it with no title.
- Work through the amber items, then run the audit again. Results are kept for ten minutes.
What the audit covers
| Area | What we look at | Why it matters |
|---|---|---|
| Title and meta tags | Title, description, canonical, robots, share tags | How the page appears in results and when shared |
| Headings | One clear H1, levels in order, no empty headings | How readers and machines follow the page |
| Structured data | JSON-LD that parses, with types listed | Helps machines tell what the page is |
| Content in the HTML | Word count before any JavaScript runs | Content added only by scripts can be missed |
| Images | Images with no alt attribute | Screen readers and image search rely on it |
| Site files | robots.txt and a listed sitemap | How crawlers discover your pages |
Why there’s no overall score
A single number looks tidy, but it hides what to do and rewards fixing easy things over important ones. A page with a perfect score can still be blocked by a noindex tag if the weighting is off. So this audit gives you a list in order of severity instead.
What an on-page audit can’t tell you
This checks whether a page is technically sound. It can’t tell you whether the content answers what people are searching for, how strong your competitors are, or how many sites link to you. Those usually decide rankings once the basics are right, so treat a clean audit as a starting point.
Example: the page that’s almost empty
A product page looks full in your browser, but the audit reports 12 words in the HTML. That means nearly everything is drawn by JavaScript after loading. Google can often render scripts, but other crawlers may not, and you’re relying on that step going well. If you see this, turn on server rendering for your key pages.
Questions
How is this different from the Meta Tags Checker?
The Meta Tags Checker goes deep on one thing and lists every tag’s value. This audit looks wider, across headings, images, links, schema and site files, so it’s the better first check. Use the focused tools to dig into whatever it flags.
Can it audit my whole website?
No, it reads one page at a time. Tags and content differ between pages, so check your most important ones individually: usually the home page, pricing and your top landing page.
Why does it say my page has few words when it looks long?
The tool counts text in the HTML your server sends, before scripts run. A low count on a long-looking page means JavaScript adds the content in the browser. Server rendering puts it in the HTML, where every crawler can read it.
Will fixing everything here improve my rankings?
It removes obstacles, but there’s no guarantee. These checks make sure search engines can read and present your page properly. Whether it ranks then depends mostly on how well it answers the search and how much other sites trust it.
Related tools
- Meta Tags CheckerSee the title, description, canonical and share tags a page actually serves.
- Heading AnalyzerOutline a page’s H1 to H6 headings and spot missing, repeated or skipped levels.
- Schema Markup CheckerExtract a page’s JSON-LD, list its schema.org types, and catch syntax errors.