The AiCM secure tag is a single line of JavaScript that lives inside your site <head>. This page covers a number of the content management systems, with the steps for each. Yours not listed? .
Pick your CMS
Select one to jump to the exact field name and steps. List continues to expand, yours not here etc words - 99% support as using tag in the header, see here.
The same secure tag pattern works on each CMS. Add it once, in the place your CMS uses for head code. The platform handles everything else.
What you add
One line of JavaScript inside the site <head>. No content rewriting, no plugin lock in.
What it does not do
It does not modify your CMS, your database or your hosting. It does not require server side changes.
What you need
Administrator access to whichever part of your CMS lets you add code to the page <head>.
Example secure tag
For illustration only. Your live secure tag includes a unique account identifier and is delivered to you during onboarding. Do not copy this snippet into a live site.
•The secure tag belongs in the <head>, not the <body>. Head placement is what gives site wide coverage.
•Add it once at the site level. Per page placement is rarely needed and creates drift.
•The script is loaded async, so it does not block your page render or hurt Core Web Vitals.
•If your site has a Content Security Policy, allow aicm.aaanow.ai under script-src.
•After saving, clear any plugin, theme or CDN cache. Stale caches are the most common reason verification fails.
•The example below is illustrative. Your live secure tag is unique to your account and is delivered during onboarding.
Before you start: get your tag from AiCM
Generate the secure tag once in your AiCM dashboard, then paste it into the head field your CMS provides. The same snippet works on each platform listed below.
2Open the Sites section of your dashboard, or finish onboarding if you are new.
3Add a new site, then enter your website URL or domain when prompted, for example www.example.com.
4Select Generate Tag to create your unique snippet.
5Use Copy tag to copy the full line to your clipboard.
6Paste the entire line, including <script> and </script>, into the area your platform provides for header, head, or site wide head HTML. When the CMS asks which pages should receive the code, choose all pages so PDF links are handled everywhere.
7After saving, publish your site, and use republish all pages if your CMS has that step. Then use the verification checks further down this page.
Quick reference
At a glance, where the secure tag lives in each CMS and what access is needed.
CMS
Where to add the secure tag
Permission
Difficulty
Section
WordPress
Theme header (header.php) or a header/footer plugin
Add the secure tag once site wide using a reputable header and footer plugin, or by editing your active theme's header.php.
1Sign in to wp-admin as an administrator.
2Install and activate a trusted plugin such as WPCode or Insert Headers and Footers.
3Open the plugin's settings and locate the Scripts in Header field.
4Paste the AiCM secure tag into the header field and save.
5Clear any caching plugin and any CDN cache so the new header is served.
Where this lives
Theme header (header.php) or a header/footer plugin
Permission needed
Administrator role with theme edit access
How to verify
Open any public page, view source, and confirm the script appears inside the <head>.
Shopify
Developer setup
Shopify themes load a single layout file. Add the secure tag to theme.liquid so it runs on each storefront page.
1From the Shopify admin, open Online Store, then Themes.
2On your live theme, open the Actions menu and choose Edit code.
3Under Layout, open theme.liquid.
4Paste the AiCM secure tag on the line directly above </head>.
5Save the file.
Where this lives
theme.liquid, just before </head>
Permission needed
Staff account with Edit code permission
How to verify
Visit the storefront, view source, and confirm the secure tag is present in the <head>.
Wix
Built in
Wix exposes a Custom Code panel for site wide head code. A Premium plan with a connected domain is required.
1Open the Wix dashboard for your site.
2Go to Settings, then Custom Code under Advanced.
3Choose Add Custom Code and select Head as the placement.
4Paste the AiCM secure tag, set Apply to All pages, and Load code on each new page.
5Save and publish the site.
Where this lives
Settings, Custom Code, Head section
Permission needed
Site owner on a Premium plan with a connected domain
How to verify
Open any published page, view source, and confirm the secure tag is in the <head>.
Squarespace
Built in
Squarespace provides a built in custom code panel. The Header field places code inside the <head> on each page.
1Open the site dashboard.
2Go to Settings, then Advanced, then Custom Code.
3Paste the AiCM secure tag into the Header field.
4Save changes.
Where this lives
Settings, Advanced, Custom Code, Header
Permission needed
Owner or Administrator on a Business plan or higher
How to verify
Open the live site, view source, and confirm the secure tag appears in the <head>.
Webflow
Built in
Webflow ships site wide head code on any paid Site plan. Code is published with the next site publish.
1Open your Webflow project.
2Go to Project Settings, then Custom Code.
3Paste the AiCM secure tag into the Head Code field.
4Save changes and publish the site.
Where this lives
Project Settings, Custom Code, Head Code
Permission needed
Workspace member with project edit rights, paid Site plan
How to verify
Visit the published domain, view source, and confirm the secure tag is in the <head>.
Joomla
Developer setup
Joomla can load the secure tag through the active template's index.php or through a small extension that adds head code.
1Sign in to the Joomla administrator panel as a Super User.
2Open System, then Site Templates, and choose your active template.
3Open index.php and locate the </head> line.
4Paste the AiCM secure tag on the line directly above </head>, or install a head code extension and paste it there.
5Save the file and clear the Joomla cache.
Where this lives
Active template's index.php, or a head code extension
Permission needed
Super User access
How to verify
Open the public site, view source, and confirm the secure tag is in the <head>.
Drupal
Developer setup
Drupal can load the secure tag through the active theme's html.html.twig template or through a small custom module that attaches a html_head item.
1Sign in to Drupal as an administrator.
2Open the active theme's html.html.twig file.
3Paste the AiCM secure tag inside the <head> block.
4Clear the Drupal cache from Configuration, Performance.
Where this lives
Theme's html.html.twig, or a small custom module
Permission needed
Administrator role with theme or module access
How to verify
Open any public page, view source, and confirm the secure tag is in the <head>.
Tilda
Built in
Tilda exposes a head field at the project level so the secure tag is added to each page in one place.
1Open the Tilda project.
2Go to Site Settings, then More.
3Paste the AiCM secure tag into HTML code for the HEAD area.
4Save changes and republish all pages.
Where this lives
Site Settings, More, HTML code for the HEAD
Permission needed
Project owner on a Personal plan or higher
How to verify
Open the published site, view source, and confirm the secure tag is in the <head>.
Duda
Built in
Duda offers a site wide header HTML field. The secure tag is published with the next site publish.
1Open the Duda editor for the site.
2Open Site, then Header HTML.
3Paste the AiCM secure tag.
4Save changes and republish the site.
Where this lives
Site wide Header HTML
Permission needed
Site owner with edit access
How to verify
Open the live site, view source, and confirm the secure tag is in the <head>.
Adobe Experience Manager
Developer setup
AEM loads page heads from the page template. The standard pattern is to add the secure tag through the customheaderlibs.html include used by the template.
1Open the relevant page template in CRXDE or your project repository.
2Locate customheaderlibs.html for the template.
3Add the AiCM secure tag to the file.
4Build and deploy the package, or push the change through your normal release process.
5Activate the affected pages so the change is live.
Where this lives
Page template head include, customheaderlibs.html
Permission needed
Developer with template and component edit rights
How to verify
Open a published page, view source, and confirm the secure tag is in the <head>.
SharePoint
Developer setup
SharePoint behavior depends on whether the site is modern or classic. Modern sites use SPFx application customizers. Classic sites accept the secure tag in the master page.
1For modern SharePoint, deploy an SPFx application customizer that adds the AiCM secure tag to the page head.
2For classic SharePoint, open the active master page in SharePoint Designer.
3Add the AiCM secure tag inside the <head> block.
4Check in and publish the master page.
Where this lives
Modern: tenant or site script. Classic: master page.
Permission needed
Site Collection Administrator or tenant administrator
How to verify
Open the site, view source, and confirm the secure tag is in the <head>.
Kentico
In test
Detailed Kentico instructions are being finalized. The secure tag is added to the master page or layout used by your site so it is present in the head of each rendered page.
1Detailed step by step instructions for Kentico Xperience are being prepared.
2In the meantime, contact the team and we will walk through the right approach for your version of Kentico.
Where this lives
Master page or layout head section
Permission needed
Global administrator with development access
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
Sitecore
In test
Detailed Sitecore instructions are being finalized. The secure tag is typically added through a head rendering or layout that is shared across the site.
1Detailed step by step instructions for Sitecore are being prepared.
2In the meantime, contact the team and we will help your developers slot the secure tag into the right rendering for your solution.
Where this lives
Layout or rendering head include
Permission needed
Sitecore administrator with template and layout access
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
Umbraco
In test
Detailed Umbraco instructions are being finalized. The secure tag belongs in the master template that wraps each page so it appears in the head everywhere.
1Detailed step by step instructions for Umbraco are being prepared.
2In the meantime, contact the team and we will help you place the secure tag correctly in your master template.
Where this lives
Master template _Layout.cshtml head section
Permission needed
Umbraco administrator with template edit access
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
Finalsite
Coming soon
Detailed Finalsite instructions are being finalized. Finalsite exposes a custom head code area at the site level so the secure tag is added in one place.
1Detailed step by step instructions for Finalsite Composer are being prepared.
2In the meantime, contact the team and we will walk through the right field for your edition.
Where this lives
Site Manager, Custom code, Head HTML
Permission needed
Site administrator in Composer / Site Manager
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
CivicPlus
In test
Detailed CivicPlus instructions are being finalized. CivicPlus government sites typically require the secure tag to be added through a site wide field, in some cases via a CivicPlus support request.
1Detailed step by step instructions for CivicPlus platforms are being prepared.
2In the meantime, contact the team and we will coordinate with CivicPlus support so the secure tag is added correctly.
Where this lives
Site wide head code field, raised through CivicPlus support
Permission needed
Site administrator, with CivicPlus support assistance
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
Jadu
Coming soon
Detailed Jadu instructions are being finalized. Jadu local government platforms expose a shared site template where the secure tag is added once and inherited across each page.
1Detailed step by step instructions for Jadu Continuum CMS and Jadu Central are being prepared.
2In the meantime, contact the team and we will coordinate with your Jadu administrator so the secure tag is added to the correct template.
Where this lives
Site wide template head, managed by Jadu administrators
Permission needed
Jadu administrator with template or design pack access
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
GOSS
In test
Detailed GOSS instructions are being finalized. GOSS iCM exposes a shared site template where the secure tag is added once and inherited across each page.
1Detailed step by step instructions for GOSS iCM are being prepared.
2In the meantime, contact the team and we will coordinate with your GOSS administrator so the secure tag is added to the correct template.
Where this lives
Site wide template head in GOSS iCM, managed by site administrators
Permission needed
GOSS iCM administrator with template access
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
CoreMedia
Coming soon
Detailed CoreMedia instructions are being finalized. CoreMedia Content Cloud uses shared page templates where the secure tag is added once and inherited across each page.
1Detailed step by step instructions for CoreMedia Content Cloud are being prepared.
2In the meantime, contact the team and we will coordinate with your CoreMedia developer so the secure tag is added to the correct template.
Where this lives
Shared page template head, managed in CoreMedia Studio
Permission needed
CoreMedia developer or template administrator
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
TYPO3
In test
Detailed TYPO3 instructions are being finalized. TYPO3 lets you add the secure tag through TypoScript page.headerData or a shared site set so it appears on each page.
1Detailed step by step instructions for TYPO3 are being prepared.
2In the meantime, contact the team and we will coordinate with your TYPO3 administrator so the secure tag is added to the correct template.
Where this lives
TypoScript page configuration or a shared site set, managed in the TYPO3 backend
Permission needed
TYPO3 administrator with template or site configuration access
How to verify
Open any page, view source, and confirm the secure tag is in the <head>.
Sanity
In build
Sanity is a headless content platform, so the secure tag is added in the front end that renders your Sanity content rather than in Sanity Studio itself. Detailed framework specific instructions are being prepared.
1Detailed step by step instructions for Sanity front ends are being prepared.
2In the meantime, contact the team and we will coordinate with your front end developer so the secure tag is added to the site <head> in your Next.js, Nuxt, Astro or other framework.
Where this lives
Front end framework <head> (Next.js, Nuxt, Astro, Remix or similar) consuming the Sanity content API
Permission needed
Front end developer with deploy access to the website that renders Sanity content
How to verify
Open any published page, view source, and confirm the secure tag is in the <head>.
Contentful
In build
Contentful is a headless content platform, so the secure tag is added in the front end that renders your Contentful content rather than in the Contentful web app itself. Detailed framework specific instructions are being prepared.
1Detailed step by step instructions for Contentful front ends are being prepared.
2In the meantime, contact the team and we will coordinate with your front end developer so the secure tag is added to the site <head> in your Next.js, Nuxt, Astro or other framework.
Where this lives
Front end framework <head> (Next.js, Nuxt, Astro, Remix or similar) consuming the Contentful Content Delivery API
Permission needed
Front end developer with deploy access to the website that renders Contentful content
How to verify
Open any published page, view source, and confirm the secure tag is in the <head>.
Liferay
In build
Liferay DXP serves pages through shared site and page templates. The secure tag is added once at the template or theme level so it appears in the <head> across each page. Detailed step by step instructions are being prepared.
1Detailed step by step instructions for Liferay DXP are being prepared.
2In the meantime, contact the team and we will coordinate with your Liferay administrator so the secure tag is added to the correct site template or theme.
Where this lives
Shared site or page template head, managed in Liferay DXP / Portal administration
Permission needed
Liferay administrator with site template or theme deployment access
How to verify
Open any published page, view source, and confirm the secure tag is in the <head>.
Modern Campus
In build
Modern Campus Omni CMS publishes pages from shared templates. The secure tag is added once at the template level so it appears in the <head> across each page on the site. Detailed step by step instructions are being prepared.
1Detailed step by step instructions for Modern Campus Omni CMS are being prepared.
2In the meantime, contact the team and we will coordinate with your Modern Campus administrator so the secure tag is added to the correct shared template and republished.
Where this lives
Shared page template head, managed in Modern Campus Omni CMS
Permission needed
Modern Campus Omni CMS administrator with template publishing rights
How to verify
Open any published page, view source, and confirm the secure tag is in the <head>.
Optimizely
In build
Optimizely CMS renders pages from a shared layout or master page. The secure tag is added once at the layout level so it appears in the <head> across each page. Detailed step by step instructions are being prepared.
1Detailed step by step instructions for Optimizely CMS are being prepared.
2In the meantime, contact the team and we will coordinate with your Optimizely developer so the secure tag is added to the correct shared layout and deployed.
Where this lives
Shared layout or master page head, managed in Optimizely CMS (formerly Episerver)
Permission needed
Optimizely CMS administrator or developer with template deployment access
How to verify
Open any published page, view source, and confirm the secure tag is in the <head>.
Verify the install
Network returns 200. Open DevTools, Network tab, reload, and confirm the request to the secure tag URL returns 200.
Console is clean. Look for the AiCM ready message and the absence of CSP or load errors.
Source shows the secure tag. View source on a public page and confirm the script appears inside the <head>.
If something looks wrong
404 on the secure tag URL: the snippet pasted does not match the one delivered during onboarding.
No console message: typically a CDN or page cache, an active ad blocker, or a Content Security Policy that blocks the host.
secure Tag is in the body, not the head: some CMS panels accept code in either position. Move it to the head field for site wide coverage.
Still need a hand?
If your CMS is not listed, or the head code field is locked behind a higher plan, get in touch and we will walk through the right path for your stack.
