Semrush Trends API
Competitive traffic and market trend analysis using Semrush-provided estimates
Coverage: Data available to the authorized account, project or eligible market · Market and traffic trend metrics for supported domains and markets
Competitive intelligence · Website technology detection and software adoption
Enrich inbound domains or build-account lists with detected frameworks, analytics, payment, hosting, and other technologies to prioritize integration prospects and tailor developer-tool outreach. SaaS founders, developer-relations teams, GTM engineers, agencies, and product teams doing stack-aware lead qualification or competitive research.
Put it to work
Enrich inbound domains or build-account lists with detected frameworks, analytics, payment, hosting, and other technologies to prioritize integration prospects and tailor developer-tool outreach. SaaS founders, developer-relations teams, GTM engineers, agencies, and product teams doing stack-aware lead qualification or competitive research.
Use the available company, website or technology signals to decide which competitors or market segments deserve closer research. Validate promising signals before using them for targeting.
What it covers
Geography: Use the geography stated by the source; coverage can vary by dataset and release.
Granularity: Enrich inbound domains or build-account lists with detected frameworks, analytics, payment, hosting, and other technologies to prioritize integration prospects and tailor developer-tool outreach.
Source type: Website technology detection and software adoption
Access and cost
Commercial API requiring an API key and credits: the lookup documentation specifies 10 requests/second, up to 10 URLs per request, one credit per URL (five with live plus recursive), and links to plan comparison.
Cost: Free account includes limited website lookups and sample lead lists. Paid plans provide lead lists, API access and CRM integrations.
Update cadence: Release cadence was not normalized in this review; check the source's dates, update notes, and API limits before comparing periods.
Before you use it
Detection is inference from observable website evidence and may be absent or stale; recursive/live crawls are asynchronous and the initial response may contain no technologies, and credits are charged per URL.; Lookup is URL/domain based; the fetched API documentation does not specify a country coverage boundary. Company-location fields may be returned when available, but should not be treated as complete geographic coverage.; Default results favor recent verification (max_age defaults to two months); historical grouping is limited to up to 12 months per request, while live mode triggers a crawl that can take up to 15 minutes.