Compare Organic and Paid Search Traffic History · Ahrefs

Provide a domain or URL and a starting date to compare historical estimates of monthly organic and paid search traffic. Choose daily, weekly or monthly date grouping, within a range of at most 60 groups.

Your AI

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Use traffic-history-ahrefs (Tool ID 036c9622-b6ff-45e0-a2ae-077584363d84). Reuse my Toolmu connection or follow https://toolmu.com/SKILL.md, within my current authorization and budget. Ask for target and date_from if missing. Send queryParams target example.com, date_from 2026-07-01, date_to 2026-09-30, history_grouping monthly, country us, mode domain and protocol both. Keep the range within 60 chosen buckets. Arrange the available dates and show estimated monthly organic and paid search traffic separately, then describe changes. Grouping is the date interval, not measured daily or weekly visits. Do not sum dated estimates as cumulative traffic or the two channels as unique visitors. Preserve missing dates and values as unknown, not zero. Country omission, bucket aggregation, earliest coverage and effective calculation settings are unspecified; today's end date does not guarantee today's data. Do not invent cost/value metrics, page or keyword lists, causes, rankings, forecasts or monitoring. Additional targets, countries or periods require authorized calls.

Task:
Show monthly visit estimates from search results without ads and search ads separately for [https://example.com] from [July 1, 2026] to [September 30, 2026]. Missing months are unknown; visits are estimates, not actual. If the range is over 60 months, ask me to shorten it.

Paste into your connected AI's conversation.

Connection guide

Up to 4.536 credits / call

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

Ahrefs

Compare Organic and Paid Search Traffic History · Ahrefs

You receive

Receive dated records with separate organic and paid search traffic estimates. Your Agent can arrange the available dates into a chart or comparison to show how the estimates changed over the requested period.

Start with your task

Show monthly visit estimates from search results without ads and search ads separately for [https://example.com] from [July 1, 2026] to [September 30, 2026]. Missing months are unknown; visits are estimates, not actual. If the range is over 60 months, ask me to shorten it.

What to know

Date grouping does not turn monthly estimates into measured daily or weekly visits. These are search-traffic estimates, not sessions or all-channel analytics. Historical coverage, missing dates and source calculation settings can affect comparisons; a change does not establish its cause.

Inputs & outputs

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

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
queryParams`queryParams`	`object`	Required	Required fields `target, date_from`
Target scope`queryParams.mode`	`string`	Optional	exact: this URL; prefix: URLs beginning with the target; domain: the domain without subdomains; subdomains: the domain and its subdomains. Default subdomains. Default `subdomains` Options `exact, prefix, domain, subdomains`
Target domain or URL`queryParams.target`	`string`	Required	Required nonempty domain or URL, such as example.com or https://example.com/page. Minimum length `1`
Country`queryParams.country`	`string`	Optional	Optional two-letter ISO 3166-1 alpha-2 code, such as us. Selects the search market; behavior when omitted is unspecified. Minimum length `2` Maximum length `2`
Ending date`queryParams.date_to`	`string`	Optional	Optional end date in YYYY-MM-DD format; defaults to today. This does not guarantee data for the latest date. Pattern `^\d{4}-\d{2}-\d{2}$`
Target protocol`queryParams.protocol`	`string`	Optional	both, http or https for the target URLs; default both. Organic and paid are separate traffic estimates, not protocol choices. Default `both` Options `both, http, https`
Starting date`queryParams.date_from`	`string`	Required	Required start of the historical period in YYYY-MM-DD format. Pattern `^\d{4}-\d{2}-\d{2}$`
Date grouping`queryParams.history_grouping`	`string`	Optional	daily, weekly or monthly; default monthly. The requested range may span at most 60 selected groups. This controls date intervals, not the monthly traffic metric's unit. Default `monthly` Options `daily, weekly, monthly`

View raw JSON

{
  "type": "object",
  "required": [
    "queryParams"
  ],
  "properties": {
    "queryParams": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "target",
        "date_from"
      ],
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      },
      "properties": {
        "mode": {
          "enum": [
            "exact",
            "prefix",
            "domain",
            "subdomains"
          ],
          "type": "string",
          "default": "subdomains",
          "description": "Scope of the target: exact (this URL only), prefix (URLs starting with the target), domain (the domain without subdomains), or subdomains (default — the domain and all its subdomains)."
        },
        "target": {
          "type": "string",
          "minLength": 1,
          "description": "The target of the report: a domain ('example.com') or a URL ('https://example.com/page')."
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter country code (ISO 3166-1 alpha-2), e.g. 'us'."
        },
        "date_to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "End date of the historical period in YYYY-MM-DD format. Defaults to today."
        },
        "protocol": {
          "enum": [
            "both",
            "http",
            "https"
          ],
          "type": "string",
          "default": "both",
          "description": "Protocol of the target: both (default), http, or https."
        },
        "date_from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Start date of the historical period in YYYY-MM-DD format."
        },
        "history_grouping": {
          "enum": [
            "daily",
            "weekly",
            "monthly"
          ],
          "type": "string",
          "default": "monthly",
          "description": "Time bucket size for history rows: daily, weekly, or monthly (default). Each bucket is one billed row."
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Keep comparisons consistent

The date attached to a row locates a historical estimate. It is not the time you fetched the report. Sorting those dates and calculating differences are tasks your Agent can perform after receiving the result.

Use the same target scope, country, protocol and grouping when comparing periods. Do not join gaps into a continuous measured series or assume that a different grouping preserves exactly the same representative values.

Ahrefs metrics-history documentation explains the source's traffic metrics.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

No. Each dated value is a monthly traffic estimate, even with daily grouping. Adding those values does not produce a measured monthly or cumulative visitor total.

Compare Organic and Paid Search Traffic History · Ahrefs

Compare Organic and Paid Search Traffic History · Ahrefs

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Keep comparisons consistent

Compare the two visit estimates over time

Choose a country for the report

Understand what visit changes mean

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Keep comparisons consistent

Compare the two visit estimates over time

Choose a country for the report

Understand what visit changes mean

Questions about this tool.

Can I sum the daily rows to get visits for the month?

Does a missing date mean there was no traffic?

Does a before-and-after change prove an SEO campaign worked?