tech-audit

Tech Audit — What a Site Is Built With: Stack, Analytics, Pixels, and Widgets

Detect the technologies on a single page: which CMS or site builder it uses, which framework renders the HTML, what runs on the backend, how traffic is measured, which advertising pixels and chats are installed, who processes payments, and who protects the site. For SEO, this answers "what can actually be changed on this site," "how is traffic measured," and "how many third-party scripts weigh down the page."

This is not a manual source-code review, but a tool in the seohead toolkit (CLI + MCP + HTTP). In MCP, it is seo_tech_detect. After one request to the page, all further analysis is static signature matching against header, value, cookie, html, and script. Every match includes the marker (evidence) that triggered it, making the conclusion verifiable.

When to Use It

• "what is the site built with," "which site engine," "which CMS," "is it WordPress," "site stack";
• "which technologies," "what does the site use," "how is traffic measured," "which pixels are installed";
• "which widgets / chats / support tools," "which consent banner," "which payment systems";
• "does it use Cloudflare / protection," "who hosts the frontend (Vercel / Netlify / CloudFront)";
• checking a headless combination (CMS + Next.js/Nuxt) before a rendering audit;
• a quick competitor profile before an audit — what it uses and how it differs.

Workflow

1. Technologies on a single page — the only command:

seohead tech-detect --url https://example.com

After one request, the tool inspects the HTML, headers, cookies, and script src attributes using ~200 built-in signatures. The response contains:

• generator — the complete contents of <meta name=generator> (often includes the CMS version);
• technologies — each entry with category, evidence (the marker that identified it), and version when exposed in generator or x-powered-by;
• by_category — the same technologies grouped by category;
• scripts_total — the total number of external scripts on the page;
• third_party_hosts — third-party domains from which scripts are loaded;
• external_db — the status of the external fingerprint database (see below);
• findings — plain-language conclusions assembled from the signatures.