Skip to content
Docs

What "a check did not run" means

When the audit path that ran cannot assess a check, RankX AI marks it Not checked, not passed. It leaves the score alone; run the path that can assess it.

A RankX AI Website Audit runs on one of three paths, and each path can assess its own set of checks. When the path that ran cannot assess a check, the report marks it Not checked: not a pass, not a failure, and no effect on the score.

That makes every green result on the report trustworthy. "Canonical tags are present" means the canonical check ran and passed, never that it was skipped.

What are the three audit paths?

The full crawl, the instant page check and sitemap analysis are three different instruments, and each one answers different checks.

PathWhat it isWhat it serves
Full crawlFetches pages and reads a summary of the whole siteEvery Full Site Scan, every scheduled audit and the quick check
Instant page checkRuns a browser on the pages you name, with markup validationThe Specific Pages check only
Sitemap analysisCompares your sitemap against what was foundThe sitemap checks, and nothing else

The crawl reads what a plain fetch returns. The instant page check renders the page, so it sees things that only exist once a browser has run the page's scripts. Sitemap analysis is not a page fetch at all.

Why can one path assess a check that another cannot?

Each check needs a particular kind of data, and only some paths collect it. There are three cases.

Site-wide checks need the crawl. Whether a sitemap exists, whether robots.txt exists, whether your 404 page behaves and whether your certificate is expiring all need a summary of the whole site. The instant page check looks at pages rather than at a site, so these are crawl-only.

Rendering checks need the browser. Layout shift is the clearest example. A plain crawl reports a layout shift of zero whether or not the real page shifts, because the page was never rendered.

Reporting "layout shift is fine" from that number would claim a pass nobody measured, so a crawl leaves it Not checked.

Three checks have no path. Duplicate content, HSTS and HTTP URLs in the sitemap stay in the list as not assessed on any path, because no audit path returns data for them. They always show as Not checked, so the list stays complete and a gap is never mistaken for a pass.

How should I read a Not checked list?

Read it as the questions this audit did not answer. It is not a list of problems on your site.

It usually has one cause. A long Not checked list after a Full Site Scan is normally the checks that need a browser. A long list after a Specific Pages check is normally the site-wide checks that need a crawl.

The remedy is a different audit, not a fix. If a check you care about shows Not checked, run the path that can assess it: Specific Pages for rendering checks, a Full Site Scan for site-wide ones.

Do not present it as coverage. In a client report, a Not checked row means "we did not look". Presenting it as anything else is exactly what this design prevents.

Where else does RankX AI apply the same rule?

The same rule runs through the whole product, and knowing it makes the rest of RankX AI easier to read.

  • AI Readiness withholds a score below a coverage floor, and never shows one without its coverage fraction.
  • AI Visibility divides rates by checks with a known verdict, and shows a blank rather than 0% when none has one.
  • Traffic shows no figure at all while a Google connection is in any state but ready.

The one sentence behind all four: RankX AI separates "we did not measure this" from "we measured this and found nothing", and never shows the first as the second. See null is not zero.

Where can I see which path assesses each check?

The issue reference lists every check with the paths that can assess it. It is generated from the product's own issue list, so it cannot claim coverage the audit does not have.

Where to go next

Questions

Does Not checked lower my audit score?

No. A Not checked row moves the score in neither direction and is counted separately from issues, warnings and passes, so the gap stays visible.

How do I get a verdict for a check marked Not checked?

Run the audit path that can assess it: a Specific Pages check for checks that need a browser, such as layout shift, or a Full Site Scan for site-wide checks such as your sitemap and robots.txt.

Is Not checked the same as not assessed?

Yes. Not checked is the label in the audit report, and the issue reference and the MCP tools call the same state not assessed.

Last updated

Cookie settings

Choose which cookies we can use. You can change this at any time from “Cookie settings” in the footer.

Essential

Security, bot protection and remembering your choice. The site needs them to run, and they do not identify you. Always on.

Google Analytics cookies that tell us which pages are read and which links are followed, so we can improve them. Off until you switch it on.

Tells advertisers when their advert led to your visit. Includes the Meta (Facebook) pixel and the LinkedIn Insight Tag, which set cookies on this domain (LinkedIn also on linkedin.com) and can be told if you later start a trial.

More in the cookie policy and the privacy policy.