Skip to content
SiteBienfait
Case study

Case study: sitebienfait.fr, built on the system it sells

How sitebienfait.fr was built on the same system it sells: the baseline facts, the shipped changes, the dated timeline and the limits of what can be claimed.

Customer
SiteBienfait
Segment
Operator-run site
Start path
Build
Permission
owned · operator-owned ·

Why this case is first

The marketing site is the first site run through the system end to end: it is written and gated by the same operator that sells the method. Publishing it as a case makes the method inspectable instead of asserted.

What the baseline measures

The baseline values come from the repository that builds this site, not from a Search Console export. That is deliberate: a build fact can be checked by anyone who clones the repository, while a traffic figure would need a data export this site does not publish.

Baseline

Build week, 2026-11-07 to 2026-11-11

Measure Value Source and date
Rendering model Static Astro 5 build, no adapter, no server runtime apps/marketing/astro.config.mjs
Client-side framework None; page JavaScript is inline and first-party only apps/marketing/package.json
Routes in the site registry 28 English pages, each with a French path apps/marketing/src/data/routes.ts

Intervention

  1. Every URL moved into one route registry, so canonical URLs, hreflang pairs, breadcrumbs and the sitemap read the same source.
  2. Per-page structured data generated from the visible page content instead of hand-written JSON-LD.
  3. A site-wide contract test that fails the build on a dead internal link, a missing image dimension or an unsourced outcome claim.
  4. Legal pages held behind a publication gate until the publishing entity is complete, so an incomplete imprint never becomes indexable.
  5. The document shell moved into one layout, with the skip link, language choice and reveal-on-scroll handled once.

Timeline


  1. The production SEO/GEO marketing site plan is committed (ba96940).

  2. The three-ways homepage hero and the Build/Rebuild/Grow workspace ship (1971b31).

  3. Route registry, generated sitemap, per-page structured data and the site-wide contract test are published.

  4. The evidence surfaces ship: case studies, examples and the changelog, and this case is published.

Outcome

Not yet measured

No measurement window has closed. This repository holds no search, traffic or ranking data for the site, so no number is printed here; the first review is due after a full measurement window from publication.

What this evidence cannot say yet

The site has no traffic history in this repository, the seasonality of the launch week is unknown, and the sample is one site. A later change in search or traffic could not be attributed to the rebuild on this evidence alone.

Where next

All case studies · Examples: before and after · Free website audit · Website migration without losing URLs

Published · Reviewed