# Dead URL Replacement Planner (`autosecurelogin/dead-url-replacement-planner`) Actor Create a reviewable redirect plan from dead product paths and your supplied catalog snapshot. No crawling or store writes. - **URL**: https://apify.com/autosecurelogin/dead-url-replacement-planner.md - **Developed by:** [Hunter Melnick](https://apify.com/autosecurelogin) (community) - **Security:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $0.05 / actor start 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/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. 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. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## 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. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Dead URL Replacement Planner Create a reviewable redirect plan from dead product paths and your supplied catalog snapshot. No crawling or store writes. ### Run and download 1. Keep the included sample or replace **Input data** with your own authorized records. 2. Start a run. Open **Report and CSV downloads** when it finishes. 3. Open **OUTPUT** for the complete JSON report and download the CSV records. 4. Review the findings before importing or publishing changes. This Actor never writes to a store. ### Hosted limits 250 dead product paths, 2500 products, 500 collections and 2500 existing redirects; 1 MiB JSON input. These tighter hosted limits take precedence over the core format limits below. Memory is fixed at 256 MB. Default timeout is 60 seconds. Output includes one dataset summary row; individual findings and records are delivered in OUTPUT and CSV files. No model subscription, external API key or other product purchase is required. ### Price **$0.05 per run**, charged once when the Actor starts. All report and CSV output is included, with no per-row fee or platform-usage surcharge. Set the maximum run cost to at least $0.05. Starts that reject invalid input or produce no findings still incur the start charge; validate the input before running. ### Storage and support Apify stores supplied data and generated reports under its storage access/retention settings. This hosted edition sends input to Apify; it is not the local-only edition. Remove sensitive run data when no longer needed. URLs in input are never fetched. Use the Actor issue tracker for support with a non-sensitive example and run ID. Do not post private exports or credentials. Hosted use does not grant source redistribution rights. ### Input contract See examples/input.json. Up to 5 MiB total, 1,000 dead paths, 10,000 products, 2,000 collections, 10,000 existing redirects and 100 literal keyword rules. Product status and online flags must be explicit. Collection publication, hidden flag and product count must be explicit. Handles use lowercase ASCII letters, digits and hyphens. The supported storefront profile uses `/products/` and `/collections/` paths and `category-` collection handles. No full URLs, query strings, encoded paths, blog posts or arbitrary regular expressions. Export customer data into the sample's documented shape. No additional software purchase or consulting engagement is required. ### Result rules - Only active, explicitly online products may become replacement targets. - Unlisted products already visible in the snapshot do not get a new redirect. - Existing redirects are preserved; they are never overwritten. - Matching uses names, numbers, category voting and optional literal keyword rules. - Unresolved rows remain unresolved. Home-page fallback redirects are never proposed. - Proposed targets entering a redirect chain or cycle are marked for review and omitted from the import CSV. Repeated input paths are accounted for separately. - Each score is an explainable heuristic, not a calibrated likelihood or proof of equivalence. The program makes no external network calls, verifies no live pages and performs no store writes. Review the snapshot and proposed plan before importing it into your platform. # Actor input Schema ## `payload` (type: `object`): 250 dead product paths, 2500 products, 500 collections and 2500 existing redirects; 1 MiB JSON input. ## Actor input object example ```json { "payload": { "deadProducts": [ "copper-skillet-copy-18", "back-again", "unknown-widget" ], "products": [ { "handle": "copper-skillet", "title": "Copper Skillet", "productType": "Kitchen > Cookware", "status": "ACTIVE", "online": true }, { "handle": "back-again", "title": "Back Again", "productType": "Kitchen", "status": "UNLISTED", "online": true } ], "collections": [ { "handle": "category-kitchen-cookware", "title": "Cookware", "published": true, "hidden": false, "count": 1 } ], "existing": [], "keywords": [ { "word": "skillet", "collection": "category-kitchen-cookware" } ] } } ``` # Actor output Schema ## `files` (type: `string`): Open OUTPUT for full JSON and the .csv records for exports. ## `summary` (type: `string`): One summary row per run; detailed findings are in the report and CSV files. # 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 = { "payload": { "deadProducts": [ "copper-skillet-copy-18", "back-again", "unknown-widget" ], "products": [ { "handle": "copper-skillet", "title": "Copper Skillet", "productType": "Kitchen > Cookware", "status": "ACTIVE", "online": true }, { "handle": "back-again", "title": "Back Again", "productType": "Kitchen", "status": "UNLISTED", "online": true } ], "collections": [ { "handle": "category-kitchen-cookware", "title": "Cookware", "published": true, "hidden": false, "count": 1 } ], "existing": [], "keywords": [ { "word": "skillet", "collection": "category-kitchen-cookware" } ] } }; // Run the Actor and wait for it to finish const run = await client.actor("autosecurelogin/dead-url-replacement-planner").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 = { "payload": { "deadProducts": [ "copper-skillet-copy-18", "back-again", "unknown-widget", ], "products": [ { "handle": "copper-skillet", "title": "Copper Skillet", "productType": "Kitchen > Cookware", "status": "ACTIVE", "online": True, }, { "handle": "back-again", "title": "Back Again", "productType": "Kitchen", "status": "UNLISTED", "online": True, }, ], "collections": [{ "handle": "category-kitchen-cookware", "title": "Cookware", "published": True, "hidden": False, "count": 1, }], "existing": [], "keywords": [{ "word": "skillet", "collection": "category-kitchen-cookware", }], } } # Run the Actor and wait for it to finish run = client.actor("autosecurelogin/dead-url-replacement-planner").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 '{ "payload": { "deadProducts": [ "copper-skillet-copy-18", "back-again", "unknown-widget" ], "products": [ { "handle": "copper-skillet", "title": "Copper Skillet", "productType": "Kitchen > Cookware", "status": "ACTIVE", "online": true }, { "handle": "back-again", "title": "Back Again", "productType": "Kitchen", "status": "UNLISTED", "online": true } ], "collections": [ { "handle": "category-kitchen-cookware", "title": "Cookware", "published": true, "hidden": false, "count": 1 } ], "existing": [], "keywords": [ { "word": "skillet", "collection": "category-kitchen-cookware" } ] } }' | apify call autosecurelogin/dead-url-replacement-planner --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,autosecurelogin/dead-url-replacement-planner" } } } ``` 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/q12MVlcBZp6QkaJ7D/builds/BgQy3feLWckVDU1IC/openapi.json