🧭 Overview
When OTTO SEO is deployed through Google Tag Manager (GTM), the platform must detect the tag on your website before activation can proceed. If the tag check fails, your OTTO SEO project will remain inactive even though GTM shows the tag as published. This article covers what to check on your end and how to escalate if the issue persists.
⚙️ How OTTO SEO Tag Detection Works
After you connect your domain to an OTTO SEO project, the platform checks whether the OTTO SEO script is present and loading correctly on your site. When the tag is deployed via GTM rather than hardcoded into your HTML, GTM-specific configuration issues can prevent the script from being detected.
🔎 Common Causes of Tag Detection Failure via GTM
- GTM container not published: The tag exists in GTM as a draft but has never been submitted and published to the live container.
- Incorrect trigger configuration: The tag is set to fire on a specific page or event rather than on all pages, so the detection check may land on a page where the tag never fires.
- Content Security Policy (CSP) blocking: Your site's CSP headers restrict third-party scripts, preventing the OTTO SEO script from executing.
- Tag firing order or sequencing: Another tag or GTM rule is pausing or blocking the OTTO SEO tag from firing during the initial page load.
- Consent Mode / cookie banner interaction: If GTM is configured with Consent Mode, the OTTO SEO tag may be held back until user consent is granted, which can interfere with detection.
- Cached page being served: A CDN or server-side cache layer may serve a stale page that pre-dates the GTM container publish, so the tag is absent from the response.
✅ Steps to Try Before Escalating
- Confirm the GTM container is published. In your GTM workspace, verify that the container version containing the OTTO SEO tag has been submitted and is live. A draft tag will not fire on the live site.
- Check the trigger scope. Open the OTTO SEO tag in GTM and confirm the trigger is set to fire on all pages. If it is scoped to a specific URL or event only, update it to fire on all pages and republish the container.
- Use GTM's Preview mode. Load your homepage while GTM Preview is active and confirm the OTTO SEO tag is firing on the initial page view. If it is not firing, review your trigger settings and any tag blocking or sequencing rules.
- Check your Content Security Policy. Review your site's CSP headers to confirm that third-party scripts required by OTTO SEO are not being blocked. If they are, add the necessary domain to your allowlist.
- Clear your CDN or server cache. If your site uses a CDN or caching layer, purge the cache after publishing your GTM container so detection checks see the latest version of your pages.
- Disable Consent Mode temporarily for testing. If your GTM setup uses Consent Mode, check whether the OTTO SEO tag is configured to require consent before firing, and adjust accordingly.
📋 How to Escalate
If you have worked through all the steps above and the OTTO SEO tag is still not being detected, please reach out to our support team. To help us investigate as quickly as possible, have the following ready:
- Your OTTO SEO project name and the domain in question
- Your GTM container ID
- A description of which steps you have already tried
- Any error messages or console output you have observed
- Approximate date and time when the issue started
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.