SiteCare – Search Engine Visibility Security & Risk Analysis

wordpress.org/plugins/discourage-search-engines-notifier

One forgotten setting can hide your site from Google. A red/green eye shows visibility at a glance, plus a one-click fix and instant email alerts.

200 active installs v2.9.5 PHP 5.6+ WP 3.5+ Updated Jul 21, 2026
developerdevelopmentnotifierseotool
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is SiteCare – Search Engine Visibility Safe to Use in 2026?

Generally Safe

Score 100/100

SiteCare – Search Engine Visibility has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1mo ago
Risk Assessment

The "discourage-search-engines-notifier" plugin v2.6.0 presents a generally positive security posture based on the provided static analysis. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code signals indicate no dangerous functions, no raw SQL queries, no file operations, and no external HTTP requests, which are all strong indicators of secure coding practices. The fact that all SQL queries utilize prepared statements is also a major strength.

However, a significant concern arises from the output escaping. With 1 total output and 0% properly escaped, any data displayed to users or browsers could potentially be vulnerable to cross-site scripting (XSS) attacks. The lack of any identified taint flows or vulnerabilities in its history is reassuring, suggesting the plugin hasn't had publicly known security flaws. Despite this positive history, the unescaped output is a concrete, actionable risk that needs immediate attention.

In conclusion, while the plugin benefits from a minimal attack surface and adherence to secure coding for database interactions, the critical flaw in output escaping poses a significant risk. The absence of historical vulnerabilities is a good sign, but it does not negate the present danger of unescaped output. Addressing the output escaping is paramount to improving its security.

Key Concerns

  • Unescaped output
Vulnerabilities
None known

SiteCare – Search Engine Visibility Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

SiteCare – Search Engine Visibility Release Timeline

v2.9.5Current
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.6
v2.8.5
v2.8.4
v2.8.3
v2.8.2
v2.8.1
v2.8.0
v2.7.0
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.0
v2.1
Code Analysis
Analyzed Mar 16, 2026

SiteCare – Search Engine Visibility Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
1
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

0% escaped1 total outputs
Attack Surface

SiteCare – Search Engine Visibility Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionadmin_bar_menudiscourage-search-engines-notifier.php:47
Maintenance & Trust

SiteCare – Search Engine Visibility Maintenance & Trust

Maintenance Signals

WordPress version tested7.0.2
Last updatedJul 21, 2026
PHP min version5.6
Downloads7K

Community Trust

Rating100/100
Number of ratings4
Active installs200
Developer Profile

SiteCare – Search Engine Visibility Developer Profile

SiteCare

2 plugins · 220 total installs

94
trust score
Avg Security Score
100/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect SiteCare – Search Engine Visibility

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
ab-icon
FAQ

Frequently Asked Questions about SiteCare – Search Engine Visibility