Car Dealership Hosting

Dealership hosting that survives the nightly inventory feed.

A dealer site is a database that rewrites itself every night. The feed, not the shoppers, is what breaks it.

Feed imports off the web workersSold vehicles redirect, not 404Free migration
Feed-import tunedLong-running cronImage derivatives offloadedDaily backupsFree SSL24/7 support
Built for stock that moves

Everything a dealer feed asks of a host.

Inventory arrives as a file at 3am and has to be live by opening. That import is the workload, not the browsing.

Imports that finish

Feed runs get their own long-lived process with raised time and memory ceilings, so a four-thousand-vehicle update completes in one pass instead of dying halfway and leaving your listings half-updated.

No web-request timeoutResumable

Sold stock keeps its link value

When a vehicle leaves the feed its URL redirects to the closest remaining match in the same model family rather than returning a 404, so the inbound links and paid clicks that page earned are not thrown away.

Model-family fallback410 for retired trims

Photos processed off the critical path

Twenty-odd images per vehicle are resized and converted in a background queue, so an import never occupies a PHP worker generating thumbnails while shoppers are browsing the lot.

Search that stays fast as stock grows

Make, model, trim, mileage and price filters run against indexed columns rather than serialised meta, so a filtered search does not slow down as the forecourt fills.

Finance enquiries handled privately

Part-exchange and finance forms bypass the cache and are stored with the same encryption as any other customer record.

Operations

See last night's import before a customer does.

The failure a dealer site has is silent: the feed ran, half the records updated, and nobody noticed until somebody called about a car that sold last week.

  • Per-run import log with record counts
  • Alert when a feed run does not finish
  • One-click admin login, no shared passwords
  • Restore any daily backup from the dashboard
Overnight feed
4,182 vehicles
03:12
Image derivatives
Queue drained
0 pending
Sold redirects
Written this run
37
Nightly backup
Replicated offsite
running
Performance

A filtered search across four thousand cars.

Shoppers filter before they browse. That first filtered result is the page that decides whether they stay on your site or go back to the aggregator.

4,000+
vehicle records per site
Indexed
filters, not meta queries
NVMe
storage on every plan
MagicWP140 ms
Typical shared host1100 ms
Untuned VPS520 ms

Illustrative comparison of a filtered inventory search on identical stock. Your numbers depend on catalogue size and filter count.

Configuration

What we change for a dealership site

These are the settings that differ from a standard WordPress site on the same plan. Every one is a consequence of inventory arriving as a bulk feed rather than being typed in.

SettingWhat we doWhy
Feed import processRuns on the CLI with its own time and memory ceilingA four-thousand-vehicle import cannot finish inside a web request, and retrying it through a browser tab is exactly how half-updated stock happens.
WP-CronPlatform-driven, scheduled against your feed windowThe import has to run at 3am whether or not a single person visited the site overnight.
Sold-vehicle URLs301 to the nearest model match, 410 once the trim is retiredA sold listing that 404s discards the advertising spend and inbound links that page accumulated while it was live.
Image derivativesGenerated in a background queue rather than on uploadTwenty photos per vehicle multiplied by a nightly feed is thumbnail work that would otherwise land on shopper requests.
Inventory filtersIndexed columns rather than serialised postmetaMeta queries across four thousand vehicles turn every filter click into a full table scan.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Can you import our DMS feed?
Yes. We handle scheduled XML, CSV and JSON feeds from the common dealer management systems, and the import runs as a platform job rather than a browser request so it cannot time out partway through.
What happens to a car's page once it sells?
It redirects to the closest remaining match in the same model family, which keeps the inbound links and paid clicks that page earned working. Once a trim is discontinued entirely we return 410 so search engines drop it cleanly.
How many vehicles can one site hold?
We run dealer sites with five-figure inventories. The constraint is filter design rather than record count, which is why we move stock attributes into indexed columns during migration.
Do you handle multi-rooftop groups?
Yes, either as separate sites or as a multisite network sharing one feed, depending on whether stock is pooled across your locations or kept per site.
Will finance applications be cached?
No. Enquiry, part-exchange and finance URLs bypass the page cache completely, so no applicant ever sees a form carrying somebody else's details.

Move your dealership site to a host that expects the feed.

Free migration, an import that finishes in one pass, and sold stock that keeps its search value.