What's Behind Their Website? Analyzing a Competitor's Tech Stack
A competitor's homepage tells you what they sell. It doesn't tell you how they actually run marketing. Every website leaves traces of the tools behind it — the CRM capturing form fills, the analytics platform measuring traffic, the CMS serving pages, the live chat widget, the ad pixels tracking conversions, the automation tools connecting it all. Read those traces and you get a map of their marketing infrastructure, not just their pitch.
Why the tech stack matters more than the copy
Copy tells you positioning. The stack tells you investment and maturity. A competitor running a marketing automation platform, a CRM and three ad pixels is running paid acquisition seriously. One with only Google Analytics and no chat widget probably isn't. The stack also shows you tools you might be missing — a retargeting pixel you haven't installed, a chat tool converting visitors while yours just sits there, an automation platform doing the follow-up you're doing manually.
What you can find, and where it lives
| Category | What to look for | Where it usually shows up |
|---|---|---|
| Analytics | Google Analytics, GA4, Hotjar, Mixpanel, Amplitude | Page source, network requests |
| CRM / forms | HubSpot, Salesforce, Zoho, Pipedrive | Form action URLs, embedded scripts, cookies |
| CMS / framework | WordPress, Webflow, Shopify, Wix, Next.js | Page source, generator meta tag, file paths |
| Live chat | Intercom, Drift, Tawk.to, WhatsApp widget | A chat bubble script loaded on every page |
| Ad pixels | Meta Pixel, Google Ads tag, LinkedIn Insight Tag | Page source, network requests |
| Automation / email | Mailchimp, ActiveCampaign, Klaviyo, Zapier webhooks | Form endpoints, embedded scripts, email headers |
| Hosting / CDN | Vercel, Netlify, Cloudflare, AWS | Response headers, DNS records |
The workflow
- Inspect the page source and network requests on a competitor's homepage and a form page.
- Detect known tool signatures — script URLs, cookie names, generator tags.
- Confirm with a second signal (a form submitting to a CRM endpoint, not just a script tag left over from testing).
- Map the tools onto categories: analytics, CRM, CMS, chat, ads, automation, hosting.
- Compare against your own stack and note the gaps.
Three ways to actually do it
1. View source and network requests, manually
- Right-click → View Page Source, and search for familiar script domains:
googletagmanager.com,hs-scripts.com(HubSpot),connect.facebook.net(Meta Pixel),intercomcdn.com,cdn.shopify.com. - Open DevTools → Network tab, reload the page, and filter by
.jsto see every script actually loading, including ones added after page load. - Check the page's
<meta name="generator">tag — many CMS platforms (WordPress, Webflow, Wix) announce themselves there.
2. Browser extensions built for this
- Wappalyzer and BuiltWith are browser extensions that detect and label most of a site's stack automatically — CMS, analytics, CRM, hosting, ad tech — in one click.
- They're a starting point, not proof. A detected tool can be unused, mid-migration, or a leftover script. Confirm anything important with a manual check.
3. Fill their own form (carefully)
- Submitting a real contact form with your own real details (never fake data) often reveals the CRM or automation platform behind it — through the confirmation page's URL, a redirect, or the follow-up email's sending domain and headers.
- Only do this if you're a genuine prospect for what they sell, or with a throwaway inquiry you're comfortable owning. Don't submit spam or false information.
Use AI to structure the findings into a report
Once you've collected the raw signals — script URLs, form endpoints, generator tags, chat widgets — an AI assistant can turn that list into a clean, categorized tech-stack report faster than doing it by hand.
You are a competitive intelligence researcher analyzing a website's technology stack. Competitor: [name / URL] Raw signals I found (paste script URLs, cookie names, generator tags, chat widget names, form endpoints, response headers, anything you noticed): [paste your raw findings here] 1. Categorize each signal into: Analytics, CRM/Forms, CMS/Framework, Live Chat, Ad Pixels, Automation/Email, Hosting/CDN. 2. Identify the specific tool for each signal where possible, and say how confident you are (confirmed / likely / uncertain). 3. Note any signal you cannot confidently categorize, and don't guess a tool name if the evidence doesn't support it. 4. Summarize what this stack suggests about their marketing maturity and paid-acquisition investment. 5. Compare against my own stack below and list tools they have that I don't. My stack: [paste your own tools here]
Use it responsibly
- You're reading what a site sends to every visitor's browser — page source, scripts, headers. That's public by design, the same way a shop window is public.
- Don't use credentials, login into their systems, or probe endpoints that aren't meant to be public. Detecting a tool from a loaded script is research; attempting to access their CRM or admin panel is not.
- A detected pixel or script doesn't tell you their budget, results, or strategy — only that the tool is installed. Don't overstate the conclusion.
- Use what you learn to close real gaps in your own stack, not to copy their exact setup blindly. What works for them may not fit your business.
Want the Claude Skill from the Day 9 video? It analyzes a competitor's website and turns the raw signals into a structured tech-stack report automatically. Follow the instructions in the video to get access, or message Free Mind and ask for it.
Ask for the Claude Skill