# Website Traffic Estimator · 100 Domains + History (`doesaiknow/website-traffic-estimator`) Actor Estimate organic traffic for up to 1000 domains per run. One row per domain: current organic traffic, monthly history, MoM/YoY deltas, a 0-100 index, and in-set ranking. Pay per domain, cache free. - **URL**: https://apify.com/doesaiknow/website-traffic-estimator.md - **Developed by:** [David S](https://apify.com/doesaiknow) (community) - **Categories:** SEO tools, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.10 / traffic estimate row This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Website Traffic Estimator for 100 Domains in Bulk Estimate organic **website traffic** for 100 domains in a single run (up to 1000 supported). Paste a list of domains and get one decision-ready row each: current organic traffic, a 12-month history, MoM and YoY change, a normalized 0–100 traffic index, and where the domain ranks inside your own list. Built for SEO agencies, market analysts, and sales-intelligence teams who benchmark competitor or prospect websites at portfolio scale — not one domain at a time in a browser tab. Data comes from a licensed traffic-estimation API, so there is no scraping, no proxies, and no anti-bot loop. ### What does the Website Traffic Estimator do? Give it a list of domains. For each one, the estimator pulls the current organic-traffic estimate and the monthly historical series, then computes the portfolio metrics — a 0–100 index normalized across your set, the rank and percentile of each domain within the list, and month-over-month and year-over-year deltas with a riser / decliner / flat flag. One domain in, one row out — it answers, at scale, how much organic traffic each domain gets, how it is trending, and how they compare. ### Why use the Website Traffic Estimator - **100 domains per run — up to 1000 supported.** One list in, one clean row per domain out — no per-domain clicking, no spreadsheet assembly. - **Historical series, not just a snapshot.** Every domain carries a monthly `history` array (up to 12 months), so you see the trajectory. - **Portfolio comparison built in.** `rank_in_set`, `percentile`, and a 0–100 `traffic_index` place every domain against the others in the same run — instant benchmarking within your list. - **Movement flags.** `mom_delta_pct`, `yoy_delta_pct`, and a `trend` of riser, decliner, or flat show which domains are gaining or losing organic traffic. - **Risers & decliners view.** A ready-made dataset view filters out flat domains so you can hand your team just the movers. - **Pay per domain, cache free.** $0.15 per delivered row on the Free plan, down to $0.10 on Gold and above; a domain checked in the last 24 hours is served from cache and costs nothing beyond the one-time run start. ### How to check website traffic in bulk 1. Open the Actor and paste your domains into the **Domains** field (one per line). Enter bare domains — the protocol, `www.`, and any path are stripped to the root automatically, and duplicates are removed, so two variants of the same site count as one row. 2. Optionally set the **Location** (numeric code, default 2840 = United States) and **Language** (two-letter code, default `en`). One market per run. 3. Run the Actor. It checks the 24-hour cache first, then fetches current and historical traffic for every new domain in a single batch, and computes the in-set metrics. 4. Open the **Overview** dataset view for the at-a-glance list: domain, organic traffic, 0–100 index, in-set rank, and trend. 5. Switch to the **Risers & decliners** view to see only the domains whose trend is not flat, then sort by the MoM column to find the biggest movers. 6. Export to JSON, CSV, or Excel, or pull results from the API and feed them into your own SEO or sales dashboard. Re-run every ~30 days to keep the portfolio current. Minimal input: ```json { "domains": ["notion.so", "figma.com", "example.com"] } ```` ### What data you get per domain One dataset row = one domain. Every row always carries the same 14 keys (nothing missing, no raw provider payload leaks through). Example row: ```json { "domain": "notion.so", "location_code": 2840, "language_code": "en", "etv_organic": 152340, "traffic_index": 100, "rank_in_set": 1, "percentile": 100, "history": [ { "month": "2025-08", "etv_organic": 141200.0 }, { "month": "2025-12", "etv_organic": 147880.2 }, { "month": "2026-07", "etv_organic": 152340.5 } ], "mom_delta_pct": 3.65, "yoy_delta_pct": null, "trend": "flat", "not_found": false, "source": "primary", "checked_at": "2026-07-24T09:14:02.371Z" } ``` | Field | Type | What it tells you | |---|---|---| | `domain` | string | The normalized root domain (echo of input) | | `country` | no | Market for the estimate — pick a country from the dropdown (92 supported markets). Defaults to United States. | | `location_code` | no | API only (hidden in the UI): numeric market code that overrides the Location picker — handy for scripted runs and saved tasks. | | `language_code` | no | Language of the estimate — leave on "Market default" to use the country's primary language (Germany → German). | | `etv_organic` | number | null | Estimated monthly organic traffic value; `null` when the domain has no metric | | `traffic_index` | number 0–100 | null | Traffic normalized against the top domain in the fetched set | | `rank_in_set` | integer | null | Rank by organic traffic within your list (1 = highest) | | `percentile` | number | null | Percentile position within your list (100 = highest) | | `history` | array | null | Monthly series `[{month, etv_organic}]`, oldest to newest; `null` when not fetched | | `mom_delta_pct` | number | null | Month-over-month change, percent; `null` when the baseline is zero, missing, or the series is too short | | `yoy_delta_pct` | number | null | Year-over-year change, percent (month vs month-12); `null` when the series is under 13 months | | `trend` | string | null | `riser`, `decliner`, or `flat` from the MoM delta; `null` when the delta is null | | `not_found` | boolean | `true` = the domain had no metrics; still a delivered, billed row | | `source` | string | Data provenance: `primary`, `historical-degraded`, or `bulk-only` | | `checked_at` | ISO 8601 | When this observation was taken | ### Traffic index, ranking, and trend explained The comparison metrics are computed **within the set of domains you submit**, so they benchmark your list against itself: - **`traffic_index`** normalizes organic traffic to 0–100 against the highest-traffic domain in the run (the top domain scores 100). - **`rank_in_set`** orders domains by organic traffic (competition ranking on ties), and **`percentile`** gives that position on a 0–100 scale. - **`trend`** reads the MoM delta with a ±5 percentage-point noise band: inside the band is `flat`, at or above it is `riser`, below is `decliner` — so representation noise is not reported as real change. Domains with no organic value fall outside the ranking (those fields are `null`), so a not-found domain never distorts the benchmark. ### Input parameters | Field | Required | Notes | |---|---|---| | `domains` | yes | Your list of domains (1–1000). Each yields one row. Normalized to the root and de-duplicated before fetching. | | `country` | no | Market for the estimate — pick a country from the dropdown (92 supported markets). Defaults to United States. | | `location_code` | no | API only (hidden in the UI): numeric market code that overrides the Location picker — handy for scripted runs and saved tasks. | | `language_code` | no | Language of the estimate — leave on "Market default" to use the country's primary language (Germany → German). | Run this Actor via the Apify API or the Apify MCP server (`mcp.apify.com`), so AI assistants can trigger a bulk traffic check straight from a domain list. ### How much does the Website Traffic Estimator cost? Billing uses Apify's pay-per-event model. You pay per **delivered row**, not per input domain and not per upstream call. | Event | When | Price | |---|---|---| | Run start | Once per run | $0.10 (flat, one-time) | | Domain estimated | Per delivered row | $0.15 per domain (Free plan) → $0.10 on Gold+ | The per-domain price is flat across every Apify plan. **You are never charged for:** - **Cache hits** — a domain estimated in the last 24 hours is served from cache and bills nothing beyond the one-time run start. - **Failures** — a domain whose data could not be fetched is skipped and never billed. A `not_found` result **is** a delivered answer and is billed as one domain — knowing a domain has no organic-traffic metric is a result. On Free accounts the run stops before the first paid call once your plan limit is reached, so you are never charged beyond your balance. ### Website Traffic Estimator vs Similarweb and manual checks | | This actor | Similarweb-style SaaS | Manual per-site checks | |---|---|---|---| | Bulk 100 domains (up to 1000) | Yes, one run | Enterprise tier only | No | | Monthly history per domain | Yes, up to 12 months | Yes | Tedious | | In-set ranking and 0–100 index | Yes | No | No | | Risers / decliners flag | Yes | Manual | No | | Cost model | From $0.10 per domain, cache free | Monthly seat | Your time | | API + MCP access | Yes | Limited | No | For a domain-authority and backlink-strength snapshot instead of traffic, pair this with the **Domain Authority Checker** below. This estimator is the traffic-and-history angle: monthly series plus portfolio comparison across a submitted set, rather than a single authority score. ### How the estimator stays reliable - **Cache (24h):** identical domains within 24 hours are served free, with the original observation time preserved. - **Deterministic metrics:** the same inputs always produce the same index, rank, and deltas. The contract version is part of the cache key, so a field change cleanly invalidates old entries. - **Graceful degradation:** if only part of the batch resolves, the row is still delivered and `source` records how (`primary`, `historical-degraded`, or `bulk-only`). Each call retries transient errors up to three times with backoff. - **Plan-limit guard:** on Free accounts the run stops before the first paid request when the forecast exceeds your plan limit — nothing is charged beyond your balance. ### What this actor does not do - It does **not** scrape websites or search engines — estimates come from a licensed traffic API. - It does **not** report exact, audited visitor counts — organic traffic figures are model-based estimates. - It does **not** measure paid, referral, direct, or social traffic in v1 — organic only. - It does **not** track domains over time on its own — it is stateless; re-run it to refresh. - It does **not** support per-domain geo or language targeting — one market and language per run. ### FAQ #### How many domains can I check at once? Up to 1000 domains per run (100 is the typical batch) — one billed row each, except free cache hits and failures. #### What is the traffic index? A 0–100 score that normalizes each domain's organic traffic against the highest-traffic domain in the same run, so you can compare your list at a glance. #### Why is yoy\_delta\_pct often null? Year-over-year change needs the exact point from 12 months earlier. The window is about 12 months, so that baseline is often unavailable — `null` means "series too short", not zero change. #### Do cache hits cost anything? No. A domain estimated within the last 24 hours is re-delivered from cache and never billed beyond the one-time run start. #### How often should I run it? About every 30 days keeps a portfolio current, since organic-traffic estimates move slowly month to month. You can also run it via the Apify API or the MCP server. ### Related actors Pair this with the rest of the doesaiknow suite for a fuller SEO and competitive-intelligence view: - [Domain Authority Checker](https://apify.com/doesaiknow/domain-authority-checker) — bulk domain-authority and backlink-strength snapshot, when you need authority rather than traffic. See the doesaiknow publisher page for more companion actors. ### Legal & support - This actor reports **model-based organic-traffic estimates** for the domains you provide. Data is sourced from a stable, licensed vendor **API**, not from scraping, proxy rotation, or anti-bot circumvention. It stores no personal data. - Output is provided **as-is** for competitive-intelligence and SEO purposes. Traffic estimates are point-in-time model figures, not guarantees of actual visitor counts. - You are responsible for using the output in line with the terms of the platforms you operate on and applicable law in your jurisdiction. - Questions or a bug? Open an issue on the Actor's **Issues** tab, or see the **API** tab for integration details. ### SEO keywords website traffic estimator, website traffic checker, bulk website traffic, check website traffic, similarweb alternative, competitor website traffic, site traffic estimator, website analytics API, organic traffic estimate, domain traffic checker, traffic estimation API, bulk domain analysis, website traffic API, competitor traffic analysis, organic traffic checker, traffic benchmarking, website traffic comparison, domain traffic estimate, monthly traffic history, traffic trend tracker, SEO traffic tool, portfolio traffic analysis, estimate website visitors, traffic index. Built by doesaiknow. # Actor input Schema ## `domains` (type: `array`): Domains to estimate organic traffic for. One delivered row per domain: current organic traffic, monthly history, MoM/YoY deltas, a 0-100 index and in-set ranking. Enter bare domains — protocol, www and path are stripped automatically to the root domain, and duplicates are removed. Up to 1000 domains per run. ## `country` (type: `string`): Geographic market for the traffic estimate — pick a country. Overrides the hidden API-only location code when set. ## `location_code` (type: `integer`): API only (hidden in the UI): numeric market code used when no country is selected above. ## `language_code` (type: `string`): Language of the traffic estimate. Leave on "Market default" to use the selected market's primary language (Germany -> German). ## Actor input object example ```json { "domains": [ "notion.so", "example.com" ], "country": "2840", "language_code": "" } ``` # Actor output Schema ## `results` (type: `string`): All delivered rows: domain, etv\_organic, traffic\_index, rank\_in\_set, percentile, history, mom\_delta\_pct, yoy\_delta\_pct, trend, not\_found, source, checked\_at. ## `cache` (type: `string`): Per-domain rows cached for 24h; a cache hit re-delivers the row free (never billed beyond the one-time run start). # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "domains": [ "notion.so", "example.com" ], "country": "2840" }; // Run the Actor and wait for it to finish const run = await client.actor("doesaiknow/website-traffic-estimator").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "domains": [ "notion.so", "example.com", ], "country": "2840", } # Run the Actor and wait for it to finish run = client.actor("doesaiknow/website-traffic-estimator").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "domains": [ "notion.so", "example.com" ], "country": "2840" }' | apify call doesaiknow/website-traffic-estimator --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=doesaiknow/website-traffic-estimator", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Website Traffic Estimator · 100 Domains + History", "description": "Estimate organic traffic for up to 1000 domains per run. One row per domain: current organic traffic, monthly history, MoM/YoY deltas, a 0-100 index, and in-set ranking. Pay per domain, cache free.", "version": "0.1", "x-build-id": "5lzAyNanfoI02cGIS" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/doesaiknow~website-traffic-estimator/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-doesaiknow-website-traffic-estimator", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/doesaiknow~website-traffic-estimator/runs": { "post": { "operationId": "runs-sync-doesaiknow-website-traffic-estimator", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/doesaiknow~website-traffic-estimator/run-sync": { "post": { "operationId": "run-sync-doesaiknow-website-traffic-estimator", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "domains" ], "properties": { "domains": { "title": "Domains", "minItems": 1, "maxItems": 1000, "type": "array", "description": "Domains to estimate organic traffic for. One delivered row per domain: current organic traffic, monthly history, MoM/YoY deltas, a 0-100 index and in-set ranking. Enter bare domains — protocol, www and path are stripped automatically to the root domain, and duplicates are removed. Up to 1000 domains per run.", "items": { "type": "string" } }, "country": { "title": "Location", "enum": [ "2008", "2012", "2024", "2032", "2051", "2036", "2040", "2031", "2048", "2050", "2056", "2068", "2070", "2076", "2100", "2854", "2116", "2120", "2124", "2152", "2170", "2188", "2384", "2191", "2196", "2203", "2208", "2218", "2818", "2222", "2233", "2246", "2250", "2276", "2288", "2300", "2320", "2348", "2356", "2360", "2372", "2376", "2380", "2392", "2400", "2398", "2404", "2428", "2440", "2458", "2470", "2484", "2498", "2492", "2504", "2104", "2528", "2554", "2558", "2566", "2807", "2578", "2586", "2591", "2600", "2604", "2608", "2616", "2620", "2642", "2682", "2686", "2688", "2702", "2703", "2705", "2710", "2410", "2724", "2144", "2752", "2756", "2764", "2788", "2792", "2804", "2784", "2826", "2840", "2858", "2862", "2704" ], "type": "string", "description": "Geographic market for the traffic estimate — pick a country. Overrides the hidden API-only location code when set." }, "location_code": { "title": "Location code (API only)", "type": "integer", "description": "API only (hidden in the UI): numeric market code used when no country is selected above." }, "language_code": { "title": "Language (optional)", "enum": [ "", "sq", "ar", "hy", "az", "bn", "bs", "bg", "zh-CN", "hr", "cs", "da", "nl", "en", "et", "fi", "fr", "de", "el", "he", "hi", "hu", "id", "it", "ja", "ko", "lv", "lt", "mk", "ms", "nb", "pl", "pt", "ro", "ru", "sr", "sk", "sl", "es", "sv", "tl", "th", "tr", "uk", "ur", "vi" ], "type": "string", "description": "Language of the traffic estimate. Leave on \"Market default\" to use the selected market's primary language (Germany -> German).", "default": "" } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```