How to Fix Search Analytics Not Recording Searches

SoftwareRoad Knowledge Base can record anonymous search totals to help you understand what visitors are looking for.

When Search Analytics is working, the dashboard can show information such as:

• Search terms entered by visitors
• How many times each term was used
• How many results were available
• When the term was searched most recently
• Searches that returned no matching articles

If searches are working publicly but nothing appears under Knowledge Base > Analytics, check the settings, licence, search length, AJAX requests, caching and database setup.

Check that knowledge base search is enabled

Search Analytics can only record searches when visitors use the SoftwareRoad Knowledge Base search feature.

Open:

Knowledge Base > Settings

Check that search is enabled for the relevant pages.

Depending on your setup, search may appear on:

• The main knowledge base homepage
• Category pages
• Individual articles
• Compact search areas
• Knowledge base sidebars

Save the settings after making any changes.

Test the public search box

Open the main page containing:

[srkb_knowledge_base]

Enter a clear search term and check whether live results appear.

For example:

licence

or:

installation

If the search itself does not work, Search Analytics cannot record the request.

Fix the public search feature before troubleshooting the Analytics dashboard.

Enable Anonymous Search Totals

SoftwareRoad Knowledge Base includes an Anonymous Search Totals setting.

This setting must be enabled for search terms to be added to the Analytics dashboard.

To check it:

1. Open Knowledge Base > Settings.
2. Select the Features, Privacy & SEO or relevant analytics section.
3. Find Anonymous Search Totals.
4. Enable the setting.
5. Select Save Changes.
6. Clear the website cache.
7. Run a new public search.

The setting may have a slightly different location depending on the installed plugin version.

Why the setting is described as anonymous

Search Analytics is designed to record grouped search activity rather than creating named visitor profiles.

The stored information can include:

• The search wording
• Total number of times it was used
• Number of matching results
• Most recent search date

It does not require the visitor to provide their name or email address.

Your hosting provider and other website services may separately process normal technical request information.

Previously completed searches may not appear

Searches made while Anonymous Search Totals was disabled are not normally added later.

After enabling the setting, run a completely new search to test it.

Do not expect the dashboard to recreate search history from before tracking was enabled.

Use a search term with at least two characters

SoftwareRoad Knowledge Base begins live search after at least two characters have been entered.

A one-character search such as:

a

will not normally run or be recorded.

Use a term such as:

ac

key

licence

article

The search must actually be submitted to the live search system before Analytics can record it.

Do not test with only one letter

Typing a single letter and then leaving the page is not a valid Search Analytics test.

The minimum length helps reduce:

• Unnecessary requests
• Meaningless search records
• Large numbers of single-letter entries
• Extra server work

Use a complete word or a useful phrase when testing.

Wait for the search request to complete

Live search may not run the instant the first eligible character is entered.

Type the full search term and pause briefly so the results can load.

If you immediately close the page, refresh or select another link, the request may not complete.

Watch for:

• Matching article results
• A no-results message
• A loading indicator
• A change in the result panel

Once the response appears, return to the Analytics dashboard and refresh it.

Test while signed out

Use a private browser window for testing.

This provides a more realistic visitor session and helps avoid differences caused by:

• WordPress administrator permissions
• Logged-in caching
• Browser extensions
• The WordPress admin toolbar
• User-role conditions

Open the public knowledge base, search for a new phrase and then check Analytics from your normal administrator window.

Use a unique test term

A unique term makes it easier to confirm that a new record was created.

For example:

licence test july

or:

article icon test

Use wording that contains at least two characters and is unlikely to have been searched before.

Remember to remove obviously artificial test data later only if your plugin version includes a safe analytics reset or deletion option.

Check the active licence

Search Analytics requires an active SoftwareRoad Knowledge Base Monthly or Yearly licence.

Open:

Knowledge Base > Licence

Confirm that the licence status is active.

If the licence is inactive, expired or cannot be verified:

• Public search may become unavailable
• Analytics requests may be rejected
• New searches may not be recorded
• Existing reports may not update normally

Reactivate the licence and clear public page caches before testing again.

Confirm the subscription is active

The purchase email and product key must be connected to an active subscription.

Check whether the Monthly or Yearly subscription is:

• Active
• Paid
• Not cancelled
• Not expired
• Not refunded
• Not suspended after a failed renewal

If the subscription is active but WordPress does not recognise it, open the Licence screen and run the activation again.

Clear caches after licence activation

A public knowledge base page may still contain an older inactive licence response.

Clear:

• WordPress page cache
• Object cache
• Hosting cache
• Server cache
• CDN cache
• Browser cache

Then open a fresh private window and run another search.

Check that the correct knowledge base page is being used

Open:

Knowledge Base > Settings > General

Confirm that the selected Knowledge Base Page is the published WordPress page containing:

[srkb_knowledge_base]

If several old test pages contain the shortcode, you may be testing a cached or outdated copy.

Only one main knowledge base page should normally be used.

Check search results are actually loading

Search Analytics is normally recorded as part of the live search request.

If no results panel appears, check whether the search request is failing.

Try a term that should definitely match a published article title.

For example, if you have an article called:

How to Activate SoftwareRoad Knowledge Base

search for:

activate

If nothing appears, the problem may affect AJAX rather than Analytics alone.

Check AJAX requests

SoftwareRoad Knowledge Base uses WordPress AJAX for interactive features.

A blocked or failed AJAX request can prevent:

• Live search results
• Search Analytics
• Helpful voting
• Article view tracking

Open the browser developer tools and use the Network tab while running a search.

Look for a request to WordPress, commonly through:

admin-ajax.php

Check whether the request completes successfully.

Common AJAX response codes

A successful request normally returns a response without a browser error.

Failed requests may show:

• 400 for an invalid request
• 403 when the request is blocked or not authorised
• 404 when the AJAX address cannot be found
• 500 for a PHP or server error
• 502 or 503 for a hosting or temporary server problem

Open the failed request to review its response where possible.

A 403 AJAX response

A 403 response often means a security or firewall rule blocked the search request.

Possible causes include:

• WordPress security plugins
• Hosting web application firewall
• Cloudflare security rules
• Bot protection
• Rate limiting
• Country restrictions
• An expired security nonce
• Anonymous POST requests being blocked

Review recent security logs to see why the request was rejected.

A 404 AJAX response

A 404 response can mean:

• The WordPress AJAX address is incorrect
• The website was moved between domains
• A redirect changed the request URL
• WordPress site addresses are wrong
• A security rule hides admin-ajax.php
• A cache or proxy is routing the request incorrectly

Open:

Settings > General

Check the WordPress Address and Site Address.

Both should use the correct live domain and HTTPS address.

A 500 AJAX response

A 500 response normally means the server encountered a PHP error while processing the search.

Check:

• WordPress debug log
• Hosting error log
• PHP error log
• Recent plugin updates
• Database errors
• Memory limit
• Plugin conflicts

The response may contain a useful error message, but do not display detailed PHP errors publicly on a live website.

Check the browser console

Open the Console tab in browser developer tools.

Run another knowledge base search and look for errors.

Possible problems include:

• JavaScript syntax errors
• Missing plugin scripts
• jQuery errors
• Blocked AJAX requests
• Content Security Policy errors
• Optimisation scripts loading files in the wrong order

A JavaScript error from another plugin can stop SoftwareRoad Knowledge Base search before Analytics has a chance to record it.

Check security plugin settings

Security plugins can block anonymous search requests because they come from visitors who are not signed in.

Review settings related to:

• Anonymous AJAX
• WordPress nonces
• Bot protection
• Rate limits
• Spam protection
• REST and AJAX restrictions
• Form submission rules
• Firewall allow lists

Do not disable your website security permanently.

Temporarily test the relevant setting, then create a narrow exception once the blocked request has been identified.

Check security logs

Many security plugins include a live traffic or firewall log.

Run a search, then immediately review the log.

Look for entries involving:

• admin-ajax.php
• SoftwareRoad Knowledge Base
• Blocked POST requests
• Invalid nonce messages
• Rate-limit rules
• Challenge pages

The log can often identify the exact rule causing the problem.

Check Cloudflare or CDN security

A content delivery network may challenge or block AJAX requests.

Review:

• Web application firewall events
• Bot protection
• Rate limiting
• Managed challenge rules
• Browser integrity checks
• Cache rules

The WordPress AJAX endpoint should not normally be cached as a static page.

Do not create a broad bypass for the whole website when a specific AJAX exception is sufficient.

Check WordPress page caching

The search page may contain an old or expired request nonce.

This can happen when a public page is cached for a long time.

Clear the cache for:

• Main knowledge base page
• Category pages with compact search
• Article pages with compact search

Then load a completely fresh page in a private browser window.

Expired nonce caused by caching

WordPress uses security nonces to help verify some AJAX actions.

A nonce does not remain valid forever.

If a cache serves the same old page for too long, the search request may contain an expired nonce and be rejected.

Possible signs include:

• Search worked previously
• It fails only on cached public pages
• Clearing the cache temporarily fixes it
• The AJAX response mentions an invalid or expired nonce

Reduce the page cache lifetime or exclude the affected dynamic search page where necessary.

Do not cache AJAX responses

Dynamic search responses should not normally be stored as normal page cache.

Review cache rules that include:

• admin-ajax.php
• POST requests
• Query strings
• JSON responses
• Dynamic search endpoints

Caching an AJAX response can cause visitors to receive outdated or incorrect results.

It may also prevent new searches from reaching WordPress and being recorded.

Check JavaScript optimisation

Performance plugins may delay, combine or remove scripts needed by live search.

Temporarily test without:

• Delayed JavaScript
• Deferred JavaScript
• Combined JavaScript files
• Removed unused JavaScript
• Aggressive minification
• Script execution delays until user interaction

Clear all caches before testing after each change.

If Search Analytics begins working, exclude the relevant SoftwareRoad Knowledge Base scripts from that optimisation.

Check whether typing is triggering a request

Open the browser Network tab and begin typing.

Once two or more characters are entered, a search request should normally appear after the search delay.

If no request appears at all, check:

• Search is enabled
• The search script loaded
• JavaScript errors
• The input is the SoftwareRoad Knowledge Base search field
• The page builder did not duplicate or alter the search element
• Script optimisation is not delaying the code indefinitely

Check the search result limit

SoftwareRoad Knowledge Base normally displays up to six live results.

The result limit does not stop Search Analytics from recording the search.

A term can still be recorded when:

• It has more than six matches
• It has one match
• It returns no matches

Do not assume a search was not recorded simply because a particular article was not displayed in the first six results.

No-result searches should still be useful

Search Analytics can help identify terms that return no matching content.

For example:

refund policy

may show a result count of zero.

These searches can reveal:

• Missing documentation
• Different customer wording
• Spelling variations
• Features visitors expect
• Article titles that need improving

If successful searches are recorded but no-result searches are not, test whether a security or JavaScript error occurs when the empty result response is returned.

Refresh the Analytics dashboard

After running a test search:

1. Open Knowledge Base > Analytics.
2. Select the Search Analytics section.
3. Refresh the page.
4. Check the search term list.
5. Review the most recent search date.

The dashboard may not update while it remains open in another browser tab.

Reload it after each test.

Check the selected Analytics section

SoftwareRoad Knowledge Base includes several analytics areas.

Make sure you are viewing Search Analytics rather than:

• Article Views
• Helpful Feedback
• General analytics summary

The search term table may appear lower down the page or under its own tab.

Grouped search terms

Search Analytics groups repeated searches for the same wording.

For example, if visitors search for:

product key

several times, the dashboard may show one row with a higher total rather than several separate rows.

This is expected behaviour.

Check whether the total count increased instead of looking only for a new row.

Capital letters may be grouped

Depending on how the search term is normalised, searches such as:

Licence

and:

licence

may be treated as the same grouped term.

The existing row may update its count and most recent date.

Search for a genuinely different phrase when testing new entries.

Extra spaces may be removed

Search terms can be cleaned before storage.

For example:

product key

may be stored as:

product key

This prevents the report from being filled with duplicate entries caused only by spacing differences.

Check existing rows before concluding that nothing was recorded.

Check the most recent search date

Even when the total count is difficult to notice, the most recent search date may update.

Compare:

• Search count
• Result count
• Last searched date

This can confirm whether a new search reached the Analytics system.

Check database access

SoftwareRoad Knowledge Base stores Search Analytics in the WordPress database.

If WordPress cannot write to the required analytics table, searches may work publicly but fail to appear in reports.

Possible causes include:

• The analytics table was not created
• Database permissions are restricted
• The table is damaged
• A migration missed plugin tables
• A security tool blocks database changes
• The database user has read-only permissions
• The site was restored from an incomplete backup

This is an advanced troubleshooting area.

Check for database errors in Site Health

Open:

Tools > Site Health

Review any database or loopback warnings.

WordPress may also report problems through:

• Hosting error logs
• WordPress debug log
• Database management tools
• Server monitoring

Look for errors that occur at the same time as the search test.

Check after a website migration

A migration may copy WordPress posts and settings but miss a custom analytics table.

If Search Analytics stopped working after moving hosts or restoring the website:

1. Check that SoftwareRoad Knowledge Base is active.
2. Confirm the licence is active.
3. Save the plugin settings again.
4. Clear all caches.
5. Run a new search.
6. Check server and database logs.
7. Confirm all plugin database tables were included in the migration.

The article and category content can continue working even when an analytics table is missing.

Check after restoring a backup

An older backup may contain:

• Older analytics totals
• Disabled tracking settings
• A missing analytics table
• An inactive licence status
• Old cached pages

Review all settings and run a fresh search after the restore.

Do not rely on a search performed before the backup date.

Check whether the analytics table exists

This step is intended for experienced WordPress administrators or developers.

SoftwareRoad Knowledge Base uses a dedicated database table for search analytics.

The full table name depends on the WordPress database prefix.

For example, a website may use:

wp_

or a custom prefix.

Do not assume the table name or create one manually without checking the installed plugin version.

A table created with the wrong columns can cause further errors.

Do not edit the database without a backup

Before inspecting or changing the WordPress database:

• Create a full database backup
• Confirm the backup can be restored
• Use a staging website where possible
• Avoid deleting analytics tables
• Avoid changing column types
• Avoid manually inserting test records

Contact support if you are unsure.

Missing analytics table

If the dedicated Search Analytics table is missing, the plugin may need to recreate it through its normal installation or upgrade routine.

Possible safe steps include:

1. Create a full backup.
2. Confirm the plugin is updated.
3. Deactivate SoftwareRoad Knowledge Base.
4. Reactivate the plugin.
5. Reopen the settings and save them.
6. Run a new public search.
7. Check Analytics again.

Do not uninstall the plugin unless you understand whether uninstalling removes saved content or settings.

Deactivation and reactivation are safer than deleting the plugin data.

Check database user permissions

The WordPress database user normally needs permission to:

• Read data
• Insert data
• Update data
• Create required plugin tables during installation or updates

A read-only database account can allow public pages to load while preventing analytics records from being saved.

Ask the hosting provider to verify the normal WordPress database permissions.

Do not send database passwords through public support messages.

Check for a damaged database table

A damaged table may cause insert or update errors.

Possible signs include:

• Search works but nothing records
• Server logs show table errors
• Analytics worked before a server crash
• Other analytics sections also fail
• Database repair tools report a problem

Ask the hosting provider or an experienced developer to inspect and repair the table after taking a full backup.

Do not delete the Search Analytics table

Deleting the table removes stored search information and may not automatically fix the cause.

It can also remove useful data such as:

• Popular search terms
• No-result searches
• Search totals
• Last searched dates

Only remove or recreate database tables when specifically instructed and after creating a backup.

Check PHP errors

A PHP warning or fatal error may stop the analytics save process after the search results have already been generated.

Review:

• WordPress debug log
• Hosting PHP logs
• Web server error logs

Run a test search and note the exact time so you can match it with the log entry.

Check WordPress debug logging

On a staging website, WordPress debugging can help identify the cause.

Useful settings include:

WP_DEBUG

and:

WP_DEBUG_LOG

Avoid displaying technical errors publicly on a live website.

Ask your host or developer to enable logging safely if needed.

Check for plugin conflicts

Another plugin may interfere with:

• AJAX actions
• Database inserts
• Security nonces
• Anonymous requests
• Search input events
• JavaScript loading

Test conflicts on a staging website:

1. Keep SoftwareRoad Knowledge Base active.
2. Deactivate other plugins.
3. Run a new search.
4. Check Analytics.
5. Reactivate plugins one at a time.
6. Repeat the test.

The plugin activated just before the problem returns is the likely conflict.

Plugins most likely to affect search tracking

Pay particular attention to:

• Security plugins
• Caching plugins
• Script optimisation plugins
• Database optimisation plugins
• Cookie or privacy plugins
• AJAX filters
• Search replacement plugins
• Maintenance plugins
• Custom code plugins

A conflict can exist even when the public search results still appear.

Check the active WordPress theme

A theme can interfere if it:

• Replaces the search JavaScript
• Duplicates element IDs
• Removes required scripts
• Alters AJAX URLs
• Prevents page content scripts from loading

On a staging website, temporarily switch to a standard WordPress theme and test again.

If Search Analytics works, review the original theme’s scripts and performance settings.

Check custom code

Custom snippets may change or block:

• admin-ajax.php
• WordPress nonces
• Public POST requests
• Plugin database actions
• JavaScript event listeners
• REST or AJAX authentication

Temporarily disable relevant custom code on staging.

Do not edit SoftwareRoad Knowledge Base plugin files directly.

Plugin updates can replace those changes.

Search Analytics worked before but has stopped

Review recent changes such as:

• Plugin update
• Theme update
• Security rule change
• Hosting migration
• PHP update
• Caching configuration change
• CDN activation
• Database repair
• Backup restoration
• Licence renewal failure

Testing changes in reverse order can help identify the cause.

Search Analytics records some searches but not others

Check whether the missing searches:

• Contain only one character
• Were typed and removed too quickly
• Were performed while the page was still loading
• Contain unusual symbols
• Were blocked by a rate-limit rule
• Match an existing grouped term
• Came from a cached page with an expired nonce

Try the same term again on a fresh uncached page.

Search Analytics records duplicate-looking terms

Terms that look similar may contain differences such as:

• Singular and plural wording
• Hyphenated and non-hyphenated wording
• UK and US spelling
• Different word order
• Extra punctuation
• Misspellings

For example:

product key

and:

key product

are separate searches.

This data can be useful because it shows the language visitors actually use.

Search totals appear lower than expected

Search Analytics is not intended to replace a full website analytics service.

Totals may be lower because:

• Tracking was enabled recently
• One-character searches are ignored
• Some requests were blocked
• Visitors selected a result before finishing another search
• Cached pages contained expired requests
• The licence was inactive
• Search terms were grouped together
• Previous data was reset or restored from backup

Use the report as a practical documentation guide rather than an exact visitor count.

Search totals appear unusually high

Possible causes include:

• Repeated testing
• Automated requests
• Bots
• A shared public terminal
• Visitors retrying several search phrases
• Search integrations making repeated requests

Review the terms and recent activity.

Do not delete all analytics immediately unless you have confirmed the data is invalid.

Search terms are recorded but result counts look wrong

Clear all caches and test again.

Also check whether:

• Articles were recently published
• Articles were made unlisted
• Categories changed
• The search index or response was cached
• The test page contains an expired result response
• The search term is very broad

Search result totals can change as the knowledge base content changes.

Analytics does not update until much later

Check:

• Object cache
• Database query cache
• Analytics page cache
• Browser cache
• CDN cache
• Scheduled database operations

WordPress administration pages should generally show current data, but aggressive server caching can delay updates.

Ask the host whether database or object caching is retaining old query results.

Privacy policy information

If Anonymous Search Totals is enabled, your privacy policy should explain that anonymous knowledge base searches may be counted to improve documentation.

A simple explanation could mention that the website records:

• Search wording
• Search frequency
• Number of matching results
• Recent search activity

Do not claim that no technical information is processed anywhere on the website, since hosting and security services may keep their own server logs.

A practical test procedure

Use this test to check the complete process:

1. Confirm the Monthly or Yearly licence is active.
2. Enable knowledge base search.
3. Enable Anonymous Search Totals.
4. Save the settings.
5. Clear all public page caches.
6. Open the knowledge base in a private window.
7. Enter a unique phrase containing at least two characters.
8. Wait for results or the no-results message.
9. Open Knowledge Base > Analytics.
10. Refresh the Search Analytics section.
11. Look for the phrase or an increased grouped total.
12. Check its result count and most recent date.

If the search results load but no record appears, inspect the browser Network tab and server logs.

Contact SoftwareRoad support

Contact support if:

• Search is enabled
• Anonymous Search Totals is enabled
• The licence is active
• The search term contains at least two characters
• Public search results load correctly
• A fresh private-browser test was completed
• No search entry or count update appears
• Caches and security restrictions have been checked

Include:

• Website address
• SoftwareRoad Knowledge Base version
• WordPress version
• PHP version
• Test search wording
• Time the test was completed
• Whether live results appeared
• AJAX response status
• Browser console errors
• Relevant PHP or database errors
• Whether the site was recently migrated
• Caching and security plugins in use

Do not publicly share your full product key or database credentials.

Search Analytics troubleshooting checklist

Before contacting support, check that:

• Knowledge base search is enabled
• Anonymous Search Totals is enabled
• Settings were saved
• The Monthly or Yearly licence is active
• The correct knowledge base page is being tested
• The search term contains at least two characters
• The search request is allowed to complete
• A unique test term has been used
• Testing was completed while signed out
• The Analytics dashboard was refreshed
• Existing grouped terms and counts were checked
• Live search results are appearing
• AJAX requests complete successfully
• Security plugins are not blocking anonymous requests
• CDN and firewall logs have been reviewed
• Cached pages do not contain expired nonces
• AJAX responses are not being cached
• JavaScript optimisation has been tested
• Browser console errors have been checked
• PHP and database logs have been reviewed
• The Search Analytics database table exists
• WordPress has permission to write to the database
• Recent migrations or backup restores have been considered
• Plugin and theme conflicts have been tested on staging
• The database has not been edited or reset without a backup

Search Analytics should begin recording anonymous grouped search totals once search is enabled, the licence is active and WordPress can complete the AJAX request and save the result to the database.