SEO & digital marketing
Your Powersports Website Sitemap: How to Build an XML Sitemap Google Can Trust
How an XML sitemap works for a powersports dealer website: what Google uses, accurate lastmod for daily inventory, sitemap index files and Search Console.
Quick answer
An XML sitemap is a file that lists the URLs you want Google to find. For a dealership it helps Google discover new units and recrawl changed ones, but it is only a hint: it does not guarantee indexing. List only live, canonical pages, keep lastmod accurate, remove sold units promptly and submit it in Search Console.
This article first ran in November 2020 under the headline "Your Powersports Website Sitemap is the Key to the SEO Kingdom." The sitemap is not quite a key to the kingdom, and some of the original advice no longer matches Google's documentation. It has been rewritten for dealer principals, marketing managers and whoever owns the website relationship, as a practical guide to the one file that tells Google which of your pages exist.
If you want the wider picture, including HTTPS, Core Web Vitals and JavaScript, start with our technical SEO audit for dealership websites. This guide stays on the sitemap.
What an XML sitemap does, and what it does not
Google defines a sitemap as "a file where you provide information about the pages, videos, and other files on your site." It helps Google find URLs and decide when to recrawl them. It does not make pages rank, and it does not force them into the index.
Several things the original 2020 post said, and that dealer vendors still repeat, do not match Google's current documentation:
| Common belief | What Google's documentation says |
|---|---|
| "Without a sitemap your site can't be found" | A site of "about 500 pages or fewer," with its important pages linked from the homepage, may not need one |
| A submitted sitemap gets every page indexed | A sitemap "doesn't guarantee that all the items in your sitemap will be crawled and indexed" |
| Set priority and change frequency to steer Google | "Google ignores <priority> and <changefreq> values" |
| Put "nofollow" in the sitemap to skip pages | There is no such setting. Leave the URL out, and handle indexing on the page itself |
| Update the date whenever the site rebuilds | Google uses lastmod only when it is "consistently and verifiably" accurate |
| Ping Google when the sitemap changes | Google retired its sitemap ping endpoint; pings now return a 404 error |
| The sitemap decides which duplicate URL is the main one | Sitemap inclusion is only "a weak signal" for canonicalization, weaker than redirects or rel="canonical" |
The honest summary: a sitemap is, in Google's own words, "merely a hint." A good one is a hint Google learns to trust.
Does a dealership need one?
Almost always yes. Google says a sitemap is most useful when a site is large, new with few links pointing to it, or heavy on images and video. A powersports dealer usually ticks at least two of those boxes. Count your new and used units, manufacturer model pages, service, parts and finance pages, and blog posts, and many stores pass the roughly 500 pages Google describes as a "small" site.
The bigger reason is churn. Units arrive and sell every week. A sitemap that updates with your inventory is the fastest way to tell Google that a new unit page exists, and that an old one changed.
What belongs in a dealer sitemap
List only the URLs you want to appear in search results, in the exact form you want indexed. Google asks for "fully-qualified, absolute URLs," meaning the full https address, not a relative path.
| Page type | Include? | Notes |
|---|---|---|
| Homepage, about, contact, directions | Yes | Fixed pages; change rarely |
| New and used inventory list pages | Yes, the canonical version only | Leave out sorted and filtered variants |
| In-stock vehicle detail pages (VDPs) | Yes | Add when listed, remove when sold |
| Manufacturer model and showroom pages | Yes, if indexable and canonical on your domain | Skip pages that point their canonical elsewhere |
| Service, parts, finance and trade pages | Yes | These earn steady local searches all year |
| Blog articles and guides | Yes | Often kept in their own sitemap |
| Sold units returning 404 or 410 | No | Remove them as soon as the page is gone |
| Redirected URLs, noindex pages, thank-you pages | No | Only list pages you want shown in results |
| Search-results URLs with sort or filter parameters | No | These are duplicates of the main list page |
Keep the sitemap in agreement with your canonical tags. Google warns against specifying one URL in a sitemap and a different canonical for the same page elsewhere. If a used-bike list page canonicalizes to /used-inventory/, that clean URL is the one in the sitemap. Duplicate descriptions and feed text are a separate problem, covered in our guide to duplicate content on dealership websites.
Lastmod for inventory that changes every day
This is where dealer sitemaps most often go wrong, and where most sitemap guides say the least.
Many dealer platforms regenerate the sitemap every night from the inventory feed and stamp every URL with that night's date. Google's sitemap team has addressed this directly. Google uses lastmod as a signal for scheduling recrawls, but it "needs to consistently match reality." If a page changed long ago and the sitemap says it changed yesterday, Google says, "eventually we're not going to believe you anymore." A sitemap that cries wolf every night loses the one thing that makes it useful for fast-moving inventory.
Google also says that "last modification" means "last significant modification." Applied to a dealer site, that gives a workable rule:
| Change on the page | Update lastmod? |
|---|---|
| Price change, new photos, new description or specs | Yes |
| Unit status change (for example, sale pending) shown on the page | Yes |
| Structured data added or changed, or links on the page updated | Yes, Google lists both as significant |
| Footer, sidebar, banner or copyright year | No |
| Nightly feed import with no change to that unit | No |
Two more points from Google help here. It is fine to leave lastmod out for pages whose date you cannot know, such as the homepage or a list page that only aggregates other pages. And the date must be in a supported format; Search Console tells you if it is not.
Our recommendation for a dealer: store a real "last changed" timestamp for each unit, set it only when one of the significant fields changes, and generate the sitemap from that field. Ask your provider to show you two VDPs and confirm their lastmod matches the last real edit.
Sitemap index files for large inventories
Google limits a single sitemap to "50MB (uncompressed) or 50,000 URLs." Few dealers hit that, but splitting the sitemap is still worth doing, because it lets you watch inventory separately from the rest of the site.
A sitemap index file is a list of sitemaps. Google allows up to 50,000 sitemaps in one index and up to 500 index files per site in Search Console. The sitemaps an index references must sit in the same directory as the index or lower, so keep them all at the site root.
A sensible structure for a dealer site:
| File | What it lists | How often it changes |
|---|---|---|
| sitemap_index.xml | The four sitemaps below | When any of them changes |
| sitemap-pages.xml | Homepage, service, parts, finance, about, contact, model pages | Rarely |
| sitemap-new-inventory.xml | In-stock new unit VDPs | Daily |
| sitemap-used-inventory.xml | In-stock used and pre-owned VDPs | Daily |
| sitemap-blog.xml | Articles and guides | When you publish |
The payoff comes in Search Console. Google lets you filter the Page indexing report by sitemap, so you can see how many of your listed used units are actually indexed, separately from your static pages.
How to submit your sitemap in Search Console
- Confirm you are an owner of the site's Search Console property. Without owner access, you can still list the sitemap in robots.txt.
- Check the file loads. Open the sitemap address in a browser. Google also suggests a live URL Inspection test to confirm the page fetch is successful.
- Add a robots.txt line such as
Sitemap: https://www.example.com/sitemap_index.xml(with your own domain), so every search engine can find it. - Submit it. In the Search Console Sitemaps report, paste the sitemap URL into "Add a new sitemap" and select Submit. Submit the index file; you do not need to submit each child sitemap separately.
- Read the status. "Success" means it was processed with no errors. "Has errors" means it was fetched but some entries failed. "Couldn't fetch" means Google could not load it.
- Compare discovered and indexed counts. "Discovered pages" shows how many URLs Google read from the file. Then filter the Page indexing report by that sitemap to see how many are indexed.
- Resubmit only after major changes. Google recrawls sitemaps on its own schedule, and the old ping method no longer works.
Common sitemap mistakes on dealer sites
These are the sitemap-specific problems to look for. For wider SEO errors, see our guide to common dealership SEO mistakes.
- Every
lastmodis today. The nightly-rebuild problem above. - Sold units left in the sitemap after the page starts returning 404 or 410, or worse, units listed that now redirect to the homepage.
- Old or mixed addresses. http instead of https, or "www" in the sitemap and no "www" on the site.
- Filtered and sorted URLs listed alongside the main inventory pages.
- Noindexed or redirected pages listed. They send Google mixed signals.
- The sitemap lives on a vendor's subdomain or in a subfolder, so it only covers part of the site.
- Two systems publish two sitemaps. Common after a platform change, when the old plugin keeps generating a file nobody watches.
- Time spent tuning priority and changefreq, which Google ignores.
The dealer sitemap checklist
Run this every quarter, and after any website change.
- One sitemap index at the site root, listed in robots.txt and submitted in Search Console
- Separate sitemaps for static pages, new inventory, used inventory and the blog
- Every URL is absolute, uses https and matches the page's canonical tag
- Only indexable pages: no noindex, redirected, filtered or thank-you URLs
- Sold units removed when the page starts returning 404 or 410
- New units appear in the sitemap the day they are listed
-
lastmodchanges only on a significant edit, and two sample VDPs prove it - Sitemaps status shows "Success" with no errors
- Indexed count for the inventory sitemaps checked in the Page indexing report
- No leftover sitemap from an old platform or plugin
The original article also praised HTML sitemaps, the page of links some sites keep for visitors. One can help shoppers on a large site, but it is a navigation aid, not a substitute for the XML file or for good menus. Our dealer website best practices checklist covers navigation in full.
How PSX Ascend websites handle inventory pages
PSX Ascend's powersports dealer websites connect with PSX inventory management so current vehicle details, pricing and photos feed each unit page, and the product page commits to protecting "speed, stability, and crawlability as the site grows." Whoever builds your site, ask to see the sitemap index, a sample of inventory lastmod dates and the Search Console indexed counts. The checklist above is the standard to hold any provider to, including us.
You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.
Sources
- Google Search Central, What is a sitemap (last updated December 10, 2025)
- Google Search Central, Build and submit a sitemap (last updated July 8, 2026)
- Google Search Central, Manage your sitemaps with sitemap index files (last updated December 10, 2025)
- Google Search Central Blog, Sitemaps ping endpoint is going away (June 26, 2023)
- Google Search Central, How to specify a canonical with rel="canonical" and other methods (last updated July 10, 2026)
- Google Crawling Infrastructure, How HTTP status codes affect Google's crawlers
- Search Console Help, Sitemaps report