← ClaudeAtlas

broken-linkslisted

Find broken internal links (404s, 5xx, timeouts) and redirect chains on a website, list each one as source page -> broken target, and give the exact edit to make on each source page. Use when the user asks to find broken links, dead links, 404 errors, 'what links to my 404s', 'fix broken links', 'check my links', link rot, or wants redirect chains cleaned up.
CrawlCove/claude-seo-plugin · ★ 0 · AI & Automation · score 72
Install: claude install-skill CrawlCove/claude-seo-plugin
# Broken links and redirect chains The deliverable is an edit list: for each broken link, the page it sits on, where it points, why that fails, and what to change it to. A list of 404 URLs without their sources is not useful, because the fix happens on the page that holds the link. ## Step 0: which mode are you in Look for the Crawl Cove crawl tools: names ending in `crawl_site`, `load_export`, `get_issues`, `get_page`, `list_broken_links`, `list_pages`. - **Crawl mode**: tools present. Follow the procedure. - **Page mode**: tools absent (claude.ai chat does not run a plugin's local tools). Go to "Page mode" and say you are checking the links on specific pages, not the site. ## Crawl mode procedure 1. **Crawl**: `crawl_site` `{ "url": "<home page>", "maxPages": 200 }`. Note `pageCount` and `truncated`. - With a file instead: `load_export` `{ "path": "<file>" }`. A crawlcove-cli JSON file keeps link sources. A Crawl Cove desktop export does not carry the link graph, so `list_broken_links` lists the broken pages without sources; say that, and offer a live `crawl_site` to get sources. 2. **Get the pairs**: `list_broken_links` `{ "limit": 500 }`. Each row is `source -> target (HTTP status or fetch error)`. Record the total from the first line. If the answer ends with a "more" line, work through the rest per source page with `get_page`, which lists that page's broken links. 3. **Get the broken targets**: `get_issues` `{ "type": "broken-page", "limit": 200 }` for the disti