How to Tell If a Website Uses Elementor
Elementor is the most popular WordPress page builder. Detect it via the elementor- body and section classes, the /wp-content/plugins/elementor/ assets and the elementorFrontend global.
Elementor is the most popular page builder for WordPress, letting people design pages visually with drag-and-drop rather than code. Because it stamps its own CSS class scheme and data attributes throughout the markup, detecting it is straightforward: inspect the page and look for elementor- classes and data-elementor-type attributes. This guide covers every reliable signal, the builder's output, the look-alikes to rule out, and what an Elementor build tells you about the site.
What is Elementor?
Elementor is a WordPress page-builder plugin that replaces the standard editor with a visual, drag-and-drop interface: users assemble pages from widgets (headings, images, buttons, forms, sliders) arranged in sections and columns, styling everything live without touching code. It became the dominant page builder by making professional-looking WordPress sites accessible to small businesses, freelancers, and agencies who want design control and speed without development. It offers a free version and Elementor Pro (theme builder, popups, more widgets, WooCommerce building).
For detection, the key context is twofold: Elementor is a WordPress plugin, so finding it confirms WordPress; and its presence indicates a site built visually rather than hand-coded — a signal about how the site was made and by whom (often a non-developer or a design-focused agency). Because Elementor wraps its content in a distinctive class scheme and data attributes, and loads from a recognisable plugin path, it is one of the easiest builders to confirm. Its presence is extremely common across the small-business WordPress web.
How Elementor renders pages
Elementor outputs a consistent, recognisable structure. Pages are built from sections/containers (elementor-section and elementor-top-section, or the newer elementor-element containers with flexbox), columns (elementor-column), and widgets (elementor-widget, with type-specific classes like elementor-widget-heading, elementor-widget-image). Container and widget elements carry data-elementor-type (e.g. wp-page, header, footer), data-id and data-element_type attributes. The <body> often gains an elementor-page elementor-page-<id> class and an elementor-kit-<id> class (the global style kit).
Assets load from /wp-content/plugins/elementor/ (and Elementor Pro from /wp-content/plugins/elementor-pro/), with generated CSS under /wp-content/uploads/elementor/css/. At runtime, the window.elementorFrontend global manages widgets and interactions. So an Elementor page shows the elementor- classes, the data-elementor-* attributes, the plugin/upload asset paths, and the elementorFrontend global. Knowing these makes detection instant and even reveals whether Pro is in use.
How to tell if a website uses Elementor
Confirm at least one strong signal (the class scheme suffices).
1. Inspect the structure. Right-click a section or widget and look for elementor-section/elementor-container, elementor-column, elementor-widget classes and data-elementor-type/data-element_type attributes.
2. Check the body classes. The <body> often carries elementor-page elementor-page-<id> and elementor-kit-<id>.
3. Use the console. Type elementorFrontend and press Enter. A returned object confirms Elementor's front-end is active.
4. Check asset paths. Look for /wp-content/plugins/elementor/, /wp-content/plugins/elementor-pro/ (Pro), and generated CSS under /wp-content/uploads/elementor/.
5. Confirm WordPress. Because Elementor is a WordPress plugin, the site will show WordPress signals (/wp-content/, /wp-includes/).
What the Elementor signals look like
<body class="elementor-page elementor-page-42 elementor-kit-5">
<div class="elementor elementor-42" data-elementor-type="wp-page" data-elementor-id="42">
<section class="elementor-section elementor-top-section" data-id="abc123" data-element_type="section">
<div class="elementor-widget elementor-widget-heading" data-element_type="widget" data-widget_type="heading.default">
window.elementorFrontend = { … }
GET /wp-content/plugins/elementor/assets/... ; /wp-content/uploads/elementor/css/post-42.css
The elementor- class scheme, the data-elementor-* attributes, and the plugin asset paths (with the elementorFrontend global) are conclusive.
Elementor versus other builders — avoiding false positives
Match the class scheme to keep WordPress page builders distinct. Elementor uses elementor- classes and data-elementor-*; Divi uses et_pb_ classes (e.g. et_pb_section, et_pb_module) and the Divi Builder; Beaver Builder uses fl-builder/fl-node- classes; WPBakery uses vc_row/wpb_ classes; Gutenberg (the core block editor) uses wp-block- classes. Each prefix is distinct, so the class scheme identifies the builder unambiguously. The elementor- prefix is unique to Elementor. A site built with Gutenberg blocks (wp-block-) is not using a page builder in the same sense — distinguish core blocks from third-party builders.
How reliable is each Elementor signal?
The elementor- class scheme and the data-elementor-* attributes are definitive. The /wp-content/plugins/elementor/ asset path and the elementorFrontend global are equally strong. The elementor-page/elementor-kit- body classes corroborate. The elementor-pro path conclusively indicates the Pro version. The WordPress context reliably accompanies it. There is essentially no false-positive risk once you see the elementor- classes. As a rule, inspecting a section settles it, and the presence of elementor-pro assets reveals the Pro tier.
What an Elementor build reveals about a site
Finding Elementor signals a WordPress site built visually with the leading page builder, almost always by a small business, freelancer or agency that wanted design control without coding. Its presence tells you the site was assembled with drag-and-drop, which has implications: such sites are quick to build and easy to edit, but page builders add markup and CSS that can affect performance, so Elementor sites are common candidates for performance optimisation. The Pro version indicates a paid, more capable setup (theme building, popups, WooCommerce). If you sell WordPress services — design, performance, maintenance, hosting — an Elementor site marks an owner comfortable with visual editing and likely receptive to design and speed improvements. Because Elementor is so common among SMBs, it is also a strong signal of the small-business WordPress segment.
What finding Elementor means for sales, agencies and competitive research
For sales and prospecting, Elementor marks a small-business or agency WordPress site built visually — a fit for WordPress design, performance, maintenance and hosting services, and for plugins/add-ons that extend Elementor.
For agencies and consultants, finding Elementor tells you the client edits visually and values design control, so engagements can focus on design polish, performance (page builders are heavy), or extending the site with Pro features. It signals a non-developer-friendly setup.
For competitive and market research, Elementor versus Divi versus Gutenberg adoption maps how WordPress sites in a segment are built, and a competitor's builder choice hints at their design workflow and likely performance characteristics.
Elementor in the wider WordPress stack
Elementor sits in the design/build layer of a WordPress stack. It accompanies a (often lightweight) theme chosen to work with the builder (Hello Elementor, Astra, GeneratePress), an SEO plugin (Yoast or Rank Math), a caching plugin (WP Rocket, since builders need performance help), a forms solution (Elementor's own forms in Pro, or Contact Form 7/WPForms), and analytics. On ecommerce it pairs with WooCommerce (built with Elementor Pro's WooCommerce widgets). For an auditor, the valuable details are whether Elementor Pro is present, the companion theme, the caching/performance setup (important given builder overhead), and the surrounding plugins; together these reveal how the WordPress site was built and where performance improvements are likely needed. The performance angle is worth dwelling on, because it is where Elementor sites most consistently fall short and where the clearest opportunities lie. Page builders generate deeply nested markup and load a fair amount of CSS and JavaScript, so an Elementor site that has not been carefully optimised will often struggle with Core Web Vitals — particularly Largest Contentful Paint and the layout shifts caused by late-loading widgets. That makes the combination of Elementor plus a caching plugin like WP Rocket extremely common, and the combination of Elementor without any caching or image optimisation a reliable flag for a site that would benefit immediately from performance work. For anyone offering speed optimisation, an unoptimised Elementor build is one of the most dependable and demonstrable leads you can find.
A quick Elementor confirmation walkthrough
Open the site with developer tools on the Elements panel and inspect a section or widget. Look for elementor-section/elementor-container, elementor-widget classes and data-elementor-type/data-element_type attributes; check the <body> for elementor-page/elementor-kit- classes. In the console, type elementorFrontend to confirm the global. In the Network tab, look for /wp-content/plugins/elementor/ (and elementor-pro/ for Pro) assets. The elementor- classes are enough to confirm Elementor, and the Pro assets reveal the tier.
A quick Elementor detection checklist
- Inspect sections/widgets for
elementor-classes anddata-elementor-*attributes — conclusive. - Check the
<body>forelementor-page/elementor-kit-classes. - Type
elementorFrontendin the console to confirm the global. - Look for
/wp-content/plugins/elementor/(andelementor-pro/) assets. - Confirm WordPress, since Elementor is a WordPress plugin.
- Distinguish Elementor (
elementor-) from Divi (et_pb_), Beaver Builder (fl-) and Gutenberg (wp-block-).
Detecting Elementor at scale
Checking one site is quick, but mapping page-builder adoption across many WordPress domains — to find small-business sites or performance-improvement opportunities — calls for automation. StackOptic detects Elementor (and Pro) and thousands of other technologies from a real browser, reading the class scheme, attributes and assets. For related reading, see our guides to identifying a WordPress theme and its plugins and making your website load faster, and the full Elementor technology profile.
Frequently asked questions
What is the fastest way to tell if a site uses Elementor?
Inspect the page structure and look for elementor- prefixed classes: elementor-element, elementor-widget, elementor-section or elementor-container, plus data-elementor-type attributes. Those classes, or assets from /wp-content/plugins/elementor/, are the definitive signal.
What is the elementorFrontend global?
elementorFrontend (window.elementorFrontend) is the JavaScript object Elementor's front-end script exposes to manage widgets, interactions and responsive behaviour. Typing elementorFrontend in the console and getting an object back confirms Elementor is active on the page.
What are the data-elementor-type attributes?
Elementor marks its templates with data-elementor-type attributes (e.g. data-elementor-type="wp-page", "header", "footer") on container elements, and uses data-id and data-element_type on widgets and sections. Finding these data-elementor-* attributes is a strong, characteristic Elementor signal.
Does Elementor mean the site uses WordPress?
Yes. Elementor is a WordPress page-builder plugin, so finding it means the site runs WordPress. It builds pages visually within WordPress, so its presence also confirms WordPress is the underlying CMS.
What does it mean if a site is built with Elementor?
Elementor is the most popular WordPress page builder. Finding it signals a WordPress site built visually (drag-and-drop) rather than hand-coded, common among small businesses, freelancers and agencies that want design control without writing code.
Analyse any website with StackOptic
Get the full technology stack, performance, security and SEO report in seconds — free.
Analyse a websiteRelated articles
How to Tell If a Website Uses Heap
Heap (Heap Analytics) autocaptures product events. Detect it via the cdn.heapanalytics.com script, the global heap object, heapanalytics.com beacons and _hp2 cookies.
How to Tell If a Website Uses Foundation
Foundation (by Zurb) is a responsive front-end framework. Detect it via its grid classes (row/columns, grid-x/cell), data-* component attributes and the foundation.css/js files.
How to Tell If a Website Uses Crisp
Crisp is a developer-friendly, affordable live-chat and messaging tool. Detect it via the client.crisp.chat/l.js script, the window.$crisp object and the CRISP_WEBSITE_ID value.