Case Study · Architecture audit

A structural audit of flowkey across eleven locales

flowkey teaches piano to learners in eleven languages, on a headless stack. In three fixed weeks the audit gave the team a structural read on the whole site, and a workbook their developers could start on the next day.

Client
flowkey, piano learning app, 11 locales
Engagement
Technical SEO Architecture Audit · fixed scope, fixed fee
Stack
Headless multilingual on a modern edge CDN

The challenge

flowkey runs a headless, multilingual stack serving learners across eleven language markets: a meaningful engineering surface, and a hard one to audit. The team had Ahrefs, Search Console and GA4 in house. What they wanted was a structural read on the site itself.

Is Googlebot receiving what the team thinks it is? Does the hreflang implementation hold at scale across eleven locales? Is the structured data layer doing the work it should, for Google and for AI search? They needed an outside answer on the architecture, not a list of generic SEO tips.

The approach

A fixed three week engagement, in a deliberate order. Week one: access, then the technical foundations: crawl, rendering, hreflang, sitemaps, robots. Week two: the architecture and entity layers: URL logic, canonical strategy, structured data strategy, brand entity. Week three: synthesis and delivery.

No keyword research, no content briefs, no implementation: strictly the architecture. Every finding traceable to a verified source, every recommendation rated for severity, owner and effort.

Built for a team across eleven markets

One document to understand it, one workbook to execute it.

The narrative explains the reasoning behind every finding. The workbook turns each one into a row with an owner (frontend, backend, CMS or content), an effort estimate and a link back to the reasoning, so engineering can plan sprints from it without a meeting.

The audit also recorded what was already working well, so the team knew what to protect: server side rendering was clean across templates, hreflang reciprocity held within declared pairs, and the canonical layer avoided the cross locale problems that often affect multilingual headless stacks.

What was delivered

Six pieces, designed for an async team across engineering, content and brand:

  1. Master Audit Document

    The long form narrative. Eleven sections, every finding written up with what was found, why it matters, the impact, the fix and a severity rating.

  2. Dev ready action plan

    The execution workbook. Every finding as one row: severity, owner, estimated effort, expected impact and a cross reference to the document. Plus six detail tabs, one per workstream: rendering, hreflang, canonicals, URL architecture, structured data, sitemaps and robots.

  3. Schema templates

    Ten ready to implement JSON-LD blocks, pre-filled with flowkey's content structure. Patterns Google has discontinued (HowTo, the sitelinks search box, the legacy video carousel markup) explicitly left out.

  4. Schema implementation guide

    Rollout order, locale handling and the pitfalls to avoid.

  5. Video schema reference guide

    The decision tree for when a video earns its own markup and when it belongs inside an Article.

  6. Baseline data overview

    Verified starting numbers, so the team can measure progress against a known point.

Plus a short walkthrough video, recorded async so anyone the team forwards it to can watch in their own time.

What this unlocks

The team got what they came for: a structural answer they can act on, in a workbook their developers can open and start sequencing straight away. The work is laid out as concrete batches (sitewide foundation first, then the high traffic templates, then the specialised layers) rather than as a wishlist.

The audit was delivered on time, on scope and within the fixed fee.

A similar surface?

If you run a multilingual platform where the basics seem to work but the structural picture is unclear, the Technical SEO Architecture Audit is built for exactly this: fixed scope, fixed fee, three weeks, ending with a workbook your developers can execute from.