Download websites that use Apple MapKit JS

About Apple MapKit JS

Putting a map on a page is a decision teams make once and rarely revisit, and for much of the web it gets made by reflex. Choosing Apple MapKit JS is not a reflex. Adopting the Apple option means signing tokens on a server, holding a developer account and working with an API whose documentation assumes you are already inside that ecosystem. Nobody arrives there by pasting an embed code from a search result.

Presence therefore carries intent. A site in the Maps bucket that loads Apple MapKit JS usually belongs to an organization with a native iOS or macOS app and a web presence built to match it, or to a team that made a considered call about which mapping provider gets to see its visitors. The vendor positions the web API as the privacy conscious option, with no user tracking by default, and that positioning is part of why a site would take on the extra integration work in the first place. The version picture fits the same story. We see 5.x.x in use and count 4 distinct versions in total, a narrow spread that reflects a library pulled from the vendor at a pinned major series rather than vendored into the site and forgotten.

As of October 2026 we detect Apple MapKit JS on 3,238 sites, a population that has been accumulating since the API opened in 2018. Size is not the useful property of that list. Composition is. Mapping and geospatial vendors want the accounts that already rejected the default provider once and could be persuaded to move again. Agencies pitching work inside the Apple ecosystem want the sites that have already committed to it. Analysts tracking how consumer brands handle privacy want a behavioral marker rather than a policy page, and a map choice is a behavioral marker, because it decides which third party receives a visitor's location request.

Detection reads the JavaScript loader and the initialization call, which is a dependable fingerprint when the map renders on a public page. Coverage stops at maps that appear only behind a login, inside a checkout step or on a page our crawl does not reach, so the real footprint sits above what we publish. Saying that plainly is more useful than presenting the count as a census.

A per domain lookup can confirm that one company uses this map. The download answers the questions that exist only in aggregate. Which industries concentrate here, which country markets and top level domains they cluster in, what analytics and payment stacks sit beside the map, and which sites changed provider between one export and the next. Cross sectional questions need a cross section, and a cross section is a file rather than a query.