Ezako
The company's own site, moved from WordPress to Elara: pages, products and articles in English and French, every old address followed, and a live chat that puts visitors straight through to the team on Matrix.
- Role
- Migration, identity, theme, development and deployment.
- Period
- 2026
- Stack
- Elara, Rust (axum), Astro, Bun, PostgreSQL, Matrix
- Links
The brief
Ezako develops AI for complex signals. Its site ran on WordPress 6.9, and the company mainly wanted to progress in GEO (Generative Engine Optimization): being understood and cited by assistants such as ChatGPT, Perplexity or Google’s AI answers.
On 15 September 2026, I audited the WordPress site for SEO and GEO and identified 29 points. I fixed them progressively, up to the migration to Elara, my CMS. Pages, articles, images and already indexed addresses had to be preserved, and the company wanted an up-to-date visual identity.
In use
The site is in English at the root and in French under /fr, with translated addresses. Every old address remains valid through a permanent redirect.
On every page, the “Talk to the team” link opens a live chat connected to a Matrix room. The team answers from its usual client, and typing and read indicators work in both directions. Outside office hours, the panel states when the team will be back; with JavaScript disabled, the same link opens the contact form.
The home page presents a spectrogram: ten seconds of hydrophone signal, from 0 to 24 kHz, with three annotated events. The annotations are text, readable by screen readers.
I also rewrote the legal notices in French and English.
Architecture
A Bun script retrieved the content through the public WordPress API: 44 pages, 48 articles, 767 media files and 141 sitemap addresses. A second script converted it to Elara’s format, one JSON file per page, article, menu and topic. The final import counts 36 pages, 33 articles, 148 media files and 79 redirects: all the useful content was carried over.
Each release switches traffic from one web instance to the other, and the site stays available during deployment.
Decisions
Generic code in Elara, specific code in the site. Any feature reusable by another client went into Elara first: translated paths, menu groups, light and dark logos, live chat. Ezako’s repository keeps the theme and the content.
An identity drawn from the logo. Ezako’s logo, four connected nodes, suggests a time series. Each section of the site opens on an annotated signal segment. I redrew the name in lowercase Mona Sans and vectorised it; the annotations use B612 Mono, a typeface designed for Airbus cockpits.
A computed spectrogram. A script generates the signal at 48 kHz and places each annotation exactly on its event. The image belongs to Ezako, and a single file serves both themes.
Measure, then fix. The mobile Lighthouse score plateaued between 91 and 94: two preloaded fonts slowed down the stylesheet. Subset to Latin characters, they weigh a third less, and the score rose to 98 or 99.
A site machines can read. Every page is rendered on the server, with a single main heading, a description and a schema.org graph (organisation, site, page). These choices follow the recommendations of Google and Bing and the Princeton GEO study (KDD 2024).
Only what has a measured effect. I set llms.txt aside: according to Ahrefs, 3% of these files receive at least one request (137,000 domains studied), and SE Ranking measures a zero correlation with citations (300,000 domains).
A single origin. All resources come from ezako.com, under a strict Content-Security-Policy.
Today
ezako.com runs on Elara, in English and French. When the theme was delivered, Lighthouse gave 100 in all four categories on desktop.