A Live Composer theme that became an Elementor theme
SEOWP's page-building layer changed identity. The changelog records version 3.0.0, released 3 January 2024, as updating "Live Composer Page Builder to support Elementor" and adding Elementor support for SEOWP templates. Until then, Live Composer was the theme's own canvas.
That history matters when you evaluate the theme today. The marketplace attributes list Elementor and Elementor Pro among compatible plugins, and the documentation and demo reflect the Elementor route, but the theme's internal structure grew up around a different builder. If you read older tutorials or forum threads about SEOWP, some will describe a Live Composer workflow that no longer matches the current templates.
Converting pages you already built in Live Composer
A month after the switch, version 3.2.0 added "functionality for converting Live Composer Page to Elementor Pages." For an agency that built client sites on SEOWP before the change, this is the migration tool — not a rebuild-from-scratch requirement.
The changelog describes the conversion feature but not its fidelity. Nothing in the supplied description states how faithfully a Live Composer layout survives the transfer, so treat the converter as a starting point and plan to check the pages that carry custom sections. For a fresh project the feature is largely irrelevant: you would build in Elementor from the beginning.
Custom scripts in the head, body and footer
Version 2.3.0, from February 2023, added a theme options field for custom JavaScript in the head, body or footer of all pages. The changelog names the intended use directly: integrating analytics code blocks without editing template files or reaching for a separate insertion plugin.
For a marketing agency that runs tag managers, call-tracking scripts and conversion pixels across client properties, that is a practical control. The placement options let you match where a given vendor expects its snippet — header scripts, body-open scripts, footer scripts — rather than dropping everything in one place. The same changelog note is the only evidence supplied for this feature; the field's limits and validation behaviour are not documented in the source material.
What the update record shows
The changelog runs from version 2.2.3 in September 2022 to 3.12.3 in July 2026, with dozens of releases in between. Recurring entries include compatibility testing against successive WordPress versions — 6.5, 6.6, 6.7, 6.7.2, 6.8, 6.8.2, 6.8.3, 6.9 and 6.9.1 — plus refreshes of bundled plugins: Easy Social Share Buttons, Master Slider, WP Cost Estimation & Payment Forms Builder, ValvePress Rankie, and Live Composer Premium Extensions.
Elementor work appears as its own thread: template design improvements in version 3.4.0 (September 2024) and a breadcrumb/Elementor option fix in version 3.11.2 (January 2026). The pattern suggests a maintainer still investing in both the builder integration and the plugin stack rather than a theme coasting on past sales. The marketplace listing shows version 3.12.6, while the changelog's last entry is 3.12.3; the gap is small and may simply reflect documentation timing, but it is a reason to confirm the version you actually receive.
Compatibility entries are claims, not package contents
The marketplace attributes, observed on 3 November 2026, list Facebook, Easy Digital Downloads, Elementor, Elementor Pro, Gravity Forms, WPML and Foundation 5 among compatible technologies. Those are vendor statements about interoperability, not indications that any of them ship inside the theme.
The file list is narrower: PHP, CSS and JS files. So a multilingual build needs its own WPML licence, and e-commerce or form functionality depends on the plugin you choose. The theme is built on the Underscores framework, marked widget-ready and Gutenberg Optimized, with PHP, CSS and JS files in the package — the block editor attribute says the theme works with blocks, not that its demo layouts are block-built.
Who the builder history and script fields suit
The conversion utility and the script fields point at the same buyer: an agency or freelancer maintaining marketing sites where tracking snippets change often and older pages may predate the Elementor switch. Both features exist because the theme has been in production long enough to accumulate real sites.
If you are starting clean, judge SEOWP on its Elementor templates and on whether its marketing-agency demo structure matches the site you need to build. The builder transition is context rather than an obstacle — but it does explain why some of the theme's documentation and community discussion describes a workflow you will not find in the current version.
Questions & answers
Do I need Elementor Pro to use SEOWP?
The marketplace lists both Elementor and Elementor Pro as compatible, and the changelog does not state that Pro is required. Nothing in the supplied material confirms whether any specific template depends on Pro features, so check the templates you intend to use before committing to the free version.
Can I still build pages with Live Composer?
The theme's page-builder layer was updated to support Elementor in version 3.0.0, and Live Composer extensions continued to receive compatibility updates afterward. The changelog does not describe the current status of Live Composer as a supported editing route, so a new build should be planned around Elementor.
Does the package include WPML or Gravity Forms?
No. The file list covers PHP, CSS and JS files, and the compatibility entries for WPML, Gravity Forms and Easy Digital Downloads describe interoperability. Each of those plugins needs its own licence.
