Website Tech Profiler — Website Technology Stack Checker

Find out what a website is built with. Website Tech Profiler detects visible CMS, ecommerce platforms, JavaScript frameworks, analytics, advertising pixels, customer-support tools, payment services, CDNs and hosting signals. Paste your website URLs, run the Actor, and export a categorized technology report — no coding required.

Use it to qualify technology-based leads, compare websites, plan migrations, or review the marketing tools visible on a page. It is an independent alternative for website technology research, not affiliated with Wappalyzer or BuiltWith.

Start in three steps

1. Add one or more websites under Start URLs.
2. Keep the default settings for a fast scan. Enable Render JavaScript if the page needs a browser to display its content or you want to observe fetch/XHR requests.
3. Click Start, then open Output and download your results as JSON, CSV or Excel.

Each analyzed page produces one row. Start with a small sample before scanning a large list.

What can I use it for?

Your goal	How to use your results
Qualify sales leads	Filter a supplied website list by CMS, ecommerce platform, CRM, marketing automation or payment tools.
Compare website stacks	Compare the technologies visible on websites you select, without manually inspecting each page.
Plan a website migration	Identify visible WordPress, Shopify, Webflow, Framer, framework and infrastructure signals.
Review marketing installations	See analytics, advertising and consent tools detected in page assets and markup.
Enrich an existing company list	Add categorized technology information to your own list of website URLs.
Repeat research over time	Schedule your saved task in Apify and compare the resulting datasets in your workflow.

This Actor analyzes the URLs you provide. It does not discover companies or verify personal contact details.

What technologies can it identify?

• CMS and site builders: WordPress, Drupal, Joomla, Wix, Squarespace, Webflow, Ghost, Framer, Duda, Weebly and more.
• Ecommerce: Shopify, WooCommerce, Magento, PrestaShop, BigCommerce, Shopware and Ecwid.
• Frontend and JavaScript: React, Vue, Angular, Svelte, Next.js, Nuxt, Astro, Alpine.js, HTMX, jQuery and others.
• Marketing and analytics: Google Analytics, Google Tag Manager, Meta Pixel, Microsoft Clarity, PostHog, Hotjar, Klaviyo, HubSpot, Mailchimp and more.
• Ads and consent: Google Ads, TikTok Pixel, LinkedIn Insight, Pinterest Tag, OneTrust, Cookiebot, Usercentrics, Iubenda, Complianz and CookieYes.
• Customer support and payments: Intercom, Zendesk, Crisp, Tawk.to, Tidio, Gorgias, Stripe, PayPal, Paddle, Klarna and others.
• Infrastructure: visible server, CDN, hosting and backend hints from HTTP headers and page assets.

Detection is based on observable signatures, not access to a site's private infrastructure. A match is a research signal; an empty category means that no matching signal was found on the pages scanned.

Ready-made examples

Open the Actor's Example tasks tab for reusable configurations:

• Compare website technology stacks: a quick scan for comparing your selected websites.
• Qualify ecommerce leads by store technology: an output view focused on ecommerce, CMS, marketing and payments.
• Audit website analytics and consent tools: browser rendering and a view focused on analytics, advertising and consent technology.

Replace the sample URLs with your own list. Saved tasks do not run on a schedule unless you create a schedule yourself.

Choose the right scan

Quick scan — recommended first. Leave Deep Scan and Render JavaScript off. The Actor reads each supplied page using HTTP. New metadata and evidence come from that same response, without extra enrichment requests.

Deep scan. Enable Deep Scan to visit additional linked pages on each site's final host. Max Pages Per Site includes the supplied start pages and is enforced separately for each input host, treating www as the same site. The crawler avoids obvious downloadable files and sign-out links. You receive a separate row for every page, not one merged company profile.

Browser scan. Enable Render JavaScript for a Chromium browser scan. This can reveal content and requests unavailable in initial HTML. Browser mode uses more resources and allows a bounded wait for page hydration. It does not click consent banners, sign in, or guarantee that every deferred script will load.

Crawling rules in robots.txt are respected by default. Disallowed pages are skipped. Request failures are retried within fixed limits and, if still unsuccessful, produce a row with scan_status: "error".

Input example

{
  "start_urls": [
    { "url": "https://apify.com" },
    { "url": "https://crawlee.dev" }
  ],
  "deep_scan": false,
  "max_pages_per_site": 5,
  "include_scripts": true,
  "include_api_detection": true,
  "render_js": false,
  "include_details": true,
  "respect_robots_txt": true
}

Setting	Default	What it does
start_urls	Required	Website URLs to analyze. Include https:// or http://.
deep_scan	false	Follow additional page links within each site's final host.
max_pages_per_site	5	Maximum pages for each site when Deep Scan is enabled; accepts 1–50.
include_scripts	true	Include external script URL analysis and the first 50 script sources.
include_api_detection	true	Include legacy API-pattern hints and, when details are enabled, concrete discovered API URLs.
render_js	false	Use a browser to analyze rendered HTML and observe fetch/XHR requests.
include_details	true	Add detection sources, visible versions, metadata, third-party domains and security-header presence.
respect_robots_txt	true	Skip pages disallowed by the website's crawling rules.

The original input fields, defaults and output field names remain supported. Script tags in HTML can still provide technology signals when include_scripts is off; that option controls the additional source list and source-list analysis.

What you get

Choose Tech Stack Overview, Qualify technology leads, Analytics and advertising, or Evidence and website details in Output. The complete dataset remains available for exports and API integrations.

Output	Meaning
url, domain, title	Requested page, its domain, and page title.
Original category arrays	Technology identifiers grouped by CMS, ecommerce, analytics, frameworks, infrastructure and other categories.
all_technologies, tech_score	Unique detected technologies and their count. The score is not a quality or security rating.
server_info	Visible server and powered-by information.
scripts	First 50 script sources, preserving their relative or absolute URL format.
api_endpoints	Original human-readable API-pattern hints, retained for compatibility.
final_url, http_status, scan_mode, scan_status	Final page location, response status, HTTP/browser mode and whether analysis succeeded.
technology_evidence	The detection source groups for each technology: HTML, script URLs and/or headers. These are evidence categories, not confidence percentages.
technology_versions	Versions explicitly visible in a named generator, asset or server header. Missing versions are not guessed.
page_metadata	Description, language, canonical URL, robots directive, generator, Open Graph fields and structured-data types.
third_party_domains	Up to 100 external hosts referenced by scripts, styles, images and embedded frames. References do not prove an active integration.
discovered_api_urls	Up to 100 API-like URLs visible in markup; browser mode also includes observed fetch/XHR URLs. These are passive observations, not verified working endpoints. Query strings and fragments are removed.
security_headers	Presence of selected response headers. This is not a security audit or a compliance assessment.
scraped_at, error	Collection time and an error description when a page cannot be analyzed.

Output example

Illustrative excerpt for a fictional WordPress site; the full record also contains every original category array, including empty categories.

{
  "url": "https://example.com/",
  "domain": "example.com",
  "title": "Example Store",
  "cms": ["wordpress"],
  "ecommerce": ["woocommerce"],
  "all_technologies": ["woocommerce", "wordpress"],
  "tech_score": 2,
  "server_info": {},
  "scripts": [],
  "api_endpoints": [],
  "final_url": "https://example.com/",
  "http_status": 200,
  "scan_mode": "http",
  "scan_status": "success",
  "technology_evidence": [
    { "technology": "woocommerce", "category": "ecommerce", "sources": ["html"] },
    { "technology": "wordpress", "category": "cms", "sources": ["html"] }
  ],
  "technology_versions": { "wordpress": ["6.8.1"] },
  "page_metadata": {
    "description": "Browse our collection",
    "language": "en",
    "canonical_url": "https://example.com/",
    "robots": null,
    "generator": "WordPress 6.8.1",
    "og_title": null,
    "og_description": null,
    "og_type": null,
    "structured_data_types": ["Organization"]
  },
  "third_party_domains": [],
  "discovered_api_urls": [],
  "scraped_at": "2026-09-20T10:00:00"
}

Pricing and cost control

See the Pricing tab for current prices and plan discounts. Deep Scan can produce several billable rows per site. Keep it off for a one-page scan, use a small per-site limit when enabled, and set a maximum charge for your run in Apify. The Actor stops additional scanning when the SDK reports the charge limit has been reached. Error records also occupy dataset rows and may count under the Actor's dataset-item pricing.

Browser rendering is useful when you need it, but HTTP mode is the lighter default. External enrichment APIs are not required.

Frequently asked questions

Can I identify every technology behind a website? No. Server-side tools, databases and hidden services may leave no public signature. Detection covers signals observable on the scanned pages.

Why did a technology disappear compared with an earlier scan? Pages can change or load different assets. This release also narrows ambiguous signatures so ordinary text such as “Spring sale” or a generic button class no longer counts as proof of a framework.

Does this work like Wappalyzer? It serves a similar website-research use case with its own signature rules and Apify datasets. It does not use the Wappalyzer database or promise identical coverage.

Can I export to a spreadsheet or connect an automation? Yes. Use Apify's dataset exports or connect the Actor through your existing Apify integrations, API, Make or n8n workflow.

Does API detection call the discovered URLs? No. It reports URLs found in the page and, in browser mode, requests made by the page itself. It does not probe API endpoints.

How do I get help with a missed detection? Open an issue on this Actor with the public page URL, expected technology and run link. Avoid posting credentials or private input.

Discover more tools for your workflow

Turn website research into your next automation. Explore all Lofomachines Actors for scraping, market research and data collection tools you can run without writing code.