The Problem (Pain Intensity: 7/10)

As documentation and READMEs pile up, so do broken links.

  • Documentation/websites accumulate broken links over time
  • Existing tools (lychee, linkchecker) only detect, fixing is manual
  • Open source projects lack maintainer bandwidth to address them
  • Broken links cause SEO score drops and poor UX
  • CI throws warnings but nobody fixes them

Detection is easy, but fixing is tedious.

Target Market

  • Primary Market: GLOBAL
  • Target Segment: Open source maintainers, technical writers, documentation teams, DevRel
  • Estimated TAM: Niche market but viral potential in developer tools

We’re in an era where documentation quality is a competitive advantage.

Broken Link Auto-Fixer detects broken links, finds replacement URLs, and automatically proposes fixes via GitHub PRs.

Core Features

  1. Broken Link Detection: Scan Markdown, HTML, RST files
  2. Wayback Machine Search: Find archived versions of dead URLs
  3. Auto GitHub PR Creation: Open PRs with fix suggestions
  4. Scheduling: Weekly/monthly automatic scan setup
  5. CI Integration: Check every PR via GitHub Actions

Differentiated Approach

❌ lychee: Detect broken links → output report
❌ linkchecker: Detect broken links → manual fix needed
✅ Our tool: Detect → find alternatives → auto-create PR

Competitive Analysis

Competitor/ToolPriceWeakness
lycheeFree (OSS)Detection only, no fixing
linkcheckerFree (OSS)Detection only, no fixing
Ahrefs$99/mo+SEO tool, poor dev workflow fit
Dead Link CheckerFree/PaidWeb-based, no CI integration

Differentiation: Existing tools stop at detection. We automate the fix.

MVP Development

  • Estimated Timeline: 4-6 weeks
  • Complexity: LOW-MEDIUM
  • Tech Fit Score: 9/10
Backend: Node.js/Go
Link Checker: Wrap lychee or custom implementation
Archive API: Wayback Machine API
GitHub: Octokit (GitHub API)
CI: GitHub Actions
Deployment: Docker/Vercel

MVP Scope

  1. CLI to scan repository
  2. Generate broken link list
  3. Search Wayback Machine for alternatives
  4. Auto-create GitHub PR
  5. Provide GitHub Actions template

Revenue Model

  • Model: USAGE-BASED
  • Pricing:
    • Free: Public repos, 100 links/month
    • Pro: $9/mo (private repos, 5,000 links/month)
    • Team: $29/mo (org repos, unlimited links)
  • MRR 6-month estimate: $1,500
  • MRR 12-month estimate: $5,000

Risk Analysis

RiskLevelMitigation
TechnicalLOWBuilt on proven tools (lychee)
MarketMEDIUMNiche market, needs developer viral
ExecutionLOW4-6 week MVP, clear scope
  • Those wanting GitHub API/Actions experience
  • Open source maintainers running projects
  • Indie makers interested in building developer tools
  • Technical writers who care about documentation quality
  • Anyone targeting developer communities on ProductHunt

💡 Idea Source: An MVP for “auto-fixing broken links via GitHub PRs” was shared on Reddit r/SaaS.

If you’ve started this side project or have thoughts, share in the comments!