[solveflow_how_it_works]
What the scanner checks
For the page you submit, the scanner looks at the HTML the server returns and tests:
- Whether the page loads over HTTPS
- Whether the page title and meta description exist and have a sensible length
- Whether there is exactly one H1 and whether heading levels skip
- Whether images have an alt attribute
- Whether the page declares a mobile viewport, a language, and a canonical link
- Whether the page tells search engines not to index it (noindex)
- Whether links have readable text
- Whether a sample of up to 8 internal links returns 404 or server errors
How we keep scanning safe
A scanner that fetches web addresses must be careful about where it connects. SolveFlow only accepts public web addresses on the standard web ports. Every address is resolved first, and anything pointing to a private network, localhost, or other internal range is refused. Redirects are checked at every step, requests have time and size limits, and each visitor can only run a limited number of scans in a short period.
What the scanner cannot see
- Only one page is checked, not your whole website.
- Content added by JavaScript after the page loads is not visible to the scan.
- It does not test security, page speed, colour contrast, or keyboard and screen-reader use.
- It cannot predict how your page will rank in Google.
When a check cannot be completed, the report says “Not checked” instead of guessing.
How the score works
Each completed check has a weight. A passed check earns its full weight, a warning earns half, and a critical finding earns none. The score is the share of points earned out of the checks that were actually completed. Checks marked “Not checked” are not counted.