On-Page SEO Source Auditor
Paste rendered or raw HTML to inspect titles, descriptions, headings, canonical links, image alt text and index directives.
Paste HTML source or rendered HTML to run a lightweight on-page inspection. The tool does not fetch a URL; this avoids misleading results from browser access restrictions and makes the inspected source explicit.
What this audit can and cannot tell you
It can count title and description tags, headings, canonical links, robots directives, images missing alt attributes, and links with empty labels. It cannot determine whether your content is useful, whether external links are trustworthy, whether JavaScript renders correctly for crawlers, or whether Google has indexed the page.
A practical note on On-Page SEO Source Auditor
The question worth answering: This page is most useful when you focus on treating source checks as diagnostics rather than rankings. Reviewing headings, canonical tags, descriptions and basic HTML signals on a page. Start by recording the input source, the date or period covered, and any assumption you had to supply yourself. That makes the result easier to reproduce and helps another person understand what the output actually says.
How to use the result responsibly
Read the output alongside the inputs rather than as a stand-alone verdict. Change one assumption at a time and observe whether the conclusion changes materially. If the tool accepts a range, test more than one plausible case; if it accepts a file or pasted data, preserve an untouched copy of the original. Where the result will support a published claim or an important decision, keep a brief record of the method and source date.
A mistake specific to this kind of task
A page can pass basic on-page checks yet remain unhelpful, inaccessible, slow or ineligible for a particular query. This is why the output should be described as an estimate, diagnostic or comparison where appropriate—not as a guarantee. Avoid mixing currencies, periods, definitions or data sources merely because their labels look similar.
Independent check before acting
Manually inspect rendered content, mobile usability, internal links and indexability; validate important structured data separately. If the result conflicts with a statement, official record, provider terms or the original dataset, investigate the difference before relying on it. The tool is intended to make a task clearer, not to replace the source system or professional advice when the consequences are material.
Reader takeaway: Keep the assumptions visible, verify the underlying evidence and use this result as one part of a reasoned decision.