Compare Website Traffic

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "elements"
  ],
  "properties": {
    "elements": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "target"
        ],
        "properties": {
          "target": {
            "type": "string"
          },
          "paid_traffic": {
            "type": [
              "number",
              "null"
            ],
            "description": "Estimated monthly PAID (ads) search traffic, as calculated by the data provider across all of the target’s paid keywords. Modelled from ad placement rather than an organic click-through curve, so the organic caveat on organic_traffic does not apply to it — and Ranked Keywords, which covers organic positions only, is not a substitute for it."
          },
          "paid_keywords": {
            "type": [
              "number",
              "null"
            ]
          },
          "organic_traffic": {
            "type": [
              "number",
              "null"
            ],
            "description": "Estimated monthly ORGANIC search traffic, as calculated by the data provider across all of the target’s keywords. The provider’s organic click-through model flattens for positions past roughly 28, so traffic earned from deep-ranking keywords is overstated. For per-keyword figures on our own position model, use Ranked Keywords."
          },
          "organic_keywords": {
            "type": [
              "number",
              "null"
            ]
          },
          "local_pack_traffic": {
            "type": [
              "number",
              "null"
            ],
            "description": "Estimated monthly search traffic the target earns from local pack placements, as calculated by the data provider across all of its keywords. The provider models this SERP feature separately from ordinary organic positions, so neither the organic click-through caveat on organic_traffic nor Ranked Keywords (organic positions only) describes it."
          },
          "local_pack_keywords": {
            "type": [
              "number",
              "null"
            ]
          },
          "featured_snippet_traffic": {
            "type": [
              "number",
              "null"
            ],
            "description": "Estimated monthly search traffic the target earns from featured snippet placements, as calculated by the data provider across all of its keywords. The provider models this SERP feature separately from ordinary organic positions, so neither the organic click-through caveat on organic_traffic nor Ranked Keywords (organic positions only) describes it."
          },
          "featured_snippet_keywords": {
            "type": [
              "number",
              "null"
            ]
          }
        },
        "additionalProperties": true
      }
    },
    "returned": {
      "type": "number",
      "description": "How many rows this run returned, after any Limit was applied."
    },
    "truncated": {
      "type": "boolean"
    },
    "suggestion": {
      "type": "string"
    },
    "totalCount": {
      "type": "number",
      "description": "How many records the provider says MATCH in total, independent of Limit — routinely in the millions (spotify.com has 2,583,327 ranking pages). It is a match count, NOT how many this endpoint will serve: Limit caps what one call returns, so do not compare it against the row count to judge completeness and do not paginate towards it. Absent when the provider sent no count."
    },
    "totalElements": {
      "type": "number",
      "description": "DEPRECATED — despite the name this is the count RETURNED by this run, not a grand total, so it equals your Limit on a limited run. Kept at that value deliberately: ENG-17058 asked for depth 5 to report 5, and it is a live number in existing flows. Use `returned` for this number or `totalCount` for how many records match."
    }
  },
  "additionalProperties": true
}

Copy