Waycraft

Our own site: showcase and back office

Waycraft Studio

  • Website
  • Back office
  • Automation
  • Internal project
Visit the site
Screenshot of the Waycraft Studio website

The problem

For a one-person studio, the website, prospecting, quotes and publishing end up scattered across several tools, with no overall view.

The solution

A bilingual website that works as the showcase, and behind it a private admin area that runs the studio: prospecting, assignments, quotes, publishing, knowledge base, analytics and project monitoring. One database, and the site is the first client of its own tools.

Approach

  1. The site is built with Next.js (TypeScript, Tailwind), in French and English: one address per language, page-specific metadata and JSON-LD structured data, a sitemap, and audience measurement that only starts after consent. It is rendered on demand, with a Content Security Policy using a per-request nonce. The free audit and the diagnostic are real online tools, not mock-ups.

  2. For search engines and AI assistants, it exposes llms.txt, llms-full.txt, ai.txt, a summary and the FAQ as JSON; the FAQ and llms-full.txt are generated from the same data as the pages so they never drift apart.

  3. Behind it, a private admin area (Convex, access limited to a single e-mail address) brings together: prospecting with Google Places search, freelance assignments fed by a local agent, a quote generator based on the price grid, publishing (ideas, AI-assisted writing, monthly calendar, the site's blog), a knowledge base, analytics (GA4, Search Console, SEO/GEO audit, speed) and a page tracking the state of the projects.

  4. On the AI side, keys are entered in the admin, encrypted, with a model and fallback models per use. Quote prices come from the price grid, never from the AI, which only writes the introduction and terms. The local agents (assignments, prospecting, post writing) write to the same database through entry points protected by a secret.

What runs on its own

  • An article scheduled in the calendar goes live on the blog at the planned minute, with no manual step, and Bing is notified through IndexNow.

  • The monitoring page reads the availability of the projects' databases and the age of their backups, and flags a backup older than eight days.

  • Assignments found by the local agent land in the admin without duplicates.

  • Prospects enriched by the prospecting agent fill in existing records without overwriting what was edited by hand.

Site SEO / GEO audit

Scores measured on October 4, 2026 across 26 public pages of waycraft.studio, with Waycraft's in-house audit tool (the same one used on waycraft.studio). They describe the site's current state.

  • 99

    Overall

    99 / 100

  • 100

    Technical

    100 / 100

  • 97

    Content

    97 / 100

  • 100

    GEO (AI assistants)

    100 / 100

What the score is based on
  • Overall: the average of the three scores.
  • Technical: page title (20 to 65 characters), meta description (70 to 160), canonical tag, page language, a single h1, indexable page, Open Graph tags, mobile viewport.
  • Content: length (at least 200 words for editorial pages), image alt text, internal links, h2 heading structure.
  • GEO: valid JSON-LD structured data, dates in that data, AI crawlers allowed, presence of llms.txt, llms-full.txt, ai.txt and ai/summary.json.

This is not a Google rating. It is a transparent checklist: each criterion is weighted and the score is the share of pages that meet it. It measures the site's technical state, not its ranking or traffic.

Got a similar project in mind?