How to run an on-page SEO check
- Open the page in your browser, view its source (Ctrl+U on Windows and Linux, Cmd+Option+U on a Mac), select all and copy.
- Paste it into the box. Optionally add the page URL so links can be split into internal and external.
- Review the score and the checklist: title, meta description, canonical, robots meta, H1, heading order, image alt text, language, mobile viewport, Open Graph tags, structured data, word count and links.
- Fix the errors (✗) first, then the warnings (!), and paste the updated HTML to confirm.
What the audit covers
These are the on-page basics that search engines and social platforms read directly from your HTML. A missing or duplicated title, an accidental noindex, a canonical pointing at the wrong URL or a page without an H1 are among the most common reasons a page underperforms, and they are easy to fix once spotted. Image alt text matters for accessibility and image search, the viewport tag for mobile-first indexing, and structured data for rich results. Links without anchor text, often icon or image links without alt, give search engines and screen readers nothing to go on.
Because the tool reads pasted source, it works for pages behind a login, on staging servers or on your own computer, where online crawlers cannot reach. It checks the HTML you paste; content that is only added later by JavaScript will not be included, so for single-page apps paste the rendered HTML from DevTools (Elements panel, copy outerHTML of <html>).
The score is a simple checklist ratio, not a ranking prediction. The audit runs in your browser and your HTML is not uploaded.
Why is my score high but the page still does not rank?
On-page basics are only part of SEO. Content quality, search intent, links from other sites, site speed and competition matter at least as much.
Is word count a ranking factor?
Not directly. Very short pages often fail to answer a query fully, which is why the tool warns under 300 words, but length for its own sake does not help.
Does it check page speed?
No. Use Google PageSpeed Insights or Lighthouse in Chrome DevTools for performance and Core Web Vitals.