Troubleshooting
Clear reasons and practical next steps.
A scan is queued
The separate Node worker must be running. Start the app with npm run dev or npm start; both start the web server and worker. Queued runs survive a restart.
A score is unavailable
Open the report’s measurement notice. A browser or Lighthouse failure reports its actual error. The remaining collected findings are preserved. Run again to retry; a missing measurement is never presented as a zero score.
A URL redirects outside scope
Use the final canonical origin, including the correct www or non-www version. Off-origin navigation is blocked so an audit cannot silently expand its authorized scope.
Robots.txt blocks the scan
Review your site’s crawl policy. SiteRadar does not bypass robots rules, login walls, CAPTCHAs, or access protection.
No keyword position appears
Connect SerpApi, save at least one keyword, and run again. Check the provider’s credits and any per-query error in the Keywords view. A website being indexable does not guarantee it appears in a returned result set.