Powersports SEO Is More Than Keywords: A Technical SEO Audit for Dealer Websites

This article first ran in November 2020 with a simple point: SEO is much more than keywords. That is still true, and this rewrite covers the part the original only hinted at, the technical layer underneath your words. It is written for dealer principals, general managers and marketing managers who do not build the website themselves but need to know whether their provider has the basics right.

Keywords only help a page Google can reach, read and keep in its index. On a powersports site, with hundreds of units arriving and selling every month, that is where most of the quiet damage happens.

What technical SEO covers on a dealer site

Google's documentation describes three main phases before a page can rank: crawling, rendering (running the JavaScript) and indexing. Technical SEO keeps each one clean. Google must find every unit, model and service page by following links, see the price, specs and photos after rendering, and index the right version of each page while sold pages drop out. Around that sit the page experience basics: a secure site that works on phones and loads fast.

One part of discovery, the sitemap file, has its own companion guide: building and maintaining an XML sitemap for a dealership website. This article is the wider audit.

The technical SEO audit table

Use this table as the scorecard. The middle column is what Google's documentation says; the right column is what a pass looks like on a dealer site.

Crawling and indexing: how Google reaches your units

Google discovers most pages by following links. Google's JavaScript guidance is blunt: it can only discover links that are <a> elements with an href. A "Load more" button or a filter that rewrites the page without a link may work for shoppers and still leave units unreachable for Google. Our guide to infinite scroll SEO for inventory pages shows how to test for it with URL Inspection and the paginated-URL fix Google documents.

Indexing is a separate decision. In Google Search Console, the Page indexing report shows three groups worth watching:

1. Indexed VDPs and model pages. If in-stock units are missing, check crawlability and rendering first.
2. Pages excluded as duplicates. Usually sorted or filtered URLs. That is expected if the canonical listing page is indexed.
3. Soft 404s. Google's status code guidance says that when a page returns a success code but its "content suggests an error for Google Search, an empty page or an error message, Search Console will show a soft 404 error." On dealer sites this is usually a sold unit left at the same URL with nothing on it.

HTTPS and mobile-first indexing

Google's page experience guidance asks whether your pages are "served in a secure fashion." For a site that takes credit applications and trade details, check that every page runs on https, the http address redirects in one hop, and no page loads insecure images or scripts.

Mobile-first indexing is the bigger risk. Google indexes and ranks the mobile version of your pages, so a phone template that drops the spec table, description or structured data drops it for Google too. The test: the phone VDP and the desktop VDP contain the same content and markup. Tap targets, galleries and the rest of the phone checklist are in our guide to mobile websites for powersports dealers.

Core Web Vitals: the exact thresholds

Google's web.dev team sets a "good" threshold for each Core Web Vital: Largest Contentful Paint (when the main unit photo appears) within 2.5 seconds, Interaction to Next Paint (how fast a tap on a filter or "Call" responds) of 200 milliseconds or less, and Cumulative Layout Shift (whether the page jumps as photos and chat widgets load) of 0.1 or less. Web.dev measures them at "the 75th percentile of page loads, segmented across mobile and desktop devices," so a desktop pass says nothing about phones.

Keep this in proportion. Google says "Core Web Vitals are used by our ranking systems," and also that "there is no single signal" for page experience. Fast pages do not outrank more useful ones. Treat the thresholds as a floor, and check them in PageSpeed Insights field data for your homepage and two VDPs.

Structured data a dealership can still use

Structured data is code that describes the page to search engines. For a dealership, the type that matters today is local business markup. Google requires name and address and recommends others, including openingHoursSpecification, telephone, geo, url and department.

• Use the most specific type. Google says to "use the most specific LocalBusiness sub-type possible." Schema.org defines MotorcycleDealer and AutoDealer as LocalBusiness types, and Google allows more than one type as an array.
• Mark up departments. Sales, service and parts often keep different hours and numbers; use department, named "{store name} {department name}".
• Expect no guarantee. Google states it "does not guarantee that features that consume structured data will show up in search results." Markup must match what the page shows.

Drop old advice about vehicle markup. Google removed its vehicle listing structured data documentation in September 2025 because that type is "no longer shown in Google Search results." Your Google Business Profile does more for local visibility than any markup; our guide to local SEO for powersports dealers covers it.

Canonical tags, briefly

A canonical tag tells Google which of several similar URLs is the main one. On dealer sites, the usual culprits are sorted and filtered inventory URLs.

Google's canonicalization guidance ranks the signals: redirects and rel="canonical" are "a strong signal," sitemap inclusion is "a weak signal." It also says "don't use the robots.txt file for canonicalization purposes" and "don't specify different URLs as canonical for the same page using different canonicalization techniques." In practice: one canonical per page, matching your sitemap and your internal links.

The bigger duplicate problem on dealer sites is copied OEM and feed descriptions. That has its own guide: duplicate content on dealership websites.

Sold units: 404, 410 or redirect?

This is the part most dealer technical SEO checklists skip, and it grows every week: a store that sells, say, 60 units a month creates 60 dead VDPs a month.

Google's status code documentation sets the mechanics. "All 4xx errors, except 429, are treated the same," so a 404 and a 410 both tell Google the content does not exist, and indexed URLs returning either are removed from the index. A 301 is "a strong signal that the redirect target should be processed," and Google uses permanent redirects as a signal "that the redirect target should be canonical." A 200 page that is empty or shows an error is reported as a soft 404. Our recommendations, built on those rules:

Two habits cause most of the trouble:

1. Leaving sold VDPs live and empty. The page says "This unit is no longer available" and returns 200, so Search Console reports a soft 404 instead of a removed page.
2. Redirecting every sold unit to the homepage or the inventory list. We recommend against it. A permanent redirect tells Google the target replaces the unit, which it does not, and a sitewide rule like that hides which pages really ended.

The shopper still matters. Your 404 page can say "This unit has sold" and link to similar in-stock units while the server returns a 404 status. Shoppers get options; Google gets an honest answer. Then take the URL out of your sitemap.

JavaScript-rendered inventory

Many dealer platforms load inventory with JavaScript from a feed. Google can render it, but a page may wait in the rendering queue "for a few seconds, but it can take longer than that," and Google still calls server-side or pre-rendering "a great idea" because "not all bots can run JavaScript." What to check on a VDP:

1. View the page source (not the rendered page) and search for the price, stock number or VIN. If they appear, the content is in the HTML Google receives.
2. Run the URL through Search Console's URL Inspection live test and compare the rendered HTML with what shoppers see.
3. Make sure pagination and filters use real links, so every unit can be reached.
4. For sold units on a client-side site, Google suggests either a JavaScript redirect to a URL that returns a 404 status, or adding a noindex robots tag to the error page.

Run the audit in eight steps

You can run this audit in an afternoon with free Google tools, or hand the list to your provider.

1. Open the Page indexing report in Search Console. Note indexed pages, duplicates and soft 404s.
2. Inspect four URLs with URL Inspection: the homepage, a new-unit VDP, a used-unit VDP and a sold unit.
3. Check HTTPS. Load the http version of your homepage and confirm one redirect to https.
4. Compare phone and desktop VDPs for the same content, photos and structured data.
5. Run PageSpeed Insights on the homepage and two VDPs. Record the mobile field data for LCP, INP and CLS.
6. Test a sold URL's status code with any HTTP header checker. You want 404 or 410, or a 301 to a true replacement.
7. Run the Rich Results Test on your homepage and contact page to confirm the local business markup reads correctly.
8. Review the sitemap against the checklist in our dealership XML sitemap guide.

Repeat it every quarter and after any redesign. If your provider cannot answer what a sold VDP returns or whether prices are in the HTML, that is the finding. For the rest of the site, from offers to service paths, use our dealer website best practices checklist.

How PSX Ascend approaches technical SEO

PSX Ascend's powersports dealer websites include built-in local SEO, relevant keyword targeting and manufacturer-specific landing pages, and connect with PSX's inventory management tools so current vehicle details, pricing and photos feed the site. The goal, in the words of the product page, is to "protect speed, stability, and crawlability as the site grows." Technical structure and useful content still need ongoing quality checks and measurement, which is why we suggest running the audit above whoever builds your site.

You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.

Sources

• Google Search Central, Understand JavaScript SEO basics (last updated March 4, 2026)
• Google Crawling Infrastructure, How HTTP status codes affect Google's crawlers (last updated February 4, 2026)
• Google Search Central, Redirects and Google Search (last updated April 14, 2026)
• Google Search Central, How to specify a canonical with rel="canonical" and other methods (last updated July 10, 2026)
• Google Search Central, Mobile site and mobile-first indexing best practices
• Google Search Central, Understanding Google page experience (last updated September 22, 2026)
• Google Search Central, Local business (LocalBusiness) structured data (last updated September 8, 2026)
• Google Search Central, Latest Google Search documentation updates (vehicle listing documentation removed, September 9, 2025)
• web.dev (Google), Web Vitals (last updated October 31, 2024)
• Schema.org, MotorcycleDealer and AutoDealer
• Google, PageSpeed Insights, Rich Results Test and Search Console