Automotive SEO. Structured Data
Automotive Schema Markup: Vehicle, Car and AutoDealer JSON-LD Examples
Quick answer
Automotive schema markup is JSON-LD that tells search engines exactly what a vehicle, a dealership or a repair shop is. Mark each vehicle page as Car (co-typed with Product) with an Offer for price and availability, the showroom as AutoDealer, and a service centre or garage as AutoRepair. Google stopped showing its Vehicle listing rich result in 2025, so the payoff now is product eligibility, local results and AI answers, and that only works if the markup is generated from the same data the page shows.
Structured data on an automotive site is one of those pieces of work that gets a tick in an audit and then quietly fails for years. Somebody added markup at some point, a validator returns green on the one page they check, and nobody discovers that a third of the listings are missing a required field or that the price in the markup is the pre-discount figure while the page displays the offer price.
At automotive volumes this matters more than in most categories, because the markup is not describing a handful of pages. It is describing your entire inventory, continuously, and it is one of the main ways a search engine works out what an inventory page even is.
This page gives you the copy-paste JSON-LD for the three types most automotive sites need (a vehicle listing, a dealership and a repair shop), a table for choosing between Vehicle, Car, Product, AutoDealer, AutoRepair and AutomotiveBusiness, and the steps to validate it all. My background here is marketplaces: I’ve spent years on global online marketplaces with millions of listing pages, where the only markup that stays correct is markup the template writes for you. A dealer site with 400 cars has the same problem at a smaller size.
Does Google Still Show Vehicle Listing Rich Results?
No. Google launched vehicle listing structured data for US car dealers in October 2023, announced in June 2025 that it was phasing the feature out as part of simplifying the results page, and removed the documentation in September 2025 with the note that the type is no longer shown in Search. The Search Console report and the Rich Results Test support for it went at the same time.
That doesn’t make vehicle markup pointless, and it doesn’t hurt rankings to keep it. It changes what you’re marking up for:
- Product eligibility. Google’s product structured data docs say
Carisn’t automatically treated as a subtype ofProduct, and tell you to include both types if you want the page eligible for product features. That’s why the example below uses["Product", "Car"]. - Local results. AutoDealer and AutoRepair markup backs up your Business Profile with consistent name, address, phone and hours.
- AI answer engines and other search engines. They still read schema.org, and a page that states price, mileage and availability in a machine-readable form is easier to quote than one they have to guess at.
If you want inventory inside Google’s own vehicle units, that’s a feed-based channel through Merchant Center (vehicle ads), separate from what you put on the page.
Which Schema Type Should You Use?
Use the most specific type that’s true for the page. For a single car for sale that’s Car plus Product; for the business it’s AutoDealer or AutoRepair; and AutomotiveBusiness is only the fallback when none of its subtypes fits.
| Page or business | Use this type | Why |
|---|---|---|
| Vehicle detail page for a car, SUV or van | ["Product", "Car"] with an Offer | Car carries the vehicle properties; Product makes it eligible for Google’s product features. |
| Motorcycle for sale | ["Product", "Motorcycle"] | Motorcycle is its own subtype of Vehicle on schema.org. |
| Truck, bus, plant or anything that isn’t a car | ["Product", "Vehicle"] (or BusOrCoach) | Vehicle is the parent type. Don’t force a lorry into Car. |
| Parts, tyres, accessories | Product | They aren’t vehicles, so the vehicle properties don’t apply. |
| Inventory, make or model category page | ItemList + BreadcrumbList | It’s a collection of cars, so don’t mark the grid as Car. |
| Franchise or used car showroom | AutoDealer | Subtype of AutomotiveBusiness and LocalBusiness, so it takes address, geo and hours. |
| Dealer with sales and a service centre | AutoDealer with department | Each department gets its own phone and hours. Service can be typed AutoRepair. |
| Independent garage or service centre | AutoRepair | Matches what the business does. Use AutoBodyShop for body and paint work. |
| Motorcycle dealer, rental desk, car wash, parts shop | MotorcycleDealer, AutoRental, AutoWash, AutoPartsStore | All listed subtypes of AutomotiveBusiness. |
| Automotive business that fits none of the above | AutomotiveBusiness | The parent type. Use it only when nothing more specific fits. |
The short version: Vehicle vs Car is about the object (Car is a Vehicle that’s an automobile), and AutoDealer vs AutoRepair is about what the business sells, cars or work on cars. Plenty of dealers are both, which is what department is for.
Why Inventory Pages Need the Help
A vehicle listing page is genuinely hard for a machine to read. The description is often short and feed-generated. The specification sits in a table or a set of icons. The price may appear more than once, in different forms, with finance figures alongside it. The distinction between the asking price and the monthly payment is obvious to a person and ambiguous to a parser.
Structured data removes the ambiguity. It states plainly that this page describes a specific vehicle, of this make and model and year, in this condition, with this mileage, at this price, currently available from this seller. Without it, a search engine is inferring all of that from layout, and inference at scale produces errors at scale.
The benefit shows up in two places. Pages become eligible for richer presentation in results, which affects click-through independently of position. And AI answer engines, which increasingly sit between a buyer and a website, rely heavily on machine-readable data when deciding what to include in a generated answer. A listing with complete markup is a listing they can describe confidently. One without is a listing they may skip in favour of a competitor they can parse.
“Without structured data a search engine is inferring what your listing page means from its layout. Inference at scale produces errors at scale, and automotive is nothing but scale.”
Ram Kr Shukla, SEO and Growth Consultant
What Actually Goes Wrong
On automotive sites, the markup problems fall into four consistent patterns and almost none of them are syntax errors.
The markup is correct on the pages somebody checked and missing required fields on thousands of others, usually because those listings arrived through a different feed or lack a value the template assumed would be present. Nobody notices because validation is done by spot check rather than at scale.
The most damaging category. Marked-up price differs from displayed price, availability says in stock on a sold vehicle, mileage in the markup is the figure at intake rather than at listing. This is worse than having no markup, because it is a claim that can be checked and found wrong.
Fields populated with defaults because the real data was missing: a placeholder colour, an assumed transmission, a rounded mileage. Individually harmless looking, collectively they make the entire dataset unreliable, and there is no way for a search engine to tell which fields you guessed at.
Attention goes to vehicle pages and the category pages, model pages, breadcrumbs and business information get nothing. For a dealer, the business and review markup is frequently worth more than anything on an individual listing, because it feeds the local results that produce showroom visits.
Vehicle Schema Markup Example: Car With an Offer
Here’s a complete vehicle listing in JSON-LD. Every value is a placeholder (the VIN, the dealer, the price), so swap each one for the field your inventory system already prints on the page. Don’t copy the numbers.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": [
"Product",
"Car"
],
"name": "2021 Toyota RAV4 XLE AWD",
"url": "https://www.example-motors.com/inventory/2021-toyota-rav4-xle-2T3P1RFV0MW000000/",
"image": [
"https://www.example-motors.com/photos/2T3P1RFV0MW000000-1.jpg",
"https://www.example-motors.com/photos/2T3P1RFV0MW000000-2.jpg"
],
"description": "One owner 2021 RAV4 XLE with all wheel drive and full service history.",
"brand": {
"@type": "Brand",
"name": "Toyota"
},
"model": "RAV4",
"vehicleConfiguration": "XLE",
"vehicleModelDate": "2021",
"bodyType": "SUV",
"vehicleIdentificationNumber": "2T3P1RFV0MW000000",
"itemCondition": "https://schema.org/UsedCondition",
"mileageFromOdometer": {
"@type": "QuantitativeValue",
"value": 34210,
"unitCode": "SMI"
},
"color": "Magnetic Gray Metallic",
"vehicleInteriorColor": "Black",
"vehicleInteriorType": "Cloth",
"fuelType": "Gasoline",
"vehicleEngine": {
"@type": "EngineSpecification",
"engineDisplacement": {
"@type": "QuantitativeValue",
"value": 2.5,
"unitCode": "LTR"
},
"enginePower": {
"@type": "QuantitativeValue",
"value": 203,
"unitCode": "BHP"
},
"fuelType": "Gasoline"
},
"vehicleTransmission": "Automatic",
"driveWheelConfiguration": "https://schema.org/AllWheelDriveConfiguration",
"numberOfDoors": 4,
"vehicleSeatingCapacity": 5,
"numberOfPreviousOwners": 1,
"offers": {
"@type": "Offer",
"url": "https://www.example-motors.com/inventory/2021-toyota-rav4-xle-2T3P1RFV0MW000000/",
"price": 27995,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/UsedCondition",
"seller": {
"@id": "https://www.example-motors.com/#dealer"
}
}
}
</script>What each property does, and the mistakes I see most
| Property | What goes in it | Common mistake |
|---|---|---|
@type | ["Product", "Car"] | Car on its own, which Google won’t treat as a Product. |
vehicleIdentificationNumber | The 17 character VIN, exactly as shown on the page | Stock number in the VIN field, or a VIN the page never displays. |
brand, model, vehicleConfiguration | Make as a Brand, model name, trim | Trim squashed into the model field (“RAV4 XLE”). |
vehicleModelDate | Model year | Registration date or listing date. |
itemCondition | NewCondition, UsedCondition or RefurbishedCondition as a full schema.org URL | Plain text like “Pre-owned”, which parsers can’t map. |
mileageFromOdometer | QuantitativeValue with SMI for miles or KMT for kilometres | A string like “34,210 miles”, or the intake mileage instead of today’s. |
vehicleEngine | EngineSpecification: engineDisplacement (LTR or CMQ), enginePower (BHP or KWT) | Displacement typed as text with no unit. |
fuelType, vehicleTransmission, driveWheelConfiguration | Plain values, or the schema.org drive enumeration | Defaults filled in when the feed was blank. |
offers.price, priceCurrency | The price the page displays, as a number, plus the ISO currency code | Pre-discount price, or a monthly payment in the price field. |
offers.availability | InStock, SoldOut or PreOrder | Still InStock a week after the car sold. |
offers.seller | A reference to your AutoDealer by @id | A different business name from the one on your Business Profile. |
Only mark up what’s visible on the page. If the price isn’t shown, leave offers.price out rather than adding a number a buyer can’t see. The same goes for owner count and history: include them when you hold the data, skip them when you don’t.
AutoDealer Schema Example for a Car Dealership
AutoDealer is a LocalBusiness, so it takes the same fields Google uses for local business markup: name, address, geo, phone, opening hours and department. The department property is the useful one for dealers, because sales and service almost never keep the same hours or answer the same phone.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AutoDealer",
"@id": "https://www.example-motors.com/#dealer",
"name": "Example Motors",
"url": "https://www.example-motors.com/",
"logo": "https://www.example-motors.com/images/logo.png",
"image": "https://www.example-motors.com/images/showroom.jpg",
"telephone": "+1-704-555-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "1200 Example Boulevard",
"addressLocality": "Charlotte",
"addressRegion": "NC",
"postalCode": "28203",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 35.2101,
"longitude": -80.8597
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday",
"Saturday"
],
"opens": "09:00",
"closes": "20:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Sunday",
"opens": "12:00",
"closes": "17:00"
}
],
"brand": {
"@type": "Brand",
"name": "Toyota"
},
"sameAs": [
"https://www.facebook.com/examplemotors",
"https://www.instagram.com/examplemotors"
],
"department": [
{
"@type": "AutoDealer",
"@id": "https://www.example-motors.com/#sales",
"name": "Example Motors Sales",
"telephone": "+1-704-555-0101",
"address": {
"@type": "PostalAddress",
"streetAddress": "1200 Example Boulevard",
"addressLocality": "Charlotte",
"addressRegion": "NC",
"postalCode": "28203",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday",
"Saturday"
],
"opens": "09:00",
"closes": "20:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Sunday",
"opens": "12:00",
"closes": "17:00"
}
]
},
{
"@type": "AutoRepair",
"@id": "https://www.example-motors.com/#service",
"name": "Example Motors Service Center",
"url": "https://www.example-motors.com/service/",
"telephone": "+1-704-555-0102",
"address": {
"@type": "PostalAddress",
"streetAddress": "1200 Example Boulevard",
"addressLocality": "Charlotte",
"addressRegion": "NC",
"postalCode": "28203",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "07:30",
"closes": "18:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "08:00",
"closes": "14:00"
}
]
}
]
}
</script>A few rules that keep this honest. The name, address and phone have to match your Google Business Profile character for character. The @id is what each car’s offers.seller points at, so the listings and the dealership are joined in one graph. And if you run several rooftops, each location gets its own AutoDealer block on its own location page. A single block listing every address helps nobody. How those location pages should be built is in the dealership local pages guide.
Auto Repair Shop Schema Markup Example
For an independent garage, a tyre and brake centre or a dealer’s standalone service site, use AutoRepair. It’s the same LocalBusiness pattern, plus the services you actually do, listed in hasOfferCatalog.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AutoRepair",
"@id": "https://www.example-autocare.com/#shop",
"name": "Example Auto Care",
"url": "https://www.example-autocare.com/",
"image": "https://www.example-autocare.com/images/workshop.jpg",
"telephone": "+1-704-555-0199",
"address": {
"@type": "PostalAddress",
"streetAddress": "45 Example Street",
"addressLocality": "Charlotte",
"addressRegion": "NC",
"postalCode": "28205",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 35.2203,
"longitude": -80.8102
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "07:30",
"closes": "18:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "08:00",
"closes": "14:00"
}
],
"areaServed": [
{
"@type": "City",
"name": "Charlotte"
},
{
"@type": "City",
"name": "Matthews"
}
],
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Repair and maintenance services",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Brake pad and rotor replacement"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Oil change"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Check engine light diagnostics"
}
}
]
}
}
</script>Two things to leave out. Don’t add aggregateRating to your own business markup: Google treats reviews a LocalBusiness or Organization publishes about itself as self-serving and won’t show stars for them. And don’t list services you don’t have a page or a line of copy for, because the markup has to describe what’s on the page. Body and paint shops should use AutoBodyShop instead, and if you do both, department works here the same way it does for dealers.
Generate It From the Page Data, Not Alongside It
The single decision that prevents most of these problems is architectural. The markup must be generated by the same template, from the same fields, that render the visible page. Not from a separate feed, not from a plugin with its own data source, and never by hand.
When the markup and the page draw from one source, mismatch becomes structurally impossible. The price in the markup is the price on the page because they are the same variable. When the vehicle sells and the record changes, both update together. When a field is genuinely missing, the markup omits it rather than inventing a value, because there is nothing to render.
When they draw from different sources, drift is guaranteed. Not possible, guaranteed, because the two systems will be updated on different schedules by different people, and nobody is looking at both. It’s common to find a site whose visible pages were rebuilt entirely while the markup kept describing the old catalogue structure.
The vehicle markup checklist:
- Generated by the template from the same data that renders the page, with no separate source
- Identity fields complete on every listing: make, model, year, body type
- Condition fields present: new or used, mileage, and ownership history where you hold it
- Commercial fields complete and matching the page exactly: price, currency, availability, seller
- Availability changes automatically the moment the vehicle is marked sold
- No placeholder or assumed values, ever: omit a field rather than guess at it
- Validated across the whole catalogue at scale, not by checking three pages by hand
- Category pages carry item list markup, and every page carries breadcrumbs
- Dealers add business, location and review markup, kept consistent with the business profile
The generation and validation problem is not unique to automotive. The general approach for large catalogues is in structured data and schema at scale, and the basics of which types matter are in the schema types most businesses need.
How Do You Test Automotive Schema Markup?
Test one page with Google’s tools, then test the whole catalogue with a crawler. The first proves the template works; only the second tells you whether the inventory does.
Paste a real vehicle page URL into Google’s Rich Results Test at https://search.google.com/test/rich-results. With the vehicle listing feature gone, you’re checking that the Product, merchant listing and breadcrumb items are detected with no errors, and that the test sees the rendered markup if your site injects it with JavaScript.
Run the same URL through https://validator.schema.org/. Google’s test only reports on features Google uses; the Schema Markup Validator flags properties used on the wrong type, misspelled property names and invalid values that Google quietly ignores.
Open the page and the extracted JSON-LD side by side. Price, mileage, availability, VIN and dealer name have to match what’s printed on screen. A mismatch here is the failure that does the most damage.
In Google Search Console, open the Product snippets and Merchant listings reports (grouped under Shopping) and check valid and invalid item counts after every template or feed change. There’s no vehicle report any more, so these are the ones that move.
Crawl the site with structured data extraction and validation switched on (Screaming Frog does this) and export every page’s markup. Count listings missing each field and list pages where the marked-up price or availability disagrees with the page.
Rerun the crawl monthly and after any platform, feed or theme release. Feeds change and new vehicle types arrive, and either one can silently break a field across a whole category.
Validate at Scale, Not by Spot Check
Checking a few pages in a validator tells you the template works. It tells you nothing about the catalogue, and the catalogue is where the failures live. The listings that break the markup are precisely the unusual ones: the imported vehicle with no standard trim name, the commercial van with a different specification structure, the vehicle that came through a part exchange with half the fields empty.
Proper validation means crawling the site, extracting the structured data from every page, and checking completeness and consistency across the whole set. The output should be a count of listings missing each required field and a list of pages where the marked-up price or availability disagrees with the rendered content. That report is usually uncomfortable the first time it is run.
It is also worth running on a schedule rather than once, because feeds change, new vehicle types get added, and a change to the inventory platform can silently break a field for an entire category. Structured data is not a project that completes.
“Validating three pages tells you the template works. The failures are always in the listings nobody thought about, and there are thousands of those.”
Ram Kr Shukla, SEO and Growth Consultant
Why This Matters More Now Than It Used To
Structured data used to be justified almost entirely by rich results: get the markup right, earn a slightly more attractive listing, gain some click-through. For dealers that argument got weaker in 2025 when Google retired the vehicle listing result. The case for doing it anyway now rests on something else.
The calculation has changed because of how buyers now research vehicles. A growing share of the process happens inside AI assistants, where somebody describes what they want in ordinary language and receives a shortlist. Those systems are assembling answers from sources they can parse confidently, and a page whose price, mileage, condition and availability are stated explicitly in machine-readable form is far easier to include than one where all of that has to be inferred from a layout.
The consequence is uncomfortable. If your inventory is not being cited in those answers, you were never in the consideration set, and nothing in your analytics will show it happening. There is no impression, no click and no bounce to investigate. The traffic simply never existed. Checking directly whether you appear is a straightforward exercise, and it is covered in AI SEO and generative engine optimisation and how sites get featured in AI overviews.
Complete, accurate, template-generated markup is the cheapest available insurance against that, because it happens to be exactly what both search engines and answer engines need. The work was always worth doing. It is now worth doing sooner.
The Layers Above the Listing
Because listings dominate the page count, they dominate attention, and the permanent layer gets neglected. That is backwards in terms of value, because the permanent pages are the ones that persist and rank.
Category and model pages benefit from item list markup describing the vehicles they contain, which helps a search engine understand that the page is a genuine collection rather than a filtered view. Breadcrumb markup across the site clarifies the hierarchy, which matters more on inventory sites than most because the structure is otherwise hard to infer from URLs full of stock references.
For dealers specifically, the business and review markup is the highest-value work in this whole area. It connects the website to the physical location, supports the local results that produce most showroom visits, and reinforces the business profile that frequently outranks the website itself. That interplay is covered in dealership local pages and local SEO.
Where This Sits in the Priority Order
Structured data is not the first thing I would fix on most automotive sites. If listings are being deleted on sale and the crawl budget is going to filter combinations, those are bigger problems and they are covered in sold vehicle lifecycle handling and faceted navigation control.
But it is close behind, and it has an unusual property: once it is generated correctly at template level, it stays correct without ongoing effort. It is one of the few pieces of automotive SEO work that is genuinely done when it is done, which makes it worth doing properly the first time rather than patching indefinitely.
Related reading: automotive SEO, what happens when a vehicle sells, dealership local pages, structured data at scale, the six schema types most businesses need, marketplace and classifieds SEO, and technical SEO services.
Automotive Schema Markup FAQ
What is automotive schema markup?
It’s structured data, usually JSON-LD, that describes automotive pages in schema.org vocabulary: Car or Vehicle for the cars you sell, with an Offer for price and availability, and AutoDealer, AutoRepair or another AutomotiveBusiness subtype for the business itself. It tells search engines and AI answer engines exactly what each page is instead of leaving them to infer it from the layout.
Does Google still show vehicle listing rich results?
No. Google announced in June 2025 that it was phasing out the vehicle listing rich result and removed the documentation in September 2025, along with the Search Console report and Rich Results Test support. Vehicle markup is still worth keeping for product eligibility, local results and AI answer engines, and keeping it doesn’t hurt rankings.
Should I use Vehicle, Car or Product schema?
For a car, SUV or van for sale, use both Product and Car as the type, with an Offer. Car holds the vehicle properties and Google’s docs say Car isn’t automatically treated as a Product, so co-typing keeps it eligible for product features. Use Motorcycle or the parent Vehicle type for things that aren’t cars, and plain Product for parts and accessories.
What’s the difference between AutoDealer and AutoRepair schema?
AutoDealer is for a business that sells vehicles; AutoRepair is for one that services and repairs them. Both are subtypes of AutomotiveBusiness and LocalBusiness. A dealership with a service centre should use AutoDealer and add the service centre as a department typed AutoRepair, with its own phone and hours.
Which properties should a vehicle listing include?
The identity fields (brand, model, trim in vehicleConfiguration, model year in vehicleModelDate, VIN in vehicleIdentificationNumber), the condition fields (itemCondition and mileageFromOdometer with a SMI or KMT unit), and an Offer with price, priceCurrency and availability. Add fuelType, vehicleEngine, vehicleTransmission, driveWheelConfiguration, colour and owner count when the page shows accurate values for them.
Why does automotive schema so often fail validation?
Rarely because of syntax. It fails on completeness, where required commercial fields are missing, and on mismatch, where the marked-up price or availability differs from what the page displays. Both usually come from generating the markup separately from the page content rather than from the same data source.
What happens to the markup when a vehicle sells?
The availability field must change, and it must change automatically. Markup still claiming a sold vehicle is available is a mismatch between the structured data and reality, which erodes trust in all of your markup rather than just that page. This is part of the same lifecycle rule that governs the URL itself.
Does structured data help pages rank?
Not directly as a ranking factor, but it changes how a page is understood and how it appears. It can make the page eligible for richer presentation in results, it removes ambiguity about what the page is, and it gives AI answer engines a machine-readable description they can rely on. On inventory pages the interpretation benefit alone is worth the work.
Is your vehicle markup describing a catalogue you no longer have?
Automotive structured data fails quietly, on completeness and on mismatch, and a spot check will never find it. I validate the markup across the whole catalogue and fix it at template level so it stays correct.
Tags: Automotive SEOStructured DataSchemaTechnical SEORich Results
Written by Ram Kr Shukla
SEO and growth consultant with 20+ years across global marketplaces, travel, BFSI and e-commerce, and 50+ brands. Google Analytics and Google Ads certified, Google Partner. Has worked on global online marketplaces with millions of listing pages, where structured data has to be generated at template level to stay accurate.




