Custom Dealer and Inventory Websites — You Own the Code, the Data, and the SEO
Hand-engineered dealer and inventory websites for auto, RV, marine, powersports, equipment, and specialty retail. You own the code, the data, the inventory feed, and the SEO. We migrate cleanly off DealerSpike, DealerOn, IDS, and Frazer.
How custom dealer websites differ from rented platforms
A typical DealerSpike, DealerOn, IDS, or Frazer site is a rented template wrapped around a shared codebase. The dealer pays a monthly fee, picks colors and a logo, and uploads inventory into a CMS the platform owns. Unit-detail pages render from a template the dealer cannot meaningfully change, the schema is whatever the platform decides to ship that quarter, and the page-speed budget is held by the vendor. The day a dealer leaves, URLs, inventory data, and indexed pages walk out with the platform.
A custom dealer website inverts those defaults. The code lives in the dealership's repo. The unit-detail template is engineered for the actual inventory shape — auto, RV, marine, powersports, equipment, specialty retail — with full Vehicle / Product / Offer JSON-LD, real photo galleries, financing and credit-app embeds where licensed, and a mobile load budget tuned for the audience. The inventory feed is configurable: ingest from the existing DMS, push to classifieds and marketplace partners, hand the CRM clean lead data with attribution.
And ownership is not a marketing line. Every layer hands off cleanly: source code in the dealer's GitHub, inventory data in the dealer's database, SEO equity attached to the dealer domain, redirect map archived in writing. If the dealership ever leaves 1WebsiteNow, nothing breaks and nothing is held hostage. That is the structural reason rented platforms cannot match a custom build.
- ✕Unit-detail pages rendered from a shared template you cannot edit
- ✕Vehicle / Product / Offer schema decided by the platform, not your SEO plan
- ✕Page-speed budget held by the vendor — mobile LCP often slow on dealer-platform sites we audit
- ✕Inventory data living in the platform's CMS, not in your database
- ✕No real control over the redirect map or the indexable URL set
- ✕Lead routing fixed to the platform's integrations — your CRM gets whatever they send
- ✕Classifieds and marketplace pushes locked to platform-blessed partners
- ✕Exit cost: URLs, schema, and indexed pages leave with the platform
- Unit-detail templates engineered for your catalog, your photos, your trim logic
- Full Vehicle / Product / Offer / Brand JSON-LD validated in Rich Results Test
- Mobile-first build; CWV measured live in Lighthouse + CrUX on the audit call
- Inventory data in a database you own; daily backups; portable export any time
- You set the redirect map, canonical rules, and URL pattern — locked in writing
- Lead-router integration with your CRM, phone tracking, email, and attribution
- Classifieds and marketplace exports configurable per partner, on your schedule
- On any future migration, every layer (code, schema, data, redirects) hands off cleanly
Our 4-step migration from DealerSpike, DealerOn, IDS, or Frazer
- 01
Inventory-feed audit
The Free Website Plan identifies the three highest-priority issues. A paid discovery scope can then map where inventory data lives, how it updates, the fields the current platform handles, and the gaps that must be resolved before implementation.
- 02
Schema mapping
Every unit type on the lot is mapped to the right JSON-LD entity — Vehicle for cars and trucks, Product for parts and accessories, Offer for active pricing, Brand and AggregateRating where the data supports it. We design the schema graph before we design the templates, so unit-detail pages ship rich-result-eligible at launch instead of retrofitted later.
- 03
Phased redirect plan
Every URL on the existing DealerSpike, DealerOn, IDS, or Frazer site is mapped to its new home with a 301. Inventory URLs map by VIN or stock number; category and content URLs map to their new equivalents. The redirect map is locked in writing, deployed on staging, and verified in Search Console and a live crawler before DNS cutover.
- 04
Launch + monitoring
Cutover happens on a low-traffic window. We watch Search Console coverage, server logs, and crawl budget for the first 2 weeks live, and we keep the old platform in read-only mode until the redirect set is verified end to end. Monthly SEO and feed monitoring are available on the optional retainer afterwards; term and cancellation follow the signed proposal.
Engineered from day one.
Vehicle / Product / Offer schema
Full JSON-LD on every unit-detail page — Vehicle, Product, Offer, Brand, AggregateRating where supported. Validated in Google's Rich Results Test before launch.
Fast unit-detail templates
Mobile-first unit-detail templates with lazy-loaded responsive AVIF/WebP media and measured performance budgets.
Inventory CMS integration
DMS integrations, manual upload, or a hybrid feed — your choice. Inventory data lives in a database you own, not in a platform CMS you rent.
Lead-router integration
Form leads, phone leads (with call tracking), credit-app submissions, and chat leads routed to your CRM with full attribution by source / medium / campaign.
Classifieds-feed configurable
Configurable export feeds for classifieds and marketplace partners on your schedule, with field mapping you control — not a platform-blessed allow-list.
Photo galleries
Unlimited high-res photos per unit with reordering, primary-image control, and optional video / 360-spin embeds. Image CDN and modern formats baked in.
Financing + credit-app embeds
Credit-application and financing-partner embeds where the dealership is licensed for them — wired with proper consent UX, GA4 events, and lead-router handoff.
Owned, portable code
Source in your GitHub. Inventory data in your database. Redirect map and schema graph documented in writing. Nothing held hostage if you ever leave.
Custom dealer site vs. rented dealer platform
Scroll horizontally to review every comparison column.
| Typical rented dealer-platform site | 1WebsiteNow custom dealer site |
|---|---|
Unit-detail page rendered from a platform template you cannot edit | Unit-detail template engineered for your catalog, your photos, your trim logic |
Vehicle / Product / Offer schema set by the platform; you cannot override | Full JSON-LD designed before the templates ship; validated in Rich Results Test |
Mobile page-speed budget held by the vendor; LCP often slow on the sites we audit | Mobile-first build; CWV measured live in Lighthouse + CrUX before launch |
Inventory CMS owned by the platform; export is read-only at best | Inventory data in a database you own; daily backups; portable export at any time |
Lead routing fixed to platform-blessed CRM / call-tracking integrations | Lead router wired to your CRM, your phone tracking, your attribution stack |
Classifieds + marketplace pushes limited to a platform allow-list | Classifieds and marketplace exports configurable per partner, on your schedule |
Redirect map and canonical rules controlled by the platform | Redirect map and canonical strategy locked in writing — you set the URL pattern |
Exit cost: URLs, schema, and indexed pages walk out with the platform | Every layer (code, schema, data, redirects) hands off cleanly on any future migration |