On-save scanning provides real-time protection by checking content as you create or edit posts. This catches threats immediately, before they can affect your site.

How On-Save Scanning Works #

When enabled, Content Guard Pro scans content:

1. Before Publishing: Pre-publish panel shows scan results
2. On Save: Content is analyzed when you save or update
3. Immediate Feedback: Results appear in the editor sidebar

Enabling On-Save Scanning #

1. Go to Content Guard Pro → Settings
2. Find the Scheduling section
3. Check Real-time On-Save Scanning
4. Click Save Changes

Gutenberg Editor Integration #

Pre-Publish Panel #

When publishing a post, Content Guard Pro shows:

• Scan Status: Clean, warnings found, or critical issues
• Finding Count: Number of issues by severity
• Details: Click to expand and see specific findings

Editor Sidebar #

Access the Content Guard Pro panel:

1. Click the Content Guard Pro icon in the editor toolbar
2. Or go to Post Settings → Content Guard Pro

The sidebar shows:

• Current scan status
• Existing findings from the database
• Manual scan button
• Link to full findings page

Status Indicators #

Manual Scanning in Editor #

Even with auto-scan disabled, you can manually scan:

1. Open the post in the editor
2. Click the Content Guard Pro panel
3. Click Scan Content
4. Review results

Important: Manual scans check the current editor content, which may differ from what’s saved in the database.

Auto-Resolution Feature #

When you fix an issue and save:

1. The save-time scan runs automatically
2. If no issues are found, existing findings are marked Resolved
3. Resolution is tracked with timestamp and user ID

How It Works #

• On Save Only: Auto-resolution only happens when content is actually saved
• Manual Scans: Show “No issues found” but don’t resolve database findings
• Why: Prevents resolving findings for unsaved content

Example Workflow #

1. You open a post with a finding (hidden spam link)
2. The editor shows the existing finding
3. You remove the malicious content
4. You click Update
5. The save-time scan finds no issues
6. The finding status changes to Resolved

Fail-Open Policy #

To prevent content loss, Content Guard Pro uses a fail-open approach:

• If scan fails: Content is saved anyway
• Error logged: The failure is recorded
• Background scan scheduled: A deeper scan runs shortly after
• You’re notified: Admin notices alert you to the issue

This ensures that technical problems never block your content workflow.

Classic Editor Support #

For sites using the Classic Editor:

• Scans run when posts are saved/published
• Results display as admin notices after save
• Finding summary shows at the top of the edit screen

Disabling On-Save Scanning #

You might disable auto-scanning if:

• Running on limited hosting resources
• Performing bulk content imports
• Troubleshooting conflicts

To disable:

1. Go to Content Guard Pro → Settings
2. Uncheck Real-time On-Save Scanning
3. Click Save Changes

Note: Manual scan button still works when auto-scan is disabled.

Best Practices #

1. Keep auto-scan enabled for day-to-day protection
2. Review warnings before publishing, even if not critical
3. Check existing findings when editing old content
4. Use manual scan when pasting content from external sources