Content Trend Research Tool — BuzzSumo Alternative

Research cited content for a topic, brand, or publisher domain. Export articles, citation metrics, phrase trends, sentiment slices, or summary rows to compare coverage and prepare source-linked content research. For content teams, dataset row meaning follows the selected report: cited article, phrase trend, sentiment slice, or summary.

Workflow: put the results to work

Choose a topic or publisher and the report mode that matches the question. Inspect cited articles before comparing phrase trends or sentiment summaries. Citation metrics describe the selected source coverage and should not be presented as universal social-share counts.

Best fit for this Actor

• Find cited articles for a topic such as content marketing, with publisher domain, snippet, citation score, and sentiment polarity.
• Score how a brand is discussed across news, blogs, and other indexed page types in one summary row.
• Chart citation volume by month, then keep the publishers that show up most often.

When you need live Google Search ads or organic SERP HTML instead of citation research, start with Google SERP All-in-One Scraper. After you pick stories to watch in news, continue with Google News Scraper.

Quick start input

{
  "mode": "content_search",
  "keyword": "content marketing",
  "maxResults": 5,
  "searchMode": "one_per_domain"
}

keyword is the topic or brand. domain is only required for domain_content.

Input reference

Field	Type	What it controls
mode	enum	content_search, content_summary, phrase_trends, sentiment, or domain_content. Default content_search.
keyword	string	Topic or brand. Example: content marketing.
domain	string	Publisher hostname for domain_content. Example: hubspot.com.
maxResults	integer	Row cap 1–100. Default 5. Summary still writes at most one overview row.
searchMode	enum	one_per_domain (default) or as_is.
pageTypes	array	Optional ecommerce, news, blogs, message-boards, organization.
countryCode	string	Optional ISO country such as US.
dateFrom	string	yyyy-mm-dd start for phrase_trends. Defaults to six months back.
dateGroup	enum	month (default), week, or day.

Owner API credentials are already configured for Store runs. This Actor does not accept user API keys.

What data you receive

One dataset item is one cited article, summary, trend bucket, or sentiment slice.

{
  "mode": "content_search",
  "keyword": "content marketing",
  "url": "https://blog.hubspot.com/marketing/content-marketing",
  "domain": "hubspot.com",
  "title": "The Ultimate Guide to Content Marketing",
  "snippet": "How teams plan, produce, and measure content that earns citations.",
  "citationScore": 5900.94,
  "dominantSentiment": "positive",
  "facebookLikeCount": 13,
  "source": "buzzsumo_alternative/content_search",
  "status": "OK",
  "fetchedAt": "2026-08-22T00:00:00.000Z"
}

Field	Meaning
citationScore	Prominence of this citation in the index, not a Buzzsumo viral score
facebookLikeCount	Indexed Facebook embed likes when present; not a live share graph
dominantSentiment	Highest of positive / negative / neutral on the citation text
source	Mode provenance label for the row

OUTPUT and RUN_SUMMARY in the default key-value store hold outcome, itemsPushed, chargedEventCounts, and providerCostUsd. Download the dataset as JSON, CSV, Excel, or HTML.

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~buzzsumo-alternative/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"content_search","keyword":"content marketing","maxResults":5}'

Use with AI agents through Apify MCP

Find Buzzsumo-style cited articles for content marketing. Return title, url, domain, citationScore, dominantSentiment, facebookLikeCount, source, and fetchedAt. Read OUTPUT.outcome and itemsPushed. Treat citationScore as an index prominence score rather than a Buzzsumo viral share count.

Connect via https://mcp.apify.com. Review the Pricing tab for the current request and result event rates, plus platform usage.

Connect the workflow

• For current news headlines after you pick a topic, continue with Google News Scraper.
• For search-interest over time instead of citation volume, continue with Google Trends Scraper.
• For live Google Search results and ads after you choose phrases, continue with Google SERP All-in-One Scraper.

How it works

1. Normalize the topic, domain, and filters for the selected mode.
2. Call the matching owner-managed content analysis endpoint for that mode.
3. Charge content-api-request after each successful task.
4. Charge content-record, then write each validated dataset row.

Best results

• Use a real topic such as content marketing rather than a Buzzsumo app URL.
• Keep maxResults at 5 while you confirm the output shape, then raise it for exports.
• Treat sentiment, citation scores, and Facebook likes as indexed estimates, not live social graphs.
• A valid query with no match finishes SUCCEEDED with VALID_EMPTY.

Builder's note

I found that classic Buzzsumo workflows still ask teams to sit in a login-walled app for “what content is cited around this topic,” while Store scrapers that promise viral Facebook shares leave share counts unread when platforms no longer expose them. Routing this SKU through owner-managed citation APIs keeps the Buzzsumo-shaped jobs (articles, summary, trends, sentiment, domain content) without claiming Buzzsumo viral scores, scraping Buzzsumo, or asking buyers for API keys. Facebook likes are only written when the citation index includes an embed metric.

Legal and responsible use

Use this Actor with public content research you are authorized to run. Metrics are independent of BuzzSumo / Brandwatch. Follow applicable law and the upstream data provider terms, and keep the output in your own compliance workflow.

Issues and feature requests: use the Actor Issues tab on Apify.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
content-api-request	Content API request	Charged once for each successful upstream content API task used to build the report.
content-record	Content record	Charged once for each validated citation, summary, trend, or sentiment row persisted to the dataset.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Independent alternative

This Actor provides the specific workflow described above. It is not affiliated with or endorsed by BuzzSumo; the named product and its trademarks belong to their respective owners.