What we read in the analytics: 90 days of patterns and what we're acting on

Pubblicato il da The Language Level Check team

We just sat down and read through 90 days of analytics. Some of what we found was expected. Some wasn’t. A few things we’re going to act on this week. This post is the readout, minus the specific numbers we’d rather keep internal.

Where we’re healthy

The in-app funnel is the part we feel best about. Users who start a test mostly finish it. Users who finish are more likely than we’d guessed to share the result with someone. The 10-minute test length tracks well against typical session duration, which suggests we’ve calibrated the time investment about right.

Reading frameworks support the same picture. The languages where we have the most session volume show consistent CEFR-level distributions across users, with the bulk of results landing in the A2-B2 range. That’s where we’d expect a self-selected audience to cluster, and it tells us the scoring isn’t quietly biased toward any one level.

Where conversion is leaking

A few patterns we want to fix:

  • Bounce rate on language landing pages is too high. Visitors arrive via SEO, look briefly, and leave without engaging with the CTA. We think we’re missing two things above the fold. A clearer “what this app actually is” line in one sentence, and social proof of some kind. The fix is mostly a hero redesign, starting with our highest-traffic language page.
  • Trailing-slash URL duplicates split our SEO juice. Google has indexed both /languages/turkish and /languages/turkish/ for almost every language. Visitors are roughly evenly split. Canonical URLs are no-slash (we’ve had trailing slashes disabled at the build level for a while), but the slashed versions are out there ranking. Adding server-side 301 redirects to consolidate.
  • Localized URLs underperform their English equivalents for native-language traffic. A native speaker searching in their own language often still lands on the English version of the page rather than the localized one. The fix is probably stronger hreflang signals and possibly explicit redirects on matching Accept-Language.
  • The App Store routing bug we fixed today. Covered in the previous post. Desktop visitors outside the US were silently redirected to the US App Store regardless of which localized button they clicked.

Surprises

A few patterns we didn’t expect:

  • AI chat assistants are a meaningful referrer. Not just incidental traffic. A real channel, and a growing one. We’re going to write separately about what that implies for how we structure pages and product descriptions, because the optimization story for AI-driven referrals is different from the SEO one.
  • Some smaller markets convert disproportionately well. Tiny sample sizes individually, but the pattern repeats across enough of them to suggest the appetite for language-testing tools is geographically uneven in ways we haven’t been targeting.
  • The share-from-results action gets used more than we expected. People want to send their CEFR estimate to someone (a tutor, a friend, a teacher). We treated the share button as table stakes when we built it. The data says it should be a first-class feature.

Internal-tool tweaks worth mentioning

A few smaller things that came out of the same review:

  • Our in-app rating prompt is currently too conservative. We tightened the logic months back after early complaints about it firing too often. We tightened it too hard. Loosening it is a one-line change for the next release.
  • The in-app affiliate card design is too easy to skip. Click-through is low enough that the cards aren’t earning the screen space they take. Redesign rather than removal.
  • Our analytics events for outbound store clicks didn’t include the visitor’s locale until today’s release. Going forward, every store-click event carries the locale, so we can measure the lift from the localized App Store routing fix country by country.

What we’re acting on this week

In rough priority order:

  1. Watch the localized App Store routing fix land. Measure the lift on outbound store clicks once we have a few weeks of data on the new build.
  2. Add 301 redirects for trailing-slash URLs to consolidate canonical ranking.
  3. Loosen the rating prompt threshold so it shows after a reasonable cadence rather than almost never.
  4. Above-the-fold redesign on the top language landing pages, starting with the highest-traffic one. Clearer one-line value prop, visible social proof, more prominent CTA.
  5. Refresh the in-app affiliate card design to make it less invisible.

We’ll write up the results of each as we ship.