Updates Are Easier To Discover And Share

Shipped

• Added analytics support to the public marketing app so product interest can be measured without changing the training flow.
• Tightened page metadata across public routes, including features, pricing, contact, comparison pages, and Updates.
• Added structured data for public pages and update entries so release notes and product updates are easier for search engines to understand.
• Refined the sitemap around public pages and update detail routes.

Why

Build-in-public only works if people can find the work.

Protocol has a lot of product surface now: routine builder, preset workout routines, quick workout tracking, workout timer flow, pricing, account behavior, comparison pages, and public updates. If those pages are vague to search engines, the product looks smaller than it is.

This pass was about making the public site more legible, not louder or more promotional; just easier to crawl, share, and understand.

Notes

• This does not change the training app itself.
• The goal is clean discovery for release notes, product updates, and comparison pages, not public exposure of implementation detail.
• Updates remains the central surface for news, release notes, and devlog posts.

Next

• Keep writing public updates around user-facing outcomes.
• Use the Updates surface for product progress without turning every commit into a public changelog.