Yesterday we sent an email to our first beta group. No fanfare, no countdown timer — just a quiet note that Optimize is finally ready for real people to use. This post is for everyone else who finds their way here.
If you're new here: Optimize is a toolkit to audit, validate, and fix your site's foundation — meta, schema, open graph, headings, links, media, and more — before you ship anything. It lives with your build process. The full picture is here.
What "Beta" Actually Means Here
This isn't a soft launch with a waitlist. It's a working tool in the hands of people using it in real workflows, with a direct line back to us when something breaks or doesn't make sense.
The first group is small on purpose — different skill levels, different stacks, different use cases. We want to see where it holds up and where it doesn't before opening it wider.
What we're focused on right now:
- Does the output make sense to developers and non-developers? The checks are only useful if the results are actionable for the person reading them.
- Does it fit into existing workflows? Whether that's setting up a config so your whole team is working to the same requirements or dropping it into a CI/CD pipeline, we want to know how well it fits into the way people already work, not the other way around.
- What should Optimize do that it doesn't yet? Beta members have direct access to the repo to flag gaps, bugs, and share ideas helping shape what gets built next.
- Who else should be here? Freelance devs and SEOs, agency teams, content folks validating before publish — all skill levels welcome. The more varied the group, the better Optimize gets.
- What could you build on top of it? Optimize is open source and built to be extended. Personal/internal tool use is free; commercial products built on top of Optimize require a paid license. If you're thinking about building something, now's a good time to get in early.
Want to join a growing community of SEOs and developers using Optimize?
Sign up for the beta. Invites go out in small batches (sort of like cohorts) so you won't be the only new person when you arrive. Once approved, you'll get two emails: a welcome from the team and an invite from GitHub to the repo.
Together, let's optimize the web. No site left behind.