Build a Broken Link Checker with Claude Code

Build a Broken Link Checker web app. People search for "broken link checker" about 23,000 times a month, plus related searches like "check broken links", "website link checker", "404 error checker". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build a broken link checker web app. Create a homepage with URL input and crawl depth settings. When users submit a website, show real-time scanning progress with found links counter. Display results in categorized lists: working links (green), broken links (red), redirects (yellow), and external links. Include status codes, response times, and fix suggestions. Add export functionality (CSV, PDF reports) and scheduled monitoring options. Use technical design with status-focused color coding. Focus on link scanning and results display first.

How to build it:
1. Read this folder first. If it is empty, set up Next.js (App Router, TypeScript, Tailwind). Write a short PLAN.md with the pages, components, any library or API you need, and what you are leaving for later. Then build.
2. Put the tool itself on the homepage so a visitor can use it within seconds, with no sign-up. Do the processing in the browser where you can, so it is fast and cheap to run. Look at how Screaming Frog, Dr. Link Check, W3C Link Checker do it and make ours simpler and faster.
3. Make it rank. Use "broken link checker" in the title tag, H1 and meta description. Under the tool, add a short how-to and an FAQ with FAQPage schema, and add a sitemap and robots.txt. Scaffold these programmatic pages from one template and a data file: /broken-link-checker-for-[platform], /check-[website-type]-links, /link-validator-[cms].
4. Monetisation: Freemium: 100 links/scan, $10/mo unlimited + monitoring. Add a pricing page and the free usage limit, and leave Stripe checkout as a clearly marked stub with the environment variables it needs.
5. Run it locally and test the main flow end to end, including edge cases like empty input and very large files. Fix what breaks, then finish with a summary of what works, what is stubbed and how to deploy it to Vercel.

Paste it into Claude Code in an empty folder. It plans first, so read PLAN.md and steer before it starts building.