Skip to content

On-page inspection

Free SEO analyzer and auditor

Check one page’s titles, headings, metadata, image alternatives and indexing directives. See the source evidence behind each finding.

Use the SEO analyzer & auditor

Your input

SEO analyzer & auditor inputs

Use a publicly accessible page. We inspect its original HTML.

No account required. Fair-use limits apply. This check analyses the input you provide.

Check the details. Then check the answers.

See when AI names your brand and which pages it cites in a free visibility report.

Get your free report

Find issues in one page’s HTML

  1. Choose the page to inspect

    Enter a public page URL. Use the exact page you plan to edit, rather than the homepage for an unrelated article.

  2. Review the on-page checks

    Inspect titles, descriptions, heading order, canonical declarations, image alt attributes, language and indexing directives.

  3. Turn findings into page edits

    Read the observed evidence and suggested fix together. Update the relevant page elements, then run the check again.

One HTML response is inspected. Scripts, link destinations, site-wide issues and rankings are outside this check.

Start with the response

What the single-page SEO audit checks

Enter a public URL to inspect its title, description, headings, canonical declarations, image alt attributes and indexing directives. The report places recommendations beside the source evidence so you can discuss each finding with an editor or developer.

Start with details that change the page’s meaning or intended availability: a missing title, an unexpected canonical or an unintended noindex. Then review the heading outline, language and image alternatives in context.

Example

Read the head, the hierarchy and the page body together

Move through the parts of a page the audit checks: head metadata, heading structure, image alt attributes and document language.

Title, description and canonical declaration

Read the subject, summary and preferred URL together. Check that they describe the page you intend to publish.

A practical workflow

How to use the SEO analyzer & auditor

  • Submit a public HTML URL

    Use the exact page address. The tool follows a bounded redirect chain and records the final response it inspected.

  • Prioritize by consequence

    Investigate missing titles and unintended noindex directives before polishing length guidelines. Read each recommendation against the page’s intended role.

  • Recheck after deployment

    Run the same URL after changes are live. Export the findings for your handoff, and use separate tools for performance, link status and index verification.

Inside the document

Three layers of an on-page review

Follow the title, headings and indexing declarations that deserve a closer HTML review.

Check the title and description together.

Use one descriptive title and a summary that accurately represents the page. Length findings are editorial prompts, not search-engine display guarantees.

Example document headExample
  1. Title<title>Container Gardening Guide</title>
  2. Description<meta name="description" content="Plan a small container garden.">
  3. ReviewOne clear topic, consistent wording

Google may select different title or snippet text.

Interpret the checks

A detected attribute is a starting point.

The image check distinguishes missing alt attributes from empty ones. Empty alt text can be appropriate for decorative images; the tool cannot decide whether the image communicates essential information. The language check observes a declaration but does not translate or verify the full page.

The canonical check counts declarations and exposes their resolved addresses. It does not fetch the canonical destination or prove that a search engine accepts that choice. Likewise, absence of noindex is not evidence that the page has entered an index.

Keep the scope clear

A page audit is one part of an SEO review.

The report uses initial HTML without executing JavaScript. Content injected in the browser may differ. Title length uses a 30–60 character guide; the description check uses 70–170. Neither range is a ranking threshold, and search-result layouts can show a different amount of text.

This tool does not test broken links, crawl neighboring pages, measure Core Web Vitals, inspect backlinks or check rankings. Use the sitemap checker for the document’s URL inventory and the robots checker for crawl policy; treat those as separate questions with separate evidence.

SEO title checker

Check title length, clarity and keyword placement before you publish.

Robots.txt checker

Test fetched or pasted robots rules against a specific URL and inspect the matching lines.

Sitemap checker

Check sitemap XML, find duplicate locations and download the parsed inventory.

Questions, answered

SEO analyzer & auditor: your questions answered

A closer look at the inputs, method and next steps.

sourcesignal.ai● ONLINE
Pick a question and I’ll explain how this tool works.

Is this a full website crawl?

No. Each run inspects one public HTML response. Links may appear in the parsed source, but their destinations are not fetched and the rest of the site is not audited.

Does it find broken links?

No. This analyzer does not request link destinations or report their HTTP status. Test suspected broken links separately rather than interpreting their presence in HTML as a successful destination check.

Does it measure page speed or Core Web Vitals?

No. It does not run a browser, execute scripts or collect field performance data. Use a performance measurement tool for loading, responsiveness and layout stability.

Will every warning hurt my rankings?

No. Warnings flag an observation for review. A title outside a suggested range or a skipped heading level needs context; the tool cannot assign a ranking impact to the finding.

Can it tell whether Google indexed the page?

No. It reports observed indexing directives, not index membership. A page without noindex can still be absent from search for reasons this inspection does not measure.

Why does the report differ from my browser?

The tool reads source HTML, not the rendered DOM. JavaScript, cookies, personalization, browser CSS and bot-specific responses can change what a visitor sees.

Can I keep the audit for a developer?

Yes. Copy the findings or export text and JSON. Include the exact URL and timestamp so the developer knows which response and deployment the report describes.

Navigate the AI landscape. Place your brand on the map.

See when AI names your brand, which competitors appear, and the pages those answers cite. Turn what you find into a practical next step.

Five AI engines. No card required.