Debug Log
SEO Booster internal debug log in the sb2_log database table, priority labels, search, access, and how it differs from WordPress debug.log.
Admin path: SEO Booster → Debug Log (admin.php?page=sb2_log)
Requires manage_options.
What this log is
SEO Booster writes internal diagnostics to the {prefix}sb2_log MySQL table via Utils::log(). Messages are plain English for operators, not translated UI strings.
This is separate from:
| Log | Location | Cleared by SEO Booster? |
|---|---|---|
| SEO Booster Debug Log | {prefix}sb2_log table | Yes, Settings → Tools → Reset SEO Booster Debug Log |
WordPress debug.log | wp-content/debug.log | No, use your host or WP_DEBUG_LOG tools separately |
When support asks for “the SEO Booster log,” they mean SEO Booster → Debug Log, not wp-content/debug.log.
Priority labels
| Priority value | Label |
|---|---|
| 0 | Normal |
| 1 | Debug |
| 2 | Error |
| 3 | Warning |
| 5 | Info |
| 10 | Success |
Each row stores logtime, prio, and log (max 2048 characters). Arrays and objects are JSON-encoded before insert.
Using the page
- Search Logs, filter message text (server-side
LIKEquery) - Refresh, reload the current page of results
- Pagination controls, 20 rows per page by default
Typical entries: GSC import progress, Action Scheduler notes, cache cleanup counts, AI referral retention, authentication warnings.
Retention and clearing
There is no automatic rotation for sb2_log. The table grows until you clear it manually, run Clear All Data and Options on Settings → Tools, or deactivate the plugin with Delete data on deactivate enabled.
To clear only the log without wiping other data, use Reset SEO Booster Debug Log on Settings → Tools.
When to check
- GSC import or keyword processing appears stuck: also review Settings → Stats Action Scheduler counts
- Weekly email or cron issues
- Support ticket asking for recent plugin-side errors
Admin notices on the dashboard may link here when background jobs fail.