# URL Parameter Indexability Auditor (`junipr/url-parameter-indexability-auditor`) Actor Audit url parameter indexability auditor inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams. - **URL**: https://apify.com/junipr/url-parameter-indexability-auditor.md - **Developed by:** [junipr](https://apify.com/junipr) (community) - **Categories:** SEO tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $4.90 / 1,000 url parameter indexability auditor page auditeds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. 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. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — 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 ## URL Parameter Indexability Auditor ### Store Positioning **Store title:** URL Parameter Indexability Auditor **Short description:** Audit url parameter indexability auditor inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams. **SEO title:** URL Parameter Indexability Auditor — technical SEO, web, and domain audit **SEO description:** Audit url parameter indexability auditor inputs and return structured findings, evidence rows, and a buyer-ready report for SEO, developer, and operations teams. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports. **Categories:** SEO\_TOOLS **Keywords:** url, parameter, indexability, auditor, structured data, public data, web/domain audit ### Fixed-Inclusive PPE Pricing This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model. - Tier: W1 — Web/domain audit - Primary event: `page-audited` at $0.00490 base - Default max charge: $10.00 - Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount Event set: - `actor-start`: base $0.00500, GOLD $0.00400. URL Parameter Indexability Auditor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended. - `page-audited`: base $0.00490, GOLD $0.00392. URL Parameter Indexability Auditor: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended. - `record-extracted`: base $0.00372, GOLD $0.00298. URL Parameter Indexability Auditor: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended. - `finding-emitted`: base $0.00372, GOLD $0.00298. URL Parameter Indexability Auditor: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended. - `audit-report-generated`: base $0.05000, GOLD $0.04000. URL Parameter Indexability Auditor: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended. ### Public Task Concepts - Audit URL Parameter Indexability controls on a capped public sample - Find high-priority URL Parameter Indexability issues before release - Validate URL Parameter Indexability evidence from supplied pages - Prioritize URL Parameter Indexability fixes with severity and proof - Export URL Parameter Indexability QA rows for client review URL Parameter Indexability Auditor evaluates parameterized pages against their clean base URL, canonical target, and robots directives. It identifies indexable tracking/filter/search variants, self-canonical parameter pages, duplicate query-order variants, and rule conflicts that can create crawl bloat. ### What it checks - Fetches public parameterized URLs or parses supplied HTML while retaining final status and URL. - Emits one computed row per query parameter, including category, clean base URL, canonical type, indexability, and risk. - Classifies tracking, navigation, search, facet, sort, and unknown parameters. - Detects self-canonical indexable variants, noindex/canonical conflicts, duplicate parameter-order groups, high parameter counts, and ignored policy rules. - Applies `parameterRules` and `trackingParameterNames` directly to classification and risk decisions. ### Reports The default key-value store includes the Markdown audit, per-URL CSV, parameter-name summary, indexable-URL list, tracking warnings, and duplicate-order groups. Reports are generated from the same rows returned in the dataset. ### Example input ```json { "startUrls": [ "https://www.wikipedia.org/" ], "sitemapUrls": [ "https://www.wikipedia.org/" ], "htmlInputs": [ { "sourceUrl": "https://www.wikipedia.org/wiki/Main_Page", "html": "URL Parameter Indexability Auditor Demo

URL Parameter Indexability Auditor

Skipped level

Updated on 2026-06-20. This page has enough text to support readability, content quality, architecture, link, image, and technical SEO checks with deterministic computed evidence generated from markup.

\"\"
", "headers": { "cache-control": "max-age=3600", "content-encoding": "br", "last-modified": "Wed, 01 Jul 2026 00:00:00 GMT" } } ], "allowedDomains": "", "parameterRules": [], "trackingParameterNames": [], "maxUrls": 3, "maxParametersPerUrl": 3, "checkCanonical": true, "checkRobotsDirectives": true, "detectDuplicateParameterOrders": true, "includeEvidence": true, "requestDelayMs": 3, "timeoutMs": 3 } ``` ### Output fields sourceUrl, finalUrl, statusCode, parameterName, parameterValue, parameterCategory, parameterCount, canonicalUrl, canonicalType, robotsIndexable, selfCanonical, baseUrl, duplicateParameterOrderGroupId, trackingParameterPresent, indexabilityRisk, issueCode, severity, recommendation ### Cost controls Use `maxUrls` and `maxParametersPerUrl` to bound work. Raw HTML inputs are useful for repeatable monitoring, while URL inputs use the same production parser after fetching the public response. ### Limitations Results describe observed indexability signals; they do not update canonical tags, robots directives, Search Console settings, or site routing. # Actor input Schema ## `startUrls` (type: `array`): start urls used by URL Parameter Indexability Auditor. ## `sitemapUrls` (type: `array`): sitemap urls used by URL Parameter Indexability Auditor. ## `htmlInputs` (type: `array`): html inputs used by URL Parameter Indexability Auditor. ## `allowedDomains` (type: `string`): allowed domains used by URL Parameter Indexability Auditor. ## `parameterRules` (type: `array`): parameter rules used by URL Parameter Indexability Auditor. ## `trackingParameterNames` (type: `array`): tracking parameter names used by URL Parameter Indexability Auditor. ## `maxUrls` (type: `integer`): max urls used by URL Parameter Indexability Auditor. ## `maxParametersPerUrl` (type: `integer`): max parameters per url used by URL Parameter Indexability Auditor. ## `checkCanonical` (type: `boolean`): check canonical used by URL Parameter Indexability Auditor. ## `checkRobotsDirectives` (type: `boolean`): check robots directives used by URL Parameter Indexability Auditor. ## `detectDuplicateParameterOrders` (type: `boolean`): detect duplicate parameter orders used by URL Parameter Indexability Auditor. ## `includeEvidence` (type: `boolean`): include evidence used by URL Parameter Indexability Auditor. ## `requestDelayMs` (type: `integer`): request delay ms used by URL Parameter Indexability Auditor. ## `timeoutMs` (type: `integer`): timeout ms used by URL Parameter Indexability Auditor. ## Actor input object example ```json { "startUrls": [ "https://www.wikipedia.org/" ], "sitemapUrls": [ "https://www.wikipedia.org/" ], "htmlInputs": [ { "sourceUrl": "https://www.wikipedia.org/", "html": "Reference Page

Reference Page

This public reference page has useful content, navigation, and links for local analysis.

Main PageWikipedia logo" } ], "allowedDomains": "", "parameterRules": [], "trackingParameterNames": [], "maxUrls": 3, "maxParametersPerUrl": 3, "checkCanonical": true, "checkRobotsDirectives": true, "detectDuplicateParameterOrders": true, "includeEvidence": true, "requestDelayMs": 3, "timeoutMs": 3 } ``` # Actor output Schema ## `results` (type: `string`): No description ## `reports` (type: `string`): No description # 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 = {}; // Run the Actor and wait for it to finish const run = await client.actor("junipr/url-parameter-indexability-auditor").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 = {} # Run the Actor and wait for it to finish run = client.actor("junipr/url-parameter-indexability-auditor").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call junipr/url-parameter-indexability-auditor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/url-parameter-indexability-auditor" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/QQEUuFbSAkpc5BfDk/builds/bP9ZPpsfHKXEcX9Ig/openapi.json