Seosight

Layout is configured per content type, not per demo

Seosight's feature list separates layout decisions by content type rather than offering one global page style. Blog and portfolio each get individual options for the header, the stunning header and the subscribe panel, plus their own sidebar settings. The stunning header is itself configurable: page-title section size, background colour and background images, text colour, and independent show/hide switches for the entire header, the page title and breadcrumbs.

That changes how you plan a site. Instead of choosing one demo and living with its spacing, you decide that portfolio items carry a large banner while blog posts carry none, and that the subscribe panel appears under articles but not under case studies. Crumina's description also mentions a customization panel whose options are split into tabs per theme section, which matches this section-by-section model. If your marketing site mixes a services catalogue, a portfolio and a blog, this is the part of the theme worth judging first.

Two editors are documented, and they are not the same product

The description is not consistent about which builder drives page content. One block says Seosight includes the KingComposer frontend live editor. Another says the theme is based on Elementor, described as a builder with around 40 blocks, and the plugin list names both KingComposer, KC Pro and Elementor among pre-packaged plugins. Marketplace attributes recorded on 4 November 2026 list Elementor and Elementor Pro as compatible.

The changelog explains why both appear. Entries across 2021 through 2025 fix KingComposer issues in some releases and Elementor widget issues in others; version 5.45.1 (January 2025, as dated in the source) records an update to the Seosight Elementor Widgets plugin, and version 5.10 records deprecated Elementor function updates. The practical reading is that this is a theme carried through a builder migration, so the demo content you import and the editor you continue with should be confirmed against each other rather than assumed. Nothing here proves both editors work on the same site without friction.

Forms, sliders and menus the vendor names

Alongside the builders, the theme bundles a form builder that the vendor says lets you create any form layout with a few mouse clicks, listed separately from the pre-packaged Contact Form 7. Both are claims from the listing; which one your forms end up running on is a decision to make before you build contact and quote pages.

A fullscreen slider is included for banners, and the vendor lists five predefined row animation backgrounds whose default images can be replaced. Multi-column mega menus and a one-page parallax option are also named, along with SVG icon support. These are the pieces that shape a landing page for an agency: a banner, an animated section behind a services grid, and a navigation row that can hold dropdown columns. Treat the slider and animation settings as things to test on a staging copy, since animation backgrounds and parallax are the kind of feature that interacts with caching and performance plugins.

Portfolio and blog controls decide what a visitor clicks

The portfolio block is the most specific part of the listing. Featured images can open either the inner portfolio page or a lightbox, chosen per setup, and there are two pagination types plus an adjustable item count. The sortable categories panel can be shown or hidden, with sort order, sort type and category selection configurable, and a related projects block is available. Portfolios display in a three-column layout, and the vendor notes that additional blocks can be added with Elementor.

The blog carries the same pagination and per-page controls, plus ordering by parameters and six post formats. For an agency publishing case studies and articles under one roof, the lightbox-versus-page choice is the one that matters most: a lightbox keeps a visitor in the grid, while an inner page gives each project its own address to link from proposals and search results.

Multilingual setup is spelled out rather than implied

The listing is unusually concrete on languages. WPML and Polylang are both declared as compatible, the theme ships a POT file for translating its own strings, and the language switcher can sit in the top bar. That switcher accepts WPML and Polylang switchers as well as custom language shortcodes from other plugins, which widens your options if you already use a translation routine.

RTL support and a bundled basic child theme are also listed. For an agency site serving more than one market, RTL support and a child theme are the two structural items: the child theme gives you a place for customisations that survive theme updates, and the RTL declaration covers right-to-left layouts. Neither is verified by the listing beyond the vendor's statement, so plan a review of menu, slider and stunning-header behaviour in an RTL locale.

What the platform declarations do and do not say

The marketplace attributes captured on 4 November 2026 declare WordPress 6.9.x down to 5.7.x, WooCommerce 6.x.x through 9.x.x, Elementor and Elementor Pro, bbPress 2.5.x and 2.6.x, Easy Digital Downloads, Events Calendar and Events Calendar Pro, and WPML. The same attributes mark Gutenberg Optimized as No. That flag describes the vendor's stated optimisation for the block editor; it is not proof that the block editor is unusable, and this theme's page content is described in terms of Elementor and KingComposer anyway.

Two details sit outside those attributes. The listing names Yoast SEO, Polylang and WPBakery Page Builder as third-party compatibility but does not surface them in the attributes, and the older feature text still mentions a WordPress 4.7 test. A declared range is a statement of intent from the vendor, not a record of the theme running on your server with your plugin set. The package is listed with layered PSD, PHP, HTML, CSS, Sass and JavaScript files, so a designer can pick up the source assets even if all layout work happens in the browser.

Where the section-level controls earn their keep

Seosight suits a site that has several content types with different presentation needs: a services or landing page set, a portfolio of client work, and a blog. Its strength is that header, banner, sidebar and subscribe decisions can differ between those types without a second theme. The form builder, slider and mega menu then cover the contact and navigation pieces an agency site usually needs.

The friction is concentrated in the editing story. With two builders documented and a changelog split between KingComposer and Elementor fixes, budget time to confirm which editor the demo you like actually uses, and check how the theme behaves with your caching and translation stack before committing. A team that wants one clearly documented block-based workflow will find the split less comfortable than the layout controls are rewarding.

Questions & answers