Skip to content
Craft Solution Tech
All work
Website2026Vocational training · France

Regarde-moi

Regarde-moi

The starting situation

A Qualiopi-certified beauty training centre near Avignon whose visibility rested on Instagram and word of mouth. Someone searching for “eyelash extension training Avignon” didn't find it, and her first question, how to pay for it, was answered nowhere.

What was delivered

A site that answers the only two questions a candidate has: what exactly will I learn, and who pays. One page per course with its official code, a page comparing the six funding schemes, the Qualiopi certification explained, and in-depth articles sourced to the official registries. All pre-rendered, with no database and no back office to maintain.

What it changes

The project as the people using it every day see it.

  1. 01

    Findable where students actually look

    The town appears in the visible copy, not just in the tags. The address is cited identically across all nineteen pages, and the centre is described to Google as a local business: hours, contact details, area served.

  2. 02

    The funding question met head-on

    Six schemes compared, with the official codes of the courses concerned. It's the first thing people ask on the phone; it no longer takes over the conversation.

  3. 03

    Nothing to maintain to stay online

    No database, no back office, no monthly subscription to a tool. The site runs on pre-computed pages: there's nothing that can break down on a Sunday evening.

The screens, one by one

Each capture stays put while you read what it demonstrates, and each is paired with its phone version.

The course page

01 / 03

The course page

The only page that has to convert. Price shown, certification code, duration, skills covered, career outcomes, and a link to the official registry for anyone who wants to check. Two buttons: ask a question right away, or request the detailed syllabus.

Under the hood

Marked up as a `Course` with its session, its offer and the professional qualification it prepares. A price that isn't known yet isn't sent to Google: the guard filters it out rather than inventing one.

On a phone

The practical-information panel moves below the content instead of disappearing, and both buttons stay within thumb reach.

Funding, met head-on

02 / 03

Funding, met head-on

It's the question that blocks everything, so it gets a page of its own. The schemes that can be used, the coverage available, payment in instalments, and help putting the file together, because nobody manages it alone.

Under the hood

The FAQ is marked up as a `FAQPage` whose text sent to Google comes from the same source table as the text on screen. They cannot drift apart.

On a phone

The summary panel moves under the headline: on a phone you read the promise before the detail.

The certification, shown

03 / 03

The certification, shown

Qualiopi is what makes the courses fundable, so it's what decides enrolment. The certificate is displayed in full, with its number, the certifying body and its expiry date, and opens as a PDF in one click.

Under the hood

The credential is declared as an `EducationalOccupationalCredential` on the organisation's identity record, with its number and its certifier.

On a phone

The certificate reads full-width below the text, rather than shrunk alongside it.

The rest of the site

Click to enlarge: a dense interface can't be read at postage-stamp size.

The same site, on a phone

Not a stripped-down version: the same pages, the same content, the same paths. Most visits come from a phone.

The decisions, and why

Each decision carries its reason, then what would break without it.

  1. 01

    The structured data refuses to lie

    Two rails in the code. A price that isn't known yet isn't marked up: a function filters out template values instead of sending them to Google. And the rating shown on the site, which comes from Google itself, is deliberately not re-declared as an `aggregateRating`.

    Without it: Marking up a third-party rating or a fictional price yourself invites a manual action. You then lose far more than you hoped to gain.

  2. 02

    Local search before anything else

    For a centre this size it's the only realistic lever: nobody outranks the large training groups on “beauty training”, but “eyelash extensions near Avignon” can be won. Hence the location in the copy humans read, an identical address citation everywhere, and markup that co-types the centre as a local business.

    Without it: A town present only in invisible tags carries no weight. Google reads what visitors read.

  3. 03

    A course is declared as a course

    Each page is marked up as a `Course`, with its session, its offer, its workload in normalised format and the professional qualification it prepares, official codes included. That's what lets a page appear as something other than a plain blue result.

    Without it: Without that markup a course page is a page like any other, competing on equal terms with directories.

  4. 04

    The marked-up FAQ says exactly what the page shows

    The text sent to Google and the text the visitor reads come from the same source table. They cannot drift apart, not even after a correction made in a hurry.

    Without it: Marked-up content that differs from visible content is treated as cloaking, the kind of fault you discover six months later.

  5. 05

    No CMS for nineteen pages

    The content lives in the code, versioned and reviewed like the rest. Every route is pre-computed at build time: no database to query, no plugin to update, nothing to back up.

    Without it: A CMS on a site this size adds a dependency, an attack surface and a monthly bill, for no gain at all.

  6. 06

    Readable, including when reading is hard

    Contrast checked to AA, a form with real labels and messages announced to screen readers, a skip link, a published accessibility statement. The audience is mostly on a phone, often outdoors.

    Without it: Light grey text on cream looks fine on the designer's screen, and becomes unreadable in sunlight on a phone.

Our role
Design, copywriting, development, search
Type
Website
Technologies
  • Next.js 16
  • TypeScript
  • Tailwind CSS v4
  • React Hook Form + Zod
  • Resend
  • JSON-LD Course / FAQPage

Tell us what you are trying to build.

Message us on WhatsApp

Other work

Bahia Renov Pro
Business software2026

Bahia Renov Pro

Business software · Spain

Sites were run on a shared spreadsheet and the phone. Three people typed the same information, and every subsidy file had to reach the scheme operator with the right papers in the right order, or be rejected.

Read the case study

Terres de Villas
Website2026

Terres de Villas

Luxury real estate · France

A young agency in a market where credibility is decided before the first appointment. Facing names established for twenty years, it had to look settled from day one, and exist in English without doubling the typing.

Read the case study

SAVY
Mobile app2026

SAVY

Personal finance · Studio product

Keeping a budget together happens in a shared spreadsheet, or not at all. Someone fronts an expense, nobody knows where the month stands, and the conversation always comes back to the same place: who paid for what.

Read the case study