Tech Stack Detection — AISeen Docs
How AISeen detects your tech stack: frameworks (Next.js, Nuxt, Astro), CMS, CDN, analytics tools, CSS frameworks, and JS libraries.
How detection works
HTTP Headers
Server, X-Powered-By, x-vercel-id, cf-ray, x-amz-cf-id, and 20+ custom headers reveal hosting and backend.
HTML Meta Tags
Generator meta, ng-version, and application-name meta tags identify CMS and frameworks.
Script URLs
URLs in <script src="..."> reveal CDN paths, chunk naming conventions, and library versions.
Cookie Names
Session cookie names (PHPSESSID, _ga, connect.sid) expose backend and analytics stack.
HTML Patterns
Class names, data-* attributes, and specific DOM structures fingerprint JS frameworks.
Response Patterns
ETag format, cache headers, and response timing patterns narrow down hosting providers.
What we detect
JavaScript Frameworks
(9 technologies)CMS Platforms
(8 technologies)CDN & Hosting
(7 technologies)E-commerce
(5 technologies)Analytics & Marketing
(8 technologies)CSS Frameworks
(5 technologies)Backend Language / Runtime
(6 technologies)Confidence levels
Multiple independent signals confirm the detection. Very unlikely to be a false positive.
One or two strong signals found. Correct in most cases but could match similar technologies.
Weak or indirect signal. Shown for transparency — may or may not be accurate.
Why tech stack detection matters for SEO
Knowing your tech stack helps diagnose issues faster. For example, if we detect WordPress + no security plugin + outdated PHP version, the security risk interpretation changes. If we detect a pure React SPA (client-side rendering only), we flag it in the Vibe Score.
Tech stack data also helps our AI fix engine generate accurate, framework-specific recommendations rather than generic advice.
Tech Stack Detection — AISeen Docs
How AISeen detects your tech stack: frameworks (Next.js, Nuxt, Astro), CMS, CDN, analytics tools, CSS frameworks, and JS libraries.