isaeo
Start free
Features Site Audit Health Scoring AI Search Readiness Meta & Tag Coverage Content Analytics Link Profile Keyword Research Keyword Ideas Competitor Keywords SERP Analysis White-Label Reports Pricing WHOIS Tech stack Blog Log in Start free
Free tool · no signup

What is any site built with?

Enter a domain to see its frameworks, analytics and eventing tools, CMS, hosting and CDN — read straight from the site's published code.

assets.vercel.com

cloudflare · 9 technologies detected
Cached result
Confirmed — unambiguous signal Likely — heuristic marker only

Framework & libraries

2
Bootstrap
jQuery

CMS

1
WordPress

Analytics

1
Google Analytics 4
Audience MeasurementConversion Tracking

Tag managers

1
Google Tag Manager GTM-5BS5ZV
Tag ManagementConversion Tracking

CDN & performance

2
Cloudflare
jsDelivr

Fonts & assets

2
Adobe Fonts
Google Fonts

Security headers

2/6
— HSTS Forces HTTPS on future visits
✓ Content Security Policy Restricts what the page may load
— X-Frame-Options Blocks clickjacking via framing
✓ X-Content-Type-Options Stops MIME-type sniffing
— Referrer Policy Controls referrer leakage
— Permissions Policy Limits browser feature access

AI readiness

Strong
90
/ 100
Content structure 76
Schema, FAQ markup and answer-shaped passages
Schema depth 100
4 valuable types detected
AI crawler access 100
13/13 tracked crawlers allowed
Machine-readable index 100
llms.txt present

Not detected

2
— No consent management detectedAnalytics and advertising cookies without consent are a GDPR exposure.
— No error tracking detectedFront-end exceptions reach users before anyone on the team hears about them.

Subdomains

0

No subdomains found in certificate transparency logs.

i

This reads the site's published HTML only. It sees what the server sends, not what runs afterwards in a browser.

A tag manager is present, so this site may load further analytics or eventing tools at runtime that don't appear above.

How does assets.vercel.com actually perform in search?

Knowing the stack is one thing. Run a full audit to score the site for search and answer engines, and see every issue holding it back.

Run a free audit →
FAQ

Frequently asked questions

How does the tech stack checker work?

+

It fetches the page's published HTML and inspects four signals: script URLs, inline script contents, meta and DOM markers, and the HTTP response headers and cookies. Each signal is matched against a table of known technology fingerprints.

Can it detect everything a site uses?

+

No, and it says so. The checker reads published HTML only, so tools loaded at runtime by a tag manager may not appear. When a tag manager is detected, the results flag that the list may be incomplete rather than implying it is exhaustive.

What do 'confirmed' and 'likely' mean?

+

Confirmed means an unambiguous signal was found, such as a Google Tag Manager container ID or a server header. Likely means only a heuristic marker matched, such as a DOM attribute that a framework usually leaves behind but which can occur by coincidence.

Is the tech stack checker free?

+

Yes. No account is required, and full results are shown without a signup wall.