How can we help?

🔍 Overview If you received a Google Search Console (GSC) email flagging a schema-related warning tied to a meta description after an OTTO Local SEO update, you are not alone. This is a known, non-critical notification that occurs when OTTO deploys Local SEO schema to your site. No action is required on your part. This article explains what triggered the warning, what it means, and why it is safe to ignore. ⚙️ What Triggered the Warning When OTTO applies a Local SEO update to your site, it injects structured data (schema markup) to help search engines better understand your business information — such as your name, address, phone number, and hours of operation. As part of this deployment, GSC may detect a mismatch between certain schema fields and page-level meta elements, including the meta description. This mismatch triggers a schema warning in GSC and, in some cases, an automated notification email from Google. This is a side effect of how Google validates structured data. It does not indicate a problem with your site, your rankings, or the quality of the schema OTTO deployed. 🟡 Warning vs. Error — What Is the Difference GSC distinguishes between two types of structured data issues: - Errors: Critical problems that prevent Google from processing your schema. These require immediate attention. - Warnings: Non-critical notices that flag a potential inconsistency. Google can still read and use your schema. Warnings do not cause your pages to lose rich result eligibility. The meta description schema warning generated by an OTTO Local SEO update is a warning, not an error. Your schema is valid, functional, and being processed by Google correctly. ✅ Should You Be Concerned No. Schema warnings related to meta descriptions after an OTTO Local SEO deployment are expected behaviour and are completely safe to ignore. Here is why: - The warning does not affect your search rankings. - The warning does not remove or invalidate the Local SEO schema OTTO applied. - The warning does not trigger any manual action or penalty from Google. - Google continues to index and understand your structured data normally. You do not need to modify your meta descriptions, remove the schema, or make any changes to your site in response to this warning. 📋 How to Confirm the Warning Is OTTO-Related If you want to verify that the GSC warning is connected to your OTTO Local SEO update, follow these steps: 1. Log in to Google Search Console and navigate to the structured data or schema-related section of your property. 2. Locate the warning associated with your Local Business schema or the affected URLs. 3. Check the warning timestamp and compare it to the date OTTO deployed the Local SEO update on your site. 4. If the dat

Troubleshooting: Titles, Meta & Headings

🛠️ OTTO Metadata Fields Not Saving Fixes

🔍 Overview Some users found that manually edited metadata fields in OTTO — including meta titles, meta descriptions, meta keywords, and Twitter site fields — appeared to accept new values but did not save or deploy them. The platform would show the edited text without actually applying the changes. This was caused by a confirmed bug where the platform stored the text but silently failed to complete the save and deployment process. This bug has been fixed and the resolution is now live. ✅ What Was Happening To be specific, the issue affected the following fields when edited manually inside OTTO: - Meta title (title tags) - Meta description - Meta keywords - Twitter site fields When a user typed new values into these fields, the save action would appear to accept the input but failed to complete the approval and deployment step. As a result, the changes never took effect on the site, even though they appeared to be accepted in the interface. 🚀 Current Status: Bug Is Fixed The engineering team identified and resolved this issue. The fix was deployed and is now live. You should be able to manually edit and save metadata fields in OTTO without any problems. If you were affected by this bug before the fix, your previously entered values may not have been deployed. You will need to re-enter and save those fields to ensure the changes are applied correctly. 📋 Steps to Re-Enter and Save Your Metadata 1. Open the OTTO session for the affected site. 2. Navigate to the on-page metadata section where the affected fields are displayed. 3. Manually re-enter the values for any fields that did not save previously, such as meta title, meta description, meta keywords, or Twitter site fields. 4. Save the changes. The approval and deployment steps should now complete successfully. 5. Verify that the saved values are reflected as approved and that the changes have been deployed to your site. 🆘 Still Experiencing Issues? If you re-enter your metadata values and they still do not save or deploy correctly after the fix, please let us know by reaching out to our support team so we can investigate further.

Pixel Installation: General Setup & Verification

🔧 Installing OTTO Tracking on a Website Studio Site

If you built your site from scratch in Website Studio and want to track it with OTTO, you do not need a separate plugin or integration. Website Studio includes a built-in option for adding custom scripts directly in the project settings, and this is where your OTTO tracking script goes. Where to Find the Setting Open your project in Website Studio and navigate to the project settings area. Look for a section dedicated to custom scripts or code embeddings — this is where you can inject code into your site's page header. How to Install the OTTO Script Within the custom scripts or embeddings section of your project settings, locate the field for header code — this is where scripts injected into the page's <head> belong. Tracking pixels such as OTTO are meant to go in the header area rather than the footer. To install OTTO, copy the OTTO tracking script from your OTTO project and paste it into the header code field in your Website Studio project settings, then save your changes. What to Expect This is a general-purpose custom code field rather than a dedicated, one-click OTTO integration. There is no automatic site detection step for Website Studio the way there might be for some other platforms, so double-check that the full script tag is pasted correctly before saving. Once saved, OTTO will begin tracking the site the same way it does on any other website where the script has been added to the header. 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.

Updates: Platform & UI Updates

📅 LinkedIn Post URLs Now Display Correctly in Calendar

A bug caused published LinkedIn posts to display "No URL available" in the Social Calendar despite having a valid published URL. This fix ensures post links are correctly shown for all published LinkedIn content. ✨ What's New LinkedIn posts that have been successfully published will now display their correct post URL in the Social Calendar view. Previously, the calendar was failing to surface the URL even when the post was live, showing "No URL available" instead. This has been resolved so you can quickly access and share your published LinkedIn content directly from the calendar. 🛠️ How to Use It 1. Navigate to the Social section of the platform. 2. Open the Calendar view. 3. Locate any published LinkedIn post. 4. The post URL will now be correctly displayed alongside the published entry. 📋 What to Expect This fix applies to all LinkedIn posts with a Published status in the Social Calendar. No action is required on your part — URLs will populate automatically for existing and future published posts. Posts in draft or scheduled status are unaffected by this change. 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: Cloud Stacks Issues

Fix a Persistent Indeed Link in Cloud Stacks

🔍 What Is This Issue? Some users have reported that an Indeed URL — often linked to a company they do not own — keeps reappearing in their Cloud Stacks footers and Knowledge Graph even after they delete it. Because the stale value is retained at the database level, deleting it through the platform UI alone will not permanently remove it from previously created stacks. Resolving this issue requires escalation to a support engineer. ✅ Steps to Take Before Contacting Support 1. Check your Knowledge Graph settings: Navigate to your Knowledge Graph settings and look for any Indeed URL stored under your brand profile. If you see it, attempt to delete or clear it and save your changes. This ensures the UI-level value is removed, even though the underlying database-level value will still need to be cleared by an engineer. 2. Identify affected Cloud Stacks: Go to your Cloud Stacks section in the platform and review your existing stacks. Note which stacks are displaying the incorrect Indeed link in their footers. Record the names or IDs of these stacks so you can share them with the support team. 3. Confirm the Indeed URL is not intentional: Make sure the URL does not belong to a legitimate profile associated with your brand. If it is definitely not yours, proceed to contact support with that confirmation. 4. Gather key details to share with support: Before reaching out, have the following ready: the exact Indeed URL that keeps appearing and the names or IDs of the affected Cloud Stacks. 🧹 What the Support Engineer Will Do Once you contact support, a support engineer will review your account, identify the affected Cloud Stack records containing the stale Indeed URL, and manually remove the value at the database level. They will confirm once the removal is complete so you can verify the footers no longer display the incorrect link. To get this resolved, please contact the Search Atlas support team via live chat and share the details you gathered above. The support team will escalate to an engineer who can perform the database-level removal — this is the confirmed path to a permanent fix.

Billing: Unexpected & Duplicate Charges

⚡ Plan Upgrade Not Applied & Duplicate Charges

🔍 Overview In some cases, a plan upgrade may fail to apply to your account even though your payment was processed successfully. If you then attempt to upgrade again, you could end up with duplicate charges while your account still shows the old plan. This article explains what to do if this happens to you. ⚠️ Signs You May Be Affected - Your account still displays your previous plan (for example, Starter or Pro) after completing an upgrade payment. - You have two or more receipts or charge confirmations for the same upgrade. - Features associated with your new plan are not available in your account. 🛠️ Steps to Take Right Away 1. Do not attempt to upgrade again. Making additional payment attempts will not fix the underlying issue and may result in further duplicate charges. 2. Try logging out and back in. After a successful payment, your plan may take a moment to propagate. Log out of Search Atlas completely, wait 2–3 minutes, then log back in and check whether your plan has updated and the expected features are now available. 3. Clear your browser cache and hard-refresh. If the plan still shows incorrectly after logging back in, clear your browser cache (or open an incognito/private window) and reload your account page. Sometimes a stale cache causes the old plan to appear even after a successful upgrade. 4. Check your email for a confirmation receipt. Locate all payment confirmation emails you received for the upgrade attempt(s). Note the exact amounts, dates, and transaction IDs shown — you will need these if you need to escalate. 5. If the issue persists, gather your receipts and contact our support team. Collect all payment confirmations or receipts you received for the upgrade. Because applying the corrected plan and processing refunds for duplicate charges requires action from our billing and engineering team, please reach out to support so they can manually correct your account and issue any refunds owed. You can contact our team directly through Search Atlas support. 💡 What Happens After You Contact Support Once our team is notified, here is what you can expect: - Account correction: Our billing and engineering team will investigate and apply your upgraded plan to your account manually. - Duplicate charge refunds: Any duplicate payments will be identified and refunded to your original payment method. - Refund timeline: Refunds typically reflect in your account within 5–10 business days, depending on your bank or card issuer. 📋 Information to Have Ready To help our team resolve your case as quickly as possible, please have the following available when you reach out: - The email address associated with your Search Atlas account - All payment confirmation emails or receipts for the upgrade attempt(s) - The exact amounts, dates, and transaction IDs from those receipts If you are still experiencing issues, please reach out to our support team and we will be happy to help.