Spam Monitor Troubleshooting

Spam Monitor Troubleshooting

Use this guide when Spam Monitor scans, rules, alerts, or scheduled monitoring are not behaving as expected.

SERP scan is not working

Check:

• SERP Provider connection
• Provider status
• Spam Rules sync status
• Current configuration
• Available request/trial status displayed by the interface

Then try the scan again.

Results are being incorrectly flagged

Review:

Spam Rules → Language Rules

Check whether legitimate website languages are included under Website Allowed Languages.

Then review:

• Spam Keyword Rules
• Custom Blocked Keywords
• URL Pattern Rules
• Blocked URL Patterns
• Scoring values
• Score Thresholds

Overly broad rules can cause legitimate results to receive higher scores.

Unexpected-language results are not being detected

Check:

• Website Allowed Languages
• Expected Spam Languages
• Flag Unexpected Languages
• Language Mismatch Score

Then save and synchronize the rules before running another scan.

Spam keywords are not being detected

Check whether the relevant category is enabled.

Also review Custom Blocked Keywords and make sure each custom keyword is entered on its own line.

Rules are not synchronized

Check Rules Sync Status.

Use Save All Rules after changing rules and use Sync Rules Now when the available synchronization action is required.

I am receiving too many alert emails

Go to:

Spam Monitor → Alerts

Review Alert on Risk Levels.

The current interface recommends enabling Suspicious, Spam, and Critical while keeping Clean disabled to reduce notification fatigue.

Also review Send Scan Summary Email if you do not need a digest after every scan.

I am not receiving alert emails

Check:

• Enable Email Alerts
• Alert Email Address
• Selected risk levels
• Send Scan Summary Email, if applicable

Then use:

Send Test Email

to test the alert workflow.

Scheduled scan did not run at the exact displayed time

The interface explains that scheduled monitoring uses WordPress Cron.

A due task runs on a subsequent site request, so low-traffic websites can experience a delay compared with the intended run time.

Wrong website is being scanned

Check Developer testing mode.

For normal scheduled monitoring, this should remain disabled so the current WordPress website is used.

Subdomains are missing from scans

Review Include Subdomains in the relevant scan/schedule configuration.

Risk scores seem incorrect

Review all scoring contributors under Spam Rules:

• Language Mismatch Score
• Spam Keyword Score
• URL Pattern Score
• Score Thresholds

Use Scoring Preview to understand how multiple matches can contribute to the final score.

---

Still Need Help?

When contacting SEO Repair Kit Support, provide the relevant:

• Spam Monitor tab
• Screenshot
• Domain being scanned
• Scan status
• Risk score/classification
• Relevant Spam Rules
• Expected behavior
• Actual behavior
• SEO Repair Kit version

Do not include SERP provider API keys or other private credentials.