WordPress

Inclusify installs on WordPress as one script tag in the site footer, added either through a plugin’s footer field, a child theme’s wp_footer hook, or a direct footer.php edit. You need an administrator account, because all three routes are behind the plugin or theme file permissions; there is no paid tier and no WordPress.com plan requirement on a self-hosted site. It is one field and one Save. What all three depend on is the theme calling wp_footer(), which WordPress documents as the theme author’s responsibility rather than a guarantee.

Register the domain first

Add your domain in the Inclusify panel before you paste the script tag. Bundles are built per registered domain, and an unregistered one fails silently: the script URL still returns HTTP 200, but what it serves is a single console.log saying the domain is not registered. There is no error to find and no widget appears.

Method 1: Theme Editor

The quickest way to add Inclusify to a classic WordPress theme, and the least durable. Block themes have no footer.php to edit at all: WordPress describes classic themes as the ones built with PHP templates and functions.php, where a block theme is built from block markup. A theme update also overwrites this edit, so Method 2 is the safer choice either way.

1

Open Theme Editor

Go to Appearance Theme File Editor in your WordPress admin. On a block theme WordPress moves it to Tools Theme File Editor instead.

2

Find footer.php

In the right sidebar, click on footer.php (or Theme Footer).

3

Add the Widget Code

Paste this code just before the closing </body> tag:

footer.php
<script src="https://app.inclusifyapp.com/w/YOUR-DOMAIN.com.js" async></script>

Replace YOUR-DOMAIN.com with your actual domain.

4

Update File

Click Update File to save your changes.

Method 2: Insert Headers and Footers Plugin

The recommended route, and the only one available on a block theme. The snippet lives in the plugin’s own storage rather than in the theme, so a theme update or a theme switch leaves it in place.

  1. Install and activate WPCode (formerly Insert Headers and Footers)
  2. Go to Code Snippets Header & Footer
  3. Paste the widget code in the Footer section
  4. Click Save Changes
HTML
<script src="https://app.inclusifyapp.com/w/YOUR-DOMAIN.com.js" async></script>

Using a Child Theme

If you're using a child theme, add the script using the wp_footer hook in your child theme's functions.php:

functions.php
add_action('wp_footer', function() {
    echo '<script src="https://app.inclusifyapp.com/w/YOUR-DOMAIN.com.js" async></script>';
});

Compatibility

  • • Works with classic and block themes (block themes need Method 2 or the child-theme hook, not Method 1)
  • • Compatible with page builders (Elementor, Divi, WPBakery, etc.)
  • • Works with WooCommerce
  • • Page caching is fine once you purge it. If a plugin combines, minifies or delays JavaScript, exclude app.inclusifyapp.com from that option

What needs attention on WordPress

Every footer method here depends on one theme-side call

WordPress documents wp_footer as printing scripts before the closing body tag, and says plainly that the hook is theme-dependent: it is up to the author of each theme to include it, and it may not be available on all themes. WPCode, a child theme's functions.php and a plugin's footer injection all hang off that one call, so a theme that skips it silently swallows all three.

A theme from the directory is required to have it

The theme review requirements list wp_footer(), immediately before </body>, among the calls a theme must make to be accepted into the WordPress theme directory. That is why this almost always works out of the box, and why the exceptions are bespoke and commercial themes that never went through that review.

Block themes have no footer.php to edit

WordPress describes classic themes as the ones built with PHP templates and functions.php; block themes are built from block markup instead and have no footer.php. So the theme-file method has nothing to edit on a block theme, and the plugin or child-theme hook is not a preference there but the only route.

Verify the installation

  1. Load the site in a private window, then use View Source and search for "inclusifyapp". The tag is server-rendered on WordPress, so if it is not in the source it never reached the page.
  2. Confirm the tag sits near the closing </body> tag rather than in the head. Footer placement is what every method here produces; anything else means the snippet went into the wrong field.
  3. Purge the page cache first if your host or a plugin runs one: HTML generated before the edit does not contain the script.
  4. Check a post, a page and the home page. Some themes render the front page through a different template, and a theme that omits wp_footer() on one of them omits the script with it.
  5. If View Source shows nothing anywhere, grep the active theme for wp_footer. A theme that never calls it cannot run a footer snippet from any plugin.

Widget bundles are served from a CDN and cached for a few hours. If you changed widget settings in the panel and the site still shows the old configuration, wait for the cache to expire or load the script URL directly with a cache-busting query string (`?v=2`) to confirm the new version is being served.

Troubleshooting WordPress installs

The widget disappeared after a theme update.
A direct footer.php edit is overwritten every time the theme updates. Move the script into WPCode (Code Snippets > Header & Footer) or a child theme's functions.php using the wp_footer hook, both of which live outside the parent theme's files.
The script is in the source but the widget never initialises.
A minification or "combine JavaScript" option has rewritten the tag. Add app.inclusifyapp.com to the JavaScript exclusion list of whichever optimisation plugin is active, then purge and retest.
Nothing appears anywhere and View Source has no tag at all.
The active theme does not call wp_footer(). WordPress makes that call the theme author's responsibility, so a theme can omit it and every footer-injection plugin goes quiet at once. Add the call to the theme's footer template, or switch to a theme that has it.
Changes are not visible even in a private window.
Purge the caching plugin and, if you use one, the CDN in front of it. Managed hosts run their own server-side cache that a plugin purge does not clear.
The browser console reports a Content Security Policy violation.
Something on the site is sending a CSP header that does not list the widget host. Add https://app.inclusifyapp.com to the script-src and connect-src directives wherever that header is set, which on WordPress is usually a security plugin rather than the server.

WordPress questions

Which of the three installation methods should I use?
WPCode, unless you already maintain a child theme. It is the simplest option that survives theme and core updates; a child theme's functions.php is the better choice if you keep site code in version control; editing footer.php directly works but is lost on the next theme update, and does not exist at all on a block theme.
Does it work with WooCommerce?
Yes, on every front-end page including shop, product, cart and checkout, because all of them render through the theme footer and therefore through wp_footer.
Does it work with Elementor, Divi or another page builder?
Yes. Page builders replace the content area but still render the theme's header and footer, so a wp_footer-hooked script loads normally.
Will it affect my Core Web Vitals?
No, on a default install: the tag is async and sits at the end of the body, so it does not block rendering or contribute to Largest Contentful Paint. If an optimisation plugin defers or combines it, test that the change has not moved it into the critical path.

WordPress documentation

Every WordPress-specific requirement, menu path and limit on this page comes from these pages. Menus move, so check them against your own admin if something does not match.

Related