Troubleshooting: Shopify, Wix & Webflow Connectors

🛠️ Webflow CMS Dynamic Fields and Template Variables

🔗 Mapping SEO Metadata to Webflow CMS Fields

🛠️ Loveable CMS Integration and Refunds

🔍 Why Loveable is unavailable Loveable is not currently listed as a supported CMS integration in Search Atlas. This means you cannot connect Loveable directly for publishing through the CMS options. 💡 Available workarounds You may be able to continue using your project by exporting it from Loveable and uploading the resulting ZIP or HTML files, where supported by your Search Atlas workflow. You can also connect a supported CMS if your website is available on another platform. Before choosing a workaround, confirm that your export includes the pages and assets you need. Export-based workflows may require additional setup and may not provide the same publishing experience as a direct CMS connection. 🚫 Cancel your subscription If Loveable support is essential to your workflow, you can request cancellation. Include the account details associated with your Search Atlas subscription and explain that the unavailable Loveable integration is the reason for your request. 💳 Request a refund Refund eligibility depends on your subscription and account circumstances. A refund is not automatic when an integration is unavailable, so request a review when you ask to cancel. The team can confirm the applicable options and any next steps. 💬 Contact the team 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.

🔧 Fix Shopify 410 Gone Error in Search Atlas

🔍 Overview If you access Search Atlas through Shopify and encounter a 410 Gone error, this is almost always caused by a conflicting browser cookie from a previous Search Atlas session — not a problem with your account or subscription. This article explains why it happens and how to fix it. ⚠️ What Is the 410 Gone Error? A 410 Gone error in Shopify means the browser cannot establish a valid session between Shopify and Search Atlas. It is caused by a conflicting browser cookie from a previous Search Atlas session. This typically happens when: - You have previously logged into Search Atlas directly at app.searchatlas.com in the same browser. - A leftover authentication cookie conflicts with the Shopify-initiated login flow. - The browser tries to use an old session token that is no longer valid. 🛠️ How to Fix the 410 Error Follow these steps to clear the conflict and restore access: 1. Clear your browser cookies and cache. Go to your browser settings, find the option to clear browsing data, select Cookies and other site data and Cached images and files, then confirm. For best results, clear data for All time. 2. Close all browser tabs that have Search Atlas or Shopify open. 3. Reopen your browser and go directly to your Shopify Admin. 4. Navigate to Apps and click on Search Atlas from your installed apps list. 5. The app should now load without the 410 error. If you prefer not to clear all cookies, you can instead try opening Search Atlas from Shopify in a private or incognito window, which starts with a clean cookie state. 💡 Pro Tip: Avoid Future Cookie Conflicts To prevent this issue from recurring, use separate browsers (or browser profiles) for your direct Search Atlas login and your Shopify Admin access. For example, use Chrome for Shopify and Firefox for direct access to app.searchatlas.com. This keeps session cookies isolated and prevents conflicts. 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. Reconnect the Search Atlas app from within Search Atlas: go to Settings → CMS Connectors, find your Shopify connection, and use the Edit, Reconnect or Disconnect options to refresh the authentication session. Your data and settings are stored in your Search Atlas account and will not be affected.

🔄 Backend Cache Flush and CMS Detection Refresh After Migration

Overview When you migrate a website between platforms — for example, from Wix to another CMS — Search Atlas may continue reading data from your previous environment. This can cause issues with on-page optimization deployment and GSC sitemap sync that appear unrelated to the migration itself. This article walks you through the steps to verify your OTTO pixel installation and restore accurate on-page optimization data after a platform migration. Why On-Page Optimization May Not Reflect Your New Platform After a CMS migration, Search Atlas may not immediately recognize your new platform environment. Until a fresh detection is triggered, on-page optimization scores and GSC sitemap sync may not reflect your current setup. This is a common occurrence after migrating platforms such as Wix. Step 1 — Verify Your OTTO Pixel Is Correctly Installed on the New Platform Before anything else, confirm that the OTTO pixel is present and correctly installed on your new platform. A missing or duplicated pixel is a frequent cause of detection failures after migration. 1. Open your website in a browser and use your browser's developer tools to search for the OTTO pixel script tag in your page source. 2. Confirm the pixel appears exactly once. If you migrated from a previous platform and the old pixel script was not fully removed, you may see two instances — remove any legacy pixel from the old platform before proceeding. 3. After confirming the pixel is installed correctly on the new platform, navigate to your OTTO setup within Search Atlas and check whether on-page optimization deployment is now registering accurately. Step 2 — Resubmit Your Sitemap in Google Search Console After a migration, your GSC sitemap sync may be pointing to an outdated sitemap or may not reflect your new platform's URL structure. To resolve GSC sitemap sync issues post-migration: 1. Log in to Google Search Console and navigate to Sitemaps under the relevant property. 2. Remove any outdated sitemap entries associated with your previous platform. 3. Submit your new sitemap URL generated by your current platform. 4. Return to Search Atlas and trigger a re-crawl or refresh of your project so that GSC data is pulled in from the updated sitemap. Step 3 — Escalate if Issues Persist After Pixel and Sitemap Verification If you have confirmed the OTTO pixel is correctly installed and your sitemap has been resubmitted but on-page optimization or GSC sync still appear incorrect, a backend reset may be required. When escalating, have the following ready: - Your website project URL - The platforms involved in your migration (for example, migrated from Wix on [date]) - A description of the specific issue — for example, on-page optimization not deploying, or GSC sitemap sync not updating - Any error messages or incorrect readings you are seeing in Search Atlas 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.

🛠️ Fix a Disconnected Shopify Connector in Search Atlas

🔍 Overview After adding or updating a Shopify API token, your connector may still show a Disconnected status in Search Atlas. This is almost always caused by cached authentication data that prevents the platform from recognising your new token. Following the steps below will clear that cache and restore the connection. 🚀 Step-by-Step: Clear Cache and Reconnect 1. Locate your Shopify connector. In Search Atlas, find your existing Shopify connector. Even if the status shows Disconnected, do not add a duplicate connector — work with the existing one. 2. Remove the existing connector. Disconnect or remove the existing Shopify connector. This clears the cached authentication session tied to the old token. 3. Hard-refresh your browser. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to clear any locally cached page data. 4. Re-add the Shopify connector. Add the Shopify connector again from scratch. 5. Enter your token. Paste your Shopify API token into the connector setup. 6. Save and verify. Save the new connector and wait for the status to update to Connected. 💡 Why This Happens When a Shopify API token is replaced or expires, cached authentication data can conflict with the new credentials, causing the connector to appear disconnected even though the token itself is valid. Removing the connector and re-adding it clears this cached data so a fresh authentication handshake can occur. ✅ Confirming the Connection is Working Once the status shows Connected, verify the integration is fully functional by checking that any reports or features relying on Shopify data are loading correctly without errors. 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.

🛠️ Wix Integration: Image Metadata, Titles & Alt-Text Defects

🔍 Overview of the Issue A confirmed defect affects Search Atlas customers who publish content directly to Wix sites via the platform integration. The three specific symptoms are: - Image metadata loss: Image file names, captions, or embedded metadata are stripped or reset during publication. - Title mutation: Page or post titles are altered from the intended value after being pushed to Wix. - Alt-text rewrite: Custom alt-text applied inside Search Atlas is overwritten or removed when content lands in Wix. These issues have been confirmed through internal reproduction testing and are being actively tracked by our engineering team. 📋 What Has Been Done So Far This defect has been escalated internally and is being investigated at the engineering level. Here is the current status: - The issue has been reproduced internally using controlled publication tests that mirror real customer publishing conditions. - Engineering has access to the evidence gathered from escalated customer conversations, including affected site configurations and publishing sequences. - A cold-load test (simulating a fresh Wix page load post-publish) and a controlled publication test are being used as the benchmark for confirming a fix. - The case will not be closed until both independent cold-load and controlled publication tests confirm full resolution. ⚠️ What This Means for Your Workflow Until a fix is confirmed and released, we recommend the following workarounds to protect your content quality when publishing to Wix: 1. Do not rely on Search Atlas to push final alt-text to Wix. After publishing, log in to your Wix editor and manually verify and re-enter alt-text for all images. 2. Copy your intended page title before publishing. After the post goes live on Wix, confirm the title matches your original and correct it manually if needed. 3. Check image metadata in Wix directly. Navigate to each published image in your Wix Media Manager and confirm that file names and any required metadata fields are intact. 4. Keep a local record of your intended titles, alt-text, and image metadata before each publishing session so you have a reference if corrections are needed. 🚀 How to Request an Active Ticket Reference or Case Status If you were previously involved in an escalation related to this defect, or if you need a current engineering ticket reference and case owner status, our support team can retrieve this for you in real time. To request this information: 1. Open the Search Atlas platform and locate the chat widget in the bottom-right corner. 2. Type human teammate to be connected with a member of our support team. 3. Share your site URL and a brief description of the symptom you experienced (title mutation, alt-text rewrite, or image metadata loss). 4. Request the active ticket reference number and the current engineering case owner and status. Our team will confirm whether your previous case is linked to the tracked defect and provide you with the latest status update. 📊 How We Will Communicate a Fix When engineering confirms that the fix has passed both the cold-load test and the controlled publication test, we will: - Update this article with a confirmed resolution date and any steps you may need to take on your end. - Proactively notify customers who were part of escalated conversations related to this defect. You do not need to reopen a ticket or submit a new report if you have already been involved in an escalation — your case remains open and linked to the active engineering investigation. 💡 Tips While You Wait for the Fix - Use the Onpage Audit tool (Left sidebar → Content → Onpage Audit) to audit your published pages and catch any metadata or title discrepancies after each Wix publication. - If you are generating content before publishing, use Content Genius (Left sidebar → Content → Content Genius) and save a copy of all title and alt-text fields locally before pushing to Wix. - Avoid bulk-publishing to Wix until the fix is confirmed, as the defect has a higher chance of appearing when multiple pages are pushed in a single session. 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.

🔌 Fix Shopify CMS Connector Authentication Failures

🔍 Overview The Search Atlas Shopify CMS Connector links your live Shopify store to the platform so you can publish and manage SEO content directly. Authentication failures prevent this connection from forming. This article explains what to expect when authentication fails and how to prepare your case for our engineering team to investigate. ⚠️ About Shopify CMS Connector Authentication Failures When the Shopify CMS Connector fails to authenticate, the connection between Search Atlas and your Shopify store cannot be established. This type of failure occurs at the integration level and typically requires backend investigation to resolve. The exact cause can vary and must be confirmed by our team after reviewing your specific case. 📋 What to Have Ready When You Escalate Because Shopify CMS Connector authentication failures require investigation at the integration level, please have the following information ready when you contact support: - Your Shopify store domain (for example, yourstore.myshopify.com) - The exact error message you see when the authentication fails - The date and time when the failure first occurred and any subsequent attempts - A description of the steps you took when the error appeared (for example, whether you were connecting for the first time or reconnecting an existing store) 📋 If Your Case Has Already Been Escalated If you have already reported this issue and were told it is under review, our engineering team is investigating the authentication failure at the integration level. No additional action is required from you at this stage. You will be updated as soon as a resolution or next step is available. 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.

🔗 Connect HubSpot CMS to OTTO SEO

🌐 Overview Search Atlas integrates with HubSpot CMS through OTTO SEO, allowing you to push SEO recommendations — including page titles and meta descriptions — directly to your live pages. Once connected, you eliminate manual copy/paste workflows and let OTTO handle implementation automatically through its CMS integration and direct content deployment capability. ⚙️ How the Integration Works OTTO SEO connects to your HubSpot CMS via a site activation. After activation, OTTO audits your pages and surfaces recommendations that can be deployed directly to HubSpot without manual editing inside HubSpot itself. The exact deployment options and controls available to you will depend on your account configuration — our support team can walk you through the specific steps for your setup. 🚀 Getting Started — Activate OTTO SEO for Your HubSpot Site To begin using OTTO's CMS integration with HubSpot, you will need to activate OTTO for your HubSpot site from within the Search Atlas platform. During activation, you will be prompted to connect your HubSpot domain and grant the necessary permissions so OTTO can read and write page metadata. If your HubSpot site does not appear as an available property during this step, you will need to connect your HubSpot domain first before proceeding. Once activation is complete, OTTO will crawl your site and generate SEO recommendations. The time this takes varies depending on the size of your site. 🛠️ Deploying SEO Recommendations to HubSpot After activation, OTTO surfaces SEO recommendations — such as page title rewrites and meta description updates — that can be deployed directly to your HubSpot CMS. You can choose to deploy recommendations individually or in bulk, depending on how much control you want over the process. A controlled review option is available if you prefer to approve changes before they go live rather than having them applied automatically. Because the exact names of buttons, tabs, and settings in OTTO may vary or be updated, we recommend the following approach if you encounter difficulty locating a specific control: 1. Log in to Search Atlas and navigate to the OTTO SEO section of the platform. 2. Locate your activated HubSpot site within OTTO. 3. Look for deployment or recommendation controls associated with that site — these will allow you to review and push changes directly to HubSpot. 4. If you cannot find a specific setting or the integration does not behave as expected, contact our support team with your project name and a description of what you are trying to do, so we can provide exact, up-to-date guidance for your account. 🛟 When to Contact Support If you are unable to locate the HubSpot CMS integration options, your site is not appearing after activation, or recommendations are not deploying as expected, our team can assist. Please have the following ready when you reach out: - Your Search Atlas project or site name - The HubSpot domain you are trying to connect - A description of the step where you are getting stuck or the exact error message you see 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.

🐦 Fix Twitter Card Metadata and Choose Your CMS

🔍 Overview Two questions come up frequently together: how to fix broken Twitter Card metadata, and which CMS platform—Shopify or WordPress—is the better home for your articles when using Search Atlas. This guide answers both clearly so you can take action right away. 🐦 What Is Twitter Card Metadata and Why Does It Break? Twitter Cards control how your content appears when shared on Twitter (now X). When the metadata is missing or misconfigured, your shared links show as plain text instead of rich previews with images, titles, and descriptions. This hurts click-through rates and brand credibility. The most common causes of broken Twitter Card metadata are: - Missing twitter:card tag — This is the required base tag. Without it, no Twitter Card will render. - Missing or incorrect twitter:title and twitter:description tags — Twitter falls back to Open Graph tags if these are absent, but explicit tags are always more reliable. - Missing twitter:image tag — No image tag means no visual preview. The image must be publicly accessible and at least 120×120 px (recommended: 1200×628 px for summary_large_image cards). - Wrong card type declared — Using summary when you intend summary_large_image results in a small, unimpressive preview. - Robots meta tag blocking crawlers — If your page has noindex or blocks Twitterbot in robots.txt, the card will not load. - Cached old metadata — Twitter caches card data aggressively. Even after a fix, old data may persist until the cache expires or you force a refresh. 🛠️ How to Fix Twitter Card Metadata 1. Audit your existing tags. Use the Twitter Card Validator (or any meta tag inspector) to see exactly which tags are present or missing on your page. 2. Add the required tags to your page's <head> section. At minimum you need: twitter:card, twitter:title, twitter:description, and twitter:image. 3. Choose the right card type. Use summary_large_image for blog posts and articles—it produces the largest, most engaging preview. 4. Verify your image is accessible. Paste the image URL directly into a browser tab. If it does not load, Twitter cannot fetch it either. 5. Check your robots settings. Confirm Twitterbot is not blocked in robots.txt and that the page is indexable. 6. Clear Twitter's cache. Re-enter your URL in the Twitter Card Validator and click Preview Card. This forces Twitter to re-crawl the page and update its cache. 7. Re-test after 15–30 minutes. Allow time for propagation, then share the URL in a tweet draft to confirm the rich preview appears correctly. 📊 Shopify vs. WordPress — Which Should You Use for Publishing Articles? If your goal is content marketing and SEO, the platform you choose has a meaningful impact on how much control you have over your metadata, technical SEO, and publishing workflow. Shopify is an excellent e-commerce platform, but its blogging capabilities are limited. Key constraints include: - Restricted access to the <head> section without theme code edits, making metadata customisation harder. - Limited SEO plugin options compared to WordPress. - Less granular control over URL structures, schema markup, and advanced on-page SEO settings. - Twitter Card and Open Graph tags often require theme-level modifications that can break during theme updates. WordPress is built for content publishing and offers significantly more flexibility for SEO: - Full control over <head> metadata via plugins like Yoast SEO or Rank Math, making Twitter Card fixes straightforward. - Extensive plugin ecosystem for schema, redirects, sitemaps, and more. - Clean, customisable URL structures that support SEO best practices. - Easier integration with third-party SEO tools. 🔄 Search Atlas CMS SYNC — The Deciding Factor Search Atlas offers CMS SYNC directly with WordPress. This means you can research, optimise, and publish content from inside the Search Atlas platform straight to your WordPress site — no copy-pasting, no formatting loss, no workflow friction. CMS SYNC lets you: - Push fully optimised articles from Search Atlas to WordPress in one click. - Maintain consistent metadata, headings, and on-page SEO elements automatically. - Save significant time by managing your entire content workflow from a single dashboard. Because CMS SYNC is built for WordPress and not Shopify, WordPress is the strongly recommended platform for publishing SEO articles when you are using Search Atlas. Shopify remains a great choice for your storefront, but your blog and content hub will perform better—and integrate more smoothly—when hosted on WordPress. ✅ Quick-Reference Checklist - Twitter Card fix: Add twitter:card, twitter:title, twitter:description, twitter:image to every article page. - Card type: Use summary_large_image for articles. - Image size: 1200×628 px, publicly accessible URL. - Cache reset: Use the Twitter Card Validator after every fix. - CMS choice: Use WordPress for content publishing to take full advantage of Search Atlas CMS SYNC. 💬 Need More Help? 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.

💳 Fix Double Billing and Shopify Publishing Failures

🔍 Overview Some customers have experienced two separate charges within a short period — one through Shopify and one directly to a credit card — alongside content quota being consumed unexpectedly and generated articles or schemas failing to publish to their Shopify blog. This article explains why these issues occur, what has been fixed, and the exact steps to take to get your account and billing corrected. 💳 Why You May Have Been Charged Twice A technical issue caused Shopify app purchases to charge merchants successfully but fail to provision access inside Search Atlas. Because the system did not recognise the Shopify payment as complete, some accounts were charged a second time through a direct credit card transaction to restore access. This happened because: - The Shopify billing confirmation was routed to an internal system address instead of completing the provisioning step. - Subscription cancellations triggered from within Search Atlas could not reach Shopify subscriptions, leaving orphaned charges that were not reconciled automatically. - Webhook events for unrecognised or orphaned Shopify subscriptions were ignored rather than flagged, so duplicate charges went undetected. These routing and reconciliation issues have since been resolved. If you were affected, your account is eligible for a full refund of the duplicate charge. 📊 Why Your Quota Was Consumed Again When access provisioning failed after a Shopify charge, some accounts were reset or re-onboarded when the second charge processed. This reset caused previously used quota to be counted again as new usage during the republishing process, effectively double-counting consumption. If you republished content specifically to regain access or to test whether your account was working correctly after a billing problem, that quota usage is considered part of the same billing incident and is also eligible for reversal. Document which content was republished and flag it when you contact support. 🛠️ Why Articles and Schemas Won't Post to Your Shopify Blog Publishing failures to Shopify blogs are connected to the same provisioning problem. If your subscription was not correctly recognised by Search Atlas after a Shopify charge, the platform's connection to your Shopify store may have been left in an incomplete state. This can cause: - Generated articles to queue but never post to your Shopify blog. - Schema markup to save inside Search Atlas but not appear on your live store pages. - Repeated publish attempts to consume quota without successfully delivering content. Re-authenticating your Shopify connection after your subscription is correctly provisioned resolves most publishing failures. ✅ Steps to Resolve Your Issue 1. Gather your billing evidence. Collect screenshots or statements showing both charges — the Shopify transaction and the direct card charge — including dates and amounts. 2. Note any republished content. List the articles or schemas you republished during the affected period so quota reversals can be applied accurately. 3. Contact support via live chat. 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. Share your billing evidence and content list directly in the chat. 4. Confirm your subscription status. Ask the support agent to verify that your Shopify subscription is correctly provisioned and that no duplicate or orphaned subscription remains active on your account. 5. Re-authenticate your Shopify connection. Once your subscription is confirmed, go to Avatar (top-right corner) → Settings → CMS Connectors → [Your CMS] → Shopify → Reconnect and reconnect your store. This refreshes the publishing connection and resolves most post-to-blog failures. 6. Test publishing. After reconnecting, attempt to publish one article or schema to your Shopify blog to confirm the integration is working before republishing in bulk. 💡 What to Expect After Contacting Support - Duplicate charge refund: The refund for the duplicate charge will be processed back to the original payment method. Timing depends on your bank or Shopify's billing cycle, but you will receive confirmation once the refund is initiated. - Quota reversal: Any quota consumed as a direct result of the billing incident — including republishing attempts made to restore access — will be reviewed and credited back to your account. - Subscription clean-up: Support will ensure only one active subscription exists on your account and that it is correctly linked to your access level. 🚀 Preventing This in the Future - If you ever lose access to Search Atlas after a Shopify payment, contact support before making any additional payment or republishing content. - Check your Avatar (top-right corner) → Billing page (Plans & Top-ups) to confirm your subscription status before assuming a charge has failed. - After any reconnection or subscription change, always test the Shopify publishing integration with a single piece of content before running bulk publish jobs. 🆘 Still Need Help? 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.

💳 Fix Duplicate Shopify and Search Atlas Billing

🔍 Why Am I Being Billed Twice? Some customers who installed Search Atlas through the Shopify App Store and later signed up directly on the Search Atlas platform end up with two active billing sources: - Shopify billing — charged automatically through your Shopify account when you installed the app. - Search Atlas direct billing — charged to your credit card when you subscribed on the Search Atlas website. This can happen when the Shopify app installation does not automatically link to your existing Search Atlas account, or when a plan is activated on both sides without the first being cancelled. The result is two charges for the same subscription period. ⚠️ Is This a Known Issue? Yes. Our engineering team has identified and resolved several root causes of duplicate billing, including cases where Shopify app purchases were charged but not correctly provisioned, and where the cancellation flow did not properly close the Shopify subscription. If you have been affected, you are not alone and we will make it right. ✅ Steps to Stop Being Billed Twice Follow these steps in order to prevent further duplicate charges: 1. Identify your preferred billing method. Decide whether you want to be billed through Shopify or directly through Search Atlas. Most customers prefer direct Search Atlas billing for easier plan management. 2. Cancel the Shopify subscription. In your Shopify admin panel, go to Apps, find Search Atlas, and uninstall or cancel the subscription. This stops future Shopify charges. If you encounter any issues cancelling through Shopify, contact our support team (see below) so we can cancel it on our end. 3. Confirm your Search Atlas plan is active. Log in to your Search Atlas account and verify your subscription is active and your plan features are accessible. Your direct billing subscription should remain untouched. 4. Monitor your next billing cycle. After cancelling the Shopify subscription, check that only one charge appears on your next statement — either from Shopify (if you kept that method) or from Search Atlas directly. 💰 How to Request a Refund for the Duplicate Charge If you were charged by both Shopify and Search Atlas for the same period, you are entitled to a refund or credit for the duplicate payment. Here is what to do: 1. Gather your billing evidence. Collect the charge dates and amounts from both your Shopify admin panel and your Search Atlas billing history. Screenshots or transaction IDs are helpful. 2. Contact our support team immediately. Our team can review your account, confirm the duplicate, and process a refund or apply a credit to your Search Atlas account. Refunds for Shopify charges are processed back to the original payment method on file with Shopify. 3. Allow processing time. Refunds to credit or debit cards typically take 5–10 business days to appear, depending on your bank or card provider. 📋 What Information to Have Ready To help our team resolve your case as quickly as possible, please have the following details on hand before reaching out: - Your Search Atlas account email address - The Shopify store URL (e.g. yourstore.myshopify.com) - The dates and amounts of both charges - Whether you prefer a refund to your original payment method or a credit applied to your Search Atlas account 🛡️ Preventing This From Happening Again Once the duplicate billing is resolved, keep these tips in mind: - Only subscribe through one billing channel — either Shopify or Search Atlas directly, never both. - If you install the Search Atlas Shopify app in the future, check your Search Atlas account to confirm no second plan has been created before completing the app setup. - Review your billing statements each month to catch any unexpected charges early. 🤝 Need Help From Our Team? 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.

Fix Shopify Connector Error 400 Fast

What Is Error 400 on the Shopify Connector? A 400 Bad Request error on the Shopify connector means the connection request was rejected and could not be processed. This error has been observed when attempting to add a co-worker to a connected Shopify store inside Search Atlas. Because this error requires investigation on the backend, it cannot be resolved through self-serve steps alone — it needs to be escalated to the Search Atlas technical support team. What to Expect Once you report the issue, the technical team will investigate the connector configuration on the backend and work to resolve the error. You do not need to disconnect or reconnect your Shopify store, and you should avoid making changes to your connector settings while the investigation is in progress, as this may complicate the troubleshooting process. What to Have Ready Before Escalating To help the technical team resolve your issue as quickly as possible, please gather the following information before reaching out: - Your Search Atlas account email address - The name of the Shopify store affected by the error - The email address of the co-worker you were attempting to add when the error occurred - The exact error message displayed (a screenshot is ideal) - The date and approximate time the error first occurred 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.

📘 Shopify CMS Connector Status in Search Atlas

The Shopify CMS connector in Search Atlas previously had a known limitation caused by a change Shopify made to how API tokens are generated. That issue has since been resolved: the connector now supports an automated authentication flow, and the manual workaround described in earlier versions of this article is no longer required. This article explains what changed, how the connector authenticates today, and how to set it up. 🧠 What Changed on Shopify's Side Shopify updated its requirements for generating API access. For a period, this meant that obtaining a usable API token required manually building a cURL request, which required technical/programming knowledge and was not a simple UI-based process. ⚙️ How the Connector Authenticates Today The Shopify CMS connector now supports two authentication methods: - Client Credentials (current, recommended): an automated OAuth flow. You create a custom app in the Shopify Partner or Dev Dashboard, then provide the Client ID and Client Secret to Search Atlas. Search Atlas handles the token exchange automatically — no manual cURL request needed. - Access Token (legacy): the older admin API token still works if you already have one configured. 🛠️ Setting Up the Shopify Connector 1. In Shopify, create a custom app in your Partner or Dev Dashboard and copy the Client ID and Client Secret. 2. In Search Atlas, click your avatar in the top-right and go to Settings → CMS Connectors tab, then choose Add Connector → Shopify. 3. Select Client Credentials as the authentication method. 4. Enter the Client ID, Client Secret, and your shop domain, then save. ❓ FAQs Is the Shopify CMS connector still broken? No. The connector now supports an automated authentication flow, and the manual token workaround is no longer needed. Do I need programming knowledge to set it up now? No. Client Credentials setup only requires copying a Client ID and Client Secret from Shopify into Search Atlas. I already set up the connector using the old access token — do I need to redo it? No, the legacy access token method still works. Switching to Client Credentials is recommended but not required. 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.

📝 Post Blogs to Your Webflow Site from Search Atlas

🌐 Webflow vs. Website Studio: Know the Difference Search Atlas supports two distinct publishing workflows. It is important to identify which one applies to your site before you begin. - Native Webflow sites — Sites built and hosted directly on Webflow (for example, aidquest.com). Content is managed inside the Webflow CMS and published through the Webflow editor or API. - Website Studio sites — Sites built using Search Atlas's own Website Studio builder. These use a one-click deployment workflow managed entirely within Search Atlas. This workflow does not apply to native Webflow sites. If your site was created on Webflow and you are simply using Search Atlas to generate content, follow the steps in this article. Do not use the Website Studio deployment instructions, as they are unrelated to your setup. ✅ Step 1: Ensure Your Webflow Site Has a Blog Collection Set Up Before you can publish any blog posts, your Webflow site must have a CMS Collection configured for blog content. If you have not done this yet, set one up inside your Webflow account by following Webflow's official documentation. You will need a collection with fields for your post content, and a collection page template so that each post has a live URL on your site. You only need to complete this setup once. Once the collection exists, you can add new posts at any time without repeating this process. ✍️ Step 2: Generate Your Blog Content in Search Atlas Use the content generation tools in Search Atlas to create your blog article. Once your article is complete, review and finalise all edits directly within Search Atlas before transferring the content to Webflow. 🔁 Step 3: Transfer Content to Webflow CMS Search Atlas does not currently offer a direct one-click publish integration with native Webflow CMS collections. Once your content is ready in Search Atlas, you will need to copy it and paste it into the appropriate fields within your Webflow CMS collection item, then publish from within Webflow. If you are unsure how to add items to your Webflow CMS collection, refer to Webflow's official help documentation for guidance specific to your site setup. 📌 Need Help With This Workflow? Because the exact steps for connecting Search Atlas content to a native Webflow site can vary depending on your Webflow setup, our support team can help you identify the right approach for your specific configuration. Please have the following ready when you reach out: - Your Webflow site URL - A description of how your blog collection is currently structured in Webflow (or whether one exists yet) - The specific step or action where you are getting stuck 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.

🛠️ Fix Shopify Mobile Menu After Script Install

🔍 What Is Happening and Why When you add the Search Atlas tracking script directly to your Shopify theme's theme.liquid file, it can interfere with how Shopify loads JavaScript for interactive elements like the mobile menu. Instead of rendering as a collapsible menu, the navigation may appear as plain, unstyled text. This happens because script placement affects the order in which the browser parses and executes JavaScript on the page. ⚠️ Before You Begin Always back up your theme before editing any liquid files. In your Shopify Admin, go to Online Store → Themes → Actions → Duplicate to create a safe copy. This ensures you can restore your site instantly if anything goes wrong. ✅ Step-by-Step Fix 1. Log in to your Shopify Admin and navigate to Online Store → Themes. 2. Next to your live theme, click Actions → Edit Code. 3. In the file list on the left, open Layout → theme.liquid. 4. Locate the Search Atlas script you previously added. It will look similar to a <script> tag containing your unique tracking ID. 5. Cut the script tag from its current position. 6. Scroll to the very bottom of the file and paste the script immediately before the closing </body> tag. Placing the script here ensures all page elements — including your mobile menu JavaScript — load fully before the tracking script runs. 7. Click Save. 8. Open your storefront on a mobile device or use your browser's mobile preview mode to confirm the menu is working correctly. 💡 Why Script Placement Matters Shopify themes rely on JavaScript to power dynamic components like mobile menus, drawers, and sliders. When an external script is placed inside the <head> tag or early in the <body>, it can block or conflict with the theme's own scripts as they load. Placing third-party scripts just before the closing </body> tag is a best practice that prevents these conflicts and keeps your store's functionality intact. 🚫 Common Mistakes to Avoid - Do not place the script inside the <head> tag. This is the most common cause of mobile menu breakage. - Do not add the script mid-way through the <body>. This can still interrupt theme JavaScript depending on your theme structure. - Do not add the script to section or snippet files. The script should only appear once, in theme.liquid, before the closing </body> tag. - Do not skip the backup step. Editing live theme code without a duplicate is risky. 🔄 If the Menu Is Still Broken After Moving the Script If repositioning the script does not resolve the issue, the problem may be related to your specific Shopify theme's JavaScript architecture. Try the following additional steps: - Open your browser's developer tools (right-click → Inspect → Console) and check for any JavaScript errors that appear when the page loads. Share these error messages with support if needed. - Temporarily remove the Search Atlas script entirely, save, and test the mobile menu. If the menu works without the script, the script is confirmed as the source of the conflict. - Check whether your theme uses a defer or async attribute on its own script tags. If so, try adding defer to the Search Atlas script tag as well: <script defer src="...">``</script>. 📋 Quick Reference — Correct Script Placement - Correct location: Immediately before </body> in theme.liquid - Incorrect location: Inside <head>, at the top of <body>, or inside any section or snippet file - One instance only: The script should appear exactly once across your theme 💬 Need More Help? 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.

🛠️ Connect Shopify via Cloudflare Worker to Search Atlas

🔍 Overview If your Shopify store uses Cloudflare as a proxy (for example, a custom domain pointed through Cloudflare), you cannot install Search Atlas using the standard Shopify app method alone. Instead, you need to deploy a Cloudflare Worker that intercepts requests and injects the Search Atlas script before pages are served to visitors. This guide walks you through the full setup. ⚙️ How It Works When a visitor lands on your Shopify store, the request passes through Cloudflare before reaching Shopify's servers. A Cloudflare Worker sits in that path and can modify the HTML response — in this case, injecting the Search Atlas tracking and optimization script into every page automatically. This ensures Search Atlas receives accurate data and can serve optimized content without modifying your Shopify theme manually. ✅ Before You Begin Make sure you have the following ready before starting: - Access to your Cloudflare account with the zone for your Shopify domain - Your Search Atlas project created and your site added inside the Search Atlas platform - Your Search Atlas script snippet — available inside your project settings - A Cloudflare plan that supports Workers (the Free plan includes Workers) 🚀 Step 1 — Create a Cloudflare Worker 1. Log in to your Cloudflare dashboard. 2. Navigate to the Workers section of your account. 3. Create a new Worker and give it a recognizable name (for example, search-atlas-injector). 4. Save or deploy the Worker with a placeholder script — you will replace the script content in the next step. ✏️ Step 2 — Add the Worker Script Once your Worker is created, open its editor and replace the default script with logic that does the following: - Intercepts every incoming request to your Shopify domain. - Fetches the original HTML response from Shopify. - Injects your Search Atlas <script> tag (copied from your Search Atlas project settings) just before the closing </head> tag in the HTML. - Returns the modified HTML to the visitor with the original response headers preserved. Because the exact script depends on your specific Search Atlas project snippet and your Cloudflare Worker runtime version, our support team can provide you with a ready-to-paste Worker script tailored to your setup. To get it, please have the following ready when you reach out: - Your Shopify store domain (the custom domain routed through Cloudflare) - Your Search Atlas project name - Your Search Atlas script snippet (found in your project settings) - Your Cloudflare Workers plan (Free, Pro, etc.) 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.

🚀 Publish Generated Articles to Webflow CMS

🌐 Overview Search Atlas lets you publish AI-generated articles directly to your Webflow CMS without leaving the platform. This guide walks you through connecting your Webflow site and pushing finished content live in just a few steps. 🔗 Step 1: Connect Your Webflow Account Before you can publish, you need to link Search Atlas to your Webflow site. You only need to do this once. 1. From the top-right avatar (Account Menu), go to Settings and select Integrations. 2. Find the Webflow card and click Connect. 3. You will be redirected to Webflow. Log in and grant Search Atlas the requested permissions. 4. Select the Webflow site you want to publish to, then click Authorize. 5. You will be returned to Search Atlas. A green Connected status confirms the integration is active. ✍️ Step 2: Open Your Generated Article Once your Webflow account is connected, navigate to the article you want to publish. 1. Go to Content (What are we writing today?) in the left-hand navigation. 2. Locate your finished article in the article list and click its title to open the editor. 3. Review the content and make any final edits before publishing. 📤 Step 3: Publish to Webflow With your article open and ready, follow these steps to send it to your Webflow CMS. 1. Click the Publish button in the top-right corner of the editor. 2. From the publishing options, select Webflow. 3. Choose the Collection within Webflow where the article should be saved (for example, your Blog Posts collection). 4. Map the article fields — such as Title, Body, and Slug — to the corresponding fields in your Webflow collection. 5. Toggle Publish to Webflow on if you want the item to go live immediately, or leave it off to save it as a draft in Webflow. 6. Click Confirm to push the article. A success notification will confirm the article has been sent to your Webflow CMS. You can verify it by logging in to Webflow and checking the relevant collection. ⚠️ Common Issues and Fixes - Connection error during authorisation: Make sure you are logged in to the correct Webflow account before clicking Connect. If the error persists, disconnect and reconnect the integration. - Collection not appearing in the dropdown: Ensure the Webflow site has at least one CMS Collection set up. Collections must exist in Webflow before they appear in Search Atlas. - Fields not mapping correctly: Field names in Search Atlas must match the field types in your Webflow collection. For example, the Body field requires a Rich Text field type in Webflow. - Article saved as draft instead of published: Check that the Publish to Webflow toggle was switched on before confirming. You can also publish the item manually inside the Webflow editor. 💡 Tips for a Smooth Workflow - Set up your Webflow CMS Collection structure before generating articles to ensure field mapping goes smoothly. - Use the Slug field to control the article URL in Webflow. Search Atlas auto-generates a slug from the title, but you can edit it before publishing. - If you manage multiple Webflow sites, you can switch the connected site at any time from the top-right avatar (Account Menu) > Settings > Integrations. 🛠️ Need More Help? 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.

🛠️ Troubleshooting an Unclickable CMS Publish Button

This article addresses a specific issue where the Publish button for a blog post appears visible but cannot be clicked. The steps below walk through common root causes and self-serve checks you can perform before escalating to support. 🔍 Common Causes of an Unclickable Publish Button - Required fields are incomplete: The CMS may block publishing if mandatory fields (such as title, meta description, featured image, or slug) are empty or contain invalid characters. - Content is still processing: If content is still being generated or saved, the publish button may remain locked until that process completes. - Unsaved changes: Edits that have not been saved can cause the publish action to be disabled. - Insufficient role permissions: Your account role may only allow drafting, not publishing. An Admin may need to update your permissions. - Stale browser session: An expired session or cached state can freeze interactive elements including the publish button. 🛠️ Steps to Try 1. Check for validation errors. Scroll through the entire blog post editor and look for any fields highlighted in red or marked with a warning. Fill in all required fields — commonly title, URL slug, and meta description — before attempting to publish again. 2. Wait for any active processing to finish. If content is still being generated or saved, wait until all activity has fully completed before clicking Publish. 3. Save the draft before publishing. Use the save option available in the editor before clicking Publish. This can clear any unsaved-state lock. 4. Check your account permissions. Confirm with your workspace Admin that your account role includes publishing rights. If your role is restricted to drafting only, ask an Admin to update your permissions. 5. Refresh your session. Log out of the platform, clear your browser cache and cookies for the site, then log back in and reopen the post. 6. Try a different browser or an incognito window. Open the same post in a second browser or an incognito tab and attempt to publish. This isolates whether the issue is browser-specific. 7. If the button remains unclickable after all of the above steps, escalate to support. When contacting the team, please have the following ready: the name of the project or blog post affected, the exact URL of the editor page, a description of any error messages or visual indicators you see, and the approximate time the issue began. This information will help the team investigate quickly. 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.

🛠️ Escalating Wix Integration Defects to Engineering

🔍 Overview If your Wix-connected site is experiencing persistent issues — such as SEO changes not publishing correctly — this article explains how to escalate your case to our engineering team and what to have ready when you do. ⚠️ Common Wix Integration Defects Some Wix-integrated sites may experience publishing issues where SEO changes applied within Search Atlas do not appear correctly on the live site. If you are seeing unexpected behavior with your Wix integration, our engineering team can investigate further. 📋 What to Have Ready When You Escalate To help our support team escalate your case to engineering as efficiently as possible, please have the following information available: - Your connected domain (e.g., yoursite.com) - A description of the specific publishing issue you are experiencing - The type of content affected (e.g., images, page titles, meta descriptions, alt text) - Whether the issue occurs consistently or intermittently - Approximate timestamps of when changes were applied and when the problem was noticed - Any screenshots or other evidence you are able to provide 🚀 How to Escalate Your Defect Case To open an engineering escalation for a Wix integration publishing defect, contact our support team directly. When you reach a teammate, clearly describe the publishing issue and provide your affected domain. Ask to have your case escalated to engineering and request confirmation of the following in writing: - Your active support ticket number or reference - Current status of the investigation - Expected next steps or resolution timeline Ask the teammate to keep your case open until the issue has been confirmed resolved on your site. 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.

🛠️ Fix Wix Integration Metadata and Content Defects

🔍 Overview of Known Wix Integration Defects Search Atlas integrates with Wix to help you publish and manage on-page SEO content directly from the platform. However, a small number of users have reported recurring defects when using this integration. This article explains the four known issue categories, what causes them, and the steps you should take to document and escalate them effectively. The four defect categories currently under investigation are: - Metadata not saving correctly — Meta descriptions or titles written in Search Atlas do not persist on the live Wix page after publication. - Title mutations — Page titles are altered unexpectedly during or after a publish action, resulting in unintended wording or formatting changes. - Alt text rewrites — Image alt text is overwritten with incorrect values, or reverts to a previous state after publishing. - Cold-load discrepancies — Changes appear saved inside the platform but do not reflect on a fresh browser load of the published Wix page. ⚠️ Why These Issues Happen Wix uses a proprietary API layer that controls how external tools write and read page content. Conflicts can occur when: - Wix's internal editor cache does not sync immediately with changes pushed via the API. - Wix applies its own formatting rules that override externally set title or alt text values. - A publish action triggers a Wix-side re-render that resets certain metadata fields to their previous state. These are integration-level defects that require engineering investigation on both the Search Atlas and Wix API sides. They cannot be resolved by changing settings within your account. 📋 How to Document Your Issue Before Escalating Strong documentation speeds up engineering investigations significantly. Before contacting support, please gather the following: 1. Affected page URLs — List every Wix page URL where the defect has occurred. 2. Screenshots or screen recordings — Capture the value as set inside Search Atlas, then the value shown on a fresh (incognito) browser load of the live page. 3. Timestamps — Note the exact date and time you published the change. 4. Steps to reproduce — Write out exactly what you did: which field you edited, what value you entered, and what you expected versus what appeared. 5. Previous ticket or case references — If you have earlier ticket numbers (for example, from a previous support conversation), include these so our team can retrieve prior evidence and link everything to a single active case. 🚀 How to Escalate to Engineering Once you have your documentation ready, use the following process to get your case escalated with a tracked reference: 1. 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. 2. Tell the teammate you are reporting a Wix integration defect and provide your documentation. 3. Ask the teammate to create or reopen an escalation ticket and confirm the active reference number with you in chat. 4. Request that the ticket be linked to any prior case references you have on file so evidence is consolidated. 5. Ask for a named owner and current status to be assigned to your case so you have a clear point of contact. Our support team will log the defect with engineering and set up the required cold-load and controlled publication tests to confirm whether the fix is working before the case is closed. ✅ What Happens After Escalation Once your case is active with engineering, the following process applies: - Engineering will review all linked evidence from previous and current tickets. - A cold-load test will be performed — this means loading the affected page on a fresh browser session with no cached data to verify whether published changes are visible. - A controlled publication test will be run — this involves making a defined change, publishing it, and independently verifying the result on the live Wix page. - The case will remain open until both tests confirm resolution. It will not be closed based solely on an internal fix being deployed. - You will receive a status update via the platform chat each time there is a meaningful change to your case. 🛡️ Temporary Workarounds While Awaiting a Fix These steps will not permanently resolve the defects, but they may reduce the impact while engineering works on a fix: - Verify changes immediately after publishing — Open the page in a private or incognito browser window right after publishing to check whether the correct values appear. - Re-publish if a revert is detected — If metadata or alt text has reverted, make the change again inside Search Atlas and publish a second time. Some users find the second publish attempt sticks. - Avoid bulk publishing — Publishing one page at a time appears to reduce the frequency of title mutations compared to publishing multiple pages simultaneously. - Keep a local record of intended values — Maintain a simple document with your intended titles, meta descriptions, and alt text so you can quickly re-enter them if a revert occurs. 💬 Need Help With Your Case? 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.

🔧 Fix Shopify Connector Disconnected After Token

🔍 Overview After adding a Shopify token in Search Atlas, you may notice the connector still shows a Disconnected status. In most cases, this is caused by stale browser cache or cookies interfering with the authentication handshake — not a problem with the token itself. Following the steps below resolves the issue for the majority of users without requiring support. ⚠️ Before You Begin Confirm the following before troubleshooting the browser: - Your Shopify token was generated with the correct permissions required for the integration. - The token was copied and pasted in full with no extra spaces. - You saved the connector settings after entering the token. If all three are confirmed and the connector still shows disconnected, proceed with the steps below. 🧹 Step 1: Clear Your Browser Cache and Cookies Cached authentication data can prevent Search Atlas from recognising a newly added token. Clearing your cache and cookies forces the browser to load a fresh session. 1. Open your browser settings and navigate to the option for clearing browsing data. 2. Set the time range to All time. 3. Check both Cached images and files and Cookies and other site data. 4. Clear the data and wait for the process to finish. 5. Close all browser tabs and reopen your browser completely. 🔄 Step 2: Reconnect the Shopify Connector After clearing the cache, log back in to Search Atlas and navigate to Avatar → Settings → CMS Connectors to access your Shopify connector settings. If the connector still shows Disconnected, try re-entering your Shopify token and saving again. Allow a moment for the status to update before refreshing the page. 🕵️ Step 3: Try a Different Browser or Incognito Window If the connector still shows disconnected after clearing cache, test in a private or incognito window, or switch to a different browser entirely. This rules out browser extensions, conflicting cookies, or persistent cache issues. Repeat Step 2 inside the new window. If the connection succeeds here, a browser extension in your main browser is likely the cause. Try disabling extensions one by one to identify the conflict. 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.

🔌 Shopify Pixel Disconnection After Version Updates

🔍 What Is This Issue? If your Shopify store's pixel connection has dropped in Search Atlas, a Shopify pixel version update is the most common cause. When Shopify releases a new pixel version, the previously installed tracking script can become invalid, breaking the connection between your store and Search Atlas. This affects all stores using the integration, including scenarios where multiple domains disconnect at the same time. This article walks you through why it happens and how to fix it by replacing the outdated script with the current version. ⚠️ Common Symptoms - One or more Shopify stores show a Disconnected status in Search Atlas. - Tracking data stops updating or shows a gap starting from a recent date. - Multiple stores owned by the same account disconnect simultaneously. - The connection was working correctly before a recent Shopify platform update. 🧠 Why This Happens Shopify periodically updates its Customer Pixel framework. When a new pixel version is released, scripts built on the previous version are no longer recognised as valid by Shopify's tracking infrastructure. The connection is not lost due to anything you changed — it is a platform-side version change that requires you to replace the installed script with an updated one generated from Search Atlas. 🔧 How to Fix It Follow these steps for each affected Shopify store. 1. Log in to Search Atlas and navigate to the Integrations section from the top-right avatar → Settings → Integrations. 2. Locate the disconnected Shopify store and click Reconnect or Manage Integration. 3. Search Atlas will generate a new pixel script based on the latest Shopify pixel version. Copy this script to your clipboard. 4. Open your Shopify Admin for the affected store. 5. Go to Settings → Customer Events. 6. Find the existing Search Atlas pixel script. Click on it to open the editor. 7. Delete the entire contents of the existing script field. 8. Paste the new script you copied from Search Atlas into the field. 9. Click Save. 10. Return to Search Atlas and verify the store status has changed to Connected. This may take up to five minutes to confirm. Repeat steps 4–10 for every disconnected Shopify store. ✅ How to Confirm the Fix Worked - The store displays a Connected status in the Search Atlas Integrations panel. - Tracking events begin appearing in your reports within 24 hours. - No error banners are shown against the store in the dashboard. 🛡️ How to Prevent Future Disconnections - Check the Search Atlas status banner when you notice a drop in tracking data — platform-wide pixel version changes will often be flagged there first. - After any Shopify platform announcement about Customer Pixel updates, proactively refresh your script using the steps above before a disconnection occurs. - If you manage multiple Shopify stores in Search Atlas, check all of them when one disconnects, as version updates affect all stores at the same time. 💬 Need More Help? If you have completed the steps above and your store still shows as disconnected, or if you are unsure which script version to use, 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.

🛍️ Connecting Your Shopify Store to the CM Connector (and Managing Your Plan)

This article walks you through correctly connecting a Shopify store to the Content Management (CM) Connector, resolving the common 404 token exchange error, and explains your options if you'd like to change your subscription or request a refund. ✅ Before You Begin To connect Shopify to the CM Connector, make sure you have the following ready: - Admin access to your Shopify store (you must be the store owner or have staff permissions to install apps). - Your exact store domain in the format your-store.myshopify.com. - An active Search Atlas plan that includes the CM Connector. A note on Shopify authentication: Shopify deprecated the legacy custom-app API token method on January 1, 2026. The CM Connector now supports two authentication schemes — a manually entered access token and OAuth2 (the "Connect/authorize" flow via Shopify). If you previously connected with a manual API token and the connection now fails, use the OAuth authorize flow described below. 🔌 How to Connect Your Shopify Store 1. In Search Atlas, click your avatar in the top-right corner, then go to Settings → CMS Connectors (tab) and choose Shopify as your platform. 2. Enter your store domain. Use the your-store.myshopify.com format, not a custom domain such as www.yourbrand.com. Using a custom domain is the most common cause of connection failures. 3. Click Connect. You'll be redirected to Shopify to authorize the app. 4. Log in to Shopify if prompted, then click Install to approve the connection. 5. You'll be returned to Search Atlas with your store marked as connected. After connecting, confirm Shopify appears as the active connector in the synchronization panel. If the panel still shows WordPress publishing options or a "Not Synced" status, the store did not finish connecting — remove the connection and reconnect using the steps above. (A bug that caused the system to fall back to WordPress publishing when Shopify wasn't fully authorized was fixed in March 2026.) 🛠️ Fixing the "404 Token Exchange Error" A 404 token exchange error appears when Shopify cannot complete the secure handshake that authorizes the CM Connector. This is almost always a configuration issue, not a problem with your account. Work through these checks in order: 1. Confirm the domain format Enter only the .myshopify.com address. Custom domains, URLs with https://, trailing slashes, or extra paths (for example /admin) will cause the handshake to fail. Re-type the domain exactly as it appears in your Shopify admin under Settings > Domains (look for the "myshopify.com" address). 2. Verify your Shopify permissions You must be signed in to Shopify as the store owner or as staff with app-installation rights. If you don't see an Install button during authorization, ask your store owner to grant the necessary permissions or complete the connection. 3. Complete authorization in one session The token exchange must finish within a short window. If you leave the Shopify approval page open too long, switch accounts midway, or close the tab before clicking Install, the token expires and returns a 404. Start the process again from the CM Connector and approve the app promptly. 4. Clear blockers in your browser - Disable ad blockers or privacy extensions that may interrupt the redirect. - Allow third-party cookies for Search Atlas and Shopify. - Try an incognito/private window or a different browser. 5. Make sure you're logged into the correct Shopify account If you manage multiple stores, your browser may default to a different one. Log out of all Shopify sessions, then start the connection again and sign in to the specific store you want to link. 6. Reconnect After making any change above, return to the CMS Connectors, remove the failed connection if one was created, and start fresh. Most 404 errors clear once the domain format and permissions are correct. If the error persists after all six steps, contact our support team and include your .myshopify.com domain and a screenshot of the error. This helps us resolve the issue faster. ⚠️ Seeing a "401 Unauthorized" instead of a 404? A 401 error is different from the 404 token exchange error: it means Shopify is rejecting credentials that were valid before. This typically happens when the Shopify app was uninstalled and reinstalled, or when the store's API token was regenerated, which invalidates the stored credentials. Search Atlas now flags these connections with an invalid-credential status and stops retrying automatically — to fix it, reconnect the store (or re-enter the token) so a fresh, valid credential is saved. 💳 Managing Your Subscription If the platform feels complex or the plan no longer fits your needs, you have options before cancelling. Many customers find that a guided onboarding session or a smaller plan resolves their concerns. Downgrading to a different plan 1. Go to Avatar (top-right) > Billing (Plans & Top-ups). 2. Select Change Plan and choose the plan that fits your budget and feature needs. 3. Confirm the change. Downgrades usually take effect at the start of your next billing cycle, so you keep current features until then. If you're unsure which plan is right, reach out and we'll recommend the best fit based on how you use Search Atlas. Charged through the Shopify App Store but can't access the app? If you subscribed via the Shopify App Store, were charged successfully, but Search Atlas keeps redirecting you to the pricing/subscribe page, your subscription may not have provisioned on our side. Don't request a refund as the first step — contact our support or billing team with your account email and the charge date so we can locate the Shopify subscription record and provision your access manually. (A provisioning fix for this scenario was released in May 2026; if you still hit it, support can resolve it directly.) Requesting a refund Refund eligibility depends on your plan type, billing cycle, and how long ago you were charged. To request a refund: - Contact our support or billing team through the in-app chat or your account email. - Include your account email, the charge date, and the reason for the request. - Our team will review your request against our refund policy and respond with the available options. Submitting a request does not guarantee a refund, but we review every case individually and will always explain the outcome. 🙋 Need More Help? Before cancelling due to complexity, we encourage you to book a free onboarding or training session. Our team can walk you through the CM Connector and the features included in your plan so you get full value from your subscription. Contact support any time through the in-app chat or your account dashboard.

🔌 Fix Wix Integration Reconnect Button Not Responding

🔍 Overview When connecting your Wix site to Search Atlas, the Reconnect button may appear clickable but produce no response. This typically happens when Search Atlas detects an invalid or expired credential state — for example, a mismatched API key, an incorrect Site ID, or a Wix account permission issue. This article walks you through the steps to resolve the problem and complete your integration successfully. ⚠️ Common Causes - The Wix API key has expired or been regenerated in your Wix dashboard since the last connection attempt. - The Site ID entered does not exactly match the site you are trying to connect. - The Wix account used to generate the API key does not have sufficient permissions for the target site. - The integration is stuck in a disconnected credential state, preventing the reconnect flow from completing. - The site's display name in Wix exceeds 200 characters, which causes a validation error during connection. 🛠️ Step-by-Step Fix 1. Log in to your Wix account and navigate to Settings → Advanced → API Keys. 2. Check whether the existing API key is still active. If it has been revoked or regenerated, create a new API key and copy it immediately. 3. Locate your Wix Site ID by going to Settings → General Info and scrolling to the Site ID field. Copy the exact value — it is case-sensitive. 4. Confirm that the Wix account you are using is listed as an Owner or Admin on the site. Contributor roles may not have the permissions needed for API access. 5. Check your Wix site's display name (the public-facing name shown in Settings → General Info). If it is longer than 200 characters, shorten it and save the change before retrying. 6. Return to Search Atlas and open Settings → Integrations → Wix. 7. If the integration shows a disconnected or error state, click Disconnect first to fully reset the connection. Wait a few seconds for the status to update. 8. Click Connect (not Reconnect) and enter your new API key and the exact Site ID from step 3. 9. Click Save and wait up to 30 seconds for Search Atlas to validate the credentials and confirm the connection. ✅ Confirming a Successful Connection Once the integration completes successfully, the status indicator next to your Wix site will change to Connected. If you still see a Reconnect or Fix Now prompt after following the steps above, refresh the page — the status sometimes requires a manual refresh to update in the UI. 💡 Tips to Prevent This Issue - Always use an API key generated by the site Owner account, not a collaborator account. - Keep your Wix site's display name under 200 characters to avoid validation errors during sync. - If you regenerate your Wix API key for any reason, update it in Search Atlas immediately to avoid credential expiry issues. - Do not close the browser tab or navigate away while the connection process is running. 💬 Still Need Help? If you have followed all the steps above and the Reconnect button is still unresponsive, our team can investigate the credential state on your account directly. 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.

🛠️ Wix Integration Known Issues and Workarounds

🔍 Overview If your Wix site is connected to Search Atlas and you are experiencing issues with stale images, delayed metadata updates, or an H1 element causing unexpected page behavior, you are not alone. These are known integration defects that affect a subset of Wix-connected sites. This article explains each issue, its current status, and what to have ready when escalating to our team. ⚠️ Known Wix Integration Defects The following defects have been identified and are under active investigation by our engineering team. - Stale images: Images on Wix sites may not refresh after being updated through Search Atlas. The old image may continue to appear even after a successful save. - Delayed mutations: Changes pushed from Search Atlas — such as metadata updates — may take longer than expected to reflect on the live Wix site. - H1 containment: On certain Wix page templates, modifications to the H1 element through Search Atlas may produce unexpected page behavior related to how Wix renders that element. 📊 Current Status All defects listed above have been escalated to our engineering team for investigation. Our team is actively working to resolve each issue and will communicate updates as they become available. If you have an open support conversation related to these issues, our team will update your ticket directly as progress is made. You do not need to reopen or re-submit a request for these known defects. 🛠️ What to Have Ready When Escalating Because these are backend integration defects, our engineering team will need specific details to investigate your case. Please have the following information ready before contacting support: - Your Wix site URL - The specific defect you are experiencing (stale images, delayed mutations, or H1 containment) - The exact page or pages affected - A description of what you changed in Search Atlas and when - Any screenshots or screen recordings showing the issue 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.

🛠️ Fix Shopify CMS Connector 400 OAuth Error

🔍 Overview Search Atlas connects to Shopify in two distinct ways. CoWorker uses a Shopify connection for SEO automation tasks, while the CMS Connector is a separate integration that allows Search Atlas to publish and manage content directly inside your Shopify store. These two connections serve different purposes and each requires its own dedicated setup. If you encounter a 400 OAuth token exchange error during CMS Connector setup, this article explains what is happening and how to get it resolved. ⚙️ Why You Need a Separate CMS Connector Even if your Shopify store is already connected through CoWorker, you must complete a separate CMS Connector setup. The two integrations are independent of one another and both can run simultaneously without conflict. 🚨 What Is a 400 OAuth Token Exchange Error A 400 error during the OAuth token exchange means that Shopify was unable to complete the authorisation process during CMS Connector setup. This is a known issue that our team needs to investigate on a case-by-case basis. 🛠️ How to Escalate This Issue Because this error requires backend investigation, please do not attempt workarounds that are not confirmed by our support team. Instead, contact us and have the following information ready so we can resolve it as quickly as possible: - Your project name in Search Atlas - The exact error message you are seeing (a screenshot is helpful) - The Shopify store URL you are trying to connect - The steps you took before the error appeared - The date and approximate time when the error occurred 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.

🔄 Fix Sync to CMS Not Updating Your CMS

🔍 Overview Some users have reported that the Sync to CMS toggle returns a Something went wrong error, and OTTO SEO optimizations — such as alt text changes or meta title updates — do not appear on their WordPress site even after reinstalling the plugin or re-authenticating their connection. This article explains the known cause, what you can check on your end, and how to get this resolved quickly if the issue persists. ⚙️ What Causes This Issue This behaviour has been traced to a software bug on the Search Atlas side that can prevent the Sync to CMS feature from pushing OTTO optimizations to WordPress correctly. The bug affects the sync process itself — not your WordPress plugin installation or authentication credentials. In confirmed cases, the engineering team identified and deployed a fix that fully resolved the problem. Because this is a platform-side issue, there are no local troubleshooting steps that will repair it on their own. However, there are a few things worth verifying before escalating, to rule out common configuration gaps. ✅ What to Check First Before contacting support, run through the following checks to confirm your setup is correct: 1. SearchAtlas WordPress plugin (MetaSync) is installed and active: Sync to CMS is available exclusively for websites connected through the SearchAtlas WordPress plugin (MetaSync). If your site uses the Cloudflare or Pixel installation method, the Sync to CMS option will not appear in your project. Confirm the plugin is installed and active on your site. 2. Your project is connected via the WordPress plugin: Sync to CMS only applies to WordPress plugin projects. If your project is not connected through the SearchAtlas WordPress plugin, the sync cannot proceed. 3. Re-authenticate if prompted: If your WordPress connection was recently changed or expired, re-authenticate the connection from within your project settings. A successful re-authentication should be confirmed before testing the sync again. 4. Test the sync again after re-authentication: After confirming the above, attempt to use the Sync to CMS toggle again. If the error persists, the issue is likely on the platform side. ⚠️ Important Limitations to Know The Sync to CMS feature has several built-in limitations that are worth keeping in mind: - WordPress plugin projects only: Sync to CMS is available only for websites connected through the SearchAtlas WordPress plugin (MetaSync). Sites using the Cloudflare or Pixel installation method do not have access to this feature. - Heading changes and Link corrections do not sync: Heading changes and Link corrections (Issues with Links) are not synced. These optimizations modify the page body content, which SEO plugins such as Yoast SEO, Rank Math, and AIOSEO do not provide equivalent fields for — so there is nothing to synchronize. - Heading and Link changes are editor-dependent: These content changes are supported only on posts and pages using the Gutenberg or Classic Editor. They are intentionally skipped on page builders such as Elementor, Divi, WPBakery, Beaver Builder, Oxygen, and Brizy, because those builders store content outside the standard WordPress post body. - All other optimization types sync regardless of editor: Meta title, meta description, focus keyword/keyphrase, Open Graph title and description, Twitter title and description, schema/structured data, canonical URL, and image alt text all sync regardless of which editor or page builder is used. Image alt text updates are written to the WordPress Media Library. 🛠️ If the Error Persists If you have confirmed your SearchAtlas WordPress plugin is active, your project is properly connected via the WordPress plugin, and the Something went wrong error still appears after attempting to sync, this indicates a platform-side issue that requires the engineering team to investigate. This type of issue cannot be resolved through self-service steps alone. In confirmed cases, our team has been able to identify the root cause, deploy a targeted fix, and fully restore sync functionality for the affected project. To get this escalated quickly, contact our support team directly so they can log the issue and engage the relevant engineers on your behalf. 💬 Contact Support 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. When reaching out, it helps to include the following details to speed up the investigation: - The domain or project name affected - The exact error message you are seeing - Whether re-authentication was attempted and whether it completed successfully - Which specific OTTO optimizations are not syncing (e.g. alt text, meta descriptions)

🛠️ Troubleshooting Shopify Connector Failures in Search Atlas

Fix the most common Search Atlas Shopify connector failures — loading glitches, page-load timing issues, 410 Gone errors, WordPress plugin confusion, and custom app problems — using the matching fix for each. Start with a hard-refresh and re-add, which resolves most cases. 📋 Overview of Shopify Connector Failures The Search Atlas Shopify connector can fail during initial setup or after a store is already connected. This article covers the most common failure modes — temporary loading issues, page-load timing problems, 410 Gone errors, WordPress plugin confusion, and custom app failures — and gives you a clear fix for each. 🔄 First Fix: Hard-Refresh and Re-Add the Shopify Connector If you can't connect your store through the plugin or custom app, or you're seeing chat disconnections and other glitches, you're likely hitting a temporary loading issue. Chat disconnections and similar glitches are usually symptoms of this same temporary loading state — not a separate problem — because the page holds a stale session that a hard-refresh clears. This fix resolves it most of the time, so try it first. If the disconnections continue even after a hard-refresh and re-add, escalate to Search Atlas support. 1. Hard-refresh the page to clear the temporary loading state: press Ctrl+Shift+R on Windows, or Cmd+Shift+R on Mac. 2. Go to Settings → Add Connector. 3. On Step 1, select New domain and manually type your domain name instead of selecting it from the existing list. 4. Enter your Shopify credentials and click Submit to create the connector. The connector creates successfully and your Shopify store appears in your connected integrations. ⚠️ Connection Won't Establish (Page-Load Timing Issue) If the Shopify connection fails immediately after you start it, a timing problem during the authorization flow may be stopping the OAuth handshake from completing. OAuth is the secure sign-in process Shopify uses to authorize the connection. How to fix it 1. Go to Coworker → Connectors (Shopify) in the left sidebar of Search Atlas. 2. Click Connect and wait for the Shopify authorization page to fully load before clicking anything. 3. Stay on the authorization page until it completes — keep the tab open and let the flow finish. 4. Approve all requested permissions on the Shopify side. 5. If the connection still fails, hard-refresh the page (see the First Fix section), then re-add the connector using the New domain option, or retry in an incognito or private window. Once the handshake completes, Search Atlas confirms the store is connected. ⚠️ 410 Gone Error on a Previously Connected Store A 410 Gone error on a store that was already connected usually means the Shopify app install was removed or the OAuth token was revoked from the Shopify admin side. How to fix it 1. In your Shopify admin, go to Apps → Installed Apps and confirm the Search Atlas app is still listed. 2. If it was removed, reinstall the Search Atlas app from the Shopify App Store. 3. Return to Search Atlas and reconnect via the left sidebar → Coworker → Connectors (Shopify). After reinstalling and reconnecting, the 410 error clears and data syncing resumes. 🔌 WordPress Plugin Method Not Working for Shopify The Search Atlas WordPress plugin is built for WordPress-based websites, not Shopify storefronts. Shopify does not run WordPress, so the WordPress plugin cannot connect a Shopify store. How to fix it 1. Use the native Shopify connector in Search Atlas instead. 2. Go to Settings → Integrations → Shopify and follow the OAuth connection flow described above. The native connector is the supported path for Shopify and connects your store directly. 🔑 Custom App (API Key) Method Failing If you're connecting with a Shopify Custom App (API key and secret) and the integration won't complete, a misconfigured domain, mismatched credentials, an app that isn't fully installed, a missing access scope, or an expired token is the usual cause. How to fix it 1. In your Shopify admin, go to Settings → Apps and sales channels → Develop apps. 2. Confirm your Shop Domain uses the .myshopify.com subdomain format (for example, your-store.myshopify.com), not your custom storefront domain. 3. Verify that the Client ID and Client Secret entered in Search Atlas exactly match the API credentials shown in your custom app's settings — a mismatch will block the connection. 4. Confirm the app is both installed and released in your Shopify admin. An app that is created but not installed and released will not authorize. 5. Check the app URL in your custom app configuration and set it if it is blank or incorrect (for example, https://shopify.dev/apps/default-app-home). 6. Open your custom app and confirm all required Admin API access scopes are enabled. 7. Verify the exact scope list against your Search Atlas connector documentation before publishing, as requirements may vary. Commonly required scopes include read_products, write_products, read_content, write_content, read_metafields, and write_metafields. 8. If any required scope is missing, add it and save the app configuration. 9. Regenerate your Admin API access token if it has expired or been revoked. Copy the new token immediately, as Shopify displays it only once. 10. Re-enter the new token in Search Atlas under the left sidebar → Coworker → Connectors (Shopify → Custom App). With the correct domain format, matching credentials, a fully installed app, the correct scopes, and a valid token, the custom app connection completes and your store syncs. 🚫 404 Token Exchange Error A 404 token exchange error during a custom app connection usually means Shopify can't complete the token handshake — typically because the app isn't fully installed, the app URL is wrong, or the Client ID/Secret don't match. How to fix it 1. Confirm the custom app is both installed and released in your Shopify admin under Settings → Apps and sales channels → Develop apps. 2. Verify the app URL is configured correctly (for example, https://shopify.dev/apps/default-app-home) — a missing or incorrect app URL will break the token exchange. 3. Double-check that the Client ID and Client Secret in Search Atlas exactly match the values in your custom app's API credentials. 4. Re-enter the credentials and retry the connection under the left sidebar → Coworker → Connectors (Shopify → Custom App). Once the app is installed and released, the app URL is correct, and the credentials match, the token exchange completes successfully. 🔔 Known Platform-Level Issue Search Atlas is aware of changes Shopify has made to its API token system that can affect some store connections. If you hit a connection or token error, run the First Fix steps above, and contact Search Atlas support if the issue continues. 🎯 You now have a fix for every common Shopify connector failure — start with the hard-refresh and re-add steps, then work through the matching failure mode if needed. If a connection still won't establish after trying these, reach out to Search Atlas support so the team can investigate token-level issues.

🔧 How to Enable Meta Keywords CMS Sync

This article helps you resolve the issue where the meta keywords CMS sync toggle cannot be turned on. This is a specific setting that must meet a few conditions before it can be enabled, and the steps below walk you through each one so you can confirm the exact cause and get sync working. 🛠️ Step-by-Step 1. Confirm your CMS integration is connected and authenticated. CMS sync — for any field including meta keywords — requires an active, authorized connection to your CMS (e.g., WordPress, Shopify, or a custom integration). Open the top-right avatar → Settings → CMS Connectors and verify that your CMS integration shows a connected status with no authentication errors. If it shows disconnected or expired, reconnect it and try the toggle again. 2. Check that the meta keywords field is mapped in your CMS integration settings. Some CMS platforms do not expose a native meta keywords field, or the field may not be mapped in Search Atlas. In your CMS integration configuration, confirm that a meta keywords field is listed and mapped to a corresponding field in your CMS. If no mapping exists, add one — without a mapped field, the sync toggle will remain inactive. 3. Verify you have the correct permission level. CMS sync settings are typically restricted to account owners or admin-level users. If you are on a sub-user or collaborator seat, you may see the toggle but be unable to enable it. Ask your account owner to either enable the setting on your behalf or elevate your permission level. 4. Disable any conflicting sync rules. If another sync rule or automation is already managing the meta keywords field for the same content, the toggle may be locked to prevent conflicts. Review your active sync rules and disable or remove any that overlap with the meta keywords field, then attempt to enable the toggle again. 5. Save all pending changes before toggling. If you have unsaved edits open in the same content editor session, the sync toggle can appear unresponsive. Save or discard any pending changes first, then reload the page and attempt to enable the sync toggle. ✅ How to Confirm It Worked Once the toggle is successfully enabled, you should see it switch to an active or highlighted state without reverting when you navigate away. To verify end-to-end sync is working: save your content, then check your CMS directly and confirm the meta keywords field has been populated with the value from Search Atlas. If the field in your CMS remains empty after saving, re-examine the field mapping in your integration settings to ensure the correct destination field is selected. 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.

⚙️ OTTO SEO and Webflow: Current Limitations Explained

🔍 Overview OTTO SEO connects to your website through a JavaScript pixel that is installed on your pages. On some platforms, OTTO can write changes directly to your page content at the source level — meaning edits land inside the actual CMS and persist as real content updates. On Webflow, this deeper integration is not yet available. This article explains what that means for your site, why the limitation exists, and what the current situation looks like. ⚙️ How the OTTO Pixel Works on Webflow When you install OTTO on a Webflow site, the pixel is injected as a client-side JavaScript snippet. This means OTTO can: - Read and analyse your page content - Surface SEO recommendations and audit findings - Apply certain on-page changes via the browser at render time However, because the pixel operates client-side, it cannot write changes back into Webflow's CMS or Designer. Any modifications OTTO applies are rendered in the browser layer — they are not stored as permanent edits inside your Webflow project. 🚧 Why a Source-Level Fix Is Not Yet Available Webflow uses a closed Designer environment and a separate CMS API that requires a different integration approach — one that goes beyond what a client-side pixel can do on its own. Bridging OTTO's automation engine with Webflow's CMS API at a source level is a significant technical undertaking, and this capability is not currently available. 📊 What This Means for Your Webflow Site Right Now If you are running OTTO on a Webflow site, here is what you can expect: - SEO audits and recommendations work fully — OTTO will scan your site and surface issues through the standard audit workflow. - Client-side optimisations applied by the pixel are active while the pixel is loaded, but are not written into Webflow's source content. - Manual implementation is currently required — to make OTTO's recommendations permanent, you or your team will need to apply the suggested changes directly inside the Webflow Designer or CMS editor. 🛠️ Interim Workaround: Applying OTTO Recommendations Manually in Webflow While native CMS-write is unavailable, you can still action every OTTO recommendation by following these steps: 1. Run an OTTO audit on your Webflow site. Navigate to OTTO SEO → Site Audit in the left sidebar, select your project, and open the Audit or Recommendations panel to see a prioritised list of issues. 2. Export or note the specific recommendations — for example, missing meta titles, meta descriptions, heading structure issues, or alt-text gaps. OTTO surfaces the exact field and suggested value for each finding. 3. Log in to your Webflow project and open the page or CMS Collection that contains the flagged content. 4. For static pages: Open the page in the Webflow Designer, click the relevant element or use the SEO settings panel (Page Settings → SEO tab) to update meta title, meta description, Open Graph fields, or on-page content as recommended by OTTO. 5. For CMS Collection items: Go to your Webflow CMS editor, open the relevant Collection, and edit the individual item fields (e.g., SEO Title, Meta Description, or custom fields) to match OTTO's suggested values. 6. Publish your Webflow site after making changes so that updates go live and are reflected when OTTO re-scans the page. 7. Re-run the OTTO audit to confirm the issues are resolved and track your progress over time. Repeating this workflow for each audit cycle allows you to systematically implement OTTO's recommendations even without automated CMS-write support. 🗺️ Roadmap Status A native, source-level Webflow integration — one that writes changes directly into your Webflow CMS — is not available at this time. There is no confirmed delivery date for this capability. 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.

🔌 Troubleshooting CMS Connector Status Mismatch

This article addresses a specific issue where Search Atlas reports that your CMS connector is not connected, but when you check your connector settings, the connection appears active and healthy. This contradiction is a known status sync issue. Because the root cause occurs at the platform level, it cannot be fixed by reconnecting or refreshing from your end alone — the steps below will help you first confirm whether this is actually a status sync issue (versus a misconfiguration), and then prepare everything needed for a fast resolution if escalation is required. 🔍 What This Issue Looks Like - Search Atlas displays a disconnected or error status for your CMS connector. - Your CMS connector settings show the connection as active and healthy. - The mismatch persists even after navigating away and returning to the affected project. 🧭 Triage First: Is This a Status Sync Issue or a Misconfiguration? Before escalating, work through the following questions to determine whether this is the known sync issue or something that can be resolved without support: 1. Which CMS are you connecting? Note the CMS name and the integration method (e.g., API key, OAuth). Confirm that the integration type is still supported and that your credentials have not recently expired or been rotated. 2. Does the disconnected status affect all of your projects, or only one specific project? If it affects only one project, check whether that project's connector was recently re-saved, duplicated, or edited — a partial save can sometimes create a false-disconnected state that resolves on its own after a few minutes. 3. Were any changes made recently? For example: a password or API key reset in your CMS, a workspace transfer, a plan change in Search Atlas, or any third-party access revocation. If so, try removing and re-adding the connector in the affected project only if the issue started immediately after that change — this may be a simple re-auth rather than a sync bug. 4. Has the status been inconsistent for more than 30 minutes without any changes on your end? If yes, and the connector settings clearly show the connection as active, this is the pattern consistent with the platform-level sync issue described in this article. 🛠️ If You Have Confirmed This Is the Sync Issue: What to Prepare 1. Open your CMS connector settings and take a screenshot showing the current connected status, including any last-sync timestamp or confirmation message displayed there. 2. Note the exact project or site within Search Atlas that is showing the disconnected warning — record its name exactly as it appears in the platform. 3. Note the approximate time you first noticed the mismatch, including your timezone. 4. Do not reconnect or revoke the connector before contacting support — doing so can make the issue harder for the team to diagnose. 5. Reach out to support (see below) with your screenshot, project name, and the timestamp of when the issue first appeared. The support team will investigate the status sync on the platform side and resolve it for you. ✅ How to Confirm It Is Resolved Once the support team has addressed the underlying sync issue, the status indicator for your CMS connector should update to show a consistent Connected state in Search Atlas. You can also confirm the fix is effective by verifying that your content or data is actively syncing and that the disconnected warning no longer appears when you navigate to the affected project. 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.

🔌 Connect GoDaddy Blog Publishing via Universal CMS

🌐 What Is the Universal CMS Connector? The Universal CMS Connector is a Search Atlas feature that lets you publish blog content directly to website platforms that are not natively integrated — including sites built and hosted on GoDaddy. Instead of copying and pasting content manually, you can push published articles straight from Search Atlas to your GoDaddy blog. ✅ Before You Begin Make sure you have the following ready before starting the setup: - An active Search Atlas account with content publishing access. - A live GoDaddy website with a blog section enabled. - Admin access to your GoDaddy account. - Your GoDaddy site's public URL (e.g., https://yourdomain.com). 🛠️ Setting Up the Universal CMS Connector for GoDaddy The exact steps to connect GoDaddy to Search Atlas via the Universal CMS Connector depend on your specific account configuration and GoDaddy's platform capabilities. Because the setup flow can vary, please use the chat widget below to be connected with a team member who can walk you through the correct process for your account and confirm whether the integration is supported for your GoDaddy setup. When reaching out, please have the following information ready: - Your Search Atlas account email or project name. - The full URL of your GoDaddy website (e.g., https://yourdomain.com). - The GoDaddy product you are using (e.g., Website Builder, WordPress on GoDaddy, or a custom hosting plan). - Any error messages or steps you have already attempted. ⚠️ Common Issues to Note - GoDaddy platform type matters: The Universal CMS Connector setup may differ depending on whether your GoDaddy site runs on GoDaddy's own Website Builder, WordPress, or another platform. Please confirm this before reaching out so our team can advise accurately. - Admin access required: Make sure you have full admin access to both your Search Atlas account and your GoDaddy account before beginning any integration steps. - Site URL format: Always include https:// when providing your site URL to avoid connection errors. 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.

🏠 Search Atlas Integration Options by CMS Platform

🔍 Overview Search Atlas supports content optimization across a wide range of CMS platforms, but integration capabilities vary depending on your platform. This article focuses on Lofty CMS (formerly Chime), a popular CRM and website platform used by real estate professionals. If you use Lofty, this guide explains exactly what is and is not currently possible, how JavaScript deployment works, and what to expect from the product roadmap. ⚙️ Current Integration Capabilities for Lofty CMS Search Atlas does not have a native plugin or direct backend integration with Lofty CMS. Unlike WordPress — which has a dedicated Search Atlas plugin that writes changes directly to your database — Lofty operates on a closed platform architecture that does not permit third-party plugins in the same way. The options currently available to Lofty users are: - JavaScript snippet deployment — Inject a script tag into your Lofty site's custom code section to enable on-page optimizations dynamically. - Manual CMS edits — Apply Search Atlas recommendations by hand inside the Lofty page editor. There is no automated sync between Search Atlas and Lofty at this time. Every change either requires manual entry or relies on the JavaScript method described below. 📜 How JavaScript Deployment Works The JavaScript deployment option allows Search Atlas to apply content and on-page optimizations dynamically — meaning changes are rendered in the browser when a visitor loads your page, rather than being saved directly into your CMS database. Here is what you need to understand about how this works in practice: - Persistence is conditional, not permanent. The JavaScript snippet must remain active and correctly installed in your Lofty custom code section at all times. Optimizations are applied each time a page loads, so they are only visible while the script is running. - There is a server dependency. The script calls Search Atlas servers to retrieve and apply your configured optimizations. If Search Atlas servers are unreachable, or if your subscription becomes inactive, the JavaScript-driven changes will not render. - Removing the script removes the changes. If you delete the JavaScript snippet from your Lofty site — intentionally or during a site rebuild — all dynamically applied optimizations will immediately disappear from your live pages. No residual edits are left behind in your CMS. - The script does not write to your Lofty database. Unlike a native integration, JavaScript deployment leaves no permanent footprint inside Lofty. Your Lofty page content stays exactly as you entered it in the editor. For changes you want to be truly permanent and independent of any external script, the correct approach is to apply Search Atlas recommendations manually inside the Lofty page editor. Manual edits are saved directly in Lofty and remain live regardless of your Search Atlas subscription status. 🔄 JavaScript vs. Manual Edits — Comparison - JavaScript deployment: Faster to apply across multiple pages, dynamically maintained, but dependent on the script staying active and Search Atlas servers being available. Removing the script removes all changes instantly. - Manual CMS edits: Slower to implement page by page, but changes are saved permanently inside Lofty. No external dependency once saved. Recommended for high-priority pages where stability matters most. Many Lofty users combine both methods: use JavaScript for broader site-wide optimizations and apply manual edits for key landing pages where permanence is critical. 🚫 Why Lofty API Integration Is Not Currently Supported Lofty does not offer a public-facing content API that allows third-party tools to programmatically read and write page content on your behalf. This is a platform-level limitation set by Lofty, not a Search Atlas product gap. Because no stable, documented API exists for content management within Lofty, Search Atlas cannot push edits directly into your Lofty pages the way it can with WordPress via the REST API and the Search Atlas plugin. Any suggestion that you can integrate Search Atlas changes permanently through the Lofty API is inaccurate — this path does not currently exist. If Lofty releases a content API in the future, Search Atlas will evaluate building a direct integration. Until then, JavaScript deployment and manual edits are the supported methods. 🏡 Real Estate Playbooks — Roadmap Status Search Atlas does not currently offer real estate-specific playbooks as a built-in feature. General content strategy playbooks are available within the platform, but vertical-specific playbooks tailored to real estate use cases — such as neighborhood pages, listing content, IDX optimization, and local market guides — are on the product roadmap and under active consideration. There is no confirmed release date for real estate playbooks at this time. If this is a priority for your team, we encourage you to submit a feature request through the platform so the product team can gauge demand. The more requests a feature receives, the higher it is prioritized in the development queue. ✅ Recommended Workflow for Lofty Users 1. Install the Search Atlas JavaScript snippet in your Lofty site's custom code section to activate dynamic optimizations across your site. 2. Use Search Atlas content recommendations and on-page tools to identify priority changes for your most important pages. 3. For high-value pages such as home, service area, or main landing pages, apply recommendations manually inside the Lofty editor to ensure permanent, script-independent changes. 4. Keep the JavaScript snippet active to maintain dynamically applied optimizations across the rest of your site. 5. Do not remove the snippet during site updates unless you have already manually replicated the changes inside Lofty. 💬 Need Help? 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.

🔗 Map CMS Connector IDs to Project Domains

🗺️ What Are CMS Connector IDs? When you connect a CMS (such as WordPress or another supported platform) to Search Atlas, the system assigns each connection a unique numeric Connector ID. Features like OTTO use these IDs internally to route SEO enhancements to the correct site. If you need to know which ID belongs to which domain, you will need to retrieve the correct account-specific mapping. ⚠️ Why This Can Be Confusing The platform may surface multiple numeric IDs in certain contexts, and some of these can belong to unrelated system-level projects rather than your own connected domains. This means you cannot always rely on an automatically generated list to be accurate without verification. 🛠️ How to Get Your Correct ID-to-Domain Mapping Because CMS Connector IDs are account-specific and must be retrieved from verified internal records, the recommended way to get an accurate mapping is to contact the Search Atlas support team. Our team can look up your account, identify each Connector ID, and provide you with the confirmed list — for example, in the format 1780 = valueinvestmentpartners.com, 1656 = webuynova.com, and so on for each connector in your account. 1. Gather the Connector IDs you need to map. Before reaching out, note down all the numeric IDs you have seen referenced in your account or in any OTTO setup instructions. 2. Contact the support team. Reach out and type human teammate to be connected with a member of our team. 3. Share your Connector IDs with the agent. Provide the list of IDs and ask for the confirmed domain mapping for your account. The agent will look up and verify each ID against your connected projects. 4. Save the mapping for future reference. Once you receive the confirmed list, keep a record of it. You can use this mapping whenever OTTO or another feature asks you to specify a Connector ID for a particular domain. 📋 How to Use the Mapping Once You Have It After you have your confirmed ID-to-domain list, you can reference it any time you need to direct OTTO SEO enhancements or other automation to a specific site. Simply match the numeric ID to the domain you want to target before submitting a configuration or scan request. This ensures changes are applied to the correct connected property. 🔍 Tips to Avoid Confusion - Always use the mapping provided directly by the support team rather than relying on IDs that appear in general system screens, as those may include unrelated project entries. - If you add or remove a CMS connection in the future, request an updated mapping to make sure your records stay accurate. - When setting up OTTO for a site, confirm the Connector ID before initiating a scan or enhancement run to prevent changes being applied to the wrong property. 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.

🛠️ Fix CMS Image Alt Text Sync Errors

🔍 Overview If you see a "Something went wrong. Please try again" error when trying to sync image alt text optimizations to your CMS through OTTO, this article explains what causes it, what you can try yourself, and how to get it escalated quickly if the error persists. ⚠️ What Causes This Error This error is a known bug that prevented OTTO from successfully syncing image alt text optimization tasks to a connected CMS. Engineering ticket SPE-1137 was raised and a fix has been deployed to production. Most users are no longer affected. However, if you are still experiencing this error, the steps below will help you resolve it or get the right team involved fast. Important: OTTO's Sync to CMS feature currently works exclusively with the WordPress plugin. If your site runs on a different CMS platform (such as Drupal), sync is not yet supported for image alt texts. ✅ Steps to Try First 1. Confirm your WordPress plugin is installed and connected. The Sync to CMS feature requires the Search Atlas WordPress plugin to be active and properly connected to your site. If the plugin is outdated or disconnected, syncing will fail. 2. Retry the sync. Go to OTTO in the platform and attempt to sync the image alt text task again. Temporary network or session issues can sometimes cause a one-off error. 3. Refresh your session. Log out of the platform, clear your browser cache, log back in, and try the sync again. 4. Try a different browser. If the error continues, attempt the sync in an alternative browser to rule out a local browser issue. 5. Check your site's theme. If your WordPress site uses the Oxygen theme, image alt text syncing has been identified as unreliable due to how that theme renders pages over HTTP. This is a known limitation — contact support (see below) so our team can advise on the best path forward for your setup. 📋 If the Error Persists If you have followed the steps above and the error still appears, our support and engineering teams will need to investigate further. To help us resolve your issue as quickly as possible, please have the following ready before reaching out: - A screen recording or screenshots clearly showing the error occurring during the sync attempt - The URL of the page or post you are trying to sync alt texts to - The name of your WordPress theme - Confirmation of whether your Search Atlas WordPress plugin is installed and which version you are running Having this information prepared allows our team to escalate your case with full context and minimise back-and-forth. 💡 Known Limitations to Be Aware Of - WordPress only: Sync to CMS for image alt texts is supported exclusively via the Search Atlas WordPress plugin. Other CMS platforms are not currently supported for this feature. - Oxygen theme: Image alt text syncing has been reported as unreliable on sites using the Oxygen theme due to its HTTP render path. Our team is aware of this behaviour. 🤝 Still Need Help? 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.

🛠️ Fix Shopify Pages Missing in OTTO

If your Shopify location pages or other /pages/ URLs are not appearing in your OTTO SEO audit, it is usually due to how our crawler detects your website's content management system (CMS). Shopify sites occasionally block automated crawlers, which can prevent OTTO from fully scanning your pages. 🔍 Understanding the Detection Issue Our team is actively improving how OTTO identifies and crawls sites built on platforms like Shopify, GoHighLevel, and HubSpot. Occasionally, these platforms restrict access to certain URL paths (like /pages/), causing them to remain undetected during a standard site audit. 🚀 What to Expect This is a known issue that our engineering team is actively working to resolve. We are currently rolling out updates to enhance Shopify crawler compatibility. Until these platform-wide fixes are finalized, some Shopify /pages/ URLs may continue to be excluded from the OTTO crawl. 📋 What to Have Ready When Contacting Support To help our engineering team investigate your specific case, please have the following information available: - Your project or website name as it appears in Search Atlas - The specific Shopify /pages/ URLs that are missing from your OTTO audit - The date you first noticed the pages were missing - Any confirmation that these pages are live and indexable (e.g., they load correctly in a browser) Our support team can manually review your account and escalate your case to engineering for further investigation. 💬 Need Further Assistance? 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.

🔧 Fix Shopify CMS Connector Authentication Errors

Overview The Shopify CMS Connector in Search Atlas can experience authentication failures when connecting Shopify for use with Content Genius. These failures are typically related to OAuth or Client Credentials authentication methods. Common Authentication Errors When connecting Shopify to Search Atlas, authentication may fail due to issues with either the OAuth flow or the Client Credentials (legacy token) method. These are backend-side connection issues that require investigation by our engineering team. What to Expect If your Shopify CMS Connector is failing to authenticate, the issue is likely occurring on the backend during the connection handshake between Search Atlas and Shopify. This is not something that can typically be resolved through the UI alone, and may require our team to review logs and connection state. Information to Have Ready When Escalating To help our team diagnose and resolve the issue quickly, please have the following details available: - Your Search Atlas project name - Your Shopify store URL (e.g., your-store-name.myshopify.com) - The exact error message you see when the authentication fails - The authentication method you are attempting to use (OAuth or Client Credentials) - The approximate timestamp of when the error occurred Next Steps Once you have the above information ready, escalate to our team so we can investigate the backend connection and resolve the authentication failure. 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.

🛠️ Fix Shopify CMS Connector OAuth 400 Errors

🔍 Overview Some customers have encountered a 400 Bad Request error when connecting their Shopify store to Search Atlas via the CMS Connector. This error typically appears during the OAuth or Client Credentials authentication step and can prevent Autopilot and Content Genius auto-publishing from functioning. This article explains what to have ready when escalating this issue to our support team so it can be resolved as quickly as possible. ⚠️ Why This Error Happens A 400 error during Shopify CMS Connector authentication indicates a failure in the token exchange or credential validation process between Search Atlas and Shopify's API. This type of issue requires investigation by our backend team, as the root cause can vary depending on your specific store and integration configuration. 🔧 What to Have Ready When Escalating Because resolving this error requires action on our backend, please have the following information ready before contacting support so our team can investigate and fix the issue promptly: - Your Search Atlas project name or workspace URL - The exact error message you are seeing (e.g. the full 400 error text or any additional error code displayed) - The timestamp of when the error first occurred or most recently occurred - Whether you are using OAuth or Client Credentials as your authentication method - Any recent changes to your Shopify store or app settings that preceded the error 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.

⚡ Fix Contentful Sync Errors Blocking Article Publishing

Overview When publishing an article from Search Atlas to Contentful fails with a sync error, one known cause is a Content Type validation restriction inside Contentful itself. This article explains what that means and how to diagnose and resolve it. What Is a Content Type Validation Error? A Content Type validation error occurs when Search Atlas successfully connects to Contentful, but Contentful rejects the content because the entry does not meet the field-level rules defined in your Contentful Content Type configuration. This is a Contentful-side restriction, not a broken connection between the two platforms. Common signs that you may be experiencing this issue include: - Reconnecting your Contentful integration or refreshing your API credentials does not resolve the error. - The sync error appears only for certain articles, not all publishes. - Publishing succeeds from Contentful directly but fails when triggered from Search Atlas. What to Do If You Encounter This Error Start by checking your Contentful Content Type configuration to identify the validation rules that may be blocking your publish: 1. Log in to your Contentful workspace. 2. Navigate to the Content Model tab. 3. Select the Content Type you are trying to publish to from Search Atlas. 4. Review each field and note which ones are marked as required, which have character limits, or which restrict the type of content allowed (for example, rich text fields that only accept plain text). 5. Compare the fields in your Search Atlas article with the validation rules in Contentful. Common mismatches include: missing required fields, field values exceeding character limits, or attempting to publish rich text or HTML to a field configured to accept plain text only. 6. If you find a mismatch, you can either adjust your article in Search Atlas to match the Contentful field rules, or contact your Contentful administrator to modify the Content Type validation rules. Because the specific Content Type configuration and validation rules vary by Contentful account, if you are unable to resolve the issue after reviewing your Content Type settings, our support team can help investigate further. When reaching out, please have the following information ready to speed up the investigation: - The exact error message or sync error text you see in Search Atlas. - The name of the Contentful Space and Content Type you are publishing to. - The name of the article or entry that failed to publish. - The approximate date and time the error occurred. - A screenshot or list of the validation rules you found in your Content Type configuration. 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.

🔧 Wix Post-Render Content Overwrites Explained

🔍 What Is the Post-Render Overwrite Issue? When Search Atlas publishes SEO changes to a Wix-hosted site, Wix can re-render the page after publishing and overwrite those changes with its own cached or default values. This is known as a post-render overwrite. The result is that your Search Atlas optimisations appear to save correctly inside the platform but do not persist on the live Wix site. This behaviour has been identified as a recurring defect affecting Wix integrations and is actively tracked by our engineering team. ⚙️ What Specifically Gets Overwritten? Metadata and content changes made through Search Atlas on Wix-connected sites may not persist after Wix re-processes the page. This can affect page-level SEO fields and content elements that Search Atlas writes via the Wix integration. 📋 Why Does This Happen? Wix uses a proprietary rendering pipeline that re-processes page content after external publish events. When Search Atlas writes metadata via the Wix API, Wix's renderer can execute a second pass that pulls values directly from its internal CMS database — overwriting the changes made by Search Atlas before the final HTML is served to visitors or cached by Wix's CDN. This is a known defect caused by a conflict between Search Atlas's publish-sync process and Wix's post-render behaviour. Our engineering team is actively working to address the underlying integration issue, and verification on affected sites is ongoing. 🛠️ What Has Been Fixed So Far? Our engineering team has shipped updates to improve the reliability of content and metadata publish events on Wix-connected sites. These fixes reduce the frequency of overwrites; however, due to the nature of Wix's rendering pipeline, full verification across all affected pages requires additional monitoring. Our team continues to test and confirm resolution on impacted sites. ✅ Steps to Take Right Now 1. Confirm which pages on your Wix site are affected by checking whether your saved changes appear on the live page after publishing. 2. Note the exact page URLs and the specific fields that appear to be overwritten (for example, page title, heading, or image metadata). 3. Note the approximate time you published the changes, so our team can cross-reference logs. 4. Contact our support team with your project name, the affected page URLs, the fields being overwritten, and the timestamps of your publish attempts — this will allow our engineering team to investigate your specific case as efficiently as possible. 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.

🔄 OTTO SEO Sync to CMS Safe Deployment Guide

What Is Sync to CMS? Sync to CMS is an OTTO SEO feature that automatically pushes approved SEO changes directly to your connected WordPress site. Instead of manually copying recommendations into your CMS, OTTO can deploy them for you — saving time and reducing human error. Important: Sync to CMS currently works exclusively with WordPress sites via the Search Atlas WordPress plugin. It is not available for other CMS platforms at this time. What Gets Synced to Your CMS? When Sync to CMS is enabled, OTTO can push SEO changes — such as meta titles, descriptions, and schema markup — directly to your WordPress site through your connected SEO plugin. Current limitations to be aware of: - Some recommendation types, such as heading structure changes and internal link suggestions, are surfaced by OTTO but may require manual implementation in your page editor rather than being automatically synced. How Disabling Sync to CMS Affects OTTO Disabling Sync to CMS does not stop OTTO from generating or displaying recommendations. OTTO continues to crawl your site, identify SEO opportunities, and surface actionable suggestions in the platform. The only difference is that approved changes will not be automatically pushed to your WordPress site. This means: - All recommendations remain visible inside OTTO SEO - You retain full control over which changes go live and when - Your live site remains unchanged until you manually apply updates in WordPress Disabling sync is a safe and reversible action — you can re-enable it at any time from within the OTTO SEO settings area of the platform. Best Practices for Managing SEO Changes Whether you use Sync to CMS or prefer manual deployment, follow these best practices to keep your SEO strategy organised and risk-free: 1. Review before approving. Always read OTTO's recommendations in full before approving them. Take time to understand the scope of each suggested change before it is pushed to your live site. 2. Review changes at the page level. Where possible, check recommendations on a per-URL basis before approving changes at scale, so you can catch any issues early. 3. Approve in batches, not all at once. Start with lower-risk changes like schema markup and meta descriptions. Review heading and internal link changes separately and apply them manually in your CMS editor. 4. Check your SEO plugin settings. Confirm your WordPress SEO plugin is properly connected and that OTTO has the permissions it needs before enabling sync. 5. Monitor your site after syncing. After approving and syncing a batch of changes, review your site to confirm everything looks and performs as expected. If you are unsure whether a particular recommendation is safe to sync, disable Sync to CMS temporarily and apply the change manually first. 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.

🔗 Webflow CMS Dynamic Fields and Metadata Mapping

🌐 Overview When you connect Search Atlas to Webflow CMS, you can use dynamic field tokens to automatically populate your content fields and control how SEO metadata — title, description, and canonical URL — is written to your Webflow collection items at publish time. This article explains what is currently supported and what to expect during the mapping process. 📋 Dynamic Field Tokens and SEO Metadata Mapping Search Atlas supports dynamic tokens that can be inserted into mapped text fields and resolved automatically when content is published to Webflow CMS. These tokens cover core content values such as the article body (HTML), title, URL slug, featured image URL, and featured image alt text. At publish time, Search Atlas also maps SEO metadata — including the SEO title, meta description, and canonical URL — to the corresponding fields configured in your Webflow CMS collection. The canonical URL is typically constructed from your connected Webflow site domain combined with the resolved slug value. If you have additional Webflow CMS fields beyond those covered by the supported tokens, you may need to populate them manually inside Webflow after publishing, as not all custom fields can be dynamically resolved. 🛠️ If Your Field Mapping Is Not Working as Expected Webflow CMS field mapping and metadata behaviour is configured at the backend level and may require investigation by our team if something is not resolving correctly. If you are experiencing unexpected behaviour — such as SEO metadata not appearing in Webflow, tokens not resolving, or fields not populating on publish — please reach out so our team can review your specific setup. To help us investigate as quickly as possible, please have the following ready: - The name of the Webflow site and CMS collection you are publishing to - The specific field or token that is not behaving as expected - The exact error message or unexpected output you are seeing - A timestamp or example of a recent publish attempt that demonstrates the issue 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.

🔗 Webflow CMS Metadata Mapping and Sync Explained

📋 Overview When you publish content from Search Atlas to a Webflow CMS collection, SEO metadata fields — including the page title, meta description, and canonical URL — may not sync as expected. This article explains what is known about Webflow CMS metadata mapping behavior, what to expect, and how to escalate if you encounter issues. 🗂️ About Webflow CMS Metadata Sync Some customers have reported that SEO metadata fields (such as meta title, meta description, and canonical URL) do not behave the same way as standard content fields during a Webflow CMS publish from Search Atlas. If you are experiencing unexpected results with metadata syncing to your Webflow CMS collection, this is a known area of investigation. Because the root cause of metadata mapping and sync issues in Webflow CMS integrations is handled at the backend level, there are no confirmed self-serve steps that reliably resolve this issue. Attempting to reconfigure field mappings on your own may not fix the problem if the underlying sync behavior is the cause. 🛠️ What to Have Ready When Escalating If you are experiencing metadata mapping or sync issues with your Webflow CMS integration, please gather the following before reaching out to our team so we can investigate as quickly as possible: - Your Webflow CMS collection name and the specific metadata fields (e.g., meta title, meta description, canonical URL) that are not syncing correctly. - The exact content item or items affected — including the article or page name and any relevant URLs. - A description of the behavior you are seeing — for example, whether fields are appearing blank, showing incorrect values, or not updating after a publish. - The timestamp of when you last attempted to publish and observed the issue. - Any error messages displayed in the Search Atlas interface during or after publishing. 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.

📥 Export OTTO AI Suggestions for Webflow Integration

🔍 Overview When you deploy title, meta, or on-page suggestions through OTTO, Search Atlas keeps a record of every accepted change. If you manage your site in Webflow or another external CMS, you can export these deployed suggestions as a reference file — so you always have an accurate, up-to-date record of what was applied and can update your pages directly. This article explains how to locate and download your deployed AI suggestions from the OTTO project dashboard. 🧭 Before You Begin Make sure you have at least one active OTTO project with deployed suggestions. If your project shows no deployed items, the export will be empty. You can confirm deployment status by reviewing your suggestions list inside the project. 📋 How to Export Your Deployed AI Suggestions 1. In the left sidebar, navigate to OTTO SEO → All Sites (SEO Automation) to open your project dashboard. 2. Locate the project you want to export from within your project list. 3. Look for the export or download option associated with that project. The exact label or icon may vary depending on your account view — look for a download or export control near the project entry. 4. Click the export control. Search Atlas will generate and download a file containing your AI Suggestions record for that project. 5. Open the downloaded file. It contains your suggestion data — including deployed titles, meta descriptions, and other on-page recommendations — formatted for easy reference. 6. Use this file as your source of truth when updating pages directly inside Webflow or any other external CMS. 📂 What the Export May Include - Page URLs — the exact pages OTTO generated suggestions for - Suggestion type — for example, title tag, meta description, heading - Suggested content — the AI-generated text that was accepted and deployed - Deployment status — confirms which suggestions were applied This gives you a portable record you can hand off to a developer, import into a spreadsheet, or reference while making edits inside Webflow. 💡 Tips for Webflow Users - Run your export after each OTTO optimization session so your Webflow pages stay in sync with the latest deployed suggestions. - If you manage multiple sites, repeat these steps for each project separately. Each project has its own export. - If you cannot locate the export option in your dashboard, a member of our team can walk you through the exact steps for your account. 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.

💡 Wix OTTO SEO Title Tags and Credit Refunds

🔍 What This Article Covers If you used Search Atlas credits to generate OTTO SEO title tag suggestions for your Wix site and expected them to publish automatically, this article explains how the Wix integration works, why auto-sync is not currently supported, and what steps to take if you believe credits were spent in error. ⚙️ How the Wix Integration Works Search Atlas connects to Wix through an authorised credential link. Once connected, the platform can analyse your Wix pages and generate AI-powered SEO suggestions — including title tags — directly inside the Search Atlas dashboard. However, there is an important limitation to be aware of: - OTTO SEO title tag suggestions do not auto-publish to your Wix site. They are generated as recommendations only. - To apply a suggested title tag, you must manually copy it and update the field inside your Wix site editor or Wix SEO settings panel. - Credits are consumed at the point of generation, not at the point of publishing. This behaviour applies to all Wix-connected sites regardless of your subscription plan. 📋 Why Credits Are Used at Generation When you request OTTO SEO title tag suggestions, the platform immediately uses computing resources to analyse your page content, evaluate keyword relevance, and produce optimised recommendations. This process consumes credits whether or not you choose to apply the suggestions to your site. This is consistent with how AI-generated content works across other areas of the platform — credits reflect the cost of generation, not the outcome. 🛠️ How to Apply Title Tag Suggestions to Your Wix Site 1. Open your Search Atlas dashboard and navigate to the page where your AI title tag suggestions were generated. 2. Copy the recommended title tag text. 3. Log in to your Wix account and open the Wix Editor or go to Marketing & SEO > SEO Tools > SEO Basics. 4. Locate the relevant page and paste the title tag into the Title Tag field. 5. Save and publish your changes in Wix. Completing these steps ensures your AI-generated title tag is live on your site. 💬 Requesting a Credit Review If you believe credits were spent due to unclear guidance about how the Wix integration works, you may be eligible for a credit review. Search Atlas does not offer automatic refunds for generated suggestions, but our team can assess your case individually. To request a review, please have the following information ready: - The date and approximate time the credits were used - The number of credits you believe were spent in error - A brief description of what you expected to happen versus what occurred Credit reviews are assessed on a case-by-case basis and are not guaranteed. Submitting a request does not automatically result in a credit restoration. 🚀 Preventing This Issue in the Future To avoid unexpected credit usage going forward: - Before generating AI suggestions, confirm that your Wix credentials are connected and in an active state inside the Search Atlas dashboard. - Review the suggestion preview before confirming generation if a preview option is available for your plan. - Treat all AI-generated content as a starting point that requires manual review and manual publishing on your Wix site. If your Wix credentials appear disconnected or you are prompted to reconnect your site, resolve the connection first before generating new suggestions to ensure credits are used effectively. 🙋 Need Further Help? 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.

🌐 Wix Integration: Automatic vs. Manual SEO Implementation

🔍 Overview Search Atlas connects with Wix to help you optimize your site for search engines. However, due to limitations in the Wix platform itself, not all OTTO SEO suggestions can be applied automatically. This article explains what you should know about Wix integration limitations and how OTTO SEO credits work with your Wix site. ⚙️ How the Wix Integration Works When you connect your Wix site to Search Atlas, the integration allows our platform to read your site's structure, pages, and existing metadata. This enables our AI to analyze your content and generate targeted SEO suggestions. However, Wix operates on a closed, proprietary platform that restricts third-party tools — including Search Atlas — from directly writing changes back to your site in many cases. This means Search Atlas functions primarily as an analysis and recommendation engine for Wix sites, rather than a fully automated implementation tool. ✅ What May Be Applied Automatically on Wix Depending on your Wix site configuration and the page types involved, some SEO changes may be pushed automatically through the Search Atlas integration. Automatic implementation is subject to what Wix's API permits for your specific pages and account setup. If you are unsure whether automatic implementation is available for a specific page or field on your site, please reach out to our team for clarification before generating suggestions. ✏️ What May Require Manual Implementation on Wix Because of Wix's platform restrictions, many SEO changes cannot be applied automatically by Search Atlas. In these cases, Search Atlas provides you with the recommended changes, and you apply them directly inside your Wix Editor or Wix dashboard. The types of changes that may need to be made manually depend on how Wix exposes access for your particular site and page types. Our suggestions include instructions to help guide you through the process inside Wix. 💳 How OTTO SEO Credits Are Used If you have questions about how OTTO SEO credits are consumed in relation to the Wix integration — for example, when credits are charged and what actions they apply to — our support team can clarify this based on your specific plan and usage. Please reach out before generating a large batch of suggestions if you have concerns about credit consumption. 📋 What to Have Ready When You Contact Us To help our team assist you as quickly as possible, please have the following information ready: - Your Search Atlas project name or the URL of your Wix site - The specific page type you are working with (e.g., standard page, blog post, dynamic page) - A description of the suggestion or action you attempted and what happened - Any error messages you encountered, including exact wording 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.

🔗 Wix Integration Limits and OTTO SEO Credits Explained

🌐 How Search Atlas Connects with Wix Search Atlas integrates with Wix through OTTO SEO, our AI-powered optimization engine. However, Wix is a closed website platform, which means it places strict limits on what third-party tools can automatically change on your site. These platform-level restrictions are set by Wix — not Search Atlas — and they affect how OTTO SEO suggestions are delivered and applied. ⚠️ Why Suggestions Don't Auto-Install on Wix Unlike open platforms such as WordPress, Wix does not allow external tools to automatically write changes directly to your site's pages, metadata, or content. As a result, OTTO SEO operates in manual implementation mode for Wix sites. This means: - OTTO SEO suggestions are generated and displayed inside your Search Atlas dashboard. - You must log in to your Wix editor and apply each recommendation yourself. - OTTO cannot push changes, inject code, or modify your site's structure automatically. This is a known limitation of the Wix platform and applies to all third-party SEO tools that integrate with it. 🔑 Wix API Key Requirements For the integration to function correctly — including blog-related recommendations — your Wix API key must have the correct permissions enabled. A common issue that prevents OTTO from retrieving data is a missing or misconfigured permission. Make sure your Wix API key has the 'Manage Blog' permission enabled. If this permission is absent or the key has expired, category and content data will not load, and some recommendations may not generate as expected. To check or update your API key permissions: 1. Log in to your Wix account and go to Settings → Advanced → API Keys. 2. Locate the key connected to Search Atlas. 3. Confirm that Manage Blog is toggled on. 4. If the key is expired, generate a new one and update it inside your Search Atlas dashboard under your Wix integration settings. 💡 How OTTO SEO Credits Are Used OTTO SEO credits are consumed at the point when suggestions are generated — not when they are applied to your site. This is important to understand for Wix users because the credit usage happens during the analysis and recommendation creation process, regardless of whether your platform supports automatic implementation. Here is how the credit process works: - Credit deducted: When OTTO analyzes your page and produces an OTTO SEO suggestion. - No additional credit: Viewing, copying, or manually applying a suggestion does not use extra credits. - Credit not refunded: If a suggestion was successfully generated and delivered to your dashboard, the credit has been used — even if you expected automatic installation. 🔄 Can I Get Credits Refunded? Credits are consumed during the generation process and are generally non-refundable once a suggestion has been successfully produced. However, if you believe credits were deducted due to a technical error — for example, if OTTO failed to generate any recommendations despite the process appearing to complete — this may qualify for review. Situations that do not qualify for a credit refund include: - Suggestions were generated but you did not apply them manually. - You expected automatic installation but the Wix platform limitation prevented it. - You changed your mind about optimizing a particular page. Situations that may qualify for review include: - OTTO showed an error during generation and no suggestion was delivered. - A confirmed platform or system error caused the process to fail on our end. ✅ Best Practices for Wix Users To get the most value from your OTTO SEO credits on a Wix site, follow these recommendations: - Before generating suggestions, ensure your Wix API key is valid and has all required permissions. - Review your existing suggestions in the dashboard before generating new ones to avoid duplicate credit usage. - Use the Search Atlas dashboard as your central reference and manually implement each recommendation in your Wix editor. - Prioritize high-impact pages — such as your homepage and top-traffic landing pages — when applying manual changes. 🛠️ Troubleshooting Common Wix Issues - Recommendations not generating: Check that your Wix API key is active and has 'Manage Blog' permission. Re-connect the integration if needed. - Blog categories not loading: This is usually caused by an expired or incorrect API key. Update the key and reconnect. - OTTO pixel not tracking: Wix requires manual pixel installation. Follow the in-platform instructions to add the OTTO pixel code to your Wix site header. 💬 Need More Help? 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.

🔌 Wix CMS Connector: Common Failures and How to Fix Them

🛠️ Common failure modes and fixes 🔑 Auth error — connector marked as invalid Cause: Your Wix OAuth token has expired, or your Wix API Key is missing a required permission. A common case is the API Key lacking the Manage Blog permission, which surfaces as: Categories endpoint failed: Invalid or expired API Key. Please ensure your Wix API Key has the 'Manage Blog' permission enabled. Fix: Delete the connector in Account Menu → Settings → CMS Connectors and reconnect with a fresh OAuth authorization. Make sure you authorize all requested permissions, including Manage Blog. The connector now tracks and exposes its credential status, so an invalid or disconnected connector is flagged in the UI before publishing; use the reconnect flow to restore it. 🔍 Meta-site not found — sync fails resolving the Wix site Cause: The credential can't be matched to a valid Wix site (meta-site), shown as Categories endpoint failed: meta-site not found. Fix: Reconnect the connector and authorize the correct Wix site so the credential is bound to a resolvable meta-site. 👤 Missing member — publish fails with member_id required Cause: No author/member was selected in the connector settings. Fix: Edit the connector and select a valid Wix member as the default author. The member must exist in your Wix site's member list. ⏳ Rate limit — publish hangs Cause: Wix API rate limit hit during batch publishing. Fix: Handled automatically with retry logic. Wait a few minutes; the publish will complete on its own. ✅ Post-publish verification error codes - CONTENT_MISSING — article didn't appear; try republishing - PAGE_NOT_ACCESSIBLE — page is live but returns an error when accessed - CONTENT_MISMATCH — content on page doesn't match what was sent Contact support with the error code and article URL if the issue persists after republishing.

🛠️ Troubleshooting the Contentful CMS Connector: Invalid or Expired Management API Token

🔧 Contentful Connector Authentication If your Contentful connector reports an invalid or expired Management API token, verify the token, Space ID, and permissions shown in your current Search Atlas connector setup. 🔍 Common causes - The token was revoked or regenerated in Contentful. - The Contentful user who created the token was removed or had permissions reduced. - The token does not have access to the selected Space, content types, or assets. - The Space ID in Search Atlas does not match the selected Contentful Space. - The token was copied with missing characters or extra whitespace. 🛠️ Troubleshooting 1. In Contentful, confirm that the token is active and has access to the target Space. 2. Confirm the Space ID in Search Atlas matches the Contentful Space. 3. In Search Atlas, open Settings → CMS Connectors and select the affected Contentful connector. 4. Follow the connection fields and actions currently displayed in the Search Atlas interface. 5. Save the connection and check whether its status becomes active. If the connector remains invalid, contact support with the exact error, Space ID, and a screenshot. Do not share the token itself. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate.

🔌 Webflow CMS Connector: Common Failures and How to Fix Them

🛠️ Common failure modes and fixes 🔑 Authentication error — connector marked invalid Click Reconnect and complete Webflow provider sign-in in the new tab. If the provider sign-in was cancelled or expired, start the reconnect flow again and wait for the connection status to update. 📁 Missing collection — publish fails immediately Edit the connector and select a valid Webflow collection before publishing. Confirm that the collection still exists in Webflow. 🧩 Custom field schema mismatch — publish fails Make sure the Webflow collection fields match the connector mapping. If fields were renamed, removed, or retyped, update the mapping and republish. ⏳ Rate limit — publish hangs or times out Search Atlas retries temporary Webflow rate-limit errors automatically. Wait 5–10 minutes and check the publish status. If the job remains pending, reconnect the connector and retry. 🖼️ Featured image missing Confirm the source image is accessible, then re-upload it in Content Genius and republish. If the connector still fails after reconnecting, open the chat widget in the bottom-right corner of the platform and type human teammate.

💸 Why You're Being Billed by Both Shopify and Search Atlas

🤔 Why you have two bills This happens when a customer signed up for Search Atlas in two different ways: 1. Through the Shopify App Store — creates a Shopify-managed account; Shopify handles billing 2. Directly on searchatlas.com — creates a separate Search Atlas account; Search Atlas handles billing These are two independent accounts and you may be charged by both. Two separate accounts each paying for their own plan is expected. However, being charged twice for the same plan and period — for example a Shopify charge and a Search Atlas credit-card charge that both cover the same subscription — is not expected and should be treated as a billing error. If you see this, contact Search Atlas support so it can be investigated and corrected. ⚠️ Important: Search Atlas cannot manage your Shopify billing If you subscribed through Shopify, Search Atlas does not control or have access to your Shopify billing. Any refund, cancellation, or plan change for the Shopify subscription must be handled directly through your Shopify admin panel. 🔄 Charged through Shopify but can't access the app? If your Shopify payment went through but Search Atlas keeps redirecting you to the pricing/subscribe page, your subscription may not have been provisioned on the Search Atlas side. A known issue caused some Shopify App Store purchases to be charged without activating the account; this has been fixed. If you're affected: - Contact Search Atlas support so your subscription can be provisioned manually and your access restored. - Have your Shopify store domain and a copy of the Shopify charge/invoice ready — support uses these to locate and reconcile the charge. - If you were billed without ever receiving access, ask support about a refund for the affected Shopify charge(s). ✅ How to resolve duplicate billing 1. Decide which account you want to keep 2. Cancel the account you don't want: - For Shopify: go to your Shopify admin > Apps > Search Atlas > Uninstall - For direct Search Atlas: go to Billing > Services > Cancel 3. Contact Search Atlas support if you need help migrating data before canceling If Shopify keeps charging you after you uninstall the app, contact Search Atlas support. A recently fixed issue could leave a Shopify-sourced subscription active even after cancellation, and support can confirm the charge has actually stopped.

🛠️ Shopify Plan Upgrade Not Provisioning After Payment

If your Shopify plan payment went through but Search Atlas keeps prompting you to select a plan, resetting your Search Atlas password and logging in with email and password — not SSO — resolves the issue in most cases. This fix applies to any Search Atlas plan purchased or upgraded through Shopify. If you cannot connect your Shopify store as a CMS connector or content source, see Shopify CMS Connector Troubleshooting instead. White Label / Agency Hub users: If you upgraded a child account plan from the Agency dashboard and the change appears saved but is not reflected on the child account, this is a separate known issue. Contact support and reference WL billing sync. 🔍 Why Shopify Upgrades Sometimes Cause a Sign-In Loop Search Atlas supports two ways to create and access an account: directly on the Search Atlas website using email and password, or through a Shopify-connected signup. When you upgrade through Shopify, the platform links your billing to your Shopify identity. If your Search Atlas account was originally created outside of Shopify, these two identities can become mismatched — causing the platform to repeatedly ask you to select a plan even though your payment was confirmed. 🛠️ How to Fix the Sign-In Loop First, clear your browser cache and cookies, or open an incognito/private window and attempt to log in. If the plan-selection screen still appears, follow the steps below in order. 1. Reset your Search Atlas password. Go to the Search Atlas login page and click Forgot password?. Enter the email address associated with your account and follow the reset link sent to your inbox. 2. Log in with email and password — not SSO. After resetting, return to the login page and enter your email and new password directly. Do not select Sign in with Shopify or any other single sign-on (SSO) option for this attempt. If your plan is correctly provisioned, you will land on the Search Atlas dashboard without being redirected to a plan-selection screen. 📞 If the Sign-In Loop Continues Contact Search Atlas support. An agent can review your account's authentication configuration and Shopify billing linkage directly, and a backend specialist team can manually reconcile the identity mismatch. When reaching out, include: - The email address used on both your Shopify and Search Atlas accounts - Your Shopify payment receipt confirming the upgrade - A screen recording or screenshots showing the sign-in loop - The date your Shopify upgrade payment was confirmed If this issue prevented you from accessing your account for one or more days after payment, mention the affected dates when contacting support to request a service credit. 🎯 A sign-in loop after a Shopify upgrade is typically caused by an authentication method mismatch between your Shopify identity and your Search Atlas account. Resetting your password and switching to email-and-password login resolves it in most cases — if the issue persists, contact Search Atlas support to investigate your account linkage and discuss any access credits.