LSD
APIEndpoint 15 of 40Keyword Research / Trends / Seasonality & Growth

Google Trends API

The trend curve API for the new local SEO stack.

Google Trends has been free on the web for years, but locked behind a manual UI. Glimpse built a browser plugin ($79+/mo) to expose it. Exploding Topics built a trend discovery tool ($39+/mo). We expose the underlying trend curves as a clean API — historical monthly interest scores (0-100 scale), peak months, and trend direction (rising, stable, declining). Five keywords per call, 3-month to 5-year historical windows. 1 credit ($0.005) per query. Your agent detects seasonality and times content and ad spend accordingly.

Start Free — 50 CreditsView Docs

POST /v1/keywords/trends · 1 credit / query

POST /v1/keywords/trends5 of 25
12-mo trend curves
KeywordVolumeCPCTrend
plumber near me12,100$45.20
emergency plumber austin2,400$38.50
best plumber austin tx880$22.10
pipe repair cost590$12.40
drain cleaning austin720$18.90
▌ Ask your agent

These prompts are the new seasonality workflow.

Connect Local SEO Data as an MCP server once (60 seconds, below). Then your agent detects seasonal patterns, forecasts peaks, and optimizes ad spend timing. Replace bracketed keywords or locations with your own.

Seasonality detection

Pull 12-month trends for [plumber, emergency plumber, pipe repair] in [Denver]. Highlight which months see peak searches. When should we ramp ad spend?

Multi-location seasonal comparison

Get trend data for [roof repair] across [Denver, Austin, Seattle, Miami]. Show me which markets peak in winter vs summer. What's the geographic pattern?

Emerging trend detection

Compare 5-year trends for [tiktok shop, ai overview, local seo] in [United States]. Flag any with trend_direction 'rising'. Which should we pivot budget toward?

Content calendar planning

Pull annual trends for all [12 service categories] our agency offers. Build a month-by-month content calendar around peak search months for each category.

▌ Real response

What you get back

Live response for trend queries in Denver. Real API response, May 2026.

response · application/json~2-4s · 1 credit
{
  "status": "success",
  "credits_used": 1,
  "data": {
    "location": "Denver, Colorado, United States",
    "period": "12m",
    "trends": [
      {
        "keyword": "plumber",
        "data_points": [
          { "month": "2025-05", "interest": 68 },
          { "month": "2025-06", "interest": 65 },
          { "month": "2025-07", "interest": 58 },
          { "month": "2025-08", "interest": 52 },
          { "month": "2025-09", "interest": 60 },
          { "month": "2025-10", "interest": 72 },
          { "month": "2025-11", "interest": 85 },
          { "month": "2025-12", "interest": 92 },
          { "month": "2026-01", "interest": 95 },
          { "month": "2026-02", "interest": 88 },
          { "month": "2026-03", "interest": 75 },
          { "month": "2026-04", "interest": 70 }
        ],
        "peak_month": "2026-01",
        "trend_direction": "stable"
      },
      {
        "keyword": "emergency plumber",
        "data_points": [
          { "month": "2025-05", "interest": 62 },
          { "month": "2025-06", "interest": 58 },
          { "month": "2025-07", "interest": 48 },
          { "month": "2025-08", "interest": 42 },
          { "month": "2025-09", "interest": 55 },
          { "month": "2025-10", "interest": 68 },
          { "month": "2025-11", "interest": 82 },
          { "month": "2025-12", "interest": 90 },
          { "month": "2026-01", "interest": 100 },
          { "month": "2026-02", "interest": 92 },
          { "month": "2026-03", "interest": 78 },
          { "month": "2026-04", "interest": 65 }
        ],
        "peak_month": "2026-01",
        "trend_direction": "stable"
      }
    ]
  }
}
▌ Returns

Exactly what agents need to time content and ad spend

Monthly interest curve

12 data points (or 24/60 for longer windows)

Each month gets a relative interest score (0-100 scale, where 100 = peak interest in the queried region and time period). Plumbing peaks in winter at 92-95 interest; summer bottoms out at 52-58. Your agent detects the curve and identifies the ramp-up and decline periods.

Peak month

When demand is highest

Extracted automatically. For 'plumber' in Denver, peak_month is '2026-01' every year. Your agent flags this for content pushes and ad spend ramps 3-4 weeks prior.

Trend direction

Rising, stable, or declining

Summarizes the multi-year direction. 'ai overview' is rising. 'facebook ads' is stable. 'print marketing' is declining. Your agent prioritizes rising keywords for investment.

Geographic and temporal flexibility

Location-scoped, 3-month to 5-year windows

Query trends for any city or state. Set period to '3m', '6m', '12m', or '5y'. Short windows catch recent momentum; long windows reveal multi-year patterns. Same keyword has different seasonality in Denver (winter plumbing peaks) vs Miami (no winter peak).

▌ Built for

What SEO operators ship with this endpoint

Seasonal content planning

Agencies pull trend data for all client service categories (plumbing, HVAC, landscaping, roofing). Map content calendar to peak months. Write blog posts and landing pages 4-6 weeks before each peak so Google can index and rank them by the time demand surges.

→ For agencies

Ad spend optimization

Multi-location PPC operators pull trends across 5-10 markets. Increase bid strategy and daily budgets 6 weeks before local peaks. Dial back spend in off-season. Winter contractors ramp up in October; landscapers in March. One API call per location per quarter keeps budgets synchronized to demand.

→ For PPC teams

Emerging trend detection

Pull 5-year trends for high-growth keywords ('ai overview', 'tiktok shop', 'local seo'). Compare them to stable keywords ('plumber', 'dentist'). Identify which emerging keywords are rising in your market and shift content strategy before competitors catch on.

→ For content strategists

Franchise resource allocation

Franchise networks pull trend data for all locations and service categories. Headquarters allocates marketing budget to franchises based on local seasonal demand. Some franchises peak in winter, others in spring — same network, different budgets per location.

→ For franchises
▌ vs. the alternatives

Why not use Google Trends (free), Glimpse ($79+/mo), or Exploding Topics ($39+/mo)?

Google Trends is free but manual. Glimpse and Exploding Topics sell dashboards. Here's how the API model beats the dashboard approach for agents and automation.

ToolCost modelData accessBulk queriesAgent-ready
Google Trends (free UI)Free (but manual)Web UI only, one keyword at a timeNo batch APINo API, screenshot-based
Google Trends API (alpha, limited)TBD (currently alpha/gated)Official but restricted to alpha testersLimited quota accessAPI-based but gated to small cohort
Glimpse ($79+/mo)$79–299/mo per seatBrowser extension overlaying Google TrendsLimited, extension-basedExtension, not API-native
Exploding Topics ($39+/mo)$39–99/mo per seatAggregates trends from Google, social, e-commerce, newsLimited dashboard exportNo native API, manual export
Semrush Topic Research (included)$139.95+/mo per seatSemrush's proprietary trend algorithmDashboard-driven batchingAPI available but secondary
Ahrefs Content Explorer (included)$129+/mo per seatAhrefs trend and content metricsLimited API integrationDashboard-first
DataForSEO Trends API ($0.001/task)$0.001 per queryProprietary normalized 0-100 scaleFull batch supportAPI-native but proprietary scale
LocalSEOData Google Trends API$0.005 per query, no seatsGoogle Trends-sourced (via DataForSEO upstream)Up to 5 keywords per call, unlimited callsNative MCP + REST, agent-first
▌ Connect in 60 seconds

Use it from your agent

Two integration surfaces: MCP for clients that speak MCP, REST API for everything else.

Direct MCP integration

Drop-in support in Claude Desktop, OpenClaw, Hermes Agent, and any MCP-aware client.

Add to your client's MCP config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "localseodata": {
      "url": "https://mcp.localseodata.com",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

REST API

For Perplexity Computer, ChatGPT Custom GPTs, custom agents, and any platform that calls REST endpoints directly.

Base URL:

api.localseodata.com

See the docs for endpoint reference and auth.

▌ Quickstart

Your first call in three lines

Same endpoint, three syntaxes. The `keywords` array accepts up to 5 keywords per call (to match Google Trends' limitation). `location` is required in 'City, State, Country' format. Optional: `period` ('3m', '6m', '12m', or '5y'; default '12m'). One call = 1 credit.

terminal · curl
POST /v1/keywords/trends
curl -X POST https://api.localseodata.com/v1/keywords/trends \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "keywords": ["plumber", "emergency plumber", "pipe repair"],
    "location": "Denver, Colorado, United States",
    "period": "12m"
  }'
Full endpoint reference → · Get an API key →
▌ Pricing for this endpoint

$0.005 per query

1 credit per trend query (supports up to 5 keywords per call). Free tier on signup includes 50 credits (50 trend queries). Monthly plans start at $19 and never expire. No per-seat fees, no team limits.

Free tier
50
trend queries on signup (50 credits)
Starter · $19/mo
3,800
queries/mo at this rate
Per-query cost
$0.005
or 1 credit per call
▌ FAQ

Common questions

What is the Google Trends API?+
A REST endpoint that returns historical search interest trends for up to 5 keywords in a specified location and time window. Each keyword returns monthly interest scores (0-100 scale, relative to peak interest in that region/period), peak_month, and trend_direction. The endpoint is POST /v1/keywords/trends. One call returns structured JSON with all trends and costs 1 credit ($0.005). Seasonality detection is the primary use case — plumbing spikes in winter, landscaping in spring, air conditioning in summer. This is the foundational endpoint for timing content and ad spend to demand curves.
Where does the Google Trends data come from?+
DataForSEO, our upstream provider. DataForSEO aggregates data from Google Trends (their public interface), Google's historical search metrics, and clickstream data from multiple sources, then normalizes it into the 0-100 scale you see in the API. Google's official Trends API is still in alpha (limited access), and DataForSEO provides the stable, production-grade alternative with enterprise SLAs. We're passing through their data transparently: $0.005 per query. Most competitive tools (Ahrefs, Semrush, Exploding Topics) use DataForSEO as their upstream source too — we're just not marking it up 100x via a per-seat subscription.
How fresh is the trends data?+
Trends data refreshes monthly. The current month's data is typically available within 2-7 days of month-end, depending on DataForSEO's aggregation timing. You'll see the newest month in your query results. Interest scores are cumulative for the month-to-date, not real-time hourly updates. That's fine for strategic content planning and ad spend optimization; it's not designed for intra-week bid adjustments.
What does the 0-100 interest scale mean?+
It's a relative scale. 100 = peak interest for that keyword in that region and time period. 50 = half the peak. 25 = quarter the peak. So 'emergency plumber' at 95 in January 2026 is almost at peak, while the same keyword at 42 in August is low-season. Absolute search volumes are not returned (use Search Volume API for that). The trend scale is purely comparative — it tells you *when* to push, not *how much* traffic you'll get.
Can I look up more than 5 keywords per call?+
No. The endpoint accepts a maximum of 5 keywords per call, matching Google Trends' own UI limit (you can compare up to 5 terms side-by-side on trends.google.com). If you need trends for 20 keywords, batch them into 4 calls. Most workflows compare 2-3 keywords per call anyway ('plumber vs emergency plumber vs plumbing services'). One call costs 1 credit, so 4 calls = 4 credits (~$0.02).
What time periods can I query?+
Four options: period: '3m' (last 3 months), '6m' (last 6 months), '12m' (last 12 months, default), or '5y' (last 5 years). Longer windows reveal multi-year patterns ('ai overview' rising sharply over 5 years). Shorter windows catch recent momentum ('tiktok shop' spike in the last 3 months). Each data point is monthly, regardless of window length.
How does this compare to Google Trends (free UI)?+
Google Trends is free but manual. You log in, type a keyword, click to compare, then screenshot or manually transcribe the data. It's one keyword at a time (or up to 5 side-by-side for comparison, but comparing takes manual interaction). The API is the same data, programmatic: five keywords in one REST call, JSON out, your agent does the rest. If you're doing trend research for 100 keywords across 10 locations, Google Trends' web UI would take days. The API does it in minutes.
How does this compare to Glimpse ($79+/mo)?+
Glimpse is a browser extension that overlays Google Trends data on your search results. It adds insight to your normal search workflow but is still dashboard-driven. You're also paying $79+/mo per seat. The API model is cheaper ($0.005 per query, no per-seat fees) and agent-native — your Claude instance runs the research, not a human clicking around an extension. For a consultant who checks trends once a month, Glimpse is probably fine. For an agency monitoring seasonality across 12 client locations weekly, the API wins on cost and automation.
How does this compare to Exploding Topics ($39+/mo)?+
Exploding Topics aggregates trends from Google, social media, e-commerce (Amazon, TikTok), news, and podcasts — so it's broader than pure Google search trends. It's designed to find emerging trends across the web, not specifically seasonal search demand. If your goal is 'spot viral TikTok trends,' Exploding Topics is better. If your goal is 'time my plumbing ad spend to winter peaks,' the Trends API is better because it's laser-focused on search demand. Exploding Topics costs $39+/mo; the API is $0.005 per trend query.
How does this compare to DataForSEO Trends API ($0.001/task)?+
DataForSEO's Trends endpoint costs $0.001 per task and uses their proprietary normalized scale (different from Google Trends' scale). LocalSEOData's version costs $0.005 per call and uses Google Trends-sourced data (via DataForSEO upstream). DataForSEO's raw API is cheaper by about 5x, but it's more complex to integrate (no MCP, no pre-built agent support). If you're already using DataForSEO for other endpoints and have SDKs set up, their API is fine. If you're looking for a simpler, agent-native alternative, this endpoint trades a small price premium for easier integration (MCP + REST, no SDK setup).
Can AI agents use this directly?+
Yes, two ways. MCP: Add Local SEO Data to your claude_desktop_config.json (or any MCP-compatible client like OpenClaw, Hermes Agent, etc.), and Claude calls this endpoint from your prompt without you writing integration code. You say 'pull 12-month trends for plumbing keywords in Denver' and it happens. REST: Any agent that can make HTTPS calls (ChatGPT Custom GPTs, Perplexity Computer, custom Python agents) hits api.localseodata.com with Authorization: Bearer sk_live_.... The agent receives structured JSON and can reason about peak months, seasonal patterns, and trend direction — 'January is peak, let's ramp content and budget in October.'
What changed in 2026 that made this category exist?+
Two things. First, Google announced their official Trends API in July 2025 as an alpha product for a limited number of testers. It's not broadly available yet. Second, MCP became mainstream through 2025, making it possible for agents to call external APIs without custom integration work. Together, these changes mean trend research flipped from a manual web UI task ('log in to Google Trends, type keywords, screenshot the curve') to an agent workflow ('pull trends for my 50 keywords, detect seasonality, suggest content timing automatically'). DataForSEO's Trends API has existed for years, but the MCP integration and agent-native positioning didn't. We're positioning the same upstream data for the new AI-driven workflow.
Do you support multi-location and multi-language trends?+
Yes to both. location is required and must be in 'City, State, Country' format (e.g., 'Denver, Colorado, United States'). Trends are always geographic — the same keyword has different seasonality in Denver (winter peak) vs Miami (no winter peak). language support is via DataForSEO's backend, so Spanish, French, German, etc. are all supported. Multi-location workflows are standard: franchises pull trends for all locations to understand local demand curves. Multi-language works too — 'plumber' (English) vs 'fontanero' (Spanish) may have different seasonal patterns in bilingual markets.
▌ Related endpoints

Often used in the same agent prompt

POST /v1/keywords/search-volume
Search Volume API

Validate seasonal trends with absolute volume, CPC, and monthly breakdown.

POST /v1/keywords/suggestions
Keyword Suggestions API

Expand seeds into variants. Pair with trends to find seasonal long-tails.

POST /v1/keywords/related
Related Keywords API

Semantically related keywords. Check trends for the whole cluster.

POST /v1/keywords/opportunities
Keyword Opportunities API

Rank keywords by difficulty vs your rank. Pair with trends for seasonal prioritization.

Time your content and ad spend to seasonal demand curves.

50 free credits on signup. 50 trend queries included. Pull 12-month trends for your target keywords in your first agent prompt.

Start FreeRead the docs
▌ MADE FOR THE NEW LOCAL SEO STACK