Why I open-sourced LinkShift.app

LinkShift.app started as a hosted product for managing redirects, branded links, QR codes, analytics, and URL migrations.

I decided to open source it because interest in the hosted version has been lower than expected. Rather than keep pushing something only a few people want, I’d rather make it available to anyone who can use it.

If the project gets real traction, I’ll keep supporting the hosted version too.

Comments

[Amit Feldman]

Respect the call to open-source rather than let it quietly die — redirect/migration tooling is exactly the kind of thing people self-host happily. From a scan of linkshift.app: you've clearly done the security-headers homework (CSP, X-Frame-Options, nosniff, Referrer-Policy, Permissions-Policy all set), which makes the three gaps stand out:

1. HSTS is missing — the one header in the set you don't have. You're behind Cloudflare, so it's a toggle: SSL/TLS → Edge Certificates → Enable HSTS (max-age 12 months, includeSubDomains on). No deploy needed.
2. No meta description — Google writes its own snippet, usually badly.
3. No <h1> on the homepage — the crawlers get "LinkShift.app" from the title and nothing else.

If the hosted version's traction problem is partly discovery, #2 and #3 are the cheapest SEO fixes you'll ever ship. Happy to run a full free scan if you want the complete report — just ask.