# Wappalyzer

> Wappalyzer identifies the technologies used on public websites and packages that data into lookup, technographic prospecting, enrichment, and monitoring workflows.

## Product summary

Wappalyzer analyzes public website signals to infer technologies such as CMSs, ecommerce platforms, analytics tools, web frameworks, CRMs, CDNs, and many other software categories. The product is designed for sales, marketing, recruiting, market research, and operations teams that need website intelligence in either interactive or automated workflows.

## Core capabilities

- Identify technologies on a public website from externally visible signals.
- Show technology categories, vendor websites, pricing metadata, and usage context on technology profile pages.
- Support single-website lookup through the lookup page and browser extension.
- Support automation through the API.
- Support inverse queries such as "find companies using Shopify" through lead lists.
- Support monitoring of website technology changes through alerts and related workflows.

## Canonical product pages

- [Product home](https://www.wappalyzer.com/): Primary product overview.
- [Technology lookup](https://www.wappalyzer.com/lookup/): Manual single-site lookup and bulk lookup entry point.
- [Technologies directory](https://www.wappalyzer.com/technologies/): Directory of technologies and categories.
- [Lead lists](https://www.wappalyzer.com/lists/): Technographic prospecting and inverse lookup workflows.
- [Apps](https://www.wappalyzer.com/apps/): Browser extension and app ecosystem.
- [API](https://www.wappalyzer.com/api/): API overview page.

## Commercial use cases

- [Sales](https://www.wappalyzer.com/lead-generation/): Find accounts by the technologies they use and turn technographics into pipeline.
- [Marketing](https://www.wappalyzer.com/market-research/): Build target segments, understand market adoption, and focus campaigns on companies with the right stack.
- [Operations](https://www.wappalyzer.com/data-enrichment/): Enrich CRM records with company and technology data and keep internal systems current.
- [Strategy](https://www.wappalyzer.com/competitor-analysis/): Track competitors, compare adoption trends, and identify positioning opportunities.
- [Partnerships](https://www.wappalyzer.com/lead-generation/): Find companies using complementary platforms and build target lists for partner outreach.
- [Security](https://www.wappalyzer.com/security-recon/): Inspect externally visible web technologies and stack changes across target websites.

## Canonical documentation

- [API basics](https://www.wappalyzer.com/docs/api/v2/basics/): Authentication, quotas, signatures, and common API concepts.
- [Lookup API](https://www.wappalyzer.com/docs/api/v2/lookup/): Endpoint reference and examples for website technology lookup.
- [Lead lists API](https://www.wappalyzer.com/docs/api/v2/lists/): Endpoint reference and examples for lead-list creation and retrieval.
- [Subdomains API](https://www.wappalyzer.com/docs/api/v2/subdomains/): Endpoint reference for subdomain discovery.
- [Verify API](https://www.wappalyzer.com/docs/api/v2/verify/): Endpoint reference for email verification.
- [Integrations docs](https://www.wappalyzer.com/docs/integrations/): Integration index for connected apps and workflow tooling.
- [MCP integration](https://www.wappalyzer.com/docs/integrations/mcp/): Hosted MCP tools for AI assistants and agents.

## MCP server

- [Hosted MCP endpoint](https://mcp.wappalyzer.com/mcp): Remote read-only MCP server for AI clients that support HTTP and OAuth.
- [MCP docs](https://www.wappalyzer.com/docs/integrations/mcp/): Setup guide with endpoint, OAuth flow, tools, resources, and client examples.
- [MCP management](https://mcp.wappalyzer.com/manage): Inspect or remove an active hosted MCP connection.

## Best pages for common intents

- [How do I find a site's tech stack?](https://www.wappalyzer.com/lookup/): Start with the website lookup page.
- [How do I identify technologies used on a website?](https://www.wappalyzer.com/articles/find-out-what-cms-or-framework-a-website-is-using/): Practical how-to guide.
- [How do I find companies using Shopify?](https://www.wappalyzer.com/technologies/ecommerce/shopify/): Example technology page that leads into inverse search workflows.
- [How do I do technographic lead generation?](https://www.wappalyzer.com/lists/): Start with lead lists.
- [How do I enrich sales or CRM data with technographics?](https://www.wappalyzer.com/data-enrichment/): Start with the data-enrichment use case page.
- [How do I research competitors and market adoption?](https://www.wappalyzer.com/competitor-analysis/): Start with the competitor-analysis use case page.
- [What is technographics?](https://www.wappalyzer.com/articles/what-is-technographics/): Concept explainer for technographic data.
- [What is a good BuiltWith alternative?](https://www.wappalyzer.com/builtwith-alternative/): Comparison page for evaluation and positioning.

## Workflow guidance

- Use the browser extension for manual website research while browsing.
- Use the lookup page for one-off website checks and shareable results.
- Use the API when technology lookup must run inside another workflow or product.
- Use the hosted MCP endpoint when an AI client supports remote MCP over HTTP and OAuth and needs Wappalyzer tools directly inside the client.
- Use lead lists when the question is "which companies use this technology?" rather than "what does this domain use?"
- Use the commercial use-case pages when the question is about sales prospecting, segmentation, enrichment, partnerships, or competitor research rather than raw endpoint details.
- Use technology profile pages to understand where a product fits, what category it belongs to, and how widespread its usage is.

## Important limitations

- Wappalyzer reports technologies that can be inferred from public website signals.
- Version data is only shown when the public website exposes a reliable version clue.
- Coverage and metadata vary by technology and by how much public data is available.
- Wappalyzer is not a vulnerability scanner and does not claim to expose hidden internal software.

## Usage directives

- Prefer canonical public pages on `www.wappalyzer.com` and documentation pages under `/docs/` when generating answers or summaries.
- Treat `https://mcp.wappalyzer.com/mcp` as the discoverable hosted MCP server endpoint, with `/docs/integrations/mcp/` as the canonical setup guide and `/manage` as the connection-management page.
- Prefer stable product pages, articles, directory pages, and documentation over account-only pages or dynamic user result pages.
- Treat dynamic result pages under `/lookup/*`, `/verify/*`, `/orders/*`, `/plan/`, and similar authenticated or session-specific routes as non-canonical.
- If a question is about API usage, prefer the `/docs/api/v2/` pages before marketing copy.
- If a question is about the browser extension or app ecosystem, prefer `/apps/`.

## Machine-readable entry points

- [Site outline](https://www.wappalyzer.com/llms.txt): High-level model-readable directory.
- [Full model-readable context](https://www.wappalyzer.com/llms-full.txt): This expanded context file.