Dealership websites
Making Your Powersports Website Ready for Mobile-First Indexing
Google indexes the mobile version of your dealer site. What must match on mobile, how to check a vehicle page with URL Inspection, and how to fix the gaps.
Quick answer
Mobile-first indexing means Google crawls and ranks the mobile version of your dealership website. If a phone vehicle page hides specs behind taps, loads photos only on swipe, or drops structured data, alt text or titles, Google indexes the thinner page. Compare mobile and desktop, then check the rendered page in Search Console's URL Inspection.
When this post first ran in 2019, the advice was simple: shoppers use phones, so make your site look good on one. That is still true, and our guide to mobile websites for powersports dealers covers the shopper side: tap targets, photo galleries, click-to-call and short forms.
This rewrite covers a narrower question that decides whether your units can be found at all: what Google sees when it reads your site as a phone. It is written for the dealer principal, marketing manager or whoever manages the website provider, and it needs no developer to run the checks.
What mobile-first indexing means for a dealer site
Google's Search Central documentation says it plainly: "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking. This is called mobile-first indexing."
For a dealership, that means the phone version of each vehicle detail page (VDP), inventory list and model page is the version Google stores and ranks. If the desktop VDP has a full spec table and 30 photos but the phone version shows a short description and one photo, Google works from the short version. Google is direct about the cost: if the mobile page has less content, "you can expect some traffic loss when your site is enabled mobile-first indexing, since Google can't get as much information from your page as before."
This is not about how pretty the phone layout is. A beautiful mobile page can still be thin to Google.
How your site is built changes the risk
Google describes three ways to serve phones. Ask your website provider which one your site uses.
| Setup | How it works | Risk for mobile-first indexing |
|---|---|---|
| Responsive design | "Serves the same HTML code on the same URL regardless of the users' device" and changes the layout by screen size | Lowest. Google notes that with responsive design "the content and the metadata are the same on the mobile and desktop version of the pages" |
| Dynamic serving | Same URL, but the server sends different HTML to phones | Medium. The phone HTML can quietly drop content |
| Separate URLs (m-dot) | A second site, such as m.yourdealership.com | Highest. Google lists extra rules for this setup, from canonical tags to error pages |
Google says it "recommends Responsive Web Design because it's the easiest design pattern to implement and maintain." If your site is still on an m-dot setup, that is worth raising at your next contract review.
What must match on mobile
Google's best-practices page lists what should be the same on both versions. Here is that list, translated to a powersports site.
| Element | What Google asks | Where dealer sites slip |
|---|---|---|
| Primary content | "Make sure that your mobile site contains the same content as your desktop site." | Spec tables, feature lists, OEM descriptions and price disclaimers dropped from the phone VDP |
| Content behind taps | Accordions and tabs are fine, but "Google won't load content that requires user interactions (for example, swiping, clicking, or typing) to load." | Specs fetched only when a "Specs" tab is tapped |
| Images | "Make sure that the mobile site has the same alt text for images as the desktop site." | Gallery photos loaded only on swipe; alt text missing on the phone template |
| Image URLs | "Don't use URLs that change every time the page loads for images." | Photo services that add a random parameter on each load |
| Structured data | "Make sure that your mobile and desktop sites have the same structured data." | Product, breadcrumb or video markup printed only by the desktop template |
| Titles and descriptions | "the title element and the meta description are equivalent across both versions" | A generic "Inventory" title on the phone VDP |
| Headings | "Use the same clear and meaningful headings on the mobile site as you do on the desktop site." | The year, make and model heading shortened on phones |
| Robots meta tags | "Use the same robots meta tags on the mobile and desktop site." | A noindex left on the mobile template after testing |
| Videos | Place the video where it is easy to find; "it might harm the video's ranking if users need to scroll down too much to find the video on mobile page." | Walkaround videos pushed below every other block on phones |
If you use structured data, Google says that when you have to prioritize types for mobile, "start with Breadcrumb, Product, and VideoObject structured data." Which markup still earns anything for a dealer is covered in our technical SEO audit for dealer websites.
Responsive is not the same as parity
Most dealer articles on this topic stop at "get a responsive site." That was the right answer in 2018. It is not the whole answer now, and this is the gap we see most.
A responsive template sends the same HTML to every device. But most dealer sites build much of the VDP after that HTML arrives: a script fetches photos from the inventory feed, another loads specs, another adds a payment widget or a chat window. Those scripts can behave differently by screen width or wait for a tap. So a site can be responsive on paper and still show Google less on mobile than on desktop.
Four dealer patterns to look for:
- The swipe gallery. The first photo is in the page and the rest are requested only when someone swipes. Google's rule is "Don't lazy-load primary content upon user interaction." Load the gallery's images in the page and let the browser defer the off-screen ones.
- The tapped spec tab. A collapsed spec table is fine when the text is already in the page. It is a problem when the tap is what fetches it.
- The phone-only template trim. Some themes hide blocks on small screens to keep the page short. Google's advice is to move content "into accordions or tabs to save space" instead of removing it.
- The "Load more" inventory list. If units 25 onward appear only after a button is tapped, give the list real paginated links too. Our technical SEO guide covers crawlable inventory in more detail.
The only reliable way to know is to look at what Google rendered, which is what the check below does.
How to check a vehicle page in URL Inspection
Search Console's URL Inspection tool shows how Google crawled a page and lets you test the live version. You need to be a user on your site's Search Console property; if your provider holds it, ask to be added. Run this on one VDP, one inventory list page and the homepage.
- Open URL Inspection in Search Console and paste the full address of a VDP for an in-stock unit.
- Read the indexed result. Note whether the page is on Google, and check "Crawled as" under page availability. It should show the smartphone crawler.
- Click "Test live URL". This fetches the page as it is now, not as Google last saw it.
- Open "View tested page". Look at the screenshot: are the price, the year, make and model heading and the first photo there?
- Search the rendered HTML for the stock number or VIN, a line from the spec table and the file name of the tenth photo. If any are missing, Google's view of the page is missing them too.
- Check "More info" for page resources that could not be loaded. Blocked scripts or images are a common cause of missing content.
- Compare with desktop. Open the same VDP on a desktop browser and list anything the desktop shows that step 5 could not find: specs, description, disclaimers, photos, video.
- Fix, re-test, then request indexing. After your provider fixes the template, run the live test again on a few pages, and request indexing for the ones that changed.
Two things to know about the tool. The live test confirms Google can access the page; it does not guarantee the page will be indexed. And it tests one URL at a time, so a template fix should be checked on several units, new and used.
Fixes by symptom
Google's troubleshooting list names the errors that stop sites from being indexed properly on mobile. These are the ones that show up on dealer sites, with the usual fix.
| What you find | Likely cause on a dealer site | Fix to ask your provider for |
|---|---|---|
| Specs or description missing in the rendered HTML | Loaded on tap, or hidden by the phone template | Put the text in the page; use accordions that only hide it |
| Only the first photo in the rendered HTML | Gallery loads on swipe | Images in the page with native lazy loading for off-screen photos |
| Missing structured data | Desktop-only markup | Same markup on every template; check URLs inside it are correct |
| Missing alt text on photos | Phone gallery component built separately | Same descriptive alt text on both, such as year, make, model and view |
| Mobile page has noindex | Leftover from testing or an m-dot setting | Same robots meta tags on both versions |
| Resources blocked | robots.txt disallows a script or image folder | Let Google crawl the files the page needs |
| Many desktop pages redirect to the mobile homepage | Old m-dot redirect rule | Give each desktop page an equivalent mobile page, or move to responsive |
| Sold or missing unit shows an error only on mobile | Mobile and desktop handle sold units differently | Same status on both versions |
Google's wording for that last case: "If a page on your desktop site serves normal contents and your mobile site's version of that page serves an error page, this page will be missing from the index."
A monthly mobile indexing check
Put this on the calendar for the first week of each month, or after any template change.
- Run URL Inspection's live test on one new VDP, one used VDP and one inventory list page
- Confirm the stock number, price, specs and all photos appear in the rendered HTML
- Confirm the title, meta description and main heading match desktop
- Confirm no noindex appears on the mobile version
- Check that a sold unit returns the same status on phone and desktop
- If you run an m-dot site, check that both versions are verified in Search Console
Speed is a separate check. For the three Core Web Vitals and how to read them on mobile, see our guide to Core Web Vitals for dealership websites. If you are comparing website providers, our guide to choosing a dealership website provider turns these checks into scored questions.
You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.
How PSX Ascend approaches mobile
The PSX Ascend powersports website experience "is designed to adapt across phones, tablets, and desktops while keeping inventory, forms, conversion paths, and essential customer actions accessible." The product page's mobile principle is "Complete on mobile": "Preserve the information and conversion paths that matter instead of hiding them for convenience." Its technical aim is to "protect speed, stability, and crawlability as the site grows," while "technical structure and useful content still require ongoing quality and measurement."
Inventory details, pricing and photos come from PSX's AI inventory management tools, so the phone and desktop pages draw on the same data. We still suggest running the URL Inspection check above on any site, ours included.
Sources
- Google Search Central, Mobile site and mobile-first indexing best practices, last updated December 10, 2025.
- Search Console Help, URL Inspection tool.
