publisher: Similarweb Inc. version: G-1.0.0 effective: 2026-09-24 schedule: G materiality: material changes: Initial Similarweb Traffic Data Source Schedule.

Source Schedule G: Website Traffic Metrics (Similarweb)

Schedule version: G-1.0.0. Provider: Similarweb Inc., of New York, New York. Provider Terms incorporated: none. You do not contract with Similarweb; its requirements for this data are stated here.

G.1 The data. Estimated traffic and engagement metrics for a website, at daily, weekly, or monthly granularity: total visits, unique visitors, pages per visit, bounce rate, average visit duration, desktop and mobile traffic share, marketing channels, top countries by visits, incoming traffic including referrals from AI platforms, and desktop and mobile paid-search spend (the "Traffic Data"). Traffic Data describes websites, not people. It consists of estimates Similarweb generates from its own and third-party sources.

G.2 Approved Use. Using Traffic Data at request time within your own products and workflows, including a web application, an API, an SDK, a CLI, an MCP server, or an agent: to answer the query that fetched it, to rank, filter, and orchestrate within that query or session, and to show the result to your users, including your customers and their end users, one query at a time.

G.3 Restrictions. You will not, and will not permit anyone acting through your account to:

(a) Cache, store, replicate, or reuse Traffic Data. Each data point may be used only to respond to the query that fetched it, within the active session, and may not be retained or repurposed for a later or unrelated query. An Automated Agent may hold it only for the session in which it was fetched.

(b) Place Traffic Data into any permanent search index, database, or dataset, or otherwise permanently ingest it.

(d) Make Traffic Data available in bulk: no bulk download, export, or extraction, no data feed or stream, and no bulk delivery through an API or other programmatic interface. Delivery one query at a time through your product is permitted.

(e) Use Traffic Data to develop or commercialize a product or service that could reasonably substitute for Similarweb's website traffic analytics products. Using Traffic Data within your product as this Schedule permits is not a violation.

(f) Exceed, or use more than one account to exceed, the monthly limit Firecrawl applies to this source.

G.4 Attribution. Firecrawl delivers attribution with Traffic Data. Wherever you show Traffic Data, or anything derived from it, to a person, keep that attribution: on a web page, the Similarweb logo, a link to www.similarweb.com, and the words "Insights by Similarweb"; in an API, SDK, CLI, MCP, agent, or other non-page response, Similarweb's name and a link to www.similarweb.com in the source or attribution metadata; in each case in keeping with Similarweb's branding guidelines at https://www.similarweb.com/corp/legal/branding-guidelines/.

G.5 Your users. If you make Traffic Data, or anything derived from it, available to your own end users, you will first bind them to terms substantially equivalent to G.6, and you remain responsible under Section 1.5 for their compliance with G.3 and G.4.

G.6 What you are accepting about the data. Traffic Data consists of estimates. Neither Similarweb nor Firecrawl is responsible for its accuracy or completeness, and you release each of them from liability for any decision that you or anyone else makes in reliance on it, in whole or in part. Traffic Data is provided as-is, and claims arising from your use of it are your responsibility under Section 10.

G.7 End of access. When your access to this source ends, you will receive no further Traffic Data. Because G.3(a) permits no retention, nothing is held to delete; if any Traffic Data nonetheless remains in your systems, delete it at once. This clause is the rule Section 7.1 refers to.

G.8 Suspension. Firecrawl may suspend or terminate your access to Traffic Data or to the Services on breach of this Schedule, or where Similarweb requires it, and will do so at once where needed to stop unauthorized bulk distribution. This Schedule survives for as long as you use Traffic Data.