Skip to main content

MBUSA dealer websites

mercedes/mbusa/dealers/website names one website per MBUSA dealer code, for mercedes/mbusa/dealers/website_platform to classify. MBUSA's own dealer URLs are not usable as given: most *.mercedesdealer.com hosts in NAFTA's website field no longer serve a page, and every candidate source names some sites that belong to another dealer.

Asset​

One row per dealer code that gets a website, keyed by dealer_code.

ColumnMeaning
dealer_codeMBUSA dealer code
websiteHost the chosen site's homepage lands on after redirects
sourcesCandidate sources that named the chosen site for this dealer
matched_fieldsDealer fields the chosen site's homepage shows: dealer_code, street, phone

Output metadata reports the dealer codes left without a website: those with tied sites (tied, with the sites) and those no candidate settled (without_website).

Candidates​

SourceSiteCounts for
nafta_websitewebsite of mercedes/mbusa/transformed/nafta_dealersThe row's dealer
nafta_serviceURL of the row's service entry in activitiesThe row's dealer
snapshotwebsite_snapshot.json in the asset's defs folder, the per-dealer site of the 2026-08-20 provider snapshotThe listed dealer
visorEvery vehicle-page host of each Visor dealer, from mercedes/mbusa/transformed/visor_dealersEvery dealer its homepage shows

A Visor dealer whose listings are at least max_van_share vans (Sprinter, Metris) offers no candidate. A van storefront can show its passenger-car dealer's address (mbfmvans.com shows Fort Mitchell's), and would then compete with that dealer's site.

transformed/visor_dealers has one row per Visor visor_dealer_id per day, with the day's vins, van_vins and vdp_hosts concatenated across Visor's listing pages.

Choosing a site​

Each distinct candidate host's homepage is fetched once, through the classifier's homepage fetch (browser impersonation, Retry-After, Zyte fallback). A site is the host its homepage lands on after redirects, so www.hoehnmercedes.com and www.mercedesbenzcarlsbad.com, which both land on mercedesbenzcarlsbad.com, are one site, whether the direct fetch or Zyte served the page. Hosts that differ only by a www prefix are one site.

  1. A served homepage shows a dealer when it contains the dealer's code after a dealer-code key in page data (dealerCode, mbz, mbusa… or mercedes-export; Dealer.com writes dealerCode = [{"mercedes-export":"59159"}, {"mbz":"59159"}]), the dealer's NAFTA street address, or the dealer's NAFTA main phone. A phone listed for more than one dealer identifies none. A street address compares as its house number and first street word, skipping a leading direction (S, SW, North, …) and writing ordinals as digits, so the page's "1730 S 1st St" is NAFTA's "1730 South First Street". The HTML is read whole, including page data and meta tags, and a house number may directly follow a phone number ("(859) 493-9320 2100 Dixie Hwy").
  2. A candidate site counts for a dealer only when its homepage shows that dealer. A nafta_* or snapshot site whose homepage shows only another dealer counts for no one.
  3. When several sites count for one dealer and any of them embeds the dealer code, only the embedding sites compete. Among the competing sites, the one the most sources name wins; otherwise the one showing more of the dealer's fields. A remaining tie leaves the dealer without a website.

Dealer-group sites that list several stores' addresses show every one of those dealers, so they compete for each; the tiebreaks settle most of them.

Dealer.com pages also carry vendor ids that look like dealer codes, such as {"mmd":"14148"} and a digital-retailing dealerId: "14148" on www.mbofrochester.com (MBUSA code 42122), so dealerId and similar keys are not read as MBUSA codes.