1Footer documentation
WordPress, HubSpot, Shopify and Wix
Find the available CMS installation path, understand native publishing requirements and prepare for a theme, plugin or platform change.
Last reviewed
Start with the available integration
Native delivery puts the footer into the HTML published by your CMS. A package download, account connection and autonomous migration repair are separate capabilities. The platform matrix lists released options; broader native automatic repair is still in development.
1Footer runs supported automatic workflows in the cloud. Installing a manual plugin or export does not give it permission to change a CMS theme, install a plugin or publish a replacement site.
WordPress: install the server-rendering plugin
The downloadable plugin provides server delivery. Automatic native installation and recovery are in development. Managed WordPress hosts can restrict plugin or hosting access; an account connection alone does not establish permission to change the installation.
- Add the public WordPress domain to your 1Footer workspace and publish the intended footer.
- Download the WordPress plugin ZIP. In WordPress, use Plugins → Add New → Upload Plugin, upload the ZIP and activate it.
- Open Settings → OneFooter and configure the connection with your 1Footer API key. Keep the key private.
- Choose the rendering settings appropriate to your theme, then check the public page for one usable footer.
- Check included and excluded routes and inspect the initial HTML. Recheck after theme changes, caching changes or a website move.
HubSpot and CMS exports: publish a snapshot
Use the native CMS templates or an HTML/CSS export as a starting point for your platform’s publishing workflow. Include both footer markup and styles in the published template. Preview the page, publish through the CMS and check the actual public response.
A snapshot does not update itself when you publish new links or change page rules in 1Footer. Export and publish the new version through your CMS. Account-connected HubSpot publishing and automatic native recovery are in development.
Shopify: native automatic repair is in development
Shopify needs a native storefront integration. The automatic theme repair adapter is not released yet, so connecting a store does not currently establish completed autonomous installation, migration or recovery.
Native publishing depends on permitted access to the actual store and theme. Theme changes and asynchronous publishing jobs need their own verification. A preview or accepted operation does not establish that the current public storefront contains the footer. Ordinary Cloudflare proxying is not a supported workaround.
Wix: native automatic repair is in development
Wix requires its own native delivery path. The automatic native adapter is not released yet. A client widget or search-engine-only markup cannot by itself establish visible footer links in the initial HTML received by ordinary visitors.
The eventual integration must preserve page targeting, styles and publication behavior for the actual Wix editor and website. Do not substitute ordinary Cloudflare proxying for the required native implementation.
After a theme, plugin or host changes
Keep your current publication, page rules and intentional pauses. Confirm the account and installation that now publish the website. A different domain, CMS instance or store requires its own binding; an old connection is not permission to change the replacement.
For a released automatic path, 1Footer checks the destination and repairs within the connected access. Old-installation cleanup is a separate recovery step and can remain unresolved. Check the latest public result before treating the migration as complete.