SEO Checker & Site Analyzer: On-Page Audit, Meta Tags & Broken Links extension
Security at a glance
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: bbgolfhloahnoeokgbhfopoeggmehdbi
Permissions (8)
- Execute scripts in pages
- View open tabs
Related extensions
SEO Meta Tags Analyzer - SEO Checker ProDeveloper
On Page SEO Checker & AnalyzerMake Chrome Yours
SEO Checker — Free On-Page SEO Audit ToolDeveloper
On Page SEO AuditorProductivity
SEO Checker & Meta Tag Analyzer + 110 Free Tools | CreativismDeveloper
SEO Audit & AI SEO Checker — Free On-Page SEO AnalyzerDeveloper
Frequently asked questions
Is SEO Checker & Site Analyzer: On-Page Audit, Meta Tags & Broken Links safe to use?
Our latest automated scan rates the Chrome listing of SEO Checker & Site Analyzer: On-Page Audit, Meta Tags & Broken Links at 73/100 (some 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 SEO Checker & Site Analyzer: On-Page Audit, Meta Tags & Broken Links require?
SEO Checker & Site Analyzer: On-Page Audit, Meta Tags & Broken Links requests 8 permissions. The most significant: Execute scripts in pages, View open tabs. See the full breakdown in the security report.
Who develops SEO Checker & Site Analyzer: On-Page Audit, Meta Tags & Broken Links?
Check the developer line on the store listing before installing — impersonators copy popular extension names.
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: 2 critical and 4 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.