How to Find 404 Errors with Copilot
Find 404 errors in your IDE with Copilot and ToolRouter. Fix broken pages directly in code.
Tool
Copilot finds 404 errors and connects them to the routing configuration in your codebase. See which URLs return errors, then fix the routes, add redirects, or restore missing pages directly in your IDE. This integrated approach is particularly effective for developers managing routing in frameworks like Next.js or Remix.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
Steps
Once connected (see setup above), use the Site Crawler tool:
- Ask: "Crawl mysite.com and report all 404 errors"
- Review the broken URL list inline
- Ask Copilot to add redirect rules to your configuration file
- Re-crawl to verify all 404s are resolved
Example Prompt
Try this with Copilot using the Site Crawler tool
Find all 404s on mysite.com and generate redirect rules for my vercel.json or next.config.js.
Tips
- Copilot can add redirects directly to your routing config
- Search your codebase for hardcoded broken URLs
- Run before deployments as a pre-merge check