Compare Google search traffic estimates for two domains

Paste two website links to compare their estimated monthly traffic from US Google searches. See unpaid results and ads separately, with separate counts of search-result pages containing each site. These are estimates, not actual visits.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use google-compare-domain-traffic-dataforseo to compare the two public website links supplied by the user. Prepare each link in the format this Tool accepts by removing its http:// or https:// beginning, a leading www., and any page path or query; submit exactly two domain names. Never ask the user to extract or edit a domain or provide an ID. If either link does not clearly identify a public website, ask for the correct website link in plain language. Reuse the existing Toolmu connection or follow https://toolmu.com/SKILL.md. Check current availability and price, and execute only within the existing authorization and budget. The search scope is fixed to US Google results in English. Match returned records by domain, preserve zero, null and missing values as distinct, and do not invent data. Explain that monthly traffic figures are estimates, not actual visits; keep non-ad and ad estimates separate from result-page counts. Do not claim a specific estimate month or data freshness unless returned.

Task:
Compare [https://openai.com] and [https://anthropic.com] in U.S. Google searches. Show estimated monthly visits from regular results (not ads) and ads separately, plus the search-result page count for each site. Estimates are not actual visits.

Paste into your connected AI's conversation.

Connection guide

Up to 0.02224 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Google

Compare Google search traffic estimates for two domains

You receive

Receive domain records with available monthly organic and paid traffic estimates, plus separate counts of search-result pages containing each domain. Your Agent can arrange these values side by side to compare search visibility.

Start with your task

Compare [https://openai.com] and [https://anthropic.com] in U.S. Google searches. Show estimated monthly visits from regular results (not ads) and ads separately, plus the search-result page count for each site. Estimates are not actual visits.

What to know

DataForSEO estimates do not measure actual visits or total website traffic. The search market is fixed to the US and English; you cannot choose a country or month, and no specific estimation month is supplied.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Two domains`domains`	`array`	Required	Required list of exactly two bare domains. The comparison uses fixed US-English Google organic and paid search data. Minimum items `2` Maximum items `2`
One domain`domains[]`	`string`	—	A domain name containing 3–253 characters. Omit https:// and www. prefixes; supply a domain rather than a page URL. Minimum length `3` Maximum length `253`

View raw JSON

{
  "type": "object",
  "required": [
    "domains"
  ],
  "properties": {
    "domains": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 253,
        "minLength": 3,
        "description": "A bare domain such as example.com, without https:// or www."
      },
      "maxItems": 2,
      "minItems": 2,
      "description": "Exactly two bare domains to compare."
    }
  },
  "additionalProperties": false
}

Result schema

No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.

Result schema
Field / Path	Type	Meaning
Compared domain`trafficEstimates.items[].target`	`string`	Target associated with this record, when returned. Match records by target rather than assuming submission order.
Organic monthly traffic estimate`trafficEstimates.items[].metrics.organic.etv`	`number`	Available modeled monthly traffic from organic search. It is an estimate, not a measured visit count; retain its numeric precision.
Organic search-result page count`trafficEstimates.items[].metrics.organic.count`	`number`	Supplier organic search-result pages containing the domain, when reported. This count is separate from traffic estimates and keyword search volume.
Paid-search monthly traffic estimate`trafficEstimates.items[].metrics.paid.etv`	`number`	Available modeled monthly traffic from paid search. It does not measure advertising spend or actual campaign visits.
Paid search-result page count`trafficEstimates.items[].metrics.paid.count`	`number`	Supplier paid search-result pages containing the domain, when reported. Keep this count separate from paid traffic estimates.
Search engine`trafficEstimates.se_type`	`string`	Search engine reported for the returned container. This Tool requests Google data.
Search market code`trafficEstimates.location_code`	`number`	Reported location context, when present. This Tool requests the United States with code 2840; the code is not a visitor-location breakdown.
Search language code`trafficEstimates.language_code`	`string`	Reported language context, when present. This Tool requests en for English; it is not a measurement of visitors’ languages.
Returned domain records`trafficEstimates.items_count`	`number`	Number of records in the returned items array, when reported. Submitting two domains does not guarantee two populated records.
Relevant database results`trafficEstimates.total_count`	`number`	Supplier-reported database results relevant to the request, when available. It is distinct from the number of returned records even when the values match.

Additional notes

DataForSEO models traffic using click-through rates and search volumes for the keywords a domain ranks for. Compare organic estimates with organic estimates and paid estimates with paid estimates, using the same search scope.

See the supplier’s traffic-estimation documentation for the metric definitions.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

DataForSEO combines click-through-rate and search-volume values for the keywords a domain ranks for in each result category. The monthly estimate is modeled search traffic, not a count from the site’s analytics. Paid traffic estimates also do not measure advertising spend.

Compare Google search traffic estimates for two domains

Compare Google search traffic estimates for two domains

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Add two website links

See what is compared

Understand the results

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Add two website links

See what is compared

Understand the results

Questions about this tool.

How is the traffic estimate calculated?

What does the search-result count tell me?

How should I read zero or missing values?

Which month do the estimates describe?