Frequently Asked Questions
Why does the audit ask for a verification code?
Each audit makes our server fetch a page on your behalf. The verification code keeps automated scripts from abusing that, which keeps the tool fast and free for everyone.
Does it check JavaScript-rendered content?
No. The audit reads the HTML exactly as the server delivers it, which matches how most crawlers first see your page. For WordPress, Wix, Squarespace, and most business sites that is the complete picture. If your site is a single-page app that builds its content in the browser, some checks (word count, headings) may come back empty.
What is a good score?
Treat anything below a pass on the Indexability category as urgent regardless of the overall number. Beyond that, most healthy pages land in the 80s and 90s. Chasing 100 is rarely worth it. Fix the reds, look at the yellows, and move on.
Why does my page score differently from other SEO tools?
Every tool picks its own checks and weights. Ours are deliberately conservative and deterministic: the same page always gets the same score, each rule is disclosed in its result row, and nothing is scored on judgment calls like "content quality". Use the score to track your own page over time, not to compare against other tools.
Is the URL I submit stored?
No. We fetch the page, run the checks, return the report, and discard the HTML. There is no audit history.
Does the audit measure page speed?
It measures server response time, meaning how long the HTML takes to arrive, since that is what every other speed metric builds on. It does not run a full lab test with scripts, images, and rendering. For that, use Google PageSpeed Insights alongside this audit.