DiagnoSEO - On-Page SEO & GEO Checker extension
Security at a glance
Describes the Chrome listing; other stores are scanned separately and can score differently. Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: oeclljnmijbnekldpmhhhhfegpnlfcck
Permissions (2)
- Execute scripts in pages
Related extensions
AIO SEO Checker – Meta Tags, SEO Audit & AI SearchTools
geochecks GEO SEO AI Search CheckerTools
DiagnoSEO - On-Page SEO & GEO CheckerWeb Development
SEOWrench — SEO & GEO CheckerProductivity
SEO AI Assistant: SEO Checker, AEO & GEO AuditTools
Free SEO & AI Visibility (GEO) Checker, Site Audit – Geo AuthorityTools
Frequently asked questions
Is DiagnoSEO - On-Page SEO & GEO Checker safe to use?
Our latest automated scan rates the Chrome listing of DiagnoSEO - On-Page SEO & GEO Checker at 86/100 (low risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does DiagnoSEO - On-Page SEO & GEO Checker require?
DiagnoSEO - On-Page SEO & GEO Checker requests 2 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops DiagnoSEO - On-Page SEO & GEO Checker?
DiagnoSEO - On-Page SEO & GEO Checker is published by diagnoseocom. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.0.0
- Current listed version
- 1.0.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.