Map Extract

To find businesses by website technology, start with a list of business websites in your target niche and area, then check each homepage for the platform's fingerprints: asset paths such as /wp-content/ for WordPress, cdn.shopify.com for Shopify, static.wixstatic.com for Wix, plus generator meta tags and response headers. Record the evidence for every detection, review a sample, and use the results to tailor an offer, not to make claims about the site's security.

Lookup services sell ready-made lists of sites by technology. This guide shows how to detect the platform yourself on a list you have already built, which suits agencies that sell by niche and town. It is part of the search, website research and AI enrichment series.

Detection signals

Every platform leaves traces in the HTML, the asset URLs it loads, or the HTTP response headers. The strongest signals are the ones the platform needs to work, because site owners cannot easily remove them.

PlatformStrong signalsSupporting signalsNotes
WordPress/wp-content/ or /wp-includes/ in asset URLs; Link header or <link> with rel="https://api.w.org/"<meta name="generator" content="WordPress ...">, /wp-json/ respondingThe generator tag is often removed; the REST API link usually remains
WooCommerce/wp-content/plugins/woocommerce/ assetswoocommerce CSS classes, wc-ajax requestsAlways on WordPress
ShopifyAssets from cdn.shopify.com; myshopify.com in the source/collections/ and /products/ paths, /pages/contactCustom domains still load Shopify assets
WixAssets from static.wixstatic.com or parastorage.comGenerator tag naming WixHard to hide
SquarespaceAssets from static1.squarespace.comSquarespace comments in the HTMLHard to hide
Webflowdata-wf-site and data-wf-page attributesAssets on Webflow's CDNCommon with design-led agencies
JoomlaGenerator tag naming Joomla/media/system/js/ paths
DrupalGenerator tag or X-Generator header naming Drupal/sites/default/files/ paths
Next.js and similar frameworks__NEXT_DATA__ script element/_next/static/ asset pathsA framework, not a CMS; often custom builds

The WordPress signal is documented: WordPress's own developer guide says "The REST API automatically adds a Link header to all front-end pages", in the form Link: <http://example.com/wp-json/>; rel="https://api.w.org/", and clients that parse HTML can find the same link element in the page head.

Other signals worth recording

  • Analytics and ad pixels: Google Analytics, Google Tag Manager, Meta Pixel, LinkedIn Insight, TikTok Pixel. A business spending on ads without conversion tracking is a clear agency opportunity.
  • Booking and chat widgets: third-party booking systems and live chat suggest a business that invests in its site.
  • Structured data: Schema.org LocalBusiness markup with address, telephone and openingHours shows someone has done local SEO work; missing markup is an opportunity. The website data extractor reads this markup in bulk.
  • SSL certificate validity and expiry: an expired certificate is a visible problem the owner will want fixed.
  • Copyright year and last updated content: a footer saying © 2017 is a weak but useful sign of an untouched site.

The bulk method

  1. Build the website list. From maps listings, search results or Companies House matches. Deduplicate by domain and remove directories and marketplaces.
  2. Check reachability. Remove domains that do not resolve, are parked or redirect to unrelated sites. See parked and dead domains in a lead list.
  3. Read robots.txt and respect rules that apply to you. RFC 9309 describes robots rules as the site owner's instructions to crawlers, though "not a form of access authorization".
  4. Fetch the homepage once, keeping the response headers and the HTML. One page is usually enough for platform detection.
  5. Render when needed. If the HTML is a near-empty shell, load it in a real browser engine so scripts run and assets load.
  6. Match signals. Apply the table above, strongest signals first. Record the platform, the matching evidence (for example asset: cdn.shopify.com/s/files/...) and a confidence level.
  7. Review a sample. Open 20 detections per platform by hand. If more than one or two are wrong, adjust the rules.
  8. Segment. Group by platform, then by niche and town.

Keep the rate polite: one homepage request per site, with a delay between sites, is plenty. Do not probe admin paths such as /wp-admin/ or /wp-login.php; you do not need them to detect the platform, and probing them looks like an attack.

Example output (fictional)

DomainPlatformEvidenceConfidencePixelsSSL
northfield-plumbing.exampleWordPressrel="https://api.w.org/", /wp-content/themes/HighNoneValid
kite-studio.exampleWebflowdata-wf-siteHighGA4Valid
ashby-catering.exampleWixstatic.wixstatic.comHighMeta PixelValid
oakroofing.exampleUnknownCustom HTML, no markersLowNoneExpired

A minimal rule set in code

If you want to try the method on a small list before using a tool, a few lines of Python with the requests library are enough to see how it behaves. This sketch fetches one homepage, keeps the headers and HTML, and checks a handful of rules:

import re, requests

RULES = [
    ("WordPress", "header", re.compile(r'rel="https://api\.w\.org/"')),
    ("WordPress", "html",   re.compile(r"/wp-(content|includes)/")),
    ("WooCommerce", "html", re.compile(r"/plugins/woocommerce/")),
    ("Shopify", "html",     re.compile(r"cdn\.shopify\.com|myshopify\.com")),
    ("Wix", "html",         re.compile(r"static\.wixstatic\.com|parastorage\.com")),
    ("Squarespace", "html", re.compile(r"static1\.squarespace\.com")),
    ("Webflow", "html",     re.compile(r"data-wf-site=")),
]

def detect(url):
    r = requests.get(url, timeout=12, headers={"User-Agent": "site-check (contact: you@yourdomain.example)"})
    headers = "\n".join(f"{k}: {v}" for k, v in r.headers.items())
    found = {}
    for name, where, rx in RULES:
        m = rx.search(headers if where == "header" else r.text)
        if m:
            found.setdefault(name, m.group(0))     # keep the evidence
    return found

It will miss script-rendered sites (which need a real browser) and anything behind a block page, which is exactly why you should record "unknown" rather than guess. Add a delay between sites and check robots.txt before you run it on a list.

Use cases for agencies

SegmentOfferWhy it fits
WordPress sites with no analyticsCare plan with tracking and monthly reportsThey have a site but no visibility
Wix or Squarespace sites in tradesLocal SEO, structured data, review generationBuilders give limited control; owners often want help
WooCommerce storesPerformance, security updates, migration optionsPlugin maintenance is a recurring need
Shopify stores without a Meta PixelPaid social setupMissing tracking limits ads
Sites with an expired SSL certificateHosting and maintenanceA visible fault the owner may not know about
Custom or unknown builds over five years oldRebuild on a maintainable platformHard to update, often unmaintained

Write outreach around what you observed and what it means for the business, accurately: "Your site runs on WooCommerce and we noticed no analytics tag on the homepage" is fine. "Your site is insecure" based on a version number is not, and it damages trust quickly. Limited companies and LLPs are corporate subscribers under PECR, so B2B email needs your identity and an opt-out; sole traders need consent or a soft opt-in. Other countries differ.

Choosing a segment

Platform alone rarely makes a segment. Combine it with two or three other fields:

  • Platform plus niche plus town: "WordPress sites of accountants in Leeds" is a list you can write one relevant message for.
  • Platform plus missing signal: "Shopify stores with no Meta Pixel" or "Wix sites with no LocalBusiness markup".
  • Platform plus business size hint: number of locations, a careers page, or a company that files small rather than micro-entity accounts on Companies House.

Small, specific segments produce better replies than "all WordPress sites in the UK", and they keep your outreach volume at a level where every message can be relevant.

Limits of detection

  • Hidden or removed markers. Security plugins remove generator tags; some hosts strip headers.
  • CDNs and proxies can rewrite or remove headers such as Server and X-Powered-By.
  • Headless setups. A shop can run Shopify or WordPress behind a custom front end, leaving few traces on the homepage.
  • Mixed estates. The main site may be WordPress while shop. is Shopify and book. is a booking platform. Check the subdomains you care about.
  • Versions are unreliable. Version strings are often missing, cached or deliberately misleading. Do not segment by version unless the evidence is strong.
  • Mentions are not usage. A blog post that mentions "Shopify" is not a Shopify store; match assets and attributes, not words.

How Map Extract helps

Map Extract's website data extractor records technology signals as part of its normal crawl of each business website, alongside the business record. It reads robots.txt and skips disallowed pages, starts with the homepage (Fast mode checks only the homepage), falls back to a rendered browser for script-only sites, and records parked, blocked or dead sites instead of treating them as data.

Technology fields it can record include the CMS, framework, ecommerce platform, server, CDN and hosting, SSL validity and expiry, structured data types found, and analytics and ad pixels (Meta Pixel, Google Analytics, Google Tag Manager, TikTok Pixel, LinkedIn Insight, Google Ads). These come from what was observed during capture, not from AI guesses. They sit next to the public business contacts, company number and website type, so you can segment by platform and niche in one export.

To build the website list in the first place, the SERP scraper collects organic results by niche and location with directory and marketplace suppression.

What it does not do: it does not test sites for vulnerabilities, it cannot see technology that leaves no trace on the pages it reads, and a detection is an observation to review, not a guarantee.

Public business and social results the app collects are uploaded automatically to Map Extract's servers while it is licensed and running; the privacy notice explains this.

Key takeaways

  • Detect platforms from signals the platform needs: asset hosts, paths, REST API links and attributes.
  • Record the evidence and a confidence level for every detection, and review a sample.
  • One polite homepage request per site is enough; never probe admin paths.
  • Pair the platform with pixels, structured data and SSL status to find a specific offer.
  • Describe what you observed accurately in outreach; never imply a site is insecure from a version string.

Frequently asked questions

How can I tell if a website uses WordPress?

Look at the page source for paths containing /wp-content/ or /wp-includes/, a generator meta tag naming WordPress, or a Link header or link element pointing to the REST API with rel="https://api.w.org/". Any one is a strong signal. The generator tag is often removed by security plugins, so check the asset paths and the REST API link as well.

How do I find Shopify stores in the UK?

Start from a list of UK retail websites, from search results, maps listings or Companies House matches, and check each for Shopify signals: assets loaded from cdn.shopify.com, a myshopify.com domain in the source, and store paths such as /collections/ and /products/. Searching for 'powered by Shopify' finds only stores that left the footer text in place.

Is website technology detection accurate?

It is accurate for platforms that leave clear fingerprints, such as Shopify, Wix and Squarespace, and good for WordPress. It is weaker for version numbers, custom builds, headless setups and sites behind a CDN that rewrites headers. Store the evidence for each detection, such as the asset URL or header, and review a sample before using the results in outreach.

Is it legal to scan websites for their technology?

Reading a public homepage and its response headers the way a browser does is ordinary web access. Respect robots.txt, keep the request rate low and do not probe for vulnerabilities, admin pages or private paths. In outreach, describe what you observed accurately and never imply a site is insecure or hacked on the basis of a detected platform or version.

Sources

  1. REST API discovery (WordPress Developer Resources)
  2. LocalBusiness (Schema.org)
  3. RFC 9309: Robots Exclusion Protocol

Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.

Find B2B Leads With Google Search Operators

Operator recipes for finding B2B prospects in any niche, how to keep directories and marketplaces out, country and language settings and repeatable lists.

10 min read

Find Wholesalers and Distributors in Any Niche

Search recipes to find wholesalers and distributors in any niche, how to tell manufacturers, distributors and retailers apart, and what to check first.

8 min read

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top