Elementor SEO — Optimize Elementor Pages
Elementor is a WordPress page builder with 10+ million active installations on WordPress.org (October 2026).
Rank Forge has no Elementor widget parser. When the body of a page (the post content) is empty, it analyzes the text found in the data Elementor stores for that page (the _elementor_data field of the page) instead, and it does the same for Beaver Builder, Divi and Oxygen. It reads the data of the page itself, not widgets one by one and not Theme Builder templates, and it does not write into Elementor’s data: a change that Rank Forge suggests for a page whose text lives only in Elementor is made in Elementor.
Schema for Elementor pages
Elementor Theme Builder single post templates are typically used for content-type pages (blog posts built in Elementor). Rank Forge outputs Article or BlogPosting schema on these pages based on the post type, regardless of whether the content comes from the native editor or Elementor.
For Elementor-built landing pages (pages using a Pages template), Rank Forge outputs WebPage schema by default, with option to override to Article or another type in the meta box.
Product pages built with Elementor Pro’s Product Archive template output Product schema from WooCommerce data, not from Elementor widgets.
Elementor Pro widgets and Theme Builder
Rank Forge has no code that treats Elementor Pro widgets or Theme Builder templates in a special way: it adds no ItemList or Service markup for them, and it does not exclude widgets from the analysis or set noindex for them.
Works alongside Elementor’s own settings
Rank Forge does not read Elementor’s own settings. The title, the description, the canonical, robots and Open Graph tags and the schema that Rank Forge prints come from the Rank Forge box, the Rank Forge settings and the page itself. The one thing it takes from Elementor is the text of the page, as described above.
Ready to optimize Elementor pages?
Elementor integration is included in every paid plan.