Embed WashIndex Data on Any Site

WashIndex now ships embeddable widgets. If you write about car wash chains, cover specific metros, run a brokerage site, prep deal memos, or maintain a city guide, you can drop a small iframe into your page and get live WashIndex data alongside your own coverage — rating, footprint, damage rate, top operators, top-rated locations, monthly trend — without us in the middle. All three widget types are live at washindex.com/embed.

Three widget types

One per audience. Pick whichever fits the article.

1. Chain profile widget

Drop in any chain’s key signals: location count, states served, weighted Google rating, reviewer-reported damage rate, membership cancellation friction, and an 18-month rating sparkline. Best for articles about a specific operator — M&A coverage, brokerage listings, journalism on a chain.

Example: a card for Mister Car Wash rendering the 553-location footprint, 4.11★ weighted rating, 4.3% damage rate, and a sparkline showing the rating drift detected in our data window. Pop the iframe into your post and the data updates automatically as the underlying dataset refreshes monthly.

Source: Mister Car Wash profile on WashIndex

2. Metro market widget

Drop in any US Metropolitan Statistical Area’s structure: total car wash count, number of chains, weighted-average rating, top-10 chain share, and the top 5 chains ranked by location count. Best for PE deal memos, broker market summaries, and consolidation analysis.

For Dallas-Fort Worth that’s 4,773 locations, 96 chains, 4.52★ market average, and the chain rank from Shell on down. The same data that powers our per-MSA market analyses, distilled into a card.

Source: Dallas-Fort Worth car wash market on WashIndex

3. City best-of widget

Drop in the top 5 best-rated car washes in any city we cover, with rating and review count for each. Best for local news, lifestyle blogs, and city guides — the kind of “best of” coverage every metropolitan publication runs at least once a year.

Source: Best car washes in Plano, TX on WashIndex

How to embed

Every widget is an iframe plus a source-credit line:

<iframe src="https://washindex.com/embed/chains/mister-car-wash"
        width="100%" height="280" frameborder="0"
        title="Mister Car Wash — WashIndex profile">
</iframe>
<p>Source: <a href="https://washindex.com/car-wash-chains/mister-car-wash">
  Mister Car Wash profile on WashIndex
</a></p>

Swap the entity slug (mister-car-wash here) in both the iframe src and the link href, set the recommended height for that widget type, and you’re done. The widget renders inline, the source-credit appears just below it, and the data refreshes automatically.

The embed page at /embed has live previews of all three widget types, a one-click Copy button on each snippet, and per-widget docs. We also added a Copy iframe code button to the methodology footer of every chain, MSA, and city detail page across the site — the fastest path is usually: find the entity page, scroll to the bottom, click copy, paste.

The honest detail on the source-credit line

We could have shipped iframes alone — one tag, copy-paste, done. We chose to include the visible source-credit line below the iframe instead. The reason is straightforward enough to share openly: iframe src URLs are treated differently from <a href> links by search engines. When you put just an iframe on your page, the embedding signal is weak; you get the visual content but neither side gets the full backlink benefit. The visible <a href> credit line is what Google reads as a real outbound link from your page to ours.

That’s a real benefit for us — backlinks help WashIndex rank better, which helps more people find the data — but it’s also why the widgets are free in the first place. If you’re using one of these, please leave the credit line visible. (We also call this out in the licensing notes.)

What’s under the hood

Each widget is a self-contained HTML page with inline styles — no external CSS, no external JS, no web fonts — so it renders identically in any embedding context regardless of the host site’s CSS. Page weight is roughly 7 KB per widget. They serve with X-Frame-Options: ALLOWALL and aggressive caching, so once your page is loaded the widget displays without delay on the next view. The underlying data flows from the same JSON endpoints we ship at /api/, so if you want the raw data instead of the widget rendering, the API is right there.

One subtle decision: the per-entity widget URLs are noindex’d and the search-engine crawl is blocked via robots.txt. The widgets aren’t meant to be standalone search-result pages — they’re iframe content, and the canonical version of the same information lives at the full HTML detail page. The embed page itself stays fully indexed; only the 1,600+ per-entity widget endpoints are kept out of the index.

If you want a different widget type

The first three cover what we expect to be the most-embedded use cases. If you have a specific need — a different chart, a head-to-head comparison widget, a multi-entity comparison card, format mix, anything — let us know at contact@washindex.com. We’re happy to ship more widget types if there’s demand for them.

And if you’re embedding WashIndex in something published, we’d love to see it — send the link. It helps us understand which widget types actually get used.

Get started: washindex.com/embed