
A visitor types a word you know is on the site, presses Enter, and gets a blank page, a “nothing found” message, or an error. When the wordpress search results page not working problem appears, visitors cannot find anything, and they leave. The content is almost always safe. The search form, the results template, or the query behind it is failing.
This guide works through the causes in order, from a search form that submits nothing to a results template that displays nothing. Test with a word from a post title you can see, in a private browser window, after each fix. Take a backup before the deeper template and database fixes. Work through the fixes one at a time, and stop when the results appear.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Test Search with a Word You Know Is in a Post
- Fix 2: Check the Search Form and Search Block Setup
- Fix 3: Flush Permalinks and Test the Search URL Directly
- Fix 4: Clear Caches and Test in a Private Window
- Fix 5: Deactivate Search and Query Plugins One by One
- Fix 6: Switch to a Default Theme to Test the Search Template
- Fix 7: Check That Posts Are Published, Public, and Indexed
- Fix 8: Rebuild the Search Index and Check the Database
- Fix 9: Fix a Custom Search Template That Returns Nothing
- Fix 10: Check Excluded Post Types and Search Scope Settings
- Fix 11: Restore the Default Search Template and Reinstall WordPress Core Files
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
Site search works in three steps: the form sends the search words to WordPress, WordPress queries the database for matching posts, and the theme template displays the results. If the form sends nothing, the query searches the wrong content, or the template shows nothing, the results page fails while the rest of the site works. These are the breaks that happen most often.
1. The Search Form Submits the Wrong Field or Nothing at All
The search form must send the search words in the field WordPress expects. A custom form, a builder search module, or a theme search widget with the wrong field name sends an empty search, and WordPress returns its “nothing found” page. The fault appears after a theme change or a header rebuild, and it affects every search from that form.
2. A Plugin Replaces or Filters the Search Query
Search plugins, relevance plugins, and query-filtering plugins can replace the built-in search entirely. When one is misconfigured, deactivated halfway, or incompatible with an update, the results page can go blank, return nothing, or throw an error. The fault starts the day the plugin changes, and it affects every search on the site.
3. The Search Template Is Missing, Empty, or Broken
The theme controls the results page. A missing search template, a block theme with an empty search template, or a custom template that queries nothing can all produce a blank results page from a healthy query. The fault appears after a theme change or a theme update, and it survives every cache clear.
4. The Content Is Excluded from Search
Posts can be excluded from search by their status, their post type, or a plugin setting. Drafts, private posts, and password-protected posts never appear. Custom post types are excluded by default unless the theme or a plugin includes them. A search that finds nothing may be searching a scope that holds nothing.
5. A Stale Cache Serves an Old Empty Results Page
Caching plugins and server caches can freeze a “nothing found” page and serve it for every search term. The live search works, but visitors never see it — they see the frozen empty result. This cause is easy to miss, because the search page looks broken in exactly the same way whether the cache or the query is at fault.
6. The Database Search Index or Tables Are Damaged
WordPress searches the post tables directly, and damaged tables or a corrupted search index can return no matches for words that plainly exist. The fault often follows a failed update, a migration, or a database error elsewhere on the site. It is the least common cause, but it explains a search that fails for every term while the posts themselves load fine.
Quick Checks
Two minutes before the deep fixes.
- Search for a single common word from a post title you can see on the homepage.
- Note what the results page shows: blank, “nothing found”, an error, or the homepage again.
- Try the search from a different search box on the site, if there is one.
- Open the search address directly — add
?s=testwordto the homepage address. - Check whether search fails for every term or only some terms.
- Check whether it started after a plugin install, a theme change, or a migration.
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Every search returns nothing found | Form sends no search term | Fix 2 |
| Results page is completely blank | Search template missing or broken | Fix 6 |
| Search returns an error page | Stale permalinks or bad query | Fix 3 |
| Works in a private window only | Stale cache serving old results | Fix 4 |
| Fault started after a plugin change | Search or query plugin conflict | Fix 5 |
| Some post types never appear | Post type excluded from search | Fix 10 |
| Search finds old posts, not new ones | Index or database fault | Fix 8 |
| Custom search page shows nothing | Custom template query fault | Fix 9 |
Fix 1: Test Search with a Word You Know Is in a Post
Before you change anything, establish the facts with a controlled test. Search for a distinctive word from a post title that is visible on the homepage, and note exactly what the results page does. A precise symptom points at the right fix; a vague “search is broken” points everywhere.

- Open the homepage and note one distinctive word from a post title.
- Type that single word into the site search box.
- Press Enter and note exactly what the results page shows.
- Repeat the test in a private browser window.
- Try a second word from a different post title.
- Try a very common word, such as “the”, and note whether anything returns.
- Write down the results — they decide which fix to try next.
- A search that returns nothing for every word, including common ones, points at the form, the template, or the query. A search that finds old posts but not new ones points at the index.
- A search that works in a private window points at a cache. Do not skip this test because the fault “obviously” needs a plugin fix — five minutes of testing saves an hour of guessing.
- If the whole site fails to load during testing, fix the loading fault first, because search cannot work on a site that does not load.
Fix 2: Check the Search Form and Search Block Setup
The search form must send the search words in the field WordPress expects, and submit to the site address. A form with the wrong field name, a builder module pointed at the wrong action, or a search block with a broken setting sends an empty search. Checking the form takes minutes and fixes a large share of these faults.
- Find every search box on the site — header, sidebar, and any search page.
- Test each box separately with the same known word from Fix 1.
- If one box works and another does not, the faulty box is the problem.
- In a block theme, open the header template and select the Search block.
- Check the block settings for a custom action or a broken configuration.
- Replace a suspect search block with a fresh Search block from the inserter.
- Test the search again in a private window.
- Custom header search forms are the usual suspects: a form built by hand, or by a builder, can carry a field name WordPress does not recognise, so the search arrives empty. The block editor’s Search block handles the field name correctly by default, which is why replacing a suspect form with a fresh block is such a reliable test.
- If the search box lives in a widget area, check the widget settings too — a search widget pointed at a custom results page can send visitors somewhere the results never render.
- A form that works after replacement proves the old form, not the search engine, was the fault.
Fix 3: Flush Permalinks and Test the Search URL Directly
Search addresses use the ?s= query format, but stale rewrite rules can still interfere — especially when a plugin registers its own search address or a custom search page exists. Flushing the rules rebuilds the address handling, and testing the address directly bypasses the form entirely.
- Open a private window and go to the homepage address.
- Add
?s=and a known word to the address, then press Enter. - Note whether the results page loads and what it shows.
- Go to Settings, then Permalinks, in the dashboard.
- Click Save Changes without changing the structure.
- Repeat the direct-address test in the private window.
- If the direct test works but the form test fails, the form is the fault — return to Fix 2.
- The direct test is decisive: if
?s=wordreturns results, the search engine and template work, and only the form is broken. If the direct test also fails, the fault is deeper — the query, the template, or the index. - The stronger flush, switching temporarily to Plain and back, clears rules that a single save leaves behind.
- If the search address redirects to the homepage, a redirection plugin or rule is intercepting it — check the redirection settings before you blame the template.
Fix 4: Clear Caches and Test in a Private Window
A cache can freeze a “nothing found” page and serve it for every search term, making a healthy search look broken. Clear every cache layer and test in a private window, where the browser cache cannot interfere. Test the private window before you purge, so you know whether the cache was ever the fault.
- Open the search in a private window and note the result, as a baseline.
- Purge the cache from your caching plugin’s menu or toolbar button.
- Purge the server or host cache from the hosting control panel, if one exists.
- Purge the content delivery network cache, if the site uses one.
- Exclude search result addresses from the cache, if the plugin offers the option.
- Hard-refresh the private window and test the search again.
- Repeat the test in a normal window after clearing the browser cache.
- Search results should never be cached as if they were ordinary pages, because every search term deserves a fresh answer. Most caching plugins exclude search addresses by default, but a misconfigured rule can include them.
- If results appear after the purge but go stale again, the cache rules — not the search — need correcting. When the site keeps showing old content after purges, our guide to WordPress website showing old content covers the stubborn-cache checks.
- A search that works privately but not normally is a cache fault, never a content fault.
Fix 5: Deactivate Search and Query Plugins One by One
Search, relevance, filtering, and query plugins can replace or rewrite the built-in search. When one is misconfigured or incompatible, the results page can go blank or return nothing for every term. Deactivating suspects one at a time finds the culprit without losing settings.
- Note which plugins were installed or updated just before the fault started.
- Go to Plugins, then Installed Plugins, in the dashboard.
- Deactivate the most recent search-related suspect first.
- Test the search in a private window with the known word.
- If nothing changes, reactivate the plugin and try the next suspect.
- When results return, you have found the culprit — check its settings for a search scope or index option.
- Leave the culprit deactivated, or reconfigure it, before you move on.
- Test dedicated search plugins first, then filtering and query plugins, then anything that modifies archives or listings. A search plugin that builds its own index can fail silently when its index is empty — check for a “rebuild index” button in its settings before you deactivate it permanently.
- Deactivate one plugin at a time, because bulk deactivation hides which plugin caused the fault. If plugin conflicts keep recurring, our guide to WordPress plugin conflict fix covers the systematic isolation method.
- A search that returns with one plugin off has named its own culprit.
Fix 6: Switch to a Default Theme to Test the Search Template
The theme renders the results page. A missing search template, an empty block-theme search template, or a custom template that queries nothing can all show a blank page from a healthy search. A brief switch to a default theme proves whether the theme or the data is at fault.

- Go to Appearance, then Themes, in the dashboard.
- Activate a default theme, such as Twenty Twenty-Four or Twenty Twenty-Five.
- Test the search in a private window with the known word.
- If results appear, the old theme’s search template is the fault.
- Switch back to your theme and open its search template settings.
- In a block theme, check the Search template in the Site Editor for a query block.
- Fix or rebuild the faulty template, then test the search again.
- Switching themes does not delete content, and your theme’s settings return when you switch back — but note customiser choices first, just in case. In a block theme, the Search template needs a query block to list results and a search-results title block to show the term; an empty template shows an empty page.
- In a classic theme, a missing or damaged search template file falls back to the index template, which may display nothing useful.
- A default theme that returns results proves the search engine is healthy and the display is broken.
Fix 7: Check That Posts Are Published, Public, and Indexed
Search only returns published, public posts. Drafts, scheduled posts, private posts, and password-protected posts are all excluded, and posts set to be hidden from search by a plugin setting are excluded too. Confirm the posts you expect to find are actually searchable before you rebuild anything.
- Open a post that should appear in the search results.
- Confirm its status reads Published, not Draft, Scheduled, or Private.
- Confirm the post has no password set in the visibility options.
- Check the post for a plugin setting that hides it from search results.
- Repeat the check for two or three other posts that should appear.
- Publish or unhide any post that should be searchable.
- Test the search in a private window with a word from the corrected post.
- Membership and restriction plugins deserve special attention: a rule that hides content from logged-out visitors also hides it from their searches, which is correct behaviour for members-only content but confusing when the rule is misconfigured. Check the plugin’s search-visibility settings for the affected posts.
- A post that appears in search after its status is corrected was never missing — it was hidden by design.
- If only new posts are missing while old ones appear, the index in Fix 8 is the next check.
Fix 8: Rebuild the Search Index and Check the Database
When search finds old posts but not new ones, or finds nothing for words that plainly exist, the database tables behind search may be damaged. A repair and optimisation rebuilds the stored data, and a search plugin’s index rebuild refreshes its own copy. Take a backup before this fix, and use reputable tools rather than hand-editing tables.
- Take a full backup of the site, including the database, before you start.
- If a search plugin is active, look for a Rebuild Index option in its settings.
- Run the index rebuild and wait for it to finish completely.
- Test the search in a private window with a word from a new post.
- If no plugin index exists, open the host’s database tool or a trusted optimisation plugin.
- Run a repair and optimisation on the posts tables.
- Test the search again, and check that single posts still load correctly.
- Database repair is a measured step, not a guess: damaged tables usually announce themselves with errors elsewhere on the site, so check the dashboard and a few single posts for errors too. Never delete rows by hand — a deleted row can orphan content across the site.
- If the repair changes the results, the damage was real, and the search should now find new posts. If database errors appear more widely, our guide to WordPress database connection error covers the connection-side checks.
- A rebuilt index that returns fresh results proves the content was there all along.
Fix 9: Fix a Custom Search Template That Returns Nothing
A custom search template — built in a builder, a child theme, or a code snippet — can query the wrong content, the wrong post type, or nothing at all. The built-in search works, but the custom template never asks it the right question. Checking the template’s query, or falling back to the default template, resolves the fault.

- Identify whether the site uses a custom search template or search results page.
- Open the template in the builder, the Site Editor, or the child theme.
- Read the query settings: which post types, which categories, which search term?
- Confirm the query uses the search term from the address, not a fixed word.
- Confirm the query includes the post post type.
- Correct the query, or remove the custom template to restore the default.
- Clear the cache and test the search in a private window.
- Builder search templates commonly carry a query block filtered to a category or a post type, which silently excludes the posts visitors search for. A fixed search term in the query is another classic: the template searches for the same word every time, whatever the visitor typed.
- Code snippets can hardcode the same mistake.
- When in doubt, remove the custom template and test with the theme default — a working default proves the custom query was the fault, and you can rebuild it correctly from there.
Fix 10: Check Excluded Post Types and Search Scope Settings
WordPress searches posts and pages by default. Custom post types, attachments, and other content types are excluded unless something includes them, and plugins can narrow the scope further. A search that returns some content but never a whole type is a scope fault, not a broken search.
- Note which content type never appears: posts, pages, products, or a custom type.
- Check the theme options for a search scope or “search includes” setting.
- Check each search and filtering plugin for a post-type inclusion list.
- Tick the missing post type in the inclusion list, if the setting exists.
- If no setting exists, check whether the post type was registered as searchable.
- Clear the cache after any scope change.
- Test the search in a private window with a word from the missing content type.
- Scope settings hide in several places: theme options, search plugin settings, and the post type registration itself. A custom post type registered without search support will never appear, whatever the settings say — that needs a code or plugin change to its registration.
- Attachments are a special case: many sites exclude them deliberately, because media files clutter results. Decide the scope deliberately, record it, and test one word per content type after every change.
- A scope that includes the missing type restores its results immediately.
Fix 11: Restore the Default Search Template and Reinstall WordPress Core Files
If every other fix fails, the search template or the core files behind search may be damaged beyond what settings can repair. Restoring the default template and reinstalling the core files gives search a clean foundation. Take a backup first, and use the dashboard’s own reinstall — never a downloaded copy from an unknown source.
- Take a full backup of the site, including the database, before you start.
- In a block theme, reset the Search template to the theme default in the Site Editor.
- In a classic theme, restore the search template file from a fresh copy of the theme.
- Go to Dashboard, then Updates, in the dashboard.
- Click Re-install Now under the WordPress version to reinstall the core files.
- Wait for the reinstall to finish, then clear every cache layer.
- Test the search in a private window with the known word from Fix 1.
- Reinstalling core files replaces only WordPress itself — your content, themes, and plugins are untouched. It repairs damaged core search files without touching a single post.
- If the search still fails after a clean template and fresh core files, the fault lives in a must-use plugin or a server rule that the earlier tests did not reach — check the
mu-pluginsfolder and ask your host whether a server rule intercepts search addresses. When caches also interfere with the final test, our guide to WordPress cache not clearing helps you get a clean result. - A wordpress search results page not working fault that survives all eleven fixes is rare, and a clean simultaneous test usually names the culprit at last.

What to Avoid
- Do not install a “search booster” plugin from an unknown source — fix the built-in search first with the checks in this guide.
- Do not cache search result pages as if they were ordinary pages — every search term deserves a fresh answer.
- Do not bulk-deactivate every plugin at once — deactivate one at a time so you learn which one caused the fault.
- Do not edit database tables by hand — use a repair tool and a backup, or ask your host for help.
- Do not build a custom search template that hardcodes a search term — the template must read the term from the visitor.
- Do not use pirated themes, plugins, activators, or cracks — they can inject code that breaks search and invites malware.
- Do not judge the fix in a normal browser window — test in a private window so a cached empty result never fools you.
Frequently Asked Questions
Why does WordPress search return “nothing found” for words on the site?
Because the form sends no term, the query searches the wrong scope, the template shows nothing, or a cache serves a frozen empty page. Test the direct address ?s=word first: if it returns results, the form is at fault. If it also fails, work through the template, plugin, and index fixes in order.
Why is the search results page blank instead of showing “nothing found”?
A blank page points at the template: a missing, empty, or broken search template renders nothing at all, while a working template always shows at least the “nothing found” message. Switch to a default theme as Fix 6 describes — results on the default theme prove the old template was the fault.
Can a caching plugin break search?
Yes, when it caches a “nothing found” page and serves it for every search term. Purge every cache layer, exclude search addresses from caching, and test in a private window. Search results should always be fresh, because each term is a different question.
Why does search find old posts but not new ones?
The search index or the database tables are stale or damaged, so new content never enters the searchable data. Rebuild the search plugin’s index, or repair the posts tables, as Fix 8 describes. After the rebuild, test with a word from the newest post to confirm fresh content is searchable.
What is the wordpress search results page not working fix after a theme change?
Check the new theme’s search template first: a block theme needs a Search template with a query block, and a classic theme needs a working search template file. Test with a default theme to confirm the fault is the template, then rebuild or restore the new theme’s search template. Also check the header search form, because a new theme brings a new form.
Will reinstalling WordPress delete my content?
No. The dashboard reinstall replaces only the WordPress core files. Your posts, pages, media, themes, and plugins are untouched. Take a backup first anyway, because a backup is cheap insurance for any site-wide change, and clear every cache after the reinstall so visitors see the repaired files.
Conclusion
When the wordpress search results page not working problem leaves visitors with no answers, the fault is usually a form that sends nothing, a template that shows nothing, a plugin that rewrites the query, or a cache serving a frozen empty page. Test with a known word, check the form and the template, flush the permalinks, clear every cache, and test plugins and the theme one at a time. Finish by searching for three different words in a private window and reading real results for each, because live results are the only proof that counts. Keep search uncached, scoped deliberately, and tested after every theme or plugin change, and visitors will always find what they came for.
