Broken Link Redirect Map
Pricing
from $4.90 / 1,000 page auditeds
Go to Apify Store
Broken Link Redirect Map
Crawl pages to identify broken links, redirect chains, status codes, and redirect-map issues.
Broken Link Redirect Map
Pricing
from $4.90 / 1,000 page auditeds
Crawl pages to identify broken links, redirect chains, status codes, and redirect-map issues.
Connect the Broken Link Redirect Map — technical SEO, web, and domain a Actor to an AI application through the Apify MCP server. MCP clients with OAuth support sign you in to Apify without an API token.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/broken-link-redirect-map" } }}Add the configuration above to your project's .mcp.json file for Claude Code, then run /mcp in Claude Code to sign in to Apify. It connects to the hosted Apify MCP server with the Broken Link Redirect Map — technical SEO, web, and domain a Actor already loaded. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
For other MCP clients, get a client-specific configuration with the Broken Link Redirect Map — technical SEO, web, and domain a Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,junipr/broken-link-redirect-map.
You can connect to the Apify MCP server using an MCP client that supports Streamable HTTP.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.