ELEMENTOR SEO AUDIT · WORDPRESS PAGE BUILDER · YOAST · RANK MATH · CORE WEB VITALS
Free Elementor SEO Audit
Elementor is a WordPress page builder — SEO metadata comes from a companion SEO plugin (Yoast SEO or Rank Math) accessible from the Elementor editor. JSON-LD structured data requires Rank Math Pro\'s Schema Builder, Elementor\'s HTML widget, or a wp_head hook — not Elementor\'s native widgets. Elementor Pro\'s Theme Builder controls which templates apply to which URL types, affecting how SEO plugin output propagates. Elementor\'s frontend rendering overhead (JS bundle, section background images, Google Fonts, animations) is the primary Core Web Vitals risk. DeepSEOAnalysis audits the rendered HTML — validating SEO plugin meta tag output, detecting JSON-LD rendering gaps from GTM-injected schema, real CrUX Core Web Vitals for Elementor\'s rendering overhead, sitemap coverage of Elementor-built pages, and all five AI visibility signals — free with no signup.
WHAT WE CHECK
6 Elementor-specific SEO checks
Elementor SEO auditing covers meta tag output from Yoast SEO or Rank Math integration (title, description, canonical, OG image, noindex — all from the SEO plugin accessible in Elementor's editor panel), Theme Builder template configuration for single post and archive URL types, JSON-LD from Rank Math Pro Schema Builder or HTML widget (with GTM rendering gap detection for client-side injected schema), sitemap and robots.txt from the SEO plugin (including Section Background Image URL exclusions), real CrUX Core Web Vitals for Elementor's JS bundle overhead and LCP from section background images, and AI visibility including llms.txt for WordPress and FAQPage JSON-LD without GTM injection.
Elementor SEO settings and meta tag output from SEO plugin integration
Elementor itself doesn\'t output SEO meta tags — meta title, description, canonical URL, OG tags, robots directives, and hreflang all come from the SEO plugin (Yoast SEO, Rank Math, SEOPress, or All in One SEO) installed alongside Elementor. The audit validates the actual rendered meta tags. Key checks: meta title quality (Yoast and Rank Math allow per-page title templates in their panels, accessible from the Elementor editor; pages using the default WordPress title template rather than a customised SEO title are flagged; Elementor\'s %site_title% and %page_title% dynamic tags in widgets must not be confused with the SEO plugin\'s title fields — they control visible page heading, not the `title` tag); meta description coverage (the SEO plugin\'s meta description field must be filled; pages with empty meta descriptions fall back to auto-generated excerpts that may be suboptimal); canonical URL accuracy (Elementor redirects, Elementor\'s "Hide Page" feature, and custom URL settings in Elementor\'s page settings can create canonical confusion — the audit checks the rendered `rel="canonical"` against the crawled URL); OG image (Rank Math and Yoast both have per-page OG image settings accessible from the Elementor editor — the audit checks OG image presence, absolute URL format, and minimum dimensions for social card display); noindex configuration (the SEO plugin\'s noindex setting must be accessible and correctly configured for pages like thank-you pages, checkout, and staging pages built with Elementor); and robots.txt (checks for accidental Disallow of Elementor asset URLs — `/wp-content/plugins/elementor/` paths — which would block Elementor\'s CSS and JS from crawling while the HTML page itself remains accessible, producing a degraded rendering for Googlebot).
Elementor Theme Builder templates and URL routing for posts and pages
Elementor Pro\'s Theme Builder creates custom WordPress archive, single post/page, and search result templates. These templates determine which Elementor widgets appear on which URL types — and whether SEO plugin output, structured data, and meta tags correctly propagate through the template. Key checks: Single Post template detection (Elementor single post templates using the "Post Content" widget correctly embed SEO plugin meta tags in the page head; single post templates that only use Elementor design widgets without the Post Content widget may bypass SEO plugin output — the audit checks for SEO plugin meta tags on post-type URLs); archive template structure (category, tag, and author archive pages built with Elementor Theme Builder must include SEO-relevant meta tags and canonical URLs appropriate for archive pages — including potential noindex decisions for thin archives); dynamic URLs (Elementor\'s dynamic tags populate visible content from post data, but the URL structure is controlled by WordPress permalink settings — the audit checks permalink quality for Elementor-built CPT (custom post type) URLs); redirect configuration (broken Elementor links after page deletion or URL changes must resolve via WordPress redirect plugins or server-level 301s; the audit checks for 404s on internally linked Elementor page URLs); and sitemap coverage (the SEO plugin\'s sitemap module should correctly include all Elementor-built pages that are indexable — the audit compares crawled URLs against sitemap entries).
JSON-LD structured data on Elementor-built pages
Elementor doesn\'t generate JSON-LD structured data natively. The audit identifies all JSON-LD present in the page HTML — whether injected via the SEO plugin\'s schema builder, Elementor\'s HTML widget, a `wp_head` hook in functions.php, or a code plugin — and validates against Google\'s Rich Results specifications. For Organisation and WebSite JSON-LD (typically site-wide via the SEO plugin): `@type: Organization`, name, url, logo (absolute URL, correct dimensions for Google Knowledge Panel), sameAs array. For Article JSON-LD on Elementor-built blog posts or news pages: headline max 110 chars, datePublished from the post\'s publish date (not the Elementor page creation date, which may differ), dateModified from the post\'s last-modified date, author from WordPress post author data, image as absolute URL from the post\'s featured image. For FAQPage JSON-LD on pages with FAQ content: mainEntity array with correct Question/Answer structure, acceptedAnswer.text as plain text (not HTML). For Product JSON-LD on WooCommerce + Elementor product pages: Product, Offer, AggregateRating integration from WooCommerce data. Critical check: **rendering gap detection** — JSON-LD injected via Google Tag Manager is client-side JavaScript execution and is absent from the initial HTML response Googlebot receives on first-pass crawl. The audit detects JSON-LD in the rendered DOM that\'s absent from the initial HTML response — a common Elementor site pattern when developers use GTM for structured data injection. FAQPage JSON-LD added via Elementor\'s HTML widget is server-rendered and doesn\'t have this problem.
Sitemap and robots.txt configuration for Elementor WordPress sites
Sitemap and robots.txt for Elementor WordPress sites are handled by the companion SEO plugin. The audit checks: sitemap accessibility (Yoast SEO generates `/sitemap_index.xml`; Rank Math generates `/sitemap_index.xml` or a custom URL; the sitemap must be referenced in robots.txt and declared in Google Search Console); Elementor page sitemap inclusion (all indexable Elementor-built pages must appear in the sitemap — pages with Elementor\'s "Hide Page" setting or the SEO plugin\'s noindex toggle enabled must be excluded; the audit checks for pages crawled that are absent from the sitemap or for sitemap entries that return noindex); `lastmod` accuracy (Yoast and Rank Math set `lastmod` from the WordPress post modified date; Elementor edits update the WordPress post modified date, so `lastmod` should reflect recent Elementor content changes accurately); robots.txt quality (the WordPress robots.txt should include `Disallow: /wp-admin/`; should NOT Disallow `/wp-content/` or `/wp-content/plugins/elementor/` as this blocks Googlebot from accessing Elementor\'s CSS/JS files, degrading the rendered output Googlebot sees; should allow all AI crawlers; should include the sitemap URL); and plugin-generated URL exclusion (Elementor creates some WordPress admin and template management URLs under `/elementor/` paths — these should be Disallowed in robots.txt to prevent crawl budget waste on non-public pages).
Core Web Vitals for Elementor-built WordPress sites
Elementor is one of the most common causes of Core Web Vitals failures on WordPress sites due to its frontend rendering overhead. The audit uses real CrUX field data — actual Chrome user experience on the live Elementor site — not Lighthouse lab estimates. **LCP**: the LCP element on Elementor pages is most commonly a hero image set as an Elementor Section Background Image (CSS `background-image`) or as an Image widget. Section Background Images are CSS-applied and not pre-loadable by the browser — causing delayed LCP. Elementor\'s "Background Overlay" feature on hero sections further delays LCP by requiring the background image to render before the overlay composites. Optimal approach: use Elementor\'s Image widget above-the-fold with WordPress\'s `loading="eager"` and `fetchpriority="high"` attributes. **CLS**: common CLS sources on Elementor sites — Google Fonts loaded from `fonts.googleapis.com` causing FOUT (Flash of Unstyled Text) before font swap; Elementor animations that reposition content after initial render; third-party widgets (chat widgets, marketing popups) injecting after initial layout; images in Elementor\'s Image widget without explicit width/height CSS causing layout shifts on load. **INP**: Elementor\'s frontend JavaScript bundle delays main thread availability for user interactions. Sites with many widgets, Elementor Pro features (popups, sticky headers, Scroll Effects), and third-party Elementor addon packs regularly fail INP on mid-tier Android devices. **TTFB**: Elementor sites on shared WordPress hosting without caching frequently have TTFB >800ms. A caching plugin (WP Rocket, LiteSpeed Cache) with full-page cache enabled reduces TTFB to the 50–200ms range. **CrUX vs Lighthouse**: Lighthouse lab scores run against a warm-cache Elementor page look much better than real user CrUX data that captures cold-cache visits, slow hosting spikes, and mobile device constraints — always validate against real CrUX field data.
AI visibility for Elementor WordPress sites
Elementor is commonly used for business websites, SaaS landing pages, WooCommerce stores, and WordPress content sites — all categories where AI visibility matters for brand and product awareness. The audit checks all five GEO signals. For `llms.txt`: Elementor sites can serve a static `llms.txt` file in the WordPress root directory (accessible at `example.com/llms.txt`), or generate it dynamically via a WordPress route registered with `add_rewrite_rule()` and a custom template file. A simple approach: create `/public_html/llms.txt` as a static text file listing the site\'s most important content. For `robots.txt`: generated by WordPress (editable via Yoast SEO or Rank Math\'s robots.txt editor). Must not Disallow AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot) — check that neither the WordPress-generated robots.txt nor any hosting-level `.htaccess` rules accidentally block AI bots. For `FAQPage` JSON-LD: must be in the initial server-rendered HTML response, not injected via GTM (rendering gap). Options: Rank Math Pro\'s Schema Builder with FAQPage type; Elementor\'s HTML widget with static JSON-LD; or a `wp_head` action hook. The audit checks whether FAQ-format content on Elementor pages has corresponding FAQPage JSON-LD. For question-heading ratio: Elementor\'s Heading widget generates semantic `<h2>`/`<h3>` elements — the audit checks whether ≥20% of headings across content pages are question-format (starting with How, What, Why, Can, Is, Does, Should). For content chunkability: Elementor\'s section-based layout should produce clean heading hierarchy — the audit measures average section length against the ≤400-word target for AI citation eligibility.
HOW IT WORKS
Audit your Elementor site in 60 seconds
- Enter your Elementor URL. Any page or post URL built with Elementor (free or Pro), hosted on any WordPress host. No WordPress admin access, Elementor license, Yoast SEO Premium, or Rank Math Pro credentials needed. Works whether your Elementor site uses Yoast SEO, Rank Math, SEOPress, All in One SEO, or any other SEO plugin for meta tag management. Works on any hosting (shared, VPS, managed WordPress like WP Engine, Kinsta, SiteGround, or Cloudways).
- We crawl and analyse. The engine validates meta tags from your SEO plugin as rendered by the WordPress + Elementor stack — checking what Googlebot actually receives; detects JSON-LD rendering gaps (schema in the rendered DOM but absent from initial HTML — common when developers inject structured data via GTM in Elementor-built sites); checks whether Elementor Theme Builder single post templates correctly propagate SEO plugin output; measures real CrUX Core Web Vitals from Chrome user field data on the live site including Elementor's rendering overhead; and evaluates all five AI visibility signals.
- You get a prioritised report. Elementor-specific issues first — Section Background Images as LCP elements that can't be pre-loaded (highest frequency Core Web Vitals issue on Elementor sites), FAQPage JSON-LD absent or GTM-injected (rendering gap), Google Fonts loaded from external CDN causing CLS, SEO plugin meta description empty on Elementor-built landing pages, noindex on thank-you pages not confirmed in sitemap exclusion, robots.txt accidentally Disallowing Elementor plugin paths — then general SEO findings, each with the Elementor-specific context (which widget, plugin panel, or theme builder setting controls the fix).
FAQ
Questions about the Elementor SEO audit
How does Elementor handle SEO?
Elementor (elementor.com) is a visual drag-and-drop page builder plugin for WordPress. It builds pages and post templates visually using a frontend editor that generates HTML, CSS, and JavaScript in the WordPress environment. Elementor\'s relationship with SEO is shaped by two factors: what Elementor itself provides for SEO, and how Elementor integrates with WordPress SEO plugins. (1) **What Elementor provides natively**: Elementor does not include a built-in SEO module. It is a page builder, not an SEO plugin. For meta tags, canonical URLs, robots directives, and Open Graph tags, Elementor relies on a companion SEO plugin. (2) **SEO plugin integration**: Elementor integrates with both Yoast SEO and Rank Math (the two most common WordPress SEO plugins). In the Elementor editor, you can access the SEO settings panel from your SEO plugin — typically via a tab in the Elementor panel or via the WordPress admin bar. Yoast\'s and Rank Math\'s meta title, meta description, focus keyword, and social preview fields are accessible without leaving the Elementor editor. (3) **Elementor Theme Builder**: Elementor Pro\'s Theme Builder allows creating custom headers, footers, single post templates, archive templates, and search results templates. This is relevant to SEO because the Template settings control which structured data and meta tag outputs apply to which page types — a poorly designed single-post template may omit the SEO plugin\'s meta tag output by using incorrect section types. (4) **Dynamic Tags**: Elementor Pro supports dynamic tags — content fields that pull values from WordPress post data (title, excerpt, date, author, custom fields, ACF fields). Dynamic tags enable creating reusable templates where SEO-relevant fields (like an article\'s publication date displayed in a widget) pull from the actual post data rather than being hard-coded. This is relevant for Article JSON-LD: the datePublished and dateModified should pull from the actual post date, not be hard-coded. (5) **Elementor-generated CSS and JS**: Elementor generates CSS and JavaScript files specific to each page\'s widget set. On pages with many widgets, this can produce significant frontend asset overhead — the primary Core Web Vitals risk for Elementor-built pages.
Why do Elementor sites sometimes have poor Core Web Vitals?
Elementor-built WordPress sites are one of the most common sources of Core Web Vitals failures in DeepSEOAnalysis audits. The causes are structural: (1) **JavaScript bundle size**: Elementor\'s frontend JS (elementor-frontend.min.js and related files) is substantial — typically 150–300KB gzipped. Every page using Elementor loads this bundle. The bundle handles Elementor\'s animations, widget interactions, parallax effects, and sticky elements. Each additional widget type installed (Elementor Pro or third-party addon packs) adds to the JS load. INP (Interaction to Next Paint) is the most commonly affected metric because main thread work from JavaScript parsing and execution directly delays interaction responsiveness. (2) **CSS specificity and inline styles**: Elementor generates inline CSS (in `<style>` tags in the page HTML) for widget-level settings (colours, spacing, fonts set in the Elementor panel). This inline CSS can reach 50–100KB on complex pages. Critical rendering path CSS bloat delays FCP and LCP. (3) **Google Fonts**: Elementor\'s default font configuration loads Google Fonts from `fonts.googleapis.com`. External font loading is a TTFB-contributing request that delays text rendering — a common CLS source when fonts load after the initial layout paint. Switching to a self-hosted Google Fonts or a variable font loaded locally eliminates this. (4) **Images**: Elementor provides an Image widget and Background Image options for sections. Images set as Elementor section backgrounds bypass WordPress\'s `img` tag mechanism — they\'re applied as CSS `background-image`, which prevents the browser from preloading them as critical images. The LCP element on many Elementor pages is a section background image that isn\'t preloadable, causing higher LCP. (5) **Animations**: Elementor\'s "Motion Effects" (scroll-triggered animations, entrance effects like fade-in and slide-in) are implemented via Intersection Observer + CSS transitions executed by Elementor\'s JS. While these don\'t directly impact LCP, they contribute to INP on scroll-heavy pages. (6) **Plugins**: Elementor sites typically have many WordPress plugins active simultaneously, each contributing PHP, JS, and CSS overhead. Third-party Elementor addon packs (Essential Addons, JetElements, Dynamic.ooo) add additional JS/CSS per page. **Mitigation options**: use Elementor\'s "Optimized DOM Output" (reduces generated HTML nesting); use a performance-focused WordPress caching plugin (WP Rocket or LiteSpeed Cache) with CSS minification, JS deferral, and CDN integration; use Cloudflare to cache HTML and compress assets; self-host Google Fonts; convert section background images to above-fold `img` elements using the Image widget with LCP prioritisation.
How do I add JSON-LD structured data to an Elementor page?
Elementor does not natively generate Article, FAQPage, LocalBusiness, or Product JSON-LD structured data. Options for adding JSON-LD to Elementor-built pages: (1) **Rank Math Pro (recommended for FAQ)**: Rank Math\'s FAQ Block (available in the WordPress block editor) generates FAQPage JSON-LD automatically. However, if the page is built entirely in Elementor\'s editor (bypassing the WordPress block editor), Rank Math\'s FAQ Block isn\'t accessible. Rank Math Pro provides a Schema Builder that allows adding custom JSON-LD schemas to pages from the WordPress admin — including FAQPage with manually entered Q&A pairs, accessible even for Elementor-built pages. (2) **Yoast SEO Premium**: Yoast\'s Structured Data Blocks (in the WordPress block editor) generate HowTo and FAQ JSON-LD. For Elementor pages, Yoast SEO Premium\'s structured data functionality is limited to the meta/head-level schemas (Organisation, Website) — page-level FAQPage requires either the block editor FAQ block or a custom integration. (3) **Elementor HTML Widget**: For any JSON-LD schema type, Elementor\'s HTML widget allows pasting raw HTML including `script type="application/ld+json"` blocks directly into the page. The widget content renders in the page HTML server-side — confirmed visible in the initial HTML response (not a rendering gap). Limitation: the JSON-LD is static (field values hard-coded) and must be manually updated when page content changes. (4) **Dynamic JSON-LD via a WordPress filter**: For Article JSON-LD on post templates, add a `wp_head` action hook in a child theme\'s `functions.php` or a code plugin (Code Snippets) that generates Article JSON-LD from WordPress post data (`get_the_title()`, `get_the_date()`, `get_the_modified_date()`, `get_the_author()`, `get_post_thumbnail_url()`) dynamically. This produces dynamic Article JSON-LD without requiring Elementor widget configuration on each post. (5) **Avoid GTM injection**: JSON-LD injected via Google Tag Manager is loaded by a client-side JavaScript execution — creating a rendering gap where the structured data is absent from the initial HTML response Googlebot sees on first-pass crawl. Use one of the server-side methods above.
Is the Elementor SEO audit free?
Yes. The complete audit is free with no signup and no email gate. Enter the URL of any page built with Elementor — the audit crawls the rendered HTML as Googlebot would, validating what the WordPress + Elementor + SEO plugin stack actually produces. No WordPress admin access, Elementor license, or SEO plugin credentials needed. The audit accurately reflects what Googlebot sees — including detecting whether JSON-LD is server-rendered (in the initial HTML) or client-side/GTM-injected (a rendering gap). Works for all Elementor plan types (free and Elementor Pro) and all compatible SEO plugins (Yoast SEO, Rank Math, SEOPress, All in One SEO). Paid DeepSEOAnalysis plans add saved report history, scheduled monitoring for ongoing Elementor site health tracking, and white-label agency reporting.