Publishers on WordPress still spend hours jumping between Trends tabs, social dashboards, and docs. Trends MCP lets the same assistant that drafts posts in the block editor call normalized search, news, and social series through MCP or REST.
Editorial teams on WordPress rarely lack ideas; they lack a fast way to check whether an idea already peaked in search, video, or news. Trends MCP hands those checks to the assistant already open beside the block editor. get_trends returns dated arrays for each source and keyword, while get_growth summarizes momentum with explicit windows in a single call.
Queries like WordPress SEO trend data, editorial calendar API, and newsroom keyword research often point to plugins or agency retainers. Trends MCP sits upstream: it supplies structured demand signals that any plugin, custom theme, or headless front end can consume through the documented POST endpoint.
The workflow begins with a candidate headline term. Editors call get_trends on google search and google news to see whether interest is sustained or a one day spike. If the piece has a video component, adding youtube or tiktok clarifies whether discovery platforms still carry the topic. Before publishing, get_growth with percent_growth values such as 30D and 12M gives a tight summary for stakeholder notes. When the newsroom needs a pulse without a keyword yet, get_top_trends against Google Trends or Google News Top News surfaces live leaders.
Rank trackers and on page tools still handle crawl issues and SERP positions. Trends MCP answers a different question: is attention rising or falling before the draft ships? The data belongs in the research paragraph of the brief, not as a replacement for Search Console metrics.
Technical SEO leads can deepen keyword work on SEO keyword research. Teams that want calendar ready rituals should read editorial calendar trends inside AI and content strategy.
FAQ