🔍 Who This Article Is For
This guide is for customers who run a custom-coded website — built with Node.js, Next.js, or a similar framework and hosted on platforms like cPanel — who are seeing zero SEO scores for content and UX signals in Search Atlas after migrating away from a CMS-based platform such as GoHighLevel, WordPress, or Webflow.
Without a native CMS connector, Search Atlas cannot automatically pull or push content to your site. This article explains why scores drop to zero and outlines the general approaches available to restore full SEO visibility and content publishing.
⚠️ Why Your SEO Scores Are Showing Zero
Search Atlas calculates content and UX signal scores by reading published, crawlable content on your live website. When you migrate from a platform with a native connector (like GoHighLevel) to a custom-coded build, two things typically break:
- No CMS connector: Search Atlas can no longer sync or verify published content automatically.
- OTTO Pixel may be missing or misconfigured: Without the tracking pixel installed on your new build, OTTO SEO cannot collect UX signals such as engagement and on-page behaviour.
Both issues must be resolved independently. The sections below cover what to prepare and what to communicate to the support team so your account can be properly configured.
✅ Step 1 — Reinstall the OTTO Pixel on Your Custom Build
Even on a custom Node.js or Next.js site, the OTTO Pixel can be installed manually by adding the pixel script to your site's global HTML template or layout file. Because the exact navigation path to retrieve your pixel script may vary based on your account configuration, contact the support team to confirm the correct steps for your setup and to obtain your unique pixel snippet.
When you reach out, have the following ready:
- Your Search Atlas project name or domain
- The framework your site is built on (e.g., Next.js, Node.js with EJS)
- Whether you have access to edit your site's root layout or HTML template file
Once the pixel script is added to your site's <head> and deployed, UX signal collection will resume within 24–48 hours of real visitor traffic.
📝 Step 2 — Choose a Content Publishing Workflow
Because your site has no CMS, you need an alternative method to create, optimise, and publish content that Search Atlas can score. The right approach depends on your technical setup and goals. Contact the support team to identify which workflow is available for your account and how to get it configured correctly.
When reaching out, be prepared to share:
-
Your project name and the domain of the custom-coded site
-
The platform or framework the site is built on
-
A brief description of how content is currently added to the site (e.g., hardcoded HTML files, a temp
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.