Kadence Pro - WordPress Plugin

Kadence Pro Setup Guide for a WordPress Site

This guide looks at Kadence Pro as a practical extension set for the Kadence theme: what to enable after installation, how to avoid getting lost in the modules, where to look for the result, and what to check before using it on a live site. Instead of repeating the product page, this article lays out a working process for a site owner, editor, or webmaster who has already chosen the Kadence ecosystem and wants to use it deliberately.

The plugin's real value does not come from a single toggle, but from how the pieces work together: the Kadence theme provides the site's base framework, while the Pro modules add conditional headers, advanced header elements, mega menus, hook-based insertions, WooCommerce settings, infinite scroll, a dark color palette, and separate archive scenarios. That is why the guide below moves from safe preparation to specific use cases instead of simply listing features.

The guide separately covers pre-installation prep, enabling modules, configuring Hooked Elements and conditional headers, a practical example with an informational banner, result validation, common issues, and similar alternatives. If a feature is unavailable in your build, use the official module list in the Kadence panel as your reference and do not rely on workarounds instead of the built-in settings.

What this Pro extension set is designed to do

Kadence Pro is not meant to replace the entire WordPress editor or turn your site into a separate page builder. Its purpose is more specific: to expand what the Kadence theme can do when the free theme is no longer enough, but you do not want to install a heavy visual builder just to manage a header, banner, conditional block, or store layout.

On a typical project, it looks like this: the site is already built on Kadence Theme, the global colors and typography are in place, the menu and footer are working, but new requirements come up that the free theme only partially covers. For example, you may need a different header on a landing page, icons in menu items, a notice above the content only in selected categories, a WooCommerce side cart that opens after adding a product, or a light/dark palette switch for visitors.

Kadence Pro's strongest advantage is conditional control over an existing site framework. It does not force you to rebuild the theme, and for most scenarios it does not require editing theme files. Instead, it adds panels and element types that work on top of the standard WordPress structure and the Kadence theme.

It is also important not to confuse several products from the same ecosystem. Kadence Theme Kit Pro extends the theme and its areas: the header, menus, hooks, archives, WooCommerce theme settings, maintenance/coming soon mode, and some system-level scenarios. Kadence Blocks Pro is focused on editor blocks and dynamic content. In more advanced setups they may be used together, but they are not the same product. If your task specifically requires a dynamic post template with fields and blocks, make sure the correct block package is installed and not just Theme Kit Pro.

Practical rule of thumb: if the task is about where a block, header, footer, archive, menu, or WooCommerce element appears on the site, start with Kadence Pro. If the task is about specific blocks inside a post or page, check Kadence Blocks and its Pro features.

Who Kadence Pro is a good fit for, and when it may be unnecessary

This plugin is especially useful for people who want to stay within WordPress's native workflow: the Customizer, block editor, menus, widgets, and theme settings. A webmaster does not have to build a separate template system for every site, and an editor can more easily understand why a block appears in a certain place: the element has an insertion point, display rules, user settings, device settings, and an expiration date.

The most natural users are:

• Owners of content-driven sites who need banners, notices, author boxes, post-paragraph CTAs, different hero sections, and controlled archive layouts.
• WooCommerce stores where a side cart, add-to-cart behavior, extra catalog elements, and a convenient header with account, search, and cart features matter.
• Agencies and freelancers who repeat similar patterns across client sites and want to manage them through the interface instead of editing templates.
• Editorial projects where the same block should appear only in selected categories, on archive pages, for specific roles, or until a certain date.

The product may be unnecessary if the site is already fully built around Elementor Pro Theme Builder, Bricks, Breakdance, or another builder that controls the header, footer, post templates, and display conditions. In that type of architecture, two tools can end up solving the same problem, and the user may waste time looking for a settings mistake when the real issue is a priority conflict.

You should also consider the experience level of the team. Kadence Pro works best when the administrator understands the difference between a global theme setting, a conditional rule, and a block inserted through a hook. If the site will be maintained by people with limited WordPress experience, it is better to keep fewer modules active and label each Element more clearly. Internal names like campaign banner before posts or landing header for logged out users are useful not because they look nice, but because they make future diagnostics easier: a month later, it will still be clear why the element exists and where it is supposed to work.

There is also the opposite scenario: a developer may decide it is faster to add everything through a child theme. Sometimes that is true, but for repeatable marketing blocks, temporary notices, condition-based headers, and editorial CTAs, the Kadence Pro interface is usually more convenient. It keeps the setup in the admin panel, where an editor or site manager can disable it without file access. That approach is especially valuable when speed of safe change matters more than maximum template-level control.

One more case where you should not rush into Pro modules is a very simple brochure site. If all you need is one menu, a standard header, a standard footer, and a few pages, the free Kadence theme is often enough. The Pro package shows its value when conditions, alternate headers, store scenarios, insertions in different site areas, and the need to quickly disable or swap those elements start to matter.

What to check before installation

This preparation is not just a formality. Kadence Pro does not change the content of a single page - it changes how the theme behaves across different areas of the site. Before installation, it is worth doing a quick review: which theme is active, which plugins already control the header and templates, where caching is enabled, what depends on WooCommerce, and which user roles should see the final result.

Active theme and baseline compatibility

Kadence Theme Kit Pro is an extension for the free Kadence theme. That means the first thing to verify is that Kadence is the active theme, not a child theme built on another framework and not a full-site theme where the header and footer have been completely replaced by a third-party builder. If you are using a Kadence child theme, that is fine, but the parent theme still needs to be in place.

Next, open Appearance -> Kadence. This page should display the Pro Addons that can be enabled one by one. If you only see the base theme settings, or fewer items than expected, do not try to compensate with custom code. First, verify that the correct Pro plugin is actually installed, that it is active in the plugins list, and that the interface is not being hidden by a conflicting admin plugin.

Who is already controlling the header, footer, and templates

The most frustrating issues happen when two tools try to replace the same site area at the same time. For example, Elementor Pro may render its own header, Kadence Conditional Header may inject an additional header, and a specific page may have the standard header disabled. Visually, that can look like a missing menu, a duplicate header, or different header versions for logged-in and regular visitors.

Before enabling conditional headers, make a simple map:

• Where the site's main header is created: in the Customizer, in a block-based Header (Adv), in Elementor, or in another builder plugin.
• Whether there are pages where the global header is already disabled through page settings.
• Whether separate templates are being used for posts, products, archives, or landing pages.
• Whether a caching plugin or server-side cache could be serving an older version of the header.

A list like this only takes a few minutes, but it can save hours of troubleshooting later.

Staging environment and backup plan

If the site already has live traffic, enable Pro modules on a staging copy first or during a low-traffic window. A minimum safe plan is this: create a backup, enable one module, configure one scenario, check the result in a regular window and a private window, and only then move on to the next module. Do not enable all Pro Addons at once just because they are available. Every module adds a new behavior point, which also means a new possible source of errors.

Installation and initial module activation

The installation process is technically the same as for any ZIP-based WordPress plugin: open Plugins -> Add New Plugin, upload the archive, install it, and activate it. The important Kadence Pro detail is that the archive must be installed as a plugin, not as a theme. If you try to upload it through the theme installer, WordPress will complain that the package structure is invalid.

After activation, do not jump straight into complex templates. First, open Appearance -> Kadence and review the list of Pro Addons. Enable only what you need for the immediate scenario. For most sites, a sensible first set looks like this:

• Header Addons - if you need more elements in the header builder: account, extra HTML areas, search, a contact block, a second button, a widget area, or additional navigation areas.
• Hooked Elements - if you need to insert blocks into specific site locations and control their display conditions.
• Conditional Headers - if different parts of the site should use different headers.
• Ultimate Menu - if you need icons, highlight tags, mega menus, or custom content inside dropdown items.
• WooCommerce Addons - if the site is a store and you need to extend catalog, cart, and product page behavior.

Modules like Infinite Scroll, Color Palette Switch, Maintenance Mode, and Header/Footer Scripts are better enabled for a specific purpose. Not every site needs them, and some of them require separate validation after setup.

How to tell whether a module was enabled correctly

After enabling each Addon, do not rely on a generic success message - look for a new interface item. For example, Hooked Elements adds access to Appearance -> Kadence -> Elements, Header Addons expands the list of available elements in the header settings, and WooCommerce Addons adds new sections under Appearance -> Customize -> WooCommerce.

If the toggle is on but the new panel does not appear, first refresh the admin page and check the current user's permissions. Then temporarily disable admin plugins that alter the WordPress menu. Front-end cache usually does not affect whether admin menu items appear, but object cache or aggressive admin-side optimization can delay interface updates.

After the first successful check, record the starting state: which module is enabled, which element was created, and which page it was tested on. You can do this in a project log or directly in the name of the test element. That small trace makes it much easier to tell a Kadence issue apart from a simple the setting was saved in the wrong place situation. This matters even more in projects with multiple admins, because one person may be editing the Customizer, another the menu, and a third a block template, while the final symptom appears as a single “broken header.”

Configuring Hooked Elements: where a block appears and who sees it

Hooked Elements is the most product-specific and most powerful section of Kadence Pro. The idea is simple: you create an element in the WordPress editor, choose an element type, assign an insertion point, and define display rules. As a result, a block can appear before post content, after the title, in place of the sidebar, in the footer, in the hero section, on archives, only for specific roles, or only until a specific date.

For a new user, the difficulty is not creating the block itself, but making three decisions: which element type to choose, which placement to assign, and which display rules will not conflict with each other. If you get even one of those wrong, the element may not appear at all, may appear everywhere, or may override an area you never intended to change.

Element types and what they are actually for

In the Elements interface, you will usually see four working models. Content Section is best for banners, notices, subscriptions, author boxes, and small content inserts. Fixed Section stays fixed on the screen and works well for sticky notices or action buttons. Template Element replaces an entire area, such as part of a post template or archive template. HTML Editor is useful for inserting HTML or scripts into supported areas, but it should be used carefully and only when the task cannot reasonably be handled with standard blocks.

For a first setup, choose Content Section. It is safer because you are adding a block to a specific location instead of replacing an entire template. Template Element should only be used once you clearly understand which area will be replaced and what data needs to be output inside that template.

Display Settings, User Settings, and Device Settings

Placement controls where the element is inserted, while Display Settings determine where that rule actually applies. For example, the same banner can be inserted before content but displayed only in posts from a specific category. User Settings restrict visibility based on user state: everyone, logged-in users, logged-out users, or specific roles. Device Settings help you exclude desktop, tablet, or mobile if the element causes problems on a particular screen size.

A safe setup starts with a narrow rule. Do not select Entire Site when testing a new element. Show it on one test page or in one category first, verify it, and only then expand the display area. This is especially important for fixed elements and template replacements.

Checklist before publishing an element

Before publishing an element, do a quick review:

1. Name the element so its location and purpose are obvious, for example Blog posts - disclosure before content.
2. Select a preview post if the element depends on post or archive context.
3. Add one display rule and one exclusion only if needed.
4. Make sure you have not selected a user rule that hides the element from a regular visitor.
5. Open the page in a private window and confirm that the element appears or stays hidden exactly as intended.

If the element does not appear, do not create a second copy of it. Open the existing element and review the settings in sequence: type, placement, display rule, user rule, device rule, expiration, cache.

Conditional headers, enhanced header tools, and Ultimate Menu

Many Kadence Pro features are tied to the top area of the site. That makes sense: nearly every visitor sees the header, and it is often where you need different experiences for a landing page, blog, store, account area, or members-only section. But the header is also a high-risk area because the menu, logo, cart, search, sticky behavior, and transparent header can all depend on different settings.

When to use Conditional Headers

Conditional Headers are useful when one site genuinely needs different headers. For example, the home page may use a transparent header over the hero section, blog posts may use a compact header with category navigation, and the store may need a header with search, account, and cart features. If you only need to change the color or spacing of the global header, do not create a conditional header - just configure the regular header builder.

When creating a conditional header, keep the menu in mind. A WordPress navigation menu can be shared by multiple header variants. If you change the menu items in one place, they may change everywhere that same menu is used. If you need truly different headers, create separate menus and assign them intentionally.

Header Addons as a modular toolkit

Header Addons increases the number of elements available in the builder. That is helpful when the standard set is not enough: you may need a second HTML block, a dedicated contact area, enhanced search, an account item, extra navigation, a divider, or a widget area. Add elements to the desktop layout first, then check the tablet and mobile layouts separately, because not every element makes sense on every screen size.

A common mistake is building a polished desktop header and forgetting about the off-canvas area for the mobile menu. On mobile devices, the goal is not to display everything - it is to keep the entry points clear: logo, menu trigger, cart, or account if needed. Everything else is usually better moved into the mobile menu or hidden.

Ultimate Menu and mega menus without the clutter

Ultimate Menu adds advanced options to classic WordPress menus: icons, highlight tags, mega menus, and custom dropdown content. Mega menus are especially useful for sites with large catalogs, knowledge bases, courses, or multiple service categories. But they should only be built where a regular dropdown menu is no longer enough.

A practical workflow is this: first create a standard menu structure and save it, then open the settings for the specific menu item and add the enhancements. If the Menu Item Settings button does not appear immediately after adding the item, save the menu and reopen it. That is a normal interface quirk, not a sign that something is broken.

Practical example: a banner above posts in one category

Let us walk through a scenario that explains how Kadence Pro works better than an abstract feature overview. Imagine a content site with a category for partner reviews, and every post in that category needs a short notice above the text. The banner should appear only in the target category, should not affect pages, archives, or other posts, and should be easy to disable safely once the campaign ends.

Goal and preparation

The goal is to create a Content Section Hooked Element, insert it before the post content, and limit its visibility with rules. Before you begin, confirm that Kadence Theme is active, the Hooked Elements module is enabled, the target category already exists, and the site has at least one test post in that category. For the banner design, you can use standard WordPress blocks or Kadence Blocks if they are installed.

Setup steps

1. Open Appearance -> Kadence and make sure Hooked Elements is enabled.
2. Go to Appearance -> Kadence -> Elements and click Add New.
3. Select Content Section, give it a clear name, and build the banner in the block editor.
4. Open the Element Settings panel and choose a placement before the post content or another location that matches the goal.
5. In Display Settings, set it to show on single posts in the target category or use the available post-selection rule.
6. In User Settings, leave All Users selected if every visitor should see the banner.
7. If the banner is temporary, configure Expires Settings or plan a manual disable date in advance.
8. Publish the element and open the test post in a private window.

How to validate the result

Your validation should cover more than one page - it should test the boundaries of the rule. Open a post from the target category, a post from another category, a regular page, the category archive, and the home page. The banner should appear only where it is intended to appear. If it shows too broadly, the Display Settings rule is too general. If it does not appear anywhere, check the placement, user rule, and expiration settings.

Quick takeaway: a proper Hooked Element has a clear name, a narrow display rule, a verified placement, and a defined way to disable it. Without those four things, even a well-designed banner quickly turns into a source of errors.

The cache-related detail

If the banner appears for the administrator but not for a regular visitor, open the page in a private window and clear the cache. Be especially careful on sites using page cache, a CDN, or HTML optimization tools. For conditional elements, it is important that the cache does not serve the same page version to users who should see different outputs.

WooCommerce, archives, and scenarios where Pro modules deliver quick wins

Kadence Pro is useful for more than just headers and hooks. For stores and archives, it handles tasks that often require a separate plugin: side cart behavior, an off-canvas sidebar for the catalog, sticky add to cart, AJAX add to cart on the product page, infinite scroll for archives, and custom settings for individual taxonomy archives.

WooCommerce Addons: what to enable first

If the site is not a store, you can leave WooCommerce Addons disabled. If WooCommerce is active, start with one specific improvement. For example, if you want the side cart to open after a product is added, first make sure the mini cart has been added to the header builder and is set to use the popout cart. Only after that should you enable the option that shows the side cart after add to cart.

On product pages, use Ajax add to cart and sticky add to cart carefully. They improve usability, but they can also conflict with variation plugins, subscription plugins, custom product fields, or third-party checkout extensions. A safe sequence is to enable the feature on a test product, add the product to the cart, and then verify the quantity update, mini cart, cart page, and checkout.

Infinite Scroll for archives and store pages

Infinite Scroll works well for blogs, catalogs, and search archives where the user browses many cards in sequence. But it should not be enabled automatically. For SEO, analytics, and usability, some projects still benefit more from standard pagination. If you enable infinite scroll, set a clear end-of-feed message and verify that the footer, filters, analytics events, and load behavior are not lost in the process.

Archive custom settings for individual categories

Archive settings are useful when different taxonomies need different presentation styles. For example, a news category may use a denser grid, while a research category may need larger cards and a different title section background. This is not a replacement for a full template system, but it is a convenient way to make specific archives more distinctive without editing theme files.

Dark palette, custom fonts, and careful enhancements

Some Pro features focus on the site's visual system rather than its structure. These include Color Palette Switch, custom fonts, and Header/Footer Scripts. They are useful features, but they require discipline: you cannot turn on a dark palette and assume that every block from every third-party plugin will automatically become readable.

Color Palette Switch without the illusion of a complete dark theme

Color Palette Switch works through Kadence's global palettes. That is a lightweight approach: the switch changes the selected palette, and elements connected to global colors respond to that change. If blocks or third-party plugins use hard-coded colors, they may remain unchanged. That is why you should first align the site's primary colors with the global palette, and only then enable the switch.

Do not test only the home page. Open posts, forms, the catalog, the cart, checkout, popout panels, and blocks with background colors. If text becomes unreadable, fix the specific element instead of randomly changing the entire palette.

Safe CSS for an element that does not follow the dark palette

The official Kadence logic adds the color-switch-dark class to the body when the dark palette is active. That gives you a precise way to fix an element that is not tied to the global colors. You can add the CSS through Appearance -> Customize -> Additional CSS or through your site's standard custom CSS method.

.color-switch-dark .custom-notice {
  color: var(--global-palette4);
  background: var(--global-palette9);
  border-color: var(--global-palette6);
}

Replace .custom-notice with the real class used by your block. After saving, open the page, switch to the dark palette, and check the contrast for text, links, and buttons. Rolling it back is simple: remove this CSS snippet or comment it out. Do not edit theme or plugin files for a task like this, because the change will be lost during updates and will make long-term maintenance harder.

Custom fonts and performance

Kadence Custom Fonts lets you connect local font files or Adobe Fonts if the brand requires them. For most sites, system fonts or Google Fonts already supported by the theme are enough. Custom fonts should only be added when there is a real branding reason to do so. Upload only the font weights you actually need, define a fallback stack, and check how the page looks before the font fully loads.

How to validate the result after setup

After configuring Kadence Pro, it is not enough to say “everything looks fine on the site.” Validation has to be tied to the specific modules you enabled. For Hooked Elements, the key factors are placement and display condition. For Conditional Headers, it is priority and the absence of duplicates. For WooCommerce, it is cart and product behavior. For Infinite Scroll, it is feed loading and footer access. For Color Palette Switch, it is the readability of all critical blocks.

Use a short validation matrix:

Also test the site in two user states: logged-in administrator and regular visitor. Many User Settings conditions only become visible that way. If an element is supposed to be hidden from the admin, create a separate test user with the required role.

After validation, clear the cache, open the page in another browser, and check the developer console if something does not respond to clicks. Red JavaScript errors are not always caused by Kadence, but they often explain why a menu, side cart, or switcher is not working.

Common Kadence Pro issues and how to diagnose them

Most Kadence Pro problems are not caused by a module being “broken,” but by an incorrect condition, a priority conflict, caching, or expecting a feature from the wrong product in the ecosystem. Below is a practical troubleshooting path based on visible symptoms.

The Pro module is enabled, but the new interface item does not appear

Symptom: the Addon toggle is active, but the expected section is missing from the Customizer, Elements, or the WordPress menu. Possible causes include the wrong product being active, the admin panel not refreshing, the current user role lacking the required permissions, or the admin menu being altered by a third-party plugin.

Check the plugins list, the active Kadence theme, the Appearance -> Kadence page, and the current user's permissions. Then refresh the admin panel, temporarily disable plugins that hide menu items, and test again. If the module is only relevant for WooCommerce, make sure WooCommerce itself is active.

A Hooked Element does not appear on the page

Symptom: the element is published, but it is missing on the front end. The usual causes are Display Settings, User Settings, Device Settings, Expires Settings, or an incorrect placement. Check the element in a private window and temporarily simplify the rule to a single test page.

If the element appears after simplifying the rule, add the conditions back one at a time. If it still does not appear even on the test page, make sure you selected an element type that can render in the intended location. Template Element and Content Section solve different problems, and changing the type after the fact may not be the safest fix.

A duplicate header appears, or the wrong header is showing

Symptom: the page shows two headers, the menu disappears, or the header from the wrong section is being displayed. The usual cause is a conflict between the global header, a Conditional Header, an Advanced Header Block on the page, a page builder template, or a setting that disables the header on a specific post.

Start by determining which source is supposed to control the header. If you are using Kadence Conditional Headers, verify that the replacement rule is assigned to the correct pages and does not overlap with another header solution. If an Advanced Header Block is inserted manually on a page, make sure the global header is disabled only where that is actually required.

The mega menu or icons do not appear after setup

Symptom: the menu item settings are saved in the admin area, but the icon, highlight tag, or mega menu does not appear on the site. Possible causes include not saving the menu after adding the item, editing the wrong menu, the header using a different menu location, cached old markup, or the mobile version using a separate menu.

Save the menu, verify the menu location assignment in the header builder, clear the cache, and test desktop and mobile separately. If the issue only appears on mobile, check the off-canvas area and the mobile navigation structure.

The WooCommerce side cart does not open after adding a product

Symptom: the product is added, but the side cart does not appear. The official logic requires a mini cart in the header, configured to use the popout cart. Only then should the corresponding WooCommerce Addons setting be enabled.

Check that the Cart item is present in the header builder, verify the popout cart setting, and test the behavior on a simple product without complex variations. If it works for a simple product but not for a variable one, look for conflicts with variation plugins, subscriptions, extra fields, or AJAX product-handling plugins.

The dark palette switches, but some blocks remain unreadable

Symptom: the background changes, but text, a button, or a form from a third-party plugin remains styled for the light theme. This is an expected limitation of a lightweight global-color approach: not every external block is tied to the Kadence palette.

Check whether the problematic block uses the theme's global colors. If it does not, add targeted CSS through the color-switch-dark class. If there are too many such blocks, the project may need a more specialized dark-theme solution rather than just a palette switch.

The Pro plugin update fails

Symptom: WordPress shows an error while updating the Pro plugin. The official documentation ties some of these cases to update access status and account settings. This article does not cover purchases or license-key entry, but the practical path is to verify update access in the developer account, make sure you have the current ZIP file, and then repeat the update from the plugins screen.

If the error persists, do not blindly remove anything from a working site. Create a backup, check the error log, temporarily disable admin-side caching or security plugins, and contact the developer's support team with the exact error message.

When Kadence Pro is the right choice

Kadence Pro is a strong option for sites that already use Kadence Theme and need control over more than a single page - repeatable areas such as the header, menus, hooks, archives, store elements, dark palette, and conditional blocks. Its biggest strength is a clear connection between the setting, the display condition, and the result on the site.

Before rolling it out, decide which two or three tasks you actually need right now. For example: enable Hooked Elements for a banner, configure a Conditional Header for a landing page, and add a WooCommerce side cart. After each step, check the result in a private window, on a mobile screen, and with cache cleared. That process is far more reliable than enabling everything at once and then trying to figure out why the site behaves unpredictably.

If, after reading this guide, you know which module your site needs and how you will verify the result, you can move on to the installation file and download the Kadence Pro archive for testing on a staging copy of the site. Do not move the configuration to the live project until you have checked the header, elements, WooCommerce scenarios, and caching behavior.

For a small site without conditions, store functionality, or special header scenarios, start with the free Kadence theme. For a site where controlled insertions, alternate headers, advanced menus, and careful archive handling matter, the Pro package becomes a practical tool rather than just another settings panel.