XooCode(){

Taxi

Taxi is a schema.org type for "a taxi" that has been superseded by TaxiService. Existing pages using Taxi still validate and still render, but new markup should use TaxiService.

Full example of schema.org/Taxi json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/Taxi
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Taxi",
  "name": "Dunmore Taxi Co-op (legacy Taxi markup)",
  "provider": { "@type": "Organization", "name": "Dunmore Taxi Co-op, LLC" },
  "areaServed": { "@type": "AdministrativeArea", "name": "Lackawanna County, Pennsylvania" }
}
</script>

Why the supersession

Taxi originally sat as a class used both for the concept of a taxi vehicle and the ride-for-hire service. Schema.org resolved the ambiguity by introducing TaxiService (a Service subtype) for the bookable service, separating it cleanly from the vehicle classification. The old Taxi class is preserved for back-compatibility but is marked as superseded in the vocabulary.

Migration

  • Replace "@type": "Taxi" with "@type": "TaxiService".
  • Keep the same property set — TaxiService inherits from Service and carries areaServed, hoursAvailable, offers, provider, providerMobility.
  • For the vehicle itself (a specific car in a fleet), use Vehicle or Car with vehicleSpecialUsage: TaxiVehicleUsage.

Minimal valid version

The smallest markup that still produces a valid Taxi entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/Taxi (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Taxi",
  "name": "Example Taxi"
}
</script>

Google rich results this unlocks

Taxi is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). Taxi becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common Taxi mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Using Taxi for a new implementation

    Wrong
    "@type": "Taxi" on new pages
    Right
    "@type": "TaxiService"

    Taxi is superseded. New content that uses it loses match quality with consumers that have already migrated to TaxiService.

  2. 02

    Taxi for a specific vehicle

    Wrong
    Taxi for one car in a fleet
    Right
    Vehicle or Car with vehicleSpecialUsage: TaxiVehicleUsage

    Taxi (and TaxiService) describe the service, not the car. A specific vehicle is a Vehicle / Car.

Schema properties in this example

TaxiTaxiServiceServiceVehicleCarvehicleSpecialUsageTaxiVehicleUsagenameproviderOrganizationareaServedAdministrativeArea

Also mentioned in 1 other example

Taxi also appears in TaxiService. See the full Taxi schema page for every reference.

About the example data

A migration illustration: the same Dunmore Taxi Co-op offering that should be migrated from Taxi to TaxiService.

Comments

Loading comments...

Leave a comment