Website Tech Stack & CMS Detector: contacts, socials and sitemap

Give it a list of domains and get one structured profile per website. No proxies to set up, no browser to maintain, JSON out.

What you get for each domain

• What the site is: type (online store, blog or content site, SaaS, local business...), description, main menu sections and topics.
• CMS and technologies: WordPress, Shopify, Wix, Webflow, Next.js, React, Nginx, Cloudflare and about 100 more, each with a confidence level and the evidence found.
• WordPress details: active theme and visible plugins, with versions when the site exposes them.
• Third-party services: analytics, advertising pixels, tag managers, chat, payments, CDNs and consent tools.
• Privacy signals: whether a cookie banner or consent tool is detected, and links to privacy, cookies, terms and legal pages.
• Public contact data: emails, phone numbers, organization data (JSON-LD) and social profiles.
• Site map: pages found through robots.txt, sitemaps and internal links, grouped by section.

Use cases

• Lead generation and prospecting: analyze a list of sites and filter by platform or tools (for example Shopify stores using Klaviyo), with a public contact when available.
• Agencies and freelancers: audit a prospect's stack before the first call.
• Competitive research: see which tools and platforms competitors use.
• AI agents: call it from an agent through the Apify MCP server to enrich a domain with structured data.

Input

Field	Description
domains	Domains or URLs to analyze, for example example.com.
includeSitemap	Discover pages via robots.txt, sitemaps and internal links. Default true.
maxSitemapUrls	Maximum URLs collected per domain. Default 500.
contactPages	Extra contact, legal or about pages to visit. Default 2.

Example output

{
  "input": "example.com",
  "url": "https://example.com/",
  "summary": { "type": "Online store", "about": "...", "sections": ["..."], "topics": ["..."] },
  "cms": ["Shopify"],
  "technologies": [{ "name": "Shopify", "category": "E-commerce", "confidence": "high", "evidence": ["..."] }],
  "wordpress": null,
  "thirdParties": { "trackers": 3, "byCategory": { "Analytics": ["Google Analytics"] } },
  "privacy": { "cookieBanner": true, "consentTool": "OneTrust", "legalPages": { "privacy": "..." } },
  "contacts": { "emails": ["..."], "phones": ["..."] },
  "socials": { "instagram": ["..."] },
  "sitemap": { "totalUrls": 250, "tree": {} }
}

Pricing

Pay per event: one domain-analyzed event per domain analyzed successfully. Domains that fail are not charged.

Limitations

• Only publicly available information is collected. Pages with no public link or sitemap entry cannot be discovered.
• Detection reads the HTML served without running JavaScript. Services loaded later (for example after accepting cookies) may not appear, and single-page apps may show fewer technologies than a browser would.
• The site summary is heuristic (metadata, headings and menu). It does not use AI and is approximate.
• The privacy section is a shallow automatic check, not legal advice.
• Sites behind strict bot protection may return partial data.

Responsible use

Respect each site's terms of use and applicable data protection law (such as GDPR) when using contact data.