Alfon Posted on Jun 1 I Built an SEO Tool That Lied to Me. So I Rebuilt It. # devchallenge # githubchallenge GitHub “Finish-Up-A-Thon” Challenge Submission This is a submission for the GitHub Finish-Up-A-Thon Challenge . What I Built SEOCORE is the project I came back to finish for this challenge. It started as a small SEO crawler I built for myself because I wanted a tool I could understand end to end. The first version looked more complete than it really was: it printed scores, generated reports, and even had a few useful ideas like crawl graph analysis and snapshot diffs. But I eventually realised I could not trust its output. This rebuild added a lot of new capabilities, but the most important change was that I finally made the tool trustworthy. I turned that abandoned prototype into a TypeScript CLI that can crawl real sites, handle redirects and robots.txt , render JavaScript-heavy pages when needed, and report issues with context and suggested fixes instead of hiding everything behind one misleading score. The Before The old script was roughly 700 lines. It had classes, interfaces, config objects, sitemap parsing, structured output, an HTML report, and a snapshot diff system. Running it on example.com looked like this: Starting SEO audit of https://example.com https://example.com Score: 80/100 Grade: B Title: Example Domain Meta description: missing Canonical: missing Audit complete. Report saved to ./audit-output/ Enter fullscreen mode Exit fullscreen mode And this was the kind of report it produced: Before screenshot placeholder: old report with a misleadingly good score That output was the problem. A page with no meta description, no canonical tag, and no robots.txt should not feel "basically fine". But the tool wrapped weak logic in clean output, so I trusted it. Two parts of the first version were actually useful: a crawl graph that mapped internal links and orphan pages a snapshot diff system that compared audits over
LIVE