The signal
Start your content decision with a search that returned no result
Content Demand tracks zero-result site searches and exposes content-demand candidates through MCP abilities. For a WordPress operator, each candidate makes the next content decision concrete: it is a term the site could not answer, not a broad guess about what to publish.
If a search returns no result for a service the site does not cover, evaluate that term as a candidate for the content plan. The decision remains the operator’s; the AI client uses the Content Demand surface to work with the candidate records.
Searches are aggregated by normalized term hash. Email-like searches are reduced to their domain, avoiding storage of full email addresses.
Supported operations
Give your AI client a focused candidate surface
List candidate records
Update one candidate
A practical review route
Turn a search gap into a content choice
01
Inspect the demand
02
Choose the response
03
Update the record
Required foundation
What Content Demand requires
Required with WordPress 6.9 or newer
WordPress Abilities APIRequired
PHP 8.0 or newerRequired
WordPress MCP AdapterRequired
MCP Expose AbilitiesNext step
