Home / Blog / IsMyCodeSafe Report: False Positives Explained
Fqalse Positives

IsMyCodeSafe Report: False Positives Explained

27 October 2026 · By John Carlsson
IsMyCodeSafe graded aiwebpageseo.com SEO E and AI Search E after reading 12 words from a 4,846-word page. It also reported compression as off when Brotli is on, called robots.txt, sitemap.xml and security.txt sensitive files, and flagged a GET search box for missing CSRF protection. Its security header, TLS and email checks were correct.

On 27 October 2026 I ran https://aiwebpageseo.com/ through IsMyCodeSafe, a website security scanner that also grades SEO, AI-generated content and AI search readiness. It gave the site an overall grade of A, "Excellent. Minimal issues found", "Low Risk". It also graded SEO E ("Bad SEO - major issues hurting visibility"), AI Risk C and AI Search E.

I am only interested in what an audit gets wrong. This post sets out each finding that does not match the site, what the site actually shows, and the proof from my own server. The full report and my live checks are saved here: IsMyCodeSafe evidence, 27 October 2026.

False positive 1: 12 words on a 4,846-word page

IsMyCodeSafe says: "Words: 12" and "Page size: 11KB", in both its SEO Analysis and its AI Search Readiness sections.

The facts: the home page is 115 KB of HTML with 4,846 visible words, checked live on my server. My server's access log shows every request for the home page during the scan window was answered with HTTP 200 and the full page. The page my server sent was not 12 words long.

The SEO grade E ("10 issues"), the AI Search grade E ("7 issues", "Poor AI citation readiness") and the AI Content grade C all appear to rest on this reading. A grade built on 12 words out of 4,846 does not describe the page.

False positive 2: "Compression: none"

IsMyCodeSafe says: "Compression: none".

The facts: when a browser says it accepts compression, my server sends the home page with Brotli compression (Content-Encoding: br). The 115 KB page goes over the network as 18.7 KB.

False positive 3: public files called "sensitive"

IsMyCodeSafe says: "3 sensitive file(s) accessible": /.well-known/security.txt, /robots.txt and /sitemap.xml, each rated Medium, under "Sensitive Files (OWASP)".

The facts: all three files are meant to be public. robots.txt tells search engines and AI crawlers which pages they may crawl. sitemap.xml lists the pages for search engines to find. security.txt is a standard (RFC 9116) that tells researchers how to report a security problem. Removing or hiding any of them would make the site worse, not safer.

The same report also shows "Sitemap:" and "Robots.txt:" with nothing after them in its SEO section, so it both found these files and failed to find them.

False positive 4: "Missing CSRF protection (AI-generated forms)"

IsMyCodeSafe says: "Missing CSRF protection (AI-generated forms)", medium, and "missing csrf token". It lists this under A07, "Identification and Authentication Failures".

The facts: the only form on the home page is the site search: `

💬 Got a problem?

aiwebpageseo.com is a data-driven SEO and AEO platform providing a free suite of technical website tools.