Website intelligence
Use SimilarWeb endpoints to turn website intelligence into repeatable API requests with documented inputs and JSON responses.
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
Use SimilarWeb endpoints for website traffic, ranking, and market intelligence workflows.
Endpoint families
2
Documented params
4
Examples
2
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
4
Schema refs
2
{
"platform": "SimilarWeb",
"endpoint": "similarweb-search",
"method": "GET",
"path": "/similarweb/search",
"auth": "apiKey"
}Related use cases
Free tools
Use cases
Use SimilarWeb endpoints for website traffic, ranking, and market intelligence workflows.
Use SimilarWeb endpoints to turn website intelligence into repeatable API requests with documented inputs and JSON responses.
Use SimilarWeb endpoints to turn competitive benchmarking into repeatable API requests with documented inputs and JSON responses.
Use SimilarWeb endpoints to turn market research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live SimilarWeb endpoint catalog — 2 endpoints, 4 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented SimilarWeb endpoints, grouped into 2 request families — Search and Web.
4 request parameters are documented across those SimilarWeb endpoints, 4 of them required — the full input contract is public before you write any integration code.
2 of the 2 SimilarWeb endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
SimilarWeb endpoints document their error responses (400, 429 and 500) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the SimilarWeb endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/similarweb/search
/similarweb/web/{domain}
Endpoint catalog
/similarweb/searchReturns SimilarWeb data for a given query (typically a domain).
MCP tool similarweb_search
/similarweb/web/{domain}Returns traffic and engagement data from SimilarWeb for a specific domain.
Response notes
- Requests that exceed your plan's credit or rate limits are rejected before the lookup runs. The `402`/`429` body reports `reason` — one of `insufficient_credits`, `daily_credit_limit`, `rate_limited`, `ip_rate_limited` — along with your position against that limit and `reset_scope`, the window that clears it: one of `daily`, `monthly`, `minute`, `ip_window`. This contract is shared by every credit-billed endpoint; see [Billing Rejections](billing-rejections.md) for the full field list and examples. Example response: ```json { "code": 200, "msg": "OK", "data": { "Version": 1, "SiteName": "openai.com", "Description": "We believe our research will eventually lead to artificial general intelligence.", "TopCountryShares": [ { "Country": 840, "CountryCode": "US", "Value": 0.2119 } ], "Title": "OpenAI", "Engagments": { "BounceRate": "0.478", "Month": "7", "Year": "2026", "PagePerVisit": "2.31", "Visits": "128455321", "TimeOnSite": "103.5" }, "AiTrafficDetails": { "TotalVisits": 40471810.45, "ReferralTraffic": 0.20555688559222743, "TopPrompts": { "Status": 0, "ErrorMessage": "", "Prompts": [ "What are the main differences between current large language model architectures?" ] }, "Traffic": { "Split": [ {"Name": "chatgpt.com", "Rank": 1, "Icon": "/image?url=chatgpt.com"} ], "Distribution": { "Boundary": "<100M", "Chatbots": [ {"Name": "chatgpt.com", "Icon": "/image?url=chatgpt.com", "Value": 84.77} ], "Chart": [ { "Name": "chatgpt.com", "Icon": "/image?url=chatgpt.com", "History": [ {"Date": "2026-07-01", "Value": 84.77} ] } ] } } }, "DataSource": "extension_api" } } ```
MCP tool similarweb_web
Related APIs
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Use a Brand Data API to turn any domain into a normalized brand profile — title, description, slogan, brand colors, logos and icons, social profiles, footer links, and schema.org organization data — as structured JSON for enrichment, branding, and research workflows.
How to scrape SimilarWeb
SimilarWeb's own API is a contract-gated enterprise product. Crawlora's 2 SimilarWeb endpoints cover the public surface instead: a search that resolves a query — usually a domain — and a web-info call that returns SimilarWeb's public data for that site as normalized JSON.
Send a query, typically a domain, to the search endpoint to confirm SimilarWeb has a profile for it.
The web endpoint takes a domain and returns SimilarWeb's public data for that site as normalized JSON.
Iterate a list of competitor domains through the same call to build a side-by-side table instead of reading one profile at a time.
FAQ
No. Crawlora is not affiliated with SimilarWeb. Its official API access is not sold on any self-serve plan (those top out around $649/mo with no API included) — it only ships through an Enterprise contract commonly quoted at $75,000-$200,000+/year or a separate standalone API purchase. These endpoints read the public SimilarWeb surface and return it as JSON, which suits research and enrichment rather than licensed redistribution.
A bare domain such as example.com. Use the search endpoint with a free-text q if you are not sure a profile exists, and the web endpoint with the domain once you do.
They are SimilarWeb's modelled estimates, not measured analytics from the site itself. Treat them as directional for competitive comparison, and never as a substitute for a site's own analytics or server logs.