WordPress 7 min read

WordPress search not finding custom fields: where I would start

WordPress site search missing custom fields or useful content? How I review searchable data, content types and result quality before planning a fix.

WordPress search not finding custom fields: where I would start

A visitor searches your WordPress site for a reference number, location or service detail that is clearly visible on a page. The search box returns nothing. Searching for a word in the page title works. That is a useful clue about which data the search is actually checking.

When WordPress search is not finding custom fields or useful content, I start by tracing a few real search terms to their expected results. This article concerns the search inside your website. Getting a page to appear in Google is a separate investigation.

Collect examples of what people expect to find

Before changing search settings, I would ask for several examples: the phrase entered, the page or record that should appear, and where the matching information is stored. A screenshot of an empty results page is less useful than a repeatable search with an agreed expected result.

For a business directory, that might mean searching by a public business name or postcode. For a document library, it might mean a document title or reference. These are example requirements to agree, rather than features I would assume the existing search supports.

I would separate three problems: the expected item is missing, it appears too far down the list, or the search itself fails to respond. They can require different changes.

Check which fields the current search uses

WordPress's search-column reference lists the title, excerpt and main content as the supported columns searched by the standard core mechanism. All three are included by default. Custom field values are separate data, so their presence on a rendered page does not automatically make them part of that search.

I would establish whether the search box uses core WordPress search, a plugin, a custom request or an external search service. Then I would inspect the fields that implementation actually queries or indexes. A site can have several search boxes using different implementations.

The WordPress query reference documents custom-field filtering separately from keyword search. That is useful for development, but simply adding a metadata condition does not define the complete matching behaviour. I would agree whether a term should match the title, a chosen custom field, or a combination before changing the query.

Confirm the right content types are included

A site might store its directory entries, resources or services as custom post types. WordPress's post type registration reference includes an exclude_from_search setting controlling inclusion in front-end search results.

I would inspect that registration alongside any filters or plugin rules restricting the search. An item can be publicly viewable while a particular search implementation excludes its content type. I would also check its publication status and the intended audience.

Broadening a search to every record is not a sensible default. The requirement should identify which content is intended to be discoverable by each user.

Can visitors find the content they need?Send me a few search terms and the pages or records you expect to appear. I can review the search implementation and scope a targeted improvement.
Discuss your site search with Adam

Trace the stored value and the displayed result

A custom field may store a simple text value, an identifier or a relationship to another record. I would inspect the actual structure and the public text it represents. Searching the stored identifier would not necessarily find the label a visitor can see.

I would also check the result template. A correct match can be hard to recognise if its card shows a generic title, omits the relevant reference or links to the wrong destination. Search quality includes how the result explains itself.

Where an existing search engine maintains a separate index, I would check its field configuration, indexing status and update process. The investigation should establish whether a missing item was excluded, never indexed or left stale after an edit.

Define useful matching and ranking rules

“Search everything” leaves several decisions unresolved. Should an exact reference number rank above a mention in a long article? Should a location match apply only to directory entries? Should archived resources appear below current ones?

I would use the agreed examples to define a modest set of matching and ranking rules. That might include exact reference matching, selected searchable fields, content-type filters or relevant public categories. Handling partial terms, alternative wording and spelling mistakes should be an explicit requirement where needed.

I would also review the empty-results experience: preserve the search term, explain the scope and offer a useful next step. A working search form needs to remain understandable on mobile and usable with a keyboard.

Choose a fix that fits the implementation

The review may point to an existing plugin setting, a faulty query filter, a missing index update or a small custom change. A more substantial search engine may be appropriate where the catalogue, matching requirements or traffic justify it.

I would compare the options against the agreed examples, ongoing maintenance and available hosting resources. Adding another search plugin without understanding the current request path can leave the original problem unresolved or introduce competing behaviour.

For a bespoke workflow, I have explained when custom WordPress plugin development is worth considering. The same principle applies here: identify the behaviour the business needs, then choose an implementation that can be supported.

Include performance and access rules in the review

I would measure representative searches against realistic content volumes before and after a proposed change. A search that finds a reference in a tiny test catalogue may behave differently with the full dataset. Any caching or indexing approach also needs a clear way to reflect edits and removals.

The list of searchable fields should be deliberate. Internal notes, customer details and private records should not become searchable simply because a developer includes all metadata. Where results vary by account, I would test both result access and the text shown in snippets.

Search visibility is only one part of access control. The destination content and any custom endpoint need their own appropriate checks. My article on planning WordPress staff roles and permissions covers the wider access discussion.

Verify the search after content changes

I would retain the agreed search examples as a small acceptance set and test them on a suitable copy of the site. The checks should include:

  • A title match and a match in each intended custom field.
  • A public custom content type that should appear.
  • A private or excluded item that must remain undiscoverable to the tested user.
  • An edited or removed record, including any index refresh.
  • Ranking, pagination, empty results and representative response times.

After release, I would review further examples of unsuccessful searches and decide whether the issue is missing content, matching logic or presentation. Those observations provide a better basis for the next improvement than promising a particular conversion increase.

My WordPress development work includes custom themes, plugins, integrations and usable admin interfaces. You work directly with me, Adam Dawson, to agree the search requirements and scope the appropriate changes.

Make your WordPress content easier to findTell me what visitors search for, what they should find and where the current results fall short. I can help trace the missing data and plan a tested improvement for your site.
Talk to Adam about your searchExplore WordPress development

Need a hand with this?

Get direct help with a WordPress fault, a custom feature or the regular upkeep of your website.

Talk directly to Adam

Share this article

Back to Blog