Our scanner gave our site 50/100. It was looking at a different page.
We ran MySiteSure against our own site during private testing. The finished report scored it 50/100 and flagged noindex, among other findings.
The screenshot was our access-request page. In my logged-in browser, the same URL opened the product.
The scanner didn't have the preview cookie, so our gate sent it to the public request page. That page deliberately had noindex. The finding was real, but it wasn't a verdict on the product page I had in mind. Removing noindex would have ‘fixed’ something we wanted to keep.
I'm building MySiteSure to help website owners review issues and hand a fix brief to their coding assistant. This was a useful reminder to check the report's screenshot and destination page before acting on the score.
My takeaway: compare the page the checker actually received with the one you meant to test, especially around login and preview gates.
Have you had a check report a real problem on the wrong page? What gave it away?
Replies
I have a rule in my own setup that a 200 response doesn't count as checked. Something has to look at the actual page before anything gets called done. Your noindex story shows exactly why. Pulling it would've broken the page you meant to keep that way.