Content Demand: find questions your site search could not answer
Visitors have already told you what they wanted to know. Review the WordPress searches that returned no results, then decide which answer needs attention.
A failed search can mean two different things.
A visitor searches a venue website for “step-free access” and gets no results. The answer may be missing, or it may already appear on a page called “Accessibility.” Those problems need different fixes.
Content Demand groups searches with no results so an editor or an authenticated MCP assistant can investigate repeated terms. The records show what visitors failed to find through that search; they do not prove that another article is needed.
Find the existing answer first. Add new information only when the useful answer is missing.
See the repeated questions. Keep the decision with each one.
Two authenticated abilities let an assistant list candidates and update their status or notes. Both require the WordPress user to have permission to edit pages.
Find terms worth reviewing
Filter by the number of searches with no results and review status. Frequently recorded terms appear first. Counts represent searches, not unique visitors or confirmed customers. Common bot user agents are excluded, but the filter cannot identify every automated request.
Record what needs to happen
Keep the evidence and next action in a note. Set the status to
new, planned, published, or ignored. Marking a candidate as published does not create or publish a WordPress page.Choose the fix that helps the visitor.
For the step-free access example, check the venue’s existing information and confirm the facts before deciding what to change.
The answer already exists
Make the wording easier to find. Add the relevant search wording to the accessibility explanation where it fits, then repeat the search and check that it returns the useful page.
The answer is missing
Confirm the entrance, route, and restrictions with the venue. Add a clear answer to the appropriate page. Create a separate page only when the subject needs one.
The search does not fit the site
Record why the term is irrelevant and mark it ignored. Frequent searches alone are not a reason to publish unrelated content.
Check the capture path and the data you keep.
Automatic capture covers frontend searches that run through WordPress and return no results. Static search and third-party search services that bypass that request are not captured automatically. The plugin provides no WordPress admin report, article generator, or automatic publication.
Search terms can contain personal information. Normalisation removes URL-like terms and the personal part of email addresses, but does not guarantee anonymity. New URL context stores only web origins; older records are not cleared. There is no automatic retention policy or deletion ability. Decide whether recording terms suits your site before enabling it.
Turn unanswered searches into a useful next action.
Install Content Demand when your site uses WordPress search and your editorial team works through MCP. Requires WordPress 6.9 or later, PHP 8.0 or later, WordPress MCP Adapter, and MCP Expose Abilities.