Questions About the Inspection
What the inspection does, what it means, and what it will not tell you. If your question is not answered here, it is probably answered on the page describing every check we run.
Using The Inspection
-
Is the inspection free?
Yes, and there is no signup. Enter a URL, get the findings.
-
How long does an inspection take?
Usually two to six seconds. QuickRankAI fetches the page, then robots.txt, then llms.txt, and sometimes sitemap.xml, and runs every check against what came back.
-
What pages can I inspect?
Any publicly reachable http or https page.
-
Do you store the URLs I check?
No. The inspection runs, the result comes back to your browser, and nothing about the target URL is written to disk.
-
Why did my inspection fail to complete?
The usual reasons are that the page blocks automated requests, sits behind a firewall or bot filter, returns something other than a 200, presents a certificate that will not verify, or is larger than the download limit.
Reading The Results
-
What does the score actually mean?
It is the share of available weight the page earned.
-
What is the difference between a quick fix and a structural issue?
A quick fix can be repaired in the tools you already have: edit the content, adjust the template, change a setting.
-
Why do investigate findings get half credit?
Because an unproven signal is not the same as a proven failure.
-
I scored well and still get no traffic. What now?
A good score means the page is readable, reachable, and clearly labeled.
-
Does a clean result mean my whole site is healthy?
No, and the tool says so on every result.
What We Check
-
Do you run the page JavaScript?
No, and that is deliberate. QuickRankAI reads the raw HTML response, because that is what most AI retrievers read.
-
Is this a page speed test?
No. QuickRankAI measures one thing about performance: how long the server took to answer.
-
Do you check backlinks, rankings, or keywords?
No. Those require data from outside the page, and this is an inspection of what one public URL shows the world.
-
How is this different from the AISymantix checker?
They answer different questions. AISymantix asks whether AI systems can understand, retrieve, and trust a page, and it is built around semantic and entity architecture.
-
Why does my platform cause so many of these findings?
Because most findings live in the template, and on a hosted platform you did not write the template.
What Happens Next
-
Do I have to buy something to use the findings?
No. Every finding includes the evidence and the repair.
-
When is a rebuild actually justified?
When the same problems keep coming back after you fix them, when the content only exists after JavaScript runs, when the response is overwhelmingly script, or when the template fights every repair you attempt.
-
Can you fix it for me?
The findings are written so you can act on them without help.