Free AI check Book a strategy call

MyRIDI Mobility platform SEO case study

800K+ organic impressions in year one by building search surfaces beyond the brand name

MyRIDI, an urban mobility platform, was visible for its own name but needed useful non-branded search surfaces while competing with established mobility platforms. MoxSEO built route content architecture, localized fare information, app-store alignment and voice-answer structure, with measurement and release validation underneath. The case reports 800K+ organic impressions in the first year.

Sector
Urban mobility platform
Window
First year of the project
Market
Not published
Work areas
Route content, local fares, app store, voice answers
Goal
Brand awareness and app acquisition
Last reviewed
2026-10-19, Sakshi Kumari
MyRIDI homepage: ride booking, delivery and other services, with a product and vendor search bar
MyRIDI homepage, client screenshot

Found by name, missing everywhere else

MyRIDI needed useful non-branded search surfaces beyond its name, while competing with established mobility platforms. People who already knew the brand could find it. People searching for a ride, a route or a fare were not yet meeting it.

  • BeforeSearch visibility depended on the brand name.
  • CompetitionEstablished mobility platforms already held the category searches.
  • GoalA city and route discovery program supporting brand awareness and app acquisition.
  • BoundaryVisibility in search is not the same as an install. The case reports impressions, so that is the claim this page makes.

Who a search reached, before the work

Illustrative
  • myridi appMyRIDI
  • ride from {area} to {area}Established platform
  • taxi fare {city} airportEstablished platform
  • cheapest ride in {city}Established platform
  • how much is a ride to {landmark}Established platform
  • ride booking app {city}Established platform
1 of 6The pattern the work set out to change: the brand only appeared once someone already knew it.

Four work areas, one measurement spine

Each area was implemented as part of the documented project scope and reviewed against the relevant search and customer journey. Measurement setup and release validation ran underneath all four.Order follows the case study. Artifacts are illustrative templates, not client files.

  1. Route content architecture

    Pages organised around the cities and routes people actually search for, so a query about getting from one place to another has a MyRIDI page that answers it.

    Route searches describe a trip, not a brand. A clear hierarchy from brand home to city hub to route page gives each of those searches a specific destination and keeps the pages connected through internal links.

    Artifact
    Route URL map and page template
    Route URL mapIllustrative
    • /brand
    • /{city}/city hub
    • /{city}/{from}-to-{to}/route page
    • /{city}/airport/route page
    • /{city}/fares/fare page
    • /app/download

  2. Localized fare information

    Fare questions are some of the most specific searches in mobility. Localized fare information turns them into pages with a direct answer for that city.

    A reusable fare block keeps the same fields on every city and route page, so each one answers the cost question in the same, checkable way.

    Artifact
    City fare block, reused on route pages
    Fare block templateIllustrative

    Ride fare from {origin} to {destination}

    Typical fare{fare_range} {currency}

    What changes ittime of day, demand, vehicle type

    City notes{local_rules}

    Last checked{date}

  3. App-store alignment

    The goal was app acquisition, so the web page and the store listing need to make the same promise. Someone who lands from search should recognise the app they are about to install.

    Artifact
    Web-to-store alignment checklist
    Web page and store listingIllustrative
    Route pageStore listing Rides in {city}Rides in {city} Fares shown up frontFares shown up front Same city namesSame city names Link to installOpens the right listing

  4. Voice-answer structure

    Spoken and AI answers read one short passage aloud. Voice-answer structure puts a clear question and a self-contained answer on the page, so it can be quoted as is.

    Our answer extractability study found only 3% of 243 sites had passages an engine could lift cleanly, which is why the pattern matters more than the markup. The voice search guide covers the method in depth.

    Artifact
    Question and answer pattern with markup
    Answer patternIllustrative

    How much is a ride from {A} to {B}?

    A ride from {A} to {B} usually costs {fare_range}, depending on time of day and vehicle type.

    { "@type": "FAQPage",
  "mainEntity": [{ "@type": "Question",
    "name": "How much is a ride from {A} to {B}?" }] }

  5. Measurement setup

    Used to separate completed work from platform movement and customer outcomes.

    Artifact
    Baseline and reporting view

    Release validation

    Each release checked before and after it went live, for the same reason: to know what changed because of the work.

    Artifact
    Release check log

  6. 800K+ organic impressions reported in the first year.Reported figure from the case study. Not a forecast for another site.

One reported number, read carefully

The case study publishes the year-one total, not the month-by-month path or the starting baseline. So the figure below shows only what is known: where the year ended.

MyRIDI organic impressions, first yearIllustrative shape

The dashed paths are illustrative: three shapes consistent with the same endpoint. Only the orange point is a reported figure.

What the figure does mean

  • MyRIDI pages were shown in organic search 800,000+ times in the first year.
  • The impressions came from a defined client context, scope and measurement period.
  • Measurement setup and release validation were in place to separate completed work from platform movement.

What it doesn't mean

  • It is not clicks, installs or revenue. Impressions count how often a page was shown.
  • It is not a forecast or a guarantee for another website or market.
  • It isn't all down to the work. Search platforms and customer behaviour were outside agency control, and attribution depends on the analytics available at the time.

Source: MoxSEO project record for MyRIDI. What an impression is: Google Search Console help. How we handle evidence: methodology. Material changes: corrections log.

If you run a platform like this

What carries over to other ride, delivery and booking apps competing with bigger names. Each lesson comes straight from one of the work areas above.

  • Build for the search before the brand

    A new platform can't win its own name and stop there. The searches that bring new users describe a trip, a place or a price, so give each one a page.

    Route content

  • Local facts are the content

    A fare for a specific city answers the question better than a general page can. Specific, checkable local information is what makes a page worth showing.

    Local fares

  • Make search and the store say the same thing

    If acquisition ends in an install, the web page and the store listing are one journey. Mismatched promises lose people at the last step.

    App store

  • Write answers that can be read aloud

    A clear question with a short, self-contained answer serves voice assistants, AI answers and impatient readers alike.

    Voice answers

  • Set up measurement before the first release

    Without a baseline and release checks you can't tell your work apart from platform changes. Set that up first, not after the results come in.

    Measurement

  • Where it may not transfer

    Comparable work can produce different outcomes in another market. Competition, demand and the analytics you have all change the result.

MyRIDI case, common questions

6 questions about this project

All MoxSEO FAQs

MoxSEO ran a city and route discovery program for MyRIDI, an urban mobility platform. The work covered four areas: route content architecture, localized fare information, app-store alignment and voice-answer structure, with measurement setup and release validation underneath all four.

Services behind this work

The case study lists work areas, not service lines. This is how they map. App-store alignment was handled within the SEO scope.

More case studies

All case studies

Competing with
bigger names? Start with the searches.

Bring your platform and the competitors you are up against. In a free 30-minute call, Sakshi Kumari or Ashish Khan, the specialists who run MoxSEO, map the non-branded searches you could own before we propose any scope.

Book a strategy call Or email contact@moxseo.com

A call is not an engagement. We never guarantee rankings, traffic or revenue.