Client Overview

Zero Longevity Science makes Zero, the world’s #1 fasting app — 810,000+ ratings at 4.8 stars, with zerolongevity.com serving 700K+ visitors a month. We’d already redesigned their site in Framer; this is the story of what happened after the build — the part that decides whether a site keeps earning.

The Challenge

In April 2026, Mike ran an AI-powered SEO audit and brought us the results: canonical issues, missing structured data, og:images served from the wrong domain, missing alt text, and a blog H1 flagged twice. Two things made it harder than a checklist — a hybrid Framer + WordPress stack stitched together by a proxy, and a single-page-app trap where naive JSON-LD injection stacks up across navigations. And every fix had to pass review by Zero’s own engineer, João, page by page.

The Solution

We built a real structured-data system, not pasted snippets: a global Organization + WebSite schema declaring site identity once, with every page-specific schema referencing it via @id. We solved the SPA duplication problem with a cleanup script that removes the previous page’s schema before injecting its own, then validated all six pages through Google’s schema validator. The unglamorous sweep followed — alt text down to the footer store badges, branded og:images on the right domain, titles aligned with schema, and the long-missing blog H1. Throughout, schemas were staged disabled so João could review before anything went live.

Results & Impact

Six pages of structured data shipped with 0 errors and 0 warnings in Google’s schema validator, and one consistent site identity now spans the hybrid Framer + WordPress stack. The audit list was cleared end to end — schemas, alt text, og:images, titles, H1s — without consuming Zero’s engineering team, with the whole engagement running async in Slack.

Why This Matters

A redesign is day one. What decides whether a site keeps earning is everything after — the audits, the structured data, the alt-text sweeps, the SPA quirks nobody budgets for. Zero’s audit went from finding-list to zero-errors without touching their engineering team, because the person fixing it already knew the site.