Strapi Detector
Paste any URL and instantly see whether the site is built with Strapi — with the matched evidence.
We do not store the URL you audit. Want the full audit (performance / images / SEO / accessibility + real-browser speed test)? → run the full audit
Why check this
Confirm the platform first: CMS decides what can be changed and whether it is worth it.
What this is
Strapi is an open-source headless CMS you can self-host. Product teams and mid-size sites use it to expose content models over REST or GraphQL. Public-page clues are sparse, so headers and branded paths matter more than a single keyword. Confirmation is what lets you plan API caching, upload sizing, and how tightly the front end is coupled.
How to tell from a public page
- [Strapi] Response header `x-powered-by` values include the product name.
- [Strapi] HTML or script paths show official branding or default admin traces.
- [Strapi] Public docs or asset links expose `/api`-style content routes.
- [Strapi] Default upload directories or media URL patterns appear in static assets.
How to read the result
Confirm only when headers or structural paths reproduce; a casual mention in body copy remains only suspected. Absence often means powered-by was stripped and the content API sits behind a reverse proxy. Job posts that list the stack explain many soft keyword hits. After a hit, check whether original uploads feed LCP and whether public APIs lack cache headers.
What to do next
Add caching and auth boundaries around the content API, compress media, and review the permission model. The front end is often Next — open Next.js detector. For a full weighted audit, return to run the full performance / images / SEO / accessibility audit on the home page. Share the Strapi evidence with whoever owns API gateway and media policy.
Related detectors
FAQ
How is Strapi detected?
From structural signatures in the public HTML and response headers (domains, paths, attributes, scripts). Every verdict lists how many times each pattern matched — nothing is guessed.
Can the result be wrong?
If only a bare brand keyword matches without structural evidence, we label it \u201clikely\u201d instead of \u201cconfirmed\u201d — we would rather under-report than cry wolf.
Do you save the URLs I check?
No. The audit runs inside the request and the URL you paste is not written to storage. There are no third-party tracking scripts on the page either, so no log of who checked what exists. Copy the result yourself if you want a record.
Can a website hide what it is built with?
Partly, but rarely completely. The HTML sent to your browser, the response headers, script paths and asset structure have to be exposed to work, so there is always something readable. Server-side code, build config and private APIs stay invisible. That is why this tool reports the evidence it found rather than claiming a full picture. No match does not mean the technology is absent.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
