| 开发者 | contentguardpro |
|---|---|
| 更新时间 | 2026年4月30日 22:24 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9.4 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp_posts, including:
display:none, visibility:hidden, opacity:0, off-screen positioning, and tiny or hidden elementsjavascript: links, and suspicious inline event handlerseval(), fromCharCode(), atob(), Base64 payloads, and large data: URIswp_posts content, including posts, pages, custom post types, titles, excerpts, and Gutenberg blockswp_posts, wp_postmeta, and selected wp_options dataThe free WordPress.org version includes Quick Scan for wp_posts. That covers posts, pages, custom post types, post titles, post excerpts, post content, and Gutenberg block content stored in WordPress.
It also includes single-post scanning in the Block Editor and Classic Editor, unlimited manual scans, all findings visible, confidence scores, admin alerts, 30-day scan history, and allowlist/denylist controls.
No. The free version shows all findings detected by the included Quick Scan. Detection quality is not reduced in the free plugin.
Standard Scan adds deeper database scanning for wp_postmeta and selected wp_options data. This helps find malware and SEO spam hidden outside the main post content, including serialized data and Elementor data stored in postmeta.
Standard Scan is available in Premium.
Run a Content Guard Pro Quick Scan first. When files are clean but Google still shows hacked content, the spam often lives in the WordPress database: posts, pages, block markup, postmeta, widgets, or selected options. Quick Scan checks posts and Gutenberg blocks. Standard Scan adds postmeta and selected options for deeper database coverage.
Yes. Content Guard Pro is built to detect hidden links, cloaked text, spam keywords, suspicious redirects, malicious scripts, and iframes stored in WordPress content.
Yes. Japanese keyword hack cleanup often requires checking database content, not only files. Content Guard Pro can detect spam patterns when they appear in posts, pages, titles, excerpts, and Gutenberg content. Standard Scan extends coverage into postmeta and selected options.
Yes. Pharma spam often hides drug-name keywords and outbound links inside existing posts, sometimes using CSS tricks such as display:none, tiny text, off-screen positioning, or hidden containers. Content Guard Pro scans for those patterns in supported database fields.
Yes. Content Guard Pro is Gutenberg-aware and scans block content stored in post_content.
Yes. Content Guard Pro supports single-post scanning in the Classic Editor and Block Editor.
The free Quick Scan checks rendered post content stored in wp_posts. Premium Standard Scan adds deeper postmeta scanning, including Elementor data stored in postmeta.
No. Content Guard Pro is review-first and non-destructive. The free version helps you find issues and edit affected content manually. Premium adds non-destructive quarantine, which neutralizes risky content without deleting the original database content.
No. Content Guard Pro is a database-first malware and SEO spam scanner. Use it alongside file scanners, firewalls, login protection, backups, and vulnerability scanners for broader WordPress security coverage.
Scans are designed to run in batches with performance-conscious limits. Content Guard Pro includes Safe Mode and throttling behavior to reduce load on typical WordPress hosting.
After you clean affected content and save the post, scan again to confirm the issue is gone. Content Guard Pro keeps scan history so you can review previous findings and cleanup progress.
Yes. You can ignore findings that you have reviewed and accepted. You can also use allowlist and denylist controls to tune scanner behavior for legitimate services used by your site.
No. Scanning runs locally. Post content, database contents, scan result excerpts, and matched findings are not sent to the cloud service. The optional cloud connection is consent-based and can be skipped. Optional telemetry, if enabled, is limited to anonymous scan metrics and environment details.
Yes. That is one of the main use cases. After file cleanup, run Content Guard Pro to check whether hidden SEO spam, malicious scripts, iframes, suspicious links, or encoded payloads remain in the database content layer.
Start with Critical findings, then review Suspicious findings, then Review findings. Open affected posts directly from the finding details, remove suspicious content, save the post, and scan again.