AAA Signal07 2802 5222Customer login
HELP CENTRE · Advanced tools

Run single-page and multi-page SEO checks

Review public HTML checks such as titles, descriptions, headings and indexing directives. The checklist is a starting point for review, not a ranking score.

Last updated 18 October 2026
WATCH THE TUTORIAL · 34 SEC

Check a page for SEO problems

A quick health check for your pages. No stethoscope needed. A short narrated walkthrough using an example report: Enter a page, Read the score, Several pages, Download it.

Read the video transcript · Watch on YouTube ↗ · All help guides

Figures and account details shown are from an example report, not customer results. Hosted by AAA Signal, so nothing loads from YouTube. Watching doesn't connect an account or change your settings.

Before you start

  • A website selected for the business and public HTTPS URLs on that website.

Set it up, step by step

  1. Open On-page SEO and enter an important page for the single-page check.
  2. Read each check and its detail before making a website change.
  3. For several pages, paste up to 10 public HTTPS addresses, one per line, in the multi-page audit form. Choose Run multi-page audit.
  4. Review available results and any pages not checked before the time limit. Put remaining pages back in the form if needed, and export the CSV.

Open On-page SEO →

In the dashboard menu: Advanced tools → On-page SEO (click Advanced tools to open that section).

How to use it

Give genuine access, canonical or accidental noindex problems priority over cosmetic checklist improvements.

Make changes in your website platform or with your developer. AAA Signal does not automatically edit or publish your website.

What the results mean

A 100-point checklist score does not measure Google rankings, Core Web Vitals or all technical SEO.

These checks inspect fetched HTML in a bounded time window. They do not crawl every page or fully render every JavaScript app.

If something goes wrong

The page cannot be checked

Confirm it is public, HTTPS, within the selected website and not blocked by access rules. Do not broadly disable site protection just for a score.

The check differs from what I see in the browser

Client-side rendering or different server responses can explain it. Ask your developer to compare the fetched HTML and rendered page.

Keep going

Still stuck? Contact support with the feature, steps and a redacted error screenshot. Never send passwords, secret keys or private report links.

Browse all help topics · Privacy · Data deletion

CallEmail