Google Trends Content Calendar Generator
Pricing
from $0.50 / 1,000 results
Turn Google Trends data into a dated content calendar — auto-prioritized publishing slots for rising, breakout, and evergreen keywords.
Pricing
from $0.50 / 1,000 results
Rating
0.0
(0)
Developer
Group Oject
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 hours ago
Last modified
Categories
Share
List of keywords to analyze. You can also paste keywords as text in the next field.
Paste one keyword per line, or comma-separated. Useful for bulk uploads (hundreds to thousands).
Google Trends geo code (e.g. US, GB, CA, AU, MA, FR, DE). Use an empty string for Worldwide.
Google Trends time window.
Google Trends category ID (default '0' = all categories).
Fetch top + rising related queries for each keyword.
Fetch related topics (entities) for each keyword.
Generate deterministic content angle suggestions based on trend status and related queries.
Maximum number of keywords to process. Excess keywords are truncated with a warning.
Delay between requests to avoid rate limiting. Recommended: 800–2000ms.
Number of keywords processed in parallel. Keep low (1–4) to avoid 429 errors.
How to fetch Google Trends data. 'serpapi' (recommended): bring your own free SerpApi key — works on any Apify plan, no proxy fight. 'apify-scraper': calls Apify's official google-trends-scraper Actor (requires Apify Starter+ plan). Other modes scrape directly and require working proxy access.
Required when fetchMode is 'serpapi'. Get a free key (100 searches/month) at https://serpapi.com. Your key is never logged.
Extra dwell time after page load to let late XHRs fire. Increase if related-queries are missed.
Use Apify Proxy (recommended: residential or Google SERP groups for best reliability).
First publish date (YYYY-MM-DD). Defaults to tomorrow.
How many content slots to schedule each week.
How many weeks to plan ahead. Total slots = postsPerWeek × calendarWeeks.
Formats to rotate through across slots (blog, video, social, newsletter).
[ "blog"]If true, declining keywords are scheduled as 'refresh existing content' tasks instead of being dropped.
If true AND debugMode is true, use synthetic data instead of fetching Google Trends. Useful for testing the pipeline.