Your site isn't finished. It's alive.

A website that's right on launch day and frozen forever slowly becomes wrong — prices change, you add a service, the seasons turn. Yoshi treats your site as a living thing: it stays current because you can change it in a sentence, and it stays good because Yoshi keeps measuring and tending it.

Change anything without rebuilding everything

Because your site is generated from a structured blueprint, edits are surgical. Update a price and only the pages that mention it change. Add a service and it appears across every area you serve, wired into the nav and sitemap — but Yoshi doesn't rebuild your other 1,800 pages to do it. Fast to change, never fragile. status: planned (the living-sites / edit-without-full-rebuild pipeline, cycle 32).

Stay findable, automatically

Search visibility isn't a one-time setup; it's upkeep. Yoshi handles the unglamorous, ongoing SEO work so you don't have to think about it:

• Built-in best practices — clean structure, schema, sitemaps, fast pages, mobile-first, by default. status: live (the SEO pipeline + lint gate).
• Gaps surfaced, not hidden — Yoshi tells you what you could rank for and what's missing, in plain language. status: planned (cycle 19 scorecard → dashboard).
• Fresh content that compounds — a blog/news stream keeps the site active, which search engines reward. Yoshi can draft posts grounded in your real business for you to approve. status: planned.

Know who's finding you — analytics, built in

Yoshi has its own native analytics — not a Google-Analytics snippet you paste in and squint at. It's wired into your site from birth and surfaced in plain language on your dashboard: how many people found you, which pages + which services and areas are pulling traffic, and where your customers are coming from. Because Yoshi made every page, it can tell you which of your 1,800 pages are actually working — and suggest doubling down. status: planned (native analytics — a paid/alive-tier feature; see Plans).

Measure what matters, honestly

The Scores widget keeps grading your live site over time — performance, accessibility, SEO — so you can see it staying healthy, or catch a regression early. The numbers are real audits of your real site, not flattering estimates. status: soon (live perf API shipped; trend view wiring up).

The flywheel. Measure → surface the gap → fix it (often automatically) → the site gets better → measure again. Over time your site doesn't decay; it improves, mostly without you lifting a finger. That's the difference between a website you bought and a website that works for you. status: planned (the self-improvement loop, cycle 19).

Yoshi can tend it for you

The deeper promise: Yoshi notices things between your visits — a page that slowed down, a new term you're ranking for, a service competitors started offering — and either fixes the safe stuff and tells you, or flags the rest for a one-tap decision. Your site has a caretaker, not just a host. status: planned (background cognition, cycle 42; the autonomy dial is an open question).

🌳 Open questions (the inquisitive seam)

• How alive is "alive"? Static-but-easily-regenerated, or truly dynamic pages that read the blueprint at request time? The first is simpler + cheaper; the second enables real-time edits + personalization. Leaning: regenerate-on-edit now, dynamic-where-it-earns-it later. Cross-ref cycle 32 forks.
• Who writes the blog — Yoshi, the owner, or both? Auto-drafted-and-approved keeps it fresh without effort, but risks generic content that hurts SEO. How do we keep auto-content genuinely specific + truthful? Leaning: grounded drafts the owner must approve, never silent auto-publish. Cross-ref cycle 17 (SEO), the integrity rule.
• The autonomy dial, again. How much should Yoshi change on a live site without asking? Perf/SEO hygiene feels safe; copy + structure feel like they need consent. Does the owner set the dial ("auto-pilot" vs "ask me")? Leaning: owner-set dial, conservative default. Big cross-cutting decision; touches 19, 32, 42, 04.
• What does "measure" mean to a non-technical owner? Lighthouse scores are for us. Owners care about calls, visits, customers. Do we surface real-world outcomes (analytics, leads) over technical scores? Leaning: lead with outcomes, keep scores as the "why". Cross-ref 04 dashboard "one number".
• Seasonality + scheduled change. "Switch to winter services in November." Should the site change on a schedule you set? Powerful for trades. Cross-ref cycle 32.