from python script to chrome extension in 4 hours — why i rebuilt my SEO tool for the browser
i had a working SEO scanner running on my linux server. python, requests, beautifulsoup. scans any URL, checks 10 things, scores out of 100. works great.
problem: nobody uses it because they have to hit my API. thats friction.
so i rebuilt the whole thing as a chrome extension. same checks, same scoring, but now its one click on any page youre already visiting.
what the extension checks
- title tag (exists, length)
- meta description (exists, length)
- alt text on images (count missing)
- heading hierarchy (h1 exists, proper nesting)
- canonical URL
- viewport meta tag
- HTTPS
- page speed indicators
- open graph tags
- structured data
why browser beats API
the API requires: find the URL, copy it, go to my site, paste it, click scan, wait. thats 6 steps.
the extension requires: click the icon. thats 1 step.
friction reduction is the entire product strategy. same functionality, 6x less effort to use.
what it costs
free tier: overall score + top 3 findings
pro tier ($9): full detailed report with all 10 checks
the free tier is marketing. the pro tier is revenue.
chrome extension: https://vemtrac.gumroad.com/l/klwksv
free sample (agency data): https://vemtrac.gumroad.com/l/blole
lead list: https://vemtrac-outreach.pages.dev/leads
have you rebuilt a backend tool as a browser extension? what changed about adoption?
