Home 🛠️ Troubleshooting

🛠️ Troubleshooting

Camilo Aponte
By Camilo Aponte
• 155 articles

🚨 Recover a Suspended Google Business Profile

Identify the suspension reason, collect the required documents, and submit Google's reinstatement form to get your Google Business Profile back online. 🔎 Confirm: Understand Why Your Profile Was Suspended What to do Check your Google Business Profile for the suspension alert and identify the reason. Why it matters Understanding the cause helps you respond with the right evidence and avoid repeating the issue. How to do it 1. Log into your Google Business Profile. 2. Look for the red "Suspended" banner at the top. 3. Click Learn more to view possible violations. 4. Review Google's guidelines for reinstatement eligibility. Common mistakes to avoid - Assuming it's a bug without checking the guidelines - Changing your business info before understanding the issue - Submitting an appeal without proper documentation Pro tip: Take a screenshot of the suspension message for reference — it may help when communicating with Google. ✅ Once done, you'll know what Google flagged and whether you're eligible to appeal. 🧾 Collect: Prepare the Required Documentation What to do Gather official documents that verify your business and location. Why it matters Google requires strong proof to confirm your business is legitimate and operating at the listed address. How to do it 1. Match your Google Business Profile info exactly to your website and documents. 2. Prepare the following items: - 📷 Storefront photo with signage (required) - 📹 Video walkthrough of storefront — show signage and address (required) - 🧾 Utility bill (required) - 🛡️ Business insurance (required) - 🪪 Business license or IRS/tax document - 💳 Business card (optional but helpful) 3. Rename each file clearly (e.g., utility-bill-mainstreet.jpg). Common mistakes to avoid - Submitting blurry or incomplete images - Using outdated or mismatched business information - Leaving out required items Pro tip: In your video, show the documents you're submitting — it builds trust with Google reviewers. ✅ Once done, you'll have a complete and clear verification package ready to submit. 📤 Submit: File a Reinstatement Request What to do Submit your case using Google's official reinstatement form. Why it matters This is the only accepted way to resolve a suspension directly with Google. How to do it 1. Visit the Google Reinstatement Form. 2. Fill out your business details exactly as listed in your Google Business Profile. 3. Upload your documents and include a brief message, for example: "I'm the owner of [Business Name] at [Address]. I've attached storefront images, utility bills, and insurance documents. Thank you for your review." Common mistakes to avoid - Skipping required fields or writing vague answers - Using a defensive or confrontational tone in your message - Omitting key documentation Pro tip: Start your timer as soon as the appeal screen appears — you only have 60 minutes to upload your documents. ✅ Once submitted, Google typically responds within 3–7 business days. 📚 Useful Official Resources - Fix suspended or disabled Business Profiles – Google Help The official guide explaining why profiles get suspended or disabled, and how to meet Google's requirements and improve eligibility for reinstatement. - Appeal a suspended or disabled Google Business Profile – Google Help The official Google Business Profile appeal tool and form for submitting your case and required documentation. 🌀 You now know how to confirm the cause of a suspension, prepare a solid documentation package, and file a reinstatement request with Google. For additional context, review Google's official Fix suspended or disabled Business Profiles guide.

Last updated on Oct 26, 2026

🗺️ Local SEO Heatmaps: Quota Exhausted Errors, Failed Top-Ups & Incorrect Pin Placement

When your heatmap shows "Quota Exhausted," your Local SEO Points for the current billing cycle have been fully consumed — or an expected top-up was never added. This article explains how points are calculated, when they reset, how to spot a failed recurring top-up, and how to fix a pin-placement bug that may have wasted credits. ⚠️ What "Quota Exhausted" Means Heatmaps draw from a pool of Local SEO Points included in your plan. Each pin on the heatmap grid costs 1 point per keyword layer. Once you've used all your points for the billing cycle, Search Atlas blocks new scans and displays "Quota Exhausted." 📊 How Heatmap Points Are Consumed Point usage scales with your grid size and keyword count: - Each grid pin = 1 Local SEO Point per keyword - A 7×7 grid with 1 keyword = 49 points - A 7×7 grid with 3 keywords = 147 points - Larger grids and more keywords consume proportionally more - Refreshing a heatmap costs the same number of points as creating it - Deleting a heatmap does not restore points already consumed 🔄 When Local SEO Points Reset Points reset monthly on your billing anniversary date — the day you subscribed or last changed your plan. This is not the 1st of the month. To find your exact reset date: 1. Click your Avatar Menu (👤) (top-right). 2. Select Billing. 3. Read your next billing date, displayed under your plan name. 💳 Failed Recurring Top-Up (Points Never Added) If you have a recurring Local SEO Points top-up — for example, 5,000 points for $50/month — those points are only added to your quota when the monthly charge succeeds. Charges most often fail because of an expired card, an invalid or removed payment method, or insufficient funds. When the charge fails, your top-up shows as Past Due and the extra points are never credited, so your quota runs out far sooner than expected. How to confirm a failed top-up To verify whether a top-up was processed, go to your Avatar Menu (👤) (top-right) → Billing → Activity Log. The Quota Log lists every Local SEO Point addition and every heatmap consumption, each with a timestamp. If your top-up date is missing from the log, the charge failed and no points were added. 1. Open Top-right corner (avatar) → Billing → Activity Log tab to review point activity. 2. Look for points being consumed normally but hitting the limit early, with no top-up credit added for the cycle. 3. Click your Avatar Menu (👤) (top-right) → Billing and check whether your top-up is marked Past Due. How to fix it 1. Check your payment method in Billing settings. 2. If your card is expired or invalid, update it. 3. The top-up will retry automatically within 24–48 hours, or you can retry the Past Due charge manually in Billing. 4. If it continues to fail, contact Support with your invoice number. Once the charge goes through, your top-up points are added to your quota and you can run heatmaps again. 🧾 Recurring vs. One-Time Top-Ups There are two ways to add Local SEO Points to your quota: - Recurring top-up: A fixed number of Local SEO Points added automatically each month when the charge succeeds (see the failed top-up section above). - One-time top-up: A single purchase of Local SEO Points that is auto-credited to your quota right after payment. One-time top-up points normally appear in your quota within 15 minutes of a successful payment. If they don't, open your order history under Billing to confirm the purchase completed, then contact Support if the points are still missing. Note: A past bug (QPB-786) caused some one-time top-ups to under-allocate Local SEO Points — crediting far fewer points than were purchased. This has been fixed. If you bought a one-time top-up previously and your quota looks lower than expected, check your Quota Log and contact Support so we can review and correct the allocation. ❓ Common Misconceptions About Points "I deleted heatmaps — why didn't my points come back?" Points are consumed at creation or refresh time. Deleting a heatmap does not refund them. "I only created a few heatmaps." Check your grid size and keyword count. A single large heatmap can consume hundreds of points. "My points should have already reset." Resets happen on your billing anniversary date, not the 1st of the month. Check Billing for your exact date. "I have a recurring top-up — why is my quota so low?" If your top-up charge is Past Due, the points were never added this cycle. Check your Quota Log and update your payment method in Billing. 📍 Incorrect Pin Placement (Lat/Long Bug) If your heatmap pins appear in the wrong geographic location — for example, dropped in Lake Michigan, or 250–375 miles away from your actual business address — even though the correct address is saved in your business profile, this is a geocoding issue, not a quota issue. It most commonly affected Service Area Business profiles, where the heatmap coordinates were resolved incorrectly from the saved address. This was a known bug affecting how heatmap coordinates were resolved from saved addresses. It has been resolved by our engineering team. Retry your heatmap to confirm that pins now display in the correct location. How to correct misplaced pins 1. Open the affected heatmap and drag the pin to the correct location, or reconfirm your business address in your profile. 2. Rerun the heatmap to generate accurate results. 3. Delete the incorrect scans that returned false results. Note that deleting a heatmap does not restore the Local SEO Points already consumed. Were your Local SEO Points consumed by an affected scan? If you ran heatmaps that returned false results due to incorrect pin placement, you may be eligible for a refund of those Local SEO Points. Contact Support with: - The affected business location(s) - The date(s) the impacted heatmap scans were run - The number of Local SEO Points you'd like reviewed (e.g., "2,000 Local SEO Points") 🛠️ How to Fix a Quota Exhausted Error Choose the option that fits your situation: - Fix a failed recurring top-up: If your top-up is Past Due, update your payment method or retry the charge in Billing so the points are added. - Top up immediately: Click your Avatar Menu (👤) (top-right) → Billing → Plans & Top-ups → Top Up. - Upgrade your plan: Higher plans include more Local SEO Points per month. - Wait for your reset: Points reset on your next billing date. Check Billing to see the exact date. - Request a Local SEO Points refund (specific cases only): If points were consumed by scans affected by the pin-placement bug, contact Support with the details listed above. 🎯 You now know how to read your Quota Log, confirm whether a Past Due top-up left points uncredited, and choose the right fix — top up, update your payment method, upgrade, wait for your reset, or request a refund. If your top-up still won't process or your Quota Log doesn't match what you expect, contact Support so we can review your account.

Last updated on Oct 26, 2026

📍 How to Manually Update Your GBP Appointment URL in Search Atlas

You updated your Appointment URL (this field may appear as either Appointment URL or Booking Link depending on your view — both refer to the same setting), everything looks correct… and yet it still says **“Not Deployed.”**If you’ve ever wondered whether the change failed, if you need to edit it again, or if Google is simply taking its time, you’re not alone. The confusion usually isn’t about what to update, but how those updates actually go live. In this guide, we’ll break down exactly how deployment works inside your GBP Project, what “Not Deployed” really means, and how to make sure your booking link is properly pushed to Google so Google’s review of your change isn’t reset by a second edit before the first one finishes. 🧠 What’s happening? You updated the Appointment URL (this field may appear as either Appointment URL or Booking Link depending on your view — both refer to the same setting) inside your GBP Project (for example, rubbl.com.au), but: - You see “NOT DEPLOYED” - The change isn’t live on Google - You can’t find the “Deploy” button - Or you’re unsure whether to edit manually again Good news: you’re in the right place. Let’s walk through it clearly. 📌 Navigation Path Left Sidebar → Local → Select Your GBP Project Once inside the project, you’ll land on the GBP Overview. From the GBP Overview, open the Business Info tab and scroll to the Business Data Optimizations panel. From there: - Scroll to Business Data Optimizations - Locate your Booking Link / Appointment URL — this field may appear under either label depending on your view, but both refer to the same setting 🔧 Why It Says “Not Deployed” There are two distinct states to be aware of when editing the Appointment URL inside Search Atlas — they are not the same thing: - Unsaved change (draft) — your edit exists only in the form field in your browser and has NOT yet been recorded in Search Atlas. The fix: click Save (or confirm the edit) so the change is captured in Search Atlas. - Saved but Not Deployed — the change is now stored in Search Atlas, but it has NOT yet been pushed to Google and Google has not reviewed it. The fix: click Deploy all changes to send the update to Google. That’s why you’ll see: ⚠️ “You have 1 unsaved change” Status: NOT DEPLOYED This is normal — it just means the next action (Save, then Deploy) is still yours to take. ✅ How to Properly Publish the Appointment URL Before you begin: ensure the Google account connected to Search Atlas has Owner or Manager access to the GBP listing. Viewer-level access will not allow changes to be pushed, and deployments may silently fail. Step 1: Click Edit Find your Booking Link / Appointment URL section and click Edit. Update the URL. Example: https://rubbl.com.au/rubbish-removal/book-online Step 2: Click “Deploy all changes” At the top of the Business Data Optimizations section, you’ll see: 🟠 Deploy all changes Click it. This pushes the update to Google. After clicking, the status should change from NOT DEPLOYED to Pending Google sync (or similar) — that confirms the push was accepted. ⏳ What Happens After Deployment? Once deployed: - Your update goes into Google Review - Google must approve the change - The typical Google propagation window is 24–72 hours. In practice this can be: - A few minutes - A few hours - Occasionally longer (up to 72 hours, sometimes more) - While waiting, the status inside Search Atlas should read Pending Google sync (or remain as Deployed pending review). Do not re-edit during this window — the change has been accepted and is on its way. You may see a message like: “Your updates must be reviewed by Google before they go live.” This is expected behavior. Once Google approves the change, check your live Google Business Profile to confirm the new Appointment URL is showing. If the status shows Deployed but the change is still not visible on Google after 72 hours, your GBP project connection may need to be re-verified — see the troubleshooting section below or contact support for assistance. ❗ Important: Do NOT Edit Again After Deploying Once you click Deploy all changes, you do NOT need to manually edit again. If you edit the field a second time before the first deployment completes, the new edit will overwrite the in-flight change and reset Google’s review cycle from the beginning. Concretely, this can: - Create confusion about which version of the URL is currently being reviewed - Reset the review cycle, delaying when your update actually goes live on Google - Cause deployment conflicts that may require support to resolve If deployment has been triggered, just wait for Google’s review. 🔍 What If You Don’t See the Deploy Button? If you only see: - “Refresh Optimization Tips” - “Pull Latest Data” It may mean: 1. There are no pending changes 2. The deployment was already triggered 3. Your screen needs refreshing Try: - Refreshing the page - Scrolling to the top of Business Data Optimizations - Checking for the orange deployment banner If the Deploy button is still missing, greyed out, or the status remains NOT DEPLOYED for more than 24 hours without changing: - Verify your GBP project connection is active under Avatar Menu (👤) → Settings → Integrations. A silently disconnected GBP project can make deployments appear stuck, and a disconnected project will not push changes to Google even if the deploy appears successful in Search Atlas. - Disconnect and reconnect your Google Business Profile account under Avatar Menu (👤) → Settings → Integrations, then retry the deployment. - Confirm the connected Google account has Owner or Manager access to the GBP listing — Viewer-level access will hide or disable the Deploy action. - If the button remains absent after a page refresh and reconnection, contact Search Atlas support. 🚀 Best Practice Moving Forward ✔ Edit once ✔ Click Deploy all changes ✔ Wait for Google review ✔ Do not re-edit during review If your GBP Appointment URL says Not Deployed, it doesn’t mean it failed, it just hasn’t been pushed to Google yet. Click Deploy all changes, allow Google’s review process, and your update will go live shortly.

Last updated on Oct 26, 2026

📍 Local SEO & Google Business Profile Connection Fixes

Use this article to reconnect a Google Business Profile (GBP) that shows as disconnected, clear the Google OAuth Error 400: invalid_request during a GBP Audit, and troubleshoot local rankings that show no data. Each fix below is a self-contained set of steps. 📋 How Local SEO syncing works in Search Atlas Local SEO in Search Atlas relies on Google APIs, Google Maps indexing, citation aggregators, geolocation data, and asynchronous sync cycles. Because these systems update on their own schedules, short delays between an action and visible results are normal. - Ranking and review data update on recurring sync cycles, not instantly. - Some sync jobs can take up to 1 hour to finish after you reconnect. - Reconnecting a Google account does not delete your historical Local SEO data. ⚠️ Fix a Google Business Profile that shows "Disconnected" A "Disconnected" status means your Google authorization token expired, your permissions changed, or Google invalidated the connection during a security refresh. While disconnected, rankings stop updating, reviews stop syncing, GBP posts fail, geo-grid scans go stale, and Local SEO reports may show incomplete data. 🔁 Reconnect your GBP account 1. Go to Avatar (top-right) → Settings → Integrations → GBP card → View Connected Accounts. 2. Click Disconnect, then click Connect Google Account to reconnect fresh. 3. Log in with the same Google account that owns or manages the GBP listing. 4. Approve all requested permissions, and confirm that Maps and Business Profile permissions are granted. 5. Wait 15–30 minutes for synchronization to restart. 6. Hard-refresh the dashboard — Windows: Ctrl + Shift + R, Mac: Cmd + Shift + R. Note: The initial count of businesses shown in the Connect Account modal may not reflect all your Google Businesses — the full count displays after connection completes. Note: After reconnecting, you may keep receiving notifications for a few minutes while the system updates your account status. This is normal. ✅ Confirm rankings are flowing again Go to Left Sidebar → Local → Local SEO Heatmaps (then click the View button for your listing → View Your Local SEO Heatmap), then check the Keyword Ranking Score. Fresh ranking scans appearing again confirm the connection is healthy. 🛠️ If your GBP keeps disconnecting - Remove the GBP integration completely, then reconnect from scratch and wait for a full sync cycle. - Contact support if reconnection fails repeatedly, the account reconnects but instantly disconnects, or no Local SEO data returns after 1 hour. ⚠️ Fix Google OAuth "Error 400: invalid_request" during a GBP Audit When Google rejects the connection as non-compliant with OAuth 2.0 policy and shows Error 400: invalid_request as you start a GBP Audit, your stored Google authorization is no longer valid. Reconnect the account to generate a new, valid authorization. 🔑 Re-authorize your Google account 1. Log into Search Atlas and open your Google account connection settings. 2. Click Disconnect on the connected Google account. 3. Click Connect Google Account and sign in with the Google account that manages the GBP listing. 4. Approve all requested permissions to establish a new valid authorization for the GBP Audit. 5. Run the GBP Audit again. If the error persists after reconnecting, contact support — the team can resolve it on the backend, usually within a few minutes. You'll be able to run the GBP Audit once the new authorization is active. ⚠️ Fix local rankings that show "No data" A geo-grid scan can show no data while it is still processing, when the listing has weak local authority signals, or when the location parameters are configured incorrectly. This most often affects new GBP listings, recently verified businesses, and incorrectly configured geo-grids. 🗺️ Check your listing and address - Verify your GBP listing is publicly visible on Google Maps. - Confirm the business address matches exactly across your GBP, Search Atlas, citations, website footer, and schema markup (NAP consistency). 📊 Check your geo-grid settings 1. Go to Left Sidebar → Local → Local SEO Heatmaps (then click the View button for your listing). 2. Confirm the target city, ZIP/postal code, radius, and keywords are correct. 3. Temporarily reduce the scan radius — smaller grids process faster and help isolate visibility issues. 4. Trigger a manual scan refresh: click View Your Local SEO Heatmap, then hover over the date area. Fresh scores appearing on the heatmap confirm the scan completed successfully. 📝 If GBP posts don't appear on Google If GBP posts created in OTTO aren't showing up on your Google Business Profile, this is typically a sync or permissions issue. Work through these checks in order: 1. Verify that OTTO sync is enabled for the GBP listing. 2. Check that the connected Google account has GBP posting permissions for the listing. 3. Clear your browser cache, or try again in an incognito/private window. 4. If posts still don't appear after a full sync cycle, contact support so the team can investigate on the backend. 🗺️ If your business location isn't updating If your service area or business location doesn't update after a relocation, clear the existing citation data or manually sync the location from your GBP listing, then allow a sync cycle to complete. Underlying sync issues affecting location updates have been fixed recently, so a fresh sync should now apply the new location. If the location still doesn't update, contact support. 🛠️ GBP completion score stuck or not updating If your GBP completion score appears stuck (for example, at 95%) or won't update, this is a known bug affecting completion scoring. Our engineering team is tracking it, and it does not reflect a problem with your listing or connection. Contact support if you'd like to be notified when the fix is released. 🛠️ If GBP data in reports won't load If GBP data in your reports shows a loading spinner and won't complete, refresh the page or clear your browser cache. If this persists, contact support. 🎯 You now know how to reconnect a disconnected GBP, clear the OAuth Error 400: invalid_request during a GBP Audit, and troubleshoot empty local rankings. If a fresh reconnection doesn't resolve the error or no data returns after 1 hour, contact Search Atlas support so the team can finish the fix on the backend.

Last updated on Oct 26, 2026

🛠️ GBP Scheduled Posts Stuck in "Scheduled" Status — Not Publishing

If your Google Business Profile posts show Scheduled status in Search Atlas but never appear on Google, a platform issue may have caused them to get stuck. Use this guide to identify the affected posts and reschedule them so they publish successfully. 📋 What "Stuck in Scheduled" Means for GBP Posts When you schedule a GBP post in Search Atlas, the platform queues it for delivery to Google's API at the chosen date and time. A post stuck in Scheduled status means Search Atlas queued the post but never sent it to Google — so it never appeared on your Business Profile. The most common causes are: - A platform-side publishing queue error (resolved) - Google Business Profile API rate limit exceeded during a high-volume publishing window (resolved) - An expired or disconnected Google Business Profile OAuth connection - The connected Google account losing Owner or Manager permissions on one or more GBP locations Posts scheduled before the platform fix was deployed in April 2026 may still show Scheduled status and will not self-publish — they require a manual reschedule to go live. Posts scheduled after that date are not affected by that issue. ⚠️ Note about automated posts: If you use GBP Galactic automation with Approve before posting enabled, those posts may also appear under the Scheduled filter even though they are actually Awaiting Approval. Before treating an automated post as stuck, open the post and check whether it was created via Galactic automation and whether an approval step is configured. If it requires approval, complete the approval step instead of rescheduling. 🔍 How to Identify Stuck Scheduled Posts in Search Atlas Follow these steps to find every post that is overdue and still showing Scheduled status: 1. In Search Atlas, go to Local → Posts (GBP Posts). 2. Open the Status filter and select Scheduled. 3. Review the DATE column — any post whose scheduled date has already passed is stuck and needs action. 4. Open each overdue post and confirm it is not a Galactic automation post awaiting approval before treating it as stuck. 5. Note the affected locations so you can resolve them all in one pass. You now have a complete list of every overdue post that did not publish to Google. 🛠️ How to Fix a Stuck Scheduled GBP Post Reschedule the stuck post to a new future date and time so Search Atlas requeues it for publishing: 1. Click the stuck post to open it. 2. Click Edit. 3. Update the Scheduled Date to a future date and time — at least 15 minutes from now. 4. Click Schedule to confirm. After the new scheduled time passes, the post status updates from Scheduled to Published, and the Fix Now button disappears from the post — both confirm the action was registered successfully. Verify the post appeared on Google by checking the Business Profile directly in Google Search or Google Business Profile Manager. ⚠️ If the Post Fails Again After Rescheduling Repeated failures usually point to a broken connection rather than a post issue. Restore your GBP integration before rescheduling again: 1. Go to Settings → Integrations → Google Business Profile. 2. Check the connection status. If it shows Disconnected or an error, click Reconnect and complete the OAuth authorization flow. 3. Confirm the reconnected Google account has Owner or Manager access on the affected GBP locations. 4. Return to Local → Posts (GBP Posts) and reschedule the post once the integration page shows a green Connected status. After a successful OAuth reconnect, the connection badge updates from Connect to a green Connected state. Once you re-publish a previously stuck post, the Fix Now button on that post also disappears — together these two signals confirm both the reconnection and the re-publish were registered successfully. 📍 How to Reschedule Stuck Posts Across Multiple Locations If the same post content is stuck across several locations, use bulk actions to fix them all at once: 1. In Local → Posts (GBP Posts), filter by Status: Scheduled. 2. Use the checkbox at the top of the list to select all overdue posts. 3. Click Bulk Edit → Reschedule. 4. Set a new future date and time to apply to all selected posts. 5. Click Confirm. All selected posts are rescheduled in one action. After the new scheduled time passes, verify each location shows Published in the Posts list. ✅ How to Confirm a GBP Post Published Successfully After rescheduling, confirm the post went live using either method: - Inside Search Atlas: Go to Local → Posts (GBP Posts) and confirm the status changed from Scheduled to Published. The Fix Now button should no longer appear on the post. - On Google directly: Search for the business on Google or open Google Business Profile Manager and confirm the post appears under Posts. A Published status in Search Atlas confirms the post was successfully delivered to and accepted by Google. 🎯 You can now identify stuck scheduled GBP posts, reschedule them, and confirm they published correctly. If posts continue to fail after reconnecting your Google Business Profile integration, contact Search Atlas Support with the affected location names and post IDs for further investigation.

Last updated on Oct 26, 2026

🛠️ GBP Automated Posts: Fixing Stale Schedule Date and Image Size Errors

Two distinct errors can prevent your GBP automated posts from publishing to Google Business Profile: a "Must be a future datetime" rejection when a post sits unapproved past its scheduled date, and an "Image is not supported" rejection when a Media Library image exceeds Google's 5 MB limit. Identify which error you are seeing below and follow the steps to resolve it. ⚠️ Understanding the Two Error Types Both errors occur inside the GBP Automated Posts workflow and block a post from reaching Google Business Profile. They have different root causes and different fixes. - "Must be a future datetime" (HTTP 400) — The post's scheduled date passed before it was approved. Google rejects any post submitted with a past timestamp. - "Image is not supported" — A Media Library image attached to the post exceeds Google's 5 MB file size limit. Google rejects the entire post, even if the image looks correct inside Search Atlas. 📅 Fixing the "Must be a future datetime" Error Why this error occurs When a GBP automated post enters Awaiting Approval status, it holds its original scheduled date. If the approver does not act before that date and time pass, the timestamp becomes stale. When you then approve the post, Search Atlas submits it to Google's API with that expired timestamp — and Google returns HTTP 400: "Must be a future datetime." The error message appears in the Status column of the Automated Posts table next to the affected post. How to fix it 1. Go to Local → Posts (GBP Posts). 2. Locate the post showing the "Must be a future datetime" error. 3. Click Edit on that post. 4. Update the Scheduled Date and Time field to any date and time in the future. 5. Save your changes, then click Approve. Note: In some cases, posts pending approval may display as Scheduled rather than Awaiting Approval. If you cannot locate the post by status, search by post title or scheduled date instead. The post submits successfully once its scheduled datetime is in the future. 🖼️ Fixing the "Image is not supported" Error Why this error occurs Google's Business Profile API enforces a strict 5 MB maximum file size for post images. When a GBP automated post uses a Media Library image that exceeds 5 MB, Google rejects the entire post with "Image is not supported" — even if the image previews correctly inside Search Atlas. The error message appears in the Status column of the Automated Posts table next to the affected post. How to fix it 1. Go to Local → Posts (GBP Posts). 2. Locate the post showing the "Image is not supported" error. 3. Click Edit and remove the current image from the post. 4. Compress or resize the image to under 5 MB using a tool such as Squoosh or TinyPNG. 5. Upload the compressed image to the Media Library or attach it directly to the post. 6. Save your changes, then click Approve. The post publishes successfully once the attached image is within Google's 5 MB limit. 💡 Preventing These Errors Going Forward Avoid stale schedule dates - Approve posts before their scheduled date passes — treat the scheduled datetime as a hard deadline for the approval action. - When approval cycles are long, schedule the post further in advance to give reviewers enough lead time. - Check the Awaiting Approval queue regularly so no post expires before it is reviewed. Keep Media Library images within Google's size limit - Before uploading any image to the Media Library for use in GBP posts, confirm it is under 5 MB. - Target a minimum resolution of 720 × 720 px and a maximum file size of 5 MB — this satisfies both Google's quality requirements and size cap. - Add image compression as a standard step in your GBP content preparation workflow to prevent failures at publish time. 🎯 You can now diagnose and resolve both the "Must be a future datetime" and "Image is not supported" errors in GBP Automated Posts — reschedule any post whose date has already passed, and compress any Media Library image above 5 MB before re-approving. For a full walkthrough of configuring GBP Automated Posts, see the GBP Automated Posts Overview article.

Last updated on Oct 26, 2026

🛠️ GBP Posts Not Publishing to Facebook or Twitter — Social Account Connection Troubleshooting

If your Google Business Profile (GBP) posts publish in Search Atlas but don't appear on Facebook or Twitter/X, your social account connection has broken. Reconnecting the affected account in Settings → Social Media restores cross-publishing immediately — even if the cause isn't obvious, since platform-side sync issues can break the link without any action on your part. 🔍 Signs Your Social Account Connection Is Broken Check for these indicators before reconnecting: - GBP posts publish successfully in Search Atlas but do not appear on your Facebook Page or Twitter/X profile. - The social account shows as connected in Settings, but posts have been missing from that channel for several days. - You recently changed your Facebook or Twitter/X password, revoked app permissions, linked a new account, or your session expired. - Posts appear to succeed in Search Atlas with no error message, or you receive a publishing-failure notification — both symptoms indicate a broken connection and are resolved by the same reconnection steps. If any of these apply, follow the reconnection steps below. 🔗 How to Reconnect Facebook to GBP Posts 1. Go to Settings → Social Media in your Search Atlas dashboard. 2. Find your Facebook Page under Connected Accounts. 3. Click Disconnect next to the Facebook account. 4. Click Connect Facebook and complete the Facebook authorization flow in the pop-up window. 5. Select the Facebook Page you want to connect, then click Confirm. 6. Go to Local → Posts (GBP Posts) and publish a test post with Facebook selected as a cross-publish destination. Note: If the account still shows as disconnected immediately after reconnecting, wait up to 30 seconds and refresh the page — connection status can take a moment to update. A persisting Fix Now button after re-publishing is a display delay, not a publishing failure; verify by checking your Facebook Page directly. Your test post should appear on your Facebook Page within a few minutes — this confirms the connection is restored. 🐦 How to Reconnect Twitter/X to GBP Posts 1. Go to Settings → Social Media in your Search Atlas dashboard. 2. Find your Twitter/X account under Connected Accounts. 3. Click Disconnect next to the Twitter/X account. 4. Click Connect Twitter/X and authorize the connection in the pop-up window. 5. Once authorized, your Twitter/X handle will reappear under Connected Accounts. 6. Go to Local → Posts (GBP Posts) and publish a test post with Twitter/X selected as a cross-publish destination. Note on past Twitter/X content issue: If your Twitter/X posts were publishing but showed an unexpected '#' at the start of the content, this was a separate platform bug that has been resolved. Republishing those posts will produce the correct content without the leading hash. Your test post should appear on your Twitter/X profile within a few minutes — this confirms the connection is restored. ✅ How to Verify Cross-Publishing Is Working After reconnecting, confirm the integration is active: - In Settings → Social Media, Facebook and Twitter/X should each show a green Connected status badge. - After publishing a GBP post, open your Facebook Page or Twitter/X profile and confirm the post appears. - In Local → Posts (GBP Posts) → Post History, confirm the post shows a published status for each connected social channel. A green status badge and a matching post on the social platform confirm cross-publishing is working correctly. ⚠️ If Posts Still Don't Publish After Reconnecting If cross-publishing still fails after reconnecting, check these common causes: - Facebook Page role: You must be an Admin on the Facebook Page — Editor or lower roles cannot authorize third-party publishing. - Twitter/X app permissions: Confirm Search Atlas has Read and Write access in your Twitter/X connected apps settings. - Multiple GBP locations: Each location has its own social media settings. Make sure the social account is connected to the correct location. - Pop-up blocker: The authorization window opens as a pop-up. If it does not appear, disable your browser's pop-up blocker for Search Atlas and try again. If none of these resolve the issue, contact Search Atlas Support with your GBP location name and the affected social platform — the team can review publishing logs directly. 📨 Still Not Working? Contact Search Atlas Support If reconnection and the troubleshooting steps above do not resolve the issue, escalate to our support team so we can investigate server-side. Include the following in your message: - Your account email. - The affected GBP location name. - A screenshot of the post in question. Our team can check server-side publishing logs to diagnose persistent failures and confirm whether the issue is account-specific or platform-wide. 🎯 You now know how to identify a broken social account connection and restore Facebook and Twitter/X cross-publishing for your GBP posts. For a full overview of creating and scheduling GBP content, see the GBP Posts Overview article.

Last updated on Oct 26, 2026

🔍 Why Some Google Business Profile Locations Are Missing from the Local Posts Section

If some of your Google Business Profile (GBP) locations don't appear in the Local → Posts section for automated Reviews and Postings, the issue is almost always related to how your Google account is connected, the status of each location, or how locations are assigned in Search Atlas. This article walks you through the most common causes and how to resolve them. ✅ Before You Start Make sure you have: - Admin or Manager access to the affected GBP locations in Google. - The Google account that owns or manages those locations. - Access to the Local SEO tool inside your Search Atlas dashboard. 🤔 Common Reasons Locations Are Missing 1️⃣ The location isn't connected to the right Google account Only locations managed by the connected Google account will sync. If a location is owned by a different Google account, it won't appear. 1. Go to Local → Posts (or your Local SEO settings). 2. Check which Google account is currently connected. 3. If the missing location is managed by a different account, disconnect and reconnect using the correct Google account, or add the location to the connected account in Google Business Profile Manager. If your account or project was recently migrated, your GBP connection may simply need to be re-established. Re-connecting your location is standard re-onboarding and does not mean your data was lost. 2️⃣ The Google connection expired and automation was paused If the connected Google account's authorization later expires or is revoked, Search Atlas automatically pauses Posts and Reviews automation for the affected locations until the connection is restored. When this happens, you'll receive an in-app notification that reads "GBP automations paused — reconnection required" with a link to the Google reconnect flow. The location can appear unavailable or stop generating posts even though nothing else changed. 1. Check your dashboard notifications for a "reconnection required" alert. 2. Reconnect the Google account from Local → Posts (or your Local SEO settings). 3. Once reconnected, the location's automation resumes. Note that any posts published directly on Google while the connection was down won't appear in Search Atlas until after you reconnect and the next sync runs. 3️⃣ The location hasn't been imported or selected After connecting your Google account, locations must be imported and enabled in Search Atlas. A location may be connected but not yet selected for automation. 1. Open your Local SEO project settings. 2. Look for the list of available GBP locations. 3. Make sure the missing location is toggled on or selected for Posts and Reviews. 4. Save your changes and refresh the page. 4️⃣ The location's verification or status isn't eligible Google only allows posts and review features on locations that are verified and in good standing. Locations that are unverified, suspended, duplicate, or pending will not appear or will be unavailable for automation. - Unverified: Complete verification in Google Business Profile Manager. - Suspended: Resolve the suspension with Google before the location can sync. - Pending or duplicate: Wait for Google to finalize the status, then re-sync. 5️⃣ Insufficient permissions on the Google account The connected Google account needs Manager or Owner access to each location. "Site manager" or limited roles may prevent a location from syncing for posting and review features. 1. In Google Business Profile, open the location and check your access level. 2. Request Manager or Owner access if needed. 3. Reconnect the account in Search Atlas after permissions are updated. 6️⃣ The location belongs to a different business group or account organization If your locations are spread across multiple business groups or location groups in Google, only the group tied to the connected account will sync. Confirm the missing location lives in the same group as the others. 7️⃣ Plan or location limits have been reached Every account has a usage limit for GBP automated posting, based on your account's allowed automated postings plus any purchased top-up quota. If you've reached your limit, additional locations won't appear as available. - Review your current plan's location allowance. - Remove an unused location or upgrade your plan to add more. - Deleted or disconnected locations do not count toward your limit. If you previously removed a location and later restore it, it may re-occupy an automation slot, so re-check your usage after restoring any locations. 🛠️ Step-by-Step Troubleshooting Work through these steps in order to resolve most missing-location issues: 1. Confirm the connected account. Verify that Search Atlas is connected to the Google account that manages all your locations. 2. Check for a reconnection alert and re-sync your locations. Look for a "GBP automations paused — reconnection required" notification. Disconnect and reconnect the Google account, or use the refresh/re-sync option in Local SEO settings to pull the latest list. 3. Check each location's status in Google. Ensure missing locations are verified, active, and not suspended or duplicated. 4. Verify your access level. Make sure the connected account has Manager or Owner permissions on every location. 5. Enable the location for automation. Toggle on the location for Posts and Reviews and save. 6. Confirm plan limits. Make sure you haven't exceeded the number of locations included in your plan. 7. Refresh and wait. After making changes, allow a few minutes and refresh the page. Newly verified or reconnected locations can take a short time to appear. 💬 Still Not Seeing Your Locations? If you've completed every step above and a location is still missing, contact our support team with the following details so we can investigate quickly: - The exact business name and address of the missing location. - The Google account email connected to Search Atlas. - The location's current status in Google Business Profile (verified, pending, suspended, etc.). - Your access level on that location (Owner or Manager). - Whether you've received a "GBP automations paused / reconnection required" notification. - A screenshot of your Local → Posts location list. Providing this information up front helps us identify the cause and restore your missing locations faster.

Last updated on Oct 26, 2026

🖼️ GBP Galactic Posts: "No Image Selected" on Automated Posts

A now-resolved platform bug caused some automated GBP Galactic posts to show a "No Image selected" placeholder instead of an image thumbnail. If any of your existing posts still display this placeholder, use the steps below to re-attach the image. 🔍 What "No Image Selected" Looks Like in GBP Galactic In Local → Posts (GBP Posts), an affected post shows a "No Image selected" placeholder in the image field instead of an image thumbnail. The symptom is intermittent — other posts in the same list may display their images correctly while only certain posts are affected, including posts across multiple business locations. ✅ Current Status: This Bug Has Been Resolved This was a confirmed Search Atlas platform bug (internal reference: GBP-1190). The engineering team identified the root cause and deployed a fix. Automated posts created after the fix are not affected. If your automated posts were created before the fix was deployed, some may still show the "No Image selected" placeholder. Use the steps below to correct any affected posts manually. 🤖 "No Image Selected" After Choosing AI Generate (GBP-1182) If you see "No Image selected" after choosing the AI Generate media option (rather than uploading your own image), this was a separate bug (internal reference: GBP-1182) that has also been resolved. Create a new post with the AI Generate option — it should now produce and attach the image correctly. If it still does not, contact Search Atlas support. 🛠️ How to Fix Posts Still Showing "No Image Selected" 1. Go to Local → Posts (GBP Posts). 2. Locate a post displaying the "No Image selected" placeholder in the image field. 3. Click Edit on that post. 4. In the Image field, re-select the intended image from your media library or upload a replacement image. 5. Click Save to update a draft or scheduled post, or click Publish to push the post live immediately. The image thumbnail will now display correctly in the post list, confirming the image has been successfully re-attached. Repeat these steps for each affected post. If the image still does not appear after saving, contact Search Atlas support and reference bug GBP-1190 so the team can investigate your specific post. 📋 How to Verify a Post Has the Correct Image After Saving After saving an edited post, confirm the image is correctly attached before moving on: - Return to Local → Posts (GBP Posts). The corrected post should now show an image thumbnail instead of the "No Image selected" text. - If the post has already published to Google Business Profile, open your Google Business Profile dashboard and check the live post to confirm the image is visible there as well. ⚠️ When to Contact Search Atlas Support Reach out to the Search Atlas support team if any of the following apply: - The "No Image selected" placeholder persists after you re-save the image and refresh the page. - A large number of posts are affected and manually re-editing each one is not practical for your account. - A post that already published to Google Business Profile is missing its image and you need help republishing it correctly. - You see the placeholder after using the AI Generate media option on a newly created post (reference bug GBP-1182). When contacting support, include your account name, the affected business location(s), and the approximate date range of the affected posts so the team can investigate faster. 🎯 You now know how to identify the "No Image selected" bug in GBP Galactic Posts, confirm it has been resolved at the platform level, and fix any posts still showing the placeholder. If re-attaching the image manually does not resolve the issue, contact Search Atlas support with your account details and the relevant bug reference (GBP-1190 or GBP-1182).

Last updated on Oct 26, 2026

🏠 Fixing GBP Audit Errors for Service-Area Businesses Without a Fixed Address

📋 Overview The GBP Audit tool scans your Google Business Profile (GBP) to surface optimization opportunities. To run a scan, the tool first has to locate and match your exact profile in Google's data. This works smoothly for businesses with a public storefront address, but it can struggle with service-area businesses (SABs)—companies that serve customers at their location and choose to hide their own address on Google. If your business is a service-area business (for example, a mobile mechanic, plumber, or cleaning service) and the audit returns "profile not found" or matches the wrong listing, this article explains why and how to resolve it. 🤔 Why This Happens When a business hides its address in Google Business Profile, Google removes the physical location pin from public search and Maps results. The GBP Audit relies on that public location data to confirm a precise match. Without a visible address, two issues can occur: - No match found: The tool cannot anchor the profile to a specific location, so a name-only search returns no result or times out. - Wrong match: If several businesses share a similar name or operate in the same region, the tool may attach to the wrong profile. This is a known limitation of how Google exposes data for hidden-address listings—not a sign that your profile is broken. ✅ Before You Start: Confirm Your Profile Is Live Run these quick checks first, as they resolve most matching problems: 1. Search your exact business name in Google Maps while signed out (or in a private browser window). If your profile does not appear publicly, the audit tool cannot see it either. 2. Confirm your profile is verified in your Google Business Profile dashboard. Unverified profiles often do not surface in public data. 3. Make sure the profile is published and active, not suspended or pending review. 🔍 How to Match a Service-Area Business in the GBP Audit Try the following methods in order until the audit locates your profile. 1️⃣ Use the Google Maps Share URL (Recommended) The most reliable method is to paste the exact share link from Google Maps: 1. Open Google Maps and search for your business name. 2. Click your business listing to open its profile panel. 3. Select Share, then copy the link shown under "Send a link." 4. Paste this full URL into the GBP Audit tool instead of using name search. This link points to a specific profile ID, which removes ambiguity even when the address is hidden. Note: Some service-area listings produce a share link in Google's CID (hexadecimal) URL format. A previous issue that prevented these CID-format links from creating an audit has been resolved, so if such a link failed for you in the past, copy a fresh share link and try again. 2️⃣ Refine Your Name Search If you prefer to search by name, add a location qualifier to narrow the results: - Enter the full, exact business name as it appears on your profile (for example, "Strong Lady Mechanics"). - Include the primary city or region you serve, if the tool allows it. - Avoid abbreviations or extra words that don't appear on the official listing. Be aware that for some hidden-address SABs, neither the share URL nor a name search will return a match, even when both are entered correctly. In that case, continue to the Place ID method below or contact support. 3️⃣ Use Your Place ID If neither method works, locate your Google Place ID and supply it directly: 1. Go to Google's Place ID Finder (search "Google Place ID Finder"). 2. Type your business name into the map search box. 3. Copy the Place ID shown in the info window. 4. Paste it into the GBP Audit if a Place ID field is available, or share it with our support team. 🛠️ If the Audit Still Can't Find Your Profile When the tool repeatedly fails, the cause is usually one of the following: - The address is fully hidden and the profile has limited public data. Some SABs simply do not return enough public signals for an automated match. - The profile is new. Recently created or recently verified profiles can take time to appear in third-party data sources. - Duplicate or similar listings exist. Competing profiles with near-identical names can interfere with matching. ⏱️ Temporary Workaround If you need to run the audit immediately, you can temporarily add a public address in your Google Business Profile, run the scan, and then re-hide the address afterward. Only do this if you are comfortable briefly displaying your location, and allow time for Google to update before scanning. ⚠️ Known Limitation: Incomplete Data After a Successful Match Even when the audit matches your profile, hidden-address service-area businesses sometimes lack public location coordinates (a "null" latitude/longitude). When that happens, you may notice: - Missing Competitor Benchmark, Citation Score, or Keyword Rankings sections. - Benchmark competitors that appear well outside your service area—in some reported cases hundreds of miles away. This is a recognized issue our engineering team is actively working on. If your audit shows incomplete or geographically inaccurate results, it reflects this data limitation rather than a problem with your profile. 📞 When to Contact Support Reach out to our support team if you have tried all of the above and the audit still cannot match your profile. To help us resolve it quickly, please include: - Your exact business name as it appears on Google. - The Google Maps share URL for your profile. - Your Google Place ID, if you found it. - Whether your profile address is hidden, and the city or region you serve. - A screenshot of the error message from the GBP Audit. With these details, our team can manually verify the match and confirm whether the limitation is on the Google data side. 💡 Key Takeaways - Hidden-address service-area businesses are harder to match because Google removes their public location data. - The Google Maps share URL is the most reliable way to locate your profile. - A Place ID offers a precise fallback when name and URL searches fail. - Confirm your profile is verified and publicly visible before troubleshooting further. - Even after a successful match, SABs may show incomplete audit data—a known issue currently being addressed.

Last updated on Oct 26, 2026

🔄 Rollback OTTO, Fix Duplicate Metadata & Local SEO

🧭 Overview This article covers three common questions from Search Atlas customers: how to roll back changes made by OTTO SEO, how to avoid duplicate metadata when using multiple SEO tools, and how to get the most value from Search Atlas as a local service business. Follow the guidance below to resolve each issue quickly. ↩️ How to Roll Back OTTO SEO Changes OTTO SEO applies on-page optimisations automatically, including meta titles, meta descriptions, keyword placements, and schema markup. If you want to undo these changes, follow the steps below. 1. Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Select the website or project where OTTO made changes. 3. Open the Deployed Fixes or Active Optimisations section. 4. Locate the specific fix or group of fixes you want to revert — you can filter by type, such as Meta Data, Keyword Optimisations, or Schema Markup. 5. Click Undeploy (or Roll Back) next to each fix to remove it from your site. 6. Confirm the action when prompted. OTTO will restore the original content that existed before the change was applied. Important notes about rolling back: - Rollback restores the previously saved version of that field. Make sure you verify the restored content looks correct in your CMS after undoing. - Schema markup fixes that were applied via bulk deployment may need to be individually undeployed if they are not visible in the standard deployment queue. If you cannot locate a specific schema fix after a bulk action, contact support using the instructions at the bottom of this article. - Meta description and keyword optimisation rollbacks take effect immediately once confirmed — no additional plugin update or cache clear is required on the Search Atlas side, though you may need to clear your site's own cache. 🚫 How to Avoid Duplicate Metadata When Using Multiple SEO Tools Duplicate meta descriptions, titles, or schema markup can occur when more than one SEO tool is writing to the same fields on your website. This is a common issue for customers who use Search Atlas alongside plugins like Yoast SEO, Rank Math, or All in One SEO. Follow these best practices to prevent conflicts: - Designate one tool as the source of truth. Decide whether Search Atlas OTTO or your WordPress SEO plugin will control meta fields and schema. Do not let both tools write to the same fields simultaneously. - Disable meta output in your WordPress plugin if you want OTTO to manage those fields. In most SEO plugins, you can disable meta title, meta description, and schema output per post type or site-wide in the plugin settings. - Disable OTTO's meta optimisations if you prefer to keep your existing plugin in control. In the OTTO SEO dashboard, you can selectively undeploy meta-related fixes while keeping other OTTO improvements (such as internal linking or heading structure) active. - Audit your schema markup regularly. Use a tool like Google's Rich Results Test to check that only one version of schema is being rendered per page. Duplicate schema can confuse search engines and may cause structured data errors in Google Search Console. - Check after every bulk deployment. Whenever OTTO runs a bulk update, spot-check a sample of pages to confirm no duplicate tags have been introduced. 📍 Getting Value from Search Atlas as a Local Service Business Search Atlas includes a dedicated Local suite built specifically for businesses that serve customers in a geographic area — such as contractors, medical practices, law firms, and home services. Key Local features and where to find them: - Left sidebar → Local → Overview — See a summary of your Google Business Profile (GBP) health, recent activity, and performance metrics in one place. - Left sidebar → Local → Posts — Publish and schedule GBP posts directly from Search Atlas to keep your profile active and engaging. - Left sidebar → Local → Reviews — Monitor and respond to customer reviews across your GBP listing without leaving the platform. - Left sidebar → Local → Local Citations — Build and manage consistent NAP (Name, Address, Phone) citations across directories to strengthen your local authority. - Left sidebar → Local → Media Library — Upload and manage photos and videos for your GBP profile to improve engagement and ranking signals. - Left sidebar → Local → My Tasks — Track outstanding local SEO tasks and recommendations assigned to your project. Maximising authority and internal linking for local businesses: - Use OTTO's internal linking suggestions (found in OTTO SEO → All Sites (SEO Automation)) to connect your service pages, location pages, and blog content. Strong internal linking helps search engines understand your site structure and distributes page authority effectively. - Build topical authority by creating content clusters around your core services and locations. OTTO can identify content gaps and suggest new pages to target local search queries. - Combine GBP optimisation with on-site SEO — consistent business information across your website and your GBP listing is a strong local ranking signal. ✅ Quick Reference Summary - Roll back OTTO changes: OTTO SEO → All Sites (SEO Automation) → Deployed Fixes → Undeploy individual fixes. - Prevent duplicate metadata: Use only one tool to write meta fields and schema per page. - Local SEO value: Use the Local suite (GBP posts, reviews, citations) alongside OTTO's on-site optimisations for the strongest results. 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.

Last updated on Oct 26, 2026

🔓 Unlock Google Business Profile to Fix Social Media Errors

🧭 Overview When you try to post or update content through the Social section of Search Atlas, you may see an error related to "disable lock on". This message means your Google Business Profile (GBP) is currently locked, which prevents any social media updates from being published to it. To resolve this, you will need to unlock the GBP project associated with the social media account you are trying to update. ⚠️ What Does the "Disable Lock On" Error Mean? The "disable lock on" message appears when a GBP project has been locked inside Search Atlas. A lock is sometimes applied automatically or manually to protect a profile from unintended changes. While the lock is active, the platform blocks any outgoing updates — including social media posts — to that profile. You must unlock the profile before your updates can go through. 🔓 How to Unlock Your Google Business Profile To resolve this error, you need to locate the locked GBP project within Search Atlas and disable the lock on it. The lock setting is managed from the Local → GBP Projects (GBP Projects) section of the platform, within your GBP project settings. Once you have found the correct GBP project — the one linked to the social media account you were trying to update — disable the lock on that project. After the lock is removed, return to the Social section and try your update again. If you are unsure which GBP project is linked to your social account, look for the profile whose name matches the account you were posting to. If you cannot identify the correct project or cannot locate the lock setting, please reach out using the contact information below so our team can assist you directly. ✅ Confirming the Unlock Worked Once the lock has been disabled on the correct GBP project, return to the Social section and attempt your post or update again. If the "disable lock on" error no longer appears, the unlock was successful and your content should publish as expected. 🔁 What If the Error Persists After Unlocking? If you have unlocked your GBP but the error still appears when trying to post, try the following: - Refresh the page and attempt the update again. - Confirm you unlocked the correct GBP project — verify that the profile name matches the social account you are posting to. - If the error continues, please reach out to our support team. When you do, have the following ready: the name of the GBP project you unlocked, the social media account you were trying to post to, and the exact error message you are seeing. 💬 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.

Last updated on Oct 26, 2026

🔗 Fix LinkedIn URL Errors in GBP Integration

🤔 Why Is My LinkedIn URL Being Rejected? Search Atlas connects your Google Business Profile (GBP) to LinkedIn using the Company Page format. If you entered a URL that looks like linkedin.com/in/YourName/, the platform will reject it — even if that profile has thousands of connections and represents a real business. This is because linkedin.com/in/ URLs belong to personal profiles, not business entities. Search Atlas requires a URL in the format linkedin.com/company/your-company-name/ to correctly map your business data, pull verified company information, and meet LinkedIn's own API requirements for business integrations. ✅ The URL Format You Need The accepted format is: - Accepted: linkedin.com/company/your-company-name/ - Not accepted: linkedin.com/in/YourName/ If you do not yet have a LinkedIn Company Page, you will need to create one before completing this step in Search Atlas. 💡 Will Creating a Company Page Delete My Connections or Profile? This is the most important thing to understand: creating a LinkedIn Company Page does not affect your personal profile in any way. - Your personal profile, its 10K+ connections, endorsements, recommendations, and history remain completely intact. - Your personal profile and your Company Page are two separate entities on LinkedIn. One does not replace or overwrite the other. - You will continue to own and manage both from the same LinkedIn account. Your existing network and social proof are not lost — they stay exactly where they are. 🔄 How Your Existing Equity Carries Over While your connections are tied to your personal profile, your Company Page benefits from your personal credibility in several real ways: - You become the Page admin, so your personal profile is visibly linked to the company. - You can invite your existing connections to follow the Company Page directly from LinkedIn — up to 250 invitations per month per admin. - Posts you share from your personal profile about the Company Page reach your full network immediately. - Your personal profile continues to show your role at the company, reinforcing the business's credibility. In short, your existing audience and reputation are an asset you can actively migrate to the Company Page — they are not abandoned. 🛠️ How to Create a LinkedIn Company Page 1. Log in to your personal LinkedIn account at linkedin.com. 2. Click the Work icon (grid of dots) in the top-right navigation bar. 3. Scroll down and select Create a Company Page. 4. Choose Company as the page type. 5. Fill in your business name, LinkedIn public URL (choose something close to your business name), industry, size, and website. 6. Upload your logo and click Create Page. 7. Copy your new Company Page URL — it will be in the format linkedin.com/company/your-company-name/. 📋 How to Add the URL in Search Atlas 1. Navigate to your GBP dashboard inside Search Atlas. 2. Open the Categories, Attributes & Services section. 3. Locate the LinkedIn field under Social Profiles or Attributes. 4. Paste your Company Page URL in the format linkedin.com/company/your-company-name/. 5. Save your changes. The field will accept the URL once it matches the correct Company Page format. ⚠️ Common Mistakes to Avoid - Do not paste a personal profile URL (linkedin.com/in/) — it will always be rejected. - Do not paste a LinkedIn post or feed URL. - Make sure there are no extra spaces before or after the URL when you paste it. - If your Company Page URL contains uppercase letters, LinkedIn will still resolve it, but use the exact URL shown on your Company Page settings to be safe. 💬 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.

Last updated on Oct 26, 2026

🗺️ Fix GBP Visibility After Business Name Change

🔍 Why This Happens Changing a business name on Google Business Profile (GBP) can trigger an automatic re-review by Google. During this review—and sometimes after it—the listing may temporarily or permanently lose visibility in Google Search and Maps. Common causes include: - Pending re-verification: Google flags the name change and requires you to re-verify ownership before restoring full visibility. - Policy violation: The new name includes keywords, taglines, or location terms that violate Google's guidelines. - Suspended listing: A significant name change can trigger an automatic suspension if Google's systems detect it as suspicious activity. - Propagation delay: Minor changes sometimes take 3–7 days to reflect in search results without any underlying issue. ✅ Step 1 — Check the Listing Status in GBP Before troubleshooting, confirm the current status of the profile directly in Google Business Profile Manager. 1. Go to business.google.com and sign in with the account that manages the profile. 2. Locate the affected business listing. 3. Look for any status banners at the top of the profile, such as "Suspended,"****"Pending review," or "Needs action." 4. If the profile shows Suspended, proceed to Step 3. If it shows Pending review, proceed to Step 2. If no banner appears, proceed to Step 4. ⏳ Step 2 — Wait Out the Re-Review Period If the profile is marked Pending review, Google is actively reviewing the name change. During this period: - Do not make further edits to the profile. Additional changes can restart the review clock. - Allow up to 7 business days for the review to complete. - Monitor the profile daily for a status update. - If the status has not resolved after 7 business days, move to Step 3. 🚫 Step 3 — Resolve a Suspended Listing A suspended listing will not appear in Google Search or Maps until the suspension is lifted. Follow these steps to appeal: 1. In Google Business Profile Manager, open the suspended listing. 2. Click Appeal suspension (shown in the suspension banner). 3. Complete the appeal form. Provide supporting documents such as a business license, utility bill, or storefront photos that confirm the business name and address. 4. Submit the appeal and allow up to 3–5 business days for a response from Google. 5. If the appeal is denied, review the new business name against Google's name guidelines and revert or adjust the name to comply before re-appealing. 📋 Step 4 — Verify the Name Complies With Google's Guidelines Even if the listing is not suspended, a non-compliant name can suppress visibility. Ensure the business name meets all of the following criteria: - Reflects the real-world name customers use to find the business (e.g., on signage, receipts, or the website). - Does not include keywords, city names, or location descriptors unless they are legally part of the registered business name. - Does not include marketing slogans or phone numbers. - Matches the name used consistently across the website and other citations. If the name does not meet these criteria, revert it to the previous name or update it to a compliant version, then monitor for visibility recovery over 3–7 days. 📍 Step 5 — Audit Local Citations for Consistency Name inconsistencies across the web can compound GBP visibility issues. After a name change, citations that still carry the old name create conflicting signals for Google. 1. In Search Atlas, go to Left sidebar → Local → GBP Projects. 2. Select your client's GBP project from the list. 3. Navigate to Left sidebar → Local → Local Citations. 4. Review the citations list for any entries that still display the old business name. 5. Update or suppress outdated citations so the name is consistent everywhere. 📈 Step 6 — Monitor Ranking Recovery Once the listing is active and compliant, track whether local visibility is recovering. 1. In Search Atlas, go to Left sidebar → Keywords → Rank Tracker. 2. Filter by the client's target local keywords (e.g., branded terms or primary service keywords). 3. Set a baseline date from the day the name change was made and monitor weekly ranking trends. 4. If rankings do not begin to recover within 2–3 weeks of the listing being reinstated, revisit citation consistency and profile completeness. ⚠️ When to Escalate to Google Support Contact Google Business Profile support directly if: - The appeal has been denied more than once despite a compliant business name. - The listing shows as Published in GBP Manager but still does not appear in Search or Maps after 14+ days. - You receive no response from Google within 5 business days of submitting an appeal. Reach Google support via the Help button inside Google Business Profile Manager to open a support case. 💬 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.

Last updated on Oct 26, 2026

🔗 Fix GBP Social Media URL Validation Errors

🔍 What Is This Error? When adding social media links to your Google Business Profile (GBP), you may see the error: INVALID_SOCIAL_MEDIA_PROFILE_URL. This means one or more of your social media URLs are not formatted in the way Google requires. Google enforces strict URL standards for each platform, and even a small formatting mistake will cause the entire submission to fail. 📋 Why URL Formatting Matters Google validates every social media URL you submit against its own rules for each supported platform. Common issues include extra query parameters, incorrect subdomains, missing path segments, or using short links instead of full profile URLs. The URL must point directly to a public profile page — not a post, a reel, a story, or a redirect link. ✅ Correct URL Formats by Platform Use the exact formats shown below. Replace the example handles with your own. - **Facebook:**https://www.facebook.com/YourPageName — Use the full www.facebook.com domain. Do not use fb.com, m.facebook.com, or any Facebook short URL (e.g. fb.me/...). - **Instagram:**https://www.instagram.com/yourusername/ — Include the trailing slash. Do not link to a specific post or reel. Avoid instagr.am short links. - **TikTok:**https://www.tiktok.com/@yourusername — The @ symbol before the username is required. Do not use vm.tiktok.com or any shortened TikTok video link. - **YouTube:**https://www.youtube.com/@YourChannel or https://www.youtube.com/channel/UCxxxxxxxxx — Avoid vanity URLs with custom slugs unless they match the verified channel URL exactly. - **LinkedIn:**https://www.linkedin.com/company/your-company-name/ — Use the company page URL, not a personal profile or LinkedIn post URL. - **X (Twitter):**https://x.com/yourusername or https://twitter.com/yourusername — Both domains are currently accepted, but avoid t.co shortened links. - **Pinterest:**https://www.pinterest.com/yourusername/ — Link to the profile root, not a specific board or pin. 🚫 Common Mistakes to Avoid - Using a shortened or redirect URL (e.g. bit.ly, fb.me, vm.tiktok.com) - Linking to a specific post, reel, video, or story instead of the profile page - Adding query parameters such as ?utm_source=... or ?ref=... to the end of the URL - Using a mobile subdomain like m.facebook.com - Forgetting the https:// prefix - Including extra spaces before or after the URL 🛠️ How to Update Your Social URLs in Search Atlas 1. In the left sidebar, click Local → GBP Projects to open your GBP projects. 2. Select the GBP project you want to update. 3. Navigate to the profile or business information section where social media links are stored. 4. Remove the existing URL that is causing the error. 5. Enter the corrected URL using the formats listed above. 6. Save your changes and re-submit to Google. If the error persists after correcting the format, double-check that your social media profile is set to public. Google cannot validate a private or restricted profile URL. 💡 Quick Checklist Before Submitting - URL starts with https://www. - URL points to the profile page, not a post or video - No shortened links or redirect URLs - No tracking parameters appended - No extra spaces at the start or end - Profile visibility is set to public on the social platform 💬 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.

Last updated on Oct 26, 2026

🗺️ Local SEO Heatmap Quota and Failed Payments

🔍 Overview Your Local SEO Heatmap quota may show as depleted — even if you believe credits should be available — when a recent payment on your account has failed. This article explains why this happens and what steps you can take to restore your full quota. 💳 Why a Failed Payment Depletes Your Quota When Search Atlas cannot process a payment, your account is temporarily restricted to prevent usage beyond what has been paid. This affects resource-heavy features like the Local SEO Heatmap, which consumes quota credits each time an audit runs. As a result: - Your displayed quota may drop to zero or to a lower-than-expected number. - Any attempt to run a new Local SEO Heatmap audit may be blocked until the payment issue is resolved. - Quota that appeared available before the failed payment may be placed on hold until billing is confirmed. This is not a bug — it is a safeguard to keep your account in good standing and ensure accurate quota tracking. ✅ How to Check Your Current Quota Before troubleshooting billing, confirm your current quota balance by logging in to Search Atlas and reviewing the quota information available in your account. If your quota reads zero or lower than expected, a billing issue is the most likely cause. 🛠️ How to Resolve a Failed Payment Fixing the failed payment will restore your quota. Follow these steps: 1. Navigate to Billing (or Subscription) from the top-right avatar (Avatar Menu (👤)) in the platform. 2. Review any outstanding invoices or payment failure notices displayed on the page. 3. Update your payment method if the card on file has expired, been declined, or been replaced. 4. Retry the failed charge manually, or wait for the next automatic retry if one is scheduled. 5. Once the payment is processed successfully, check whether your quota has been restored. If it has not updated after a few minutes, refresh your browser and check again. 🗺️ Running a Local SEO Heatmap Audit After Quota Is Restored After your payment is confirmed, return to the Local SEO Heatmap section of the platform and attempt to run your audit as normal. If your quota still appears depleted after a successful payment, allow a few minutes for the system to sync and then refresh your browser before trying again. 🚫 Still Seeing Issues? If your quota remains depleted after successfully resolving a failed payment, please be ready to share the following when reaching out for support: your account email, the approximate date and time the payment was processed, and any confirmation or error messages you received. 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.

Last updated on Oct 26, 2026

📊 Citation Dashboard Access After Plan Cancellation

🔍 Overview If you have cancelled your Local Citation Builder subscription but still have time remaining in your paid billing period, you should retain full access to your citation dashboard until that period ends. This article explains how access works after cancellation, what to do if you are locked out unexpectedly, and how to request a refund for active citations if access cannot be restored. 📋 How Access Works After Cancellation When you cancel a Local Citation Builder plan, your subscription moves to a pending cancellation status. This means: - Your access remains active until the end of your current paid billing period. - You can continue to manage your citations, view your dashboard, and make updates during this time. - Once the billing period fully expires, your dashboard access is removed and citations can no longer be managed through Search Atlas. You should not be locked out immediately upon cancelling — only after your paid period has ended. ⚠️ What to Do If You Are Locked Out Early If you cancelled your plan but your paid period has not yet ended and you are now unable to access your citation dashboard, this is not expected behaviour. Follow these steps: 1. Navigate to Left sidebar → Local → Local Citations to confirm whether your citations and dashboard are visible. 2. Check whether you can access any other Local sub-pages, such as Left sidebar → Local → Overview, to determine if the issue is limited to citations or affects the entire Local section. 3. Try refreshing your browser and logging out, then logging back in to rule out a session issue. 4. If you are still locked out, contact our support team immediately using the live chat widget (see below) so we can investigate and restore your access for the remaining period. 💡 Requesting a Refund for Active Citations If your access cannot be restored for the remainder of your paid period, you may be entitled to a refund for any active citations that were included in your plan. When contacting support, please have the following information ready: - The email address associated with your Search Atlas account. - Your plan name and billing period start and end dates. - The number of active citations you had at the time of cancellation. - Any confirmation emails or receipts related to your purchase. Our team will review your case and advise on eligibility for a partial or full refund based on the remaining time and active citations on your account. 🛠️ Troubleshooting Citation Dashboard Errors After cancellation or during a pending cancellation period, you may occasionally see errors such as Refresh Failed on your Citations modal, or citation counts that do not display correctly. If this happens: - Ensure your business profile is fully completed, as incomplete profiles can prevent citation data from loading accurately. - Try navigating away from the page and returning via Left sidebar → Local → Local Citations. - If the error persists, reach out to support with a screenshot and a description of what you were doing when the error appeared. 💬 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.

Last updated on Oct 26, 2026

🗺️ GBP Import and Ranking Visibility Troubleshooting

🔍 Overview There are two common issues users encounter with Google Business Profiles (GBPs) in Search Atlas: being unable to import a GBP from Google Business Manager, and rankings not displaying after a GBP has been added. Both issues have specific root causes and clear fixes — this article walks you through each one. 📋 Prerequisites for Importing a GBP Before you can import a GBP from your Google Business Manager account into Search Atlas, the following conditions must be met: - Owner or Manager access level: You must have Owner or Manager permission on the GBP inside Google Business Manager. Viewer-level access is not sufficient to authorise the import. Check your access level directly in your Google Business Manager account before attempting to import. - The correct Google account is connected: Search Atlas syncs GBPs from the Google account that was used during OAuth authorisation. If your GBP lives under a different Google account, the profile will not appear in the import list. Reconnect Search Atlas using the Google account that owns or manages the GBP. - The profile is verified and active: Suspended, unverified, or duplicate profiles in Google Business Manager cannot be imported. Confirm the profile status is Published inside Google Business Manager before attempting the import. - Sync has completed: After connecting or reconnecting your Google account, allow up to a few minutes for Search Atlas to sync available profiles. Refresh the page before concluding that a profile is missing. To import a GBP, go to Left sidebar → Local → GBP Projects (GBP Projects) (URL: /gbp-galactic/gbp-projects) and follow the on-screen import flow. 📍 Why Rankings May Not Display for an Added GBP Adding a GBP to Search Atlas does not automatically produce ranking data. Rankings are generated only when specific conditions are satisfied. Below are the most common reasons rankings show as NR (Not Ranked) or do not appear at all. 🗂️ Understanding the NR Status NR (Not Ranked) means Search Atlas ran a keyword search in the defined area and your GBP did not appear in the local results for that grid point. This is a valid data result — it is not an error. It confirms the profile exists but is not ranking for that keyword at that location. NR is different from missing data, which indicates the ranking scan has not yet run or is still in progress. 📡 Service Area Configuration Is Required Rankings are generated based on a geographic grid mapped to your GBP's service area or physical location. If your service area is not configured correctly, the ranking grid cannot be placed accurately and results will be incomplete or missing entirely. - If your GBP is a Service Area Business (SAB) — meaning it has no visible address — you must define the service area inside Google Business Manager. Search Atlas uses this data to determine where to run ranking scans. Without it, no grid can be generated. - If your GBP has a physical address, confirm the address is accurate and fully verified in Google Business Manager. An incorrect address will misplace the ranking grid. 🔑 Keyword-to-Heatmap Mapping Rankings only display when at least one keyword has been assigned to the GBP and linked to a heatmap scan. Simply adding a GBP does not trigger ranking data — you must configure keywords for that profile. 1. Navigate to Left sidebar → Local → GBP Projects (GBP Projects) and open the relevant GBP project. 2. Confirm that keywords have been added to the project. 3. Verify that a heatmap scan has been created and uses those keywords. 4. Check whether the scan has completed. Scans may take several minutes depending on grid size and keyword volume. If a heatmap scan has not been created yet, create one inside the GBP project and allow it to complete before expecting ranking data to populate. ✅ Ranking Visibility Troubleshooting Checklist Work through this checklist in order if rankings are not displaying for your GBP: 1. Confirm the GBP is active and verified in Google Business Manager — suspended or unverified profiles produce no ranking data. 2. Check your access level — ensure you have Owner or Manager permissions on the profile in Google Business Manager. 3. Verify the service area or physical address is set correctly inside Google Business Manager so the ranking grid can be placed accurately. 4. Confirm keywords have been added to the GBP project inside Search Atlas. 5. Confirm a heatmap scan has been created using those keywords and that the scan status shows as completed. 6. Review NR results — if you see NR rather than no data, the scan ran successfully but the profile is not ranking at those grid points. This is expected behaviour for competitive keywords or new profiles. 7. Refresh the page after completing scans. Data sometimes requires a manual refresh to display. 8. Reconnect your Google account if imported profiles are missing — go to Left sidebar → Local → GBP Projects (GBP Projects), disconnect the account, and reconnect using the correct Google login. 💬 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.

Last updated on Oct 26, 2026

🛠️ GBP Review Reply AI Instructions Not Saving

We identified and resolved an issue where AI instructions for automated review replies on Google Business Profile (GBP) locations appeared to save successfully but were silently discarded. If you were affected, please try updating your instructions now — the fix is live. 🐛 What Was Happening When editing AI instructions for automated review replies on a GBP location, changes appeared to succeed — sometimes with no visible error message at all — but the original instructions remained stored. Navigating away from and returning to the review reply configuration page confirmed that no updates had been persisted. No workaround was available while the issue was active. If you reported this issue, your report helped us identify and fix the problem — thank you. ✅ What to Do Now The fix is deployed. Follow these steps to update your AI instructions and confirm they save correctly: 1. In Search Atlas, navigate to Locations, select your GBP location, then go to Review Reply Settings. 2. Enter or update your AI instructions for automated review replies. 3. Click Save. 4. Navigate away from the page, then return to confirm your instructions appear as entered. If your instructions now persist after navigating away, the fix has taken effect for your account. ⚙️ Engineering Status Our team identified the root cause: the system wasn't validating whether required fields were present before saving, causing changes to be silently rejected without an error message. We deployed a fix (GBP-1370 and GBP-1374) that ensures AI review reply instructions now save and persist correctly. No further action is needed beyond re-entering any instructions that were discarded during the affected period. 📞 When to Contact Support If your AI instructions are still not saving correctly after following the steps above, please reach out to our support team through the chat widget in Search Atlas. Share the name of the affected GBP location and describe what you observe so we can investigate and assist you promptly. We typically respond within one business day. 🌀 This issue is resolved and your AI review reply instructions should now save and persist correctly — if you continue to experience problems, contact our support team and we will assist you right away.

Last updated on Oct 26, 2026

📍 Fix GBP Projects Showing No Address Found

🔍 Why This Happens Search Atlas's Local SEO Heatmaps let you enter any target address manually, so they work independently of your live Google Business Profile data. GBP Projects works differently — it fetches your business details directly from the Google Business Profile API. When the API does not return an address, GBP Projects displays "No address found." The three most common causes are: - Your listing is a service-area business (SAB) with the physical address hidden on Google — the API does not expose hidden addresses - Your Google account connection in Search Atlas has expired or lost permission - The GBP location was not linked correctly when the project was created ✅ Fix 1 — Check Whether Your Address Is Hidden on Google Service-area businesses often choose to hide their address on Google. If your address is hidden, the GBP API will never return it and GBP Projects will always show "No address found." This is the most common cause of the issue. 1. Open Google Business Profile Manager at business.google.com and sign in. 2. Select your location and go to Edit profile → Business information → Location. 3. If "Hide my address" is enabled, you have two options: (a) uncheck it to make your address visible so the API can return it, or (b) keep it hidden and use Left sidebar → Local → Local SEO Heatmaps instead, where you can enter your address manually for rank-tracking purposes. 🔗 Fix 2 — Reconnect Your Google Account An expired or revoked Google authorization prevents Search Atlas from reading your GBP data. Reconnecting takes about two minutes. 1. In Search Atlas, go to Site Metrics → GSC Performance (Your connected GSC Accounts). 2. Find your Google account under Connected Accounts and click Disconnect. 3. Click Connect GSC Account (or Connect GA Account) and complete the Google authorization flow. 4. When prompted, sign in with the Google account that holds Owner or Manager access to your GBP location — Editor access is not sufficient to retrieve location data. 5. Once reconnected, go to Left sidebar → Local (lands on GBP Projects) and open your project to confirm the address now appears. Note: If you see the error message "Failed to connect GBP locations" during step 3, this was a known platform issue that has since been resolved. Disconnect and repeat the steps above — the error should not recur. 🏗️ Fix 3 — Re-link the GBP Location Inside Your Project If the address is still missing after reconnecting, the project may not be pointing to the correct GBP location. 1. Go to Left sidebar → Local SEO → GBP Projects and open the affected project. 2. Click Edit Project or the settings icon within the project card. 3. In the Business Location field, clear the current selection and re-select your GBP location from the dropdown. Verify the full address is displayed before saving. 4. Click Save. The address should now populate in your project dashboard. If no locations appear in the dropdown, return to Fix 2 and ensure your Google account is connected with the correct access level. If only some of your locations appear rather than all of them, this was a known platform issue that has since been resolved — reconnecting your Google account as described in Fix 2 and then reopening the project settings should restore the complete location list. 💡 When to Use Local Heatmaps Instead If your business must keep its address hidden on Google — common for home-based businesses and mobile service providers — GBP Projects will not be able to display a street address. This is a Google API limitation, not a Search Atlas issue. In this situation: - Use Left sidebar → Local → Local SEO Heatmaps for local rank tracking — it accepts any address you enter, regardless of your GBP visibility settings. - You can still use GBP Projects at Left sidebar → Local (lands on GBP Projects) for review management, post scheduling, Q&A, and photo management, all of which do not require a returned address. 💬 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. Additional Notes Search Atlas stores a local snapshot of your GBP data when a project is first created or last synced. If your address was added, edited, or verified in Google after that snapshot was taken, GBP Projects will not reflect the change automatically — a manual data refresh/sync from within the project resolves this.

Last updated on Oct 26, 2026

🛠️ Fixing GBP-Project Mismatch and Finding Onpage Optimizations

🔍 Understanding the Problem When you have more than one Google Business Profile (GBP) connected to your account, Search Atlas can sometimes audit a URL that does not match your active project. For example, your project may be set to ericrounds.com, but the system pulls a different website (such as a "Total Service" listing) because a second GBP is linked to that domain. This happens when the tool defaults to a GBP whose website field points somewhere other than your intended project URL. The good news: this is a configuration issue, not a bug, and you can correct it in a few minutes. ​ ⚙️ Why the Wrong URL Is Being Pulled Search Atlas associates audits with the project and the GBP that are currently selected. The wrong URL usually appears for one of these reasons: - Multiple GBPs connected: Two or more profiles are linked, and the wrong one is active. - Mismatched website field: The active GBP has a different website URL listed than your project domain. - Project not set as active: The audit was run against a project other than the one you intended.​ 🧭 How to Select the Correct Project and GBP Follow these steps to make sure the audit targets the right website: 1. Open the project selector at the top of your dashboard. 2. Confirm that your intended project (for example, ericrounds.com) is selected and active. 3. Go to Left sidebar → Local → GBP Projects for that project. Review the list of connected Google Business Profiles. 4. Confirm that the active GBP shows the correct website URL. If it lists a different domain, switch to the GBP that matches your project. 5. If a GBP is no longer needed, disconnect it so it cannot be selected by mistake.​ Once the correct project and GBP are paired, re-run the audit. The tool will now analyze your intended URL. ​ 📊 Verifying the Audit Targets the Right URL Before reviewing results, double-check the audited domain: - Look at the URL displayed at the top of the audit or report screen. - Confirm it matches your active project domain exactly. - If it still shows the wrong site, clear the current selection, reselect the correct project, and run a fresh audit rather than reopening an older report.​ 🐞 Known Audit Reporting Issues (Now Resolved)​ Not every "mismatch" comes from your configuration — a few were caused by bugs that have since been fixed. If you previously saw any of the following, re-run a fresh audit to get accurate results: - Address reported as missing or mismatched even though it was set correctly on your GBP profile — resolved. - Service pages flagged as "missing" by the GBP Assistant due to a fuzzy-matching failure on nested URLs — resolved. - Competitor audit score differing between the comparison view and a standalone audit — resolved. Because these fixes are already deployed, a current audit should reflect your real on-page and profile data. If you still see an unexpected mismatch after re-running, start a live chat so the team can investigate. 🚀 How to Actually Fix the Audit Issues Many customers expect the audit to only tell them how to fix issues, but Search Atlas can apply many on-page fixes for you automatically through OTTO SEO. Instead of manually editing alt tags, schema, or meta data, let OTTO deploy the changes. 1. Make sure OTTO is activated for your correct project (the one matching your intended URL). 2. Install the OTTO Pixel on your website. This small snippet lets Search Atlas push approved changes live without manual coding. 3. Open OTTO SEO → Overview (OTTO Grader) and review the list of suggested optimizations, including missing alt tags, schema markup, and meta titles or descriptions. 4. Select the fixes you want to apply. You can approve them individually or in bulk. 5. Click Deploy. OTTO applies the approved changes through the Pixel, so they appear on your live site without you editing the source code.​ This is the difference between the audit's "how to fix" guidance and an actual fix: the audit identifies the issue, and OTTO implements the correction once the Pixel is installed and the change is approved. ​ 💡 Best Practices to Avoid Future Mismatches​ - Connect only the GBPs you actively manage for each project to reduce confusion. - Keep the GBP website field accurate so it matches your project domain. - Confirm the audited URL at the top of every report before acting on results. - Activate OTTO and install the Pixel early so fixes can be deployed as soon as issues are found.

Last updated on Oct 26, 2026

⚠️ GBP Posts: "Post Updated Successfully" Appears But Changes Are Not Saved

We previously identified an issue where GBP Posts displayed a "Post updated successfully!" message even though changes were not saved. While this has been resolved, if you experience similar failures, use the workaround steps below to ensure your intended content goes live. 🔍 What's Happening When you edit a published GBP post — for example, removing an image or changing the post body — and click Update Post, a green "Post updated successfully!" notification appears. Despite this message, the update is rejected and your changes are discarded with no visible error. This means a post can appear updated when it has not actually changed. This issue primarily affects published GBP posts. In some cases, draft posts may also experience similar save failures, particularly when images are involved. 🛠️ Workaround Steps Follow these steps to ensure your updated content goes live: 1. After clicking Update Post, navigate away from the post and return to it to confirm whether your changes appear. 2. If your changes are not visible, do not retry editing the published post — it will fail silently again. 3. Delete the published post, then recreate it from scratch with your updated content. This bypasses the issue and ensures your intended content is published correctly. 🔧 Engineering Status This issue has been identified and resolved. If you continue to experience save or update failures when editing GBP posts, please contact our support team for assistance. 📞 When to Contact Support If you are unable to delete and recreate the post, or if the workaround does not resolve your situation, contact our support team for direct assistance. Include the name of the affected post and your GBP account details so we can investigate quickly. 🎯 If you continue to encounter issues with saving or updating GBP posts, our support team is ready to help. Please reach out with details of the post and your account information, and we'll assist you promptly.

Last updated on Oct 26, 2026

📍 Fix GBP Automated Posting & Billing Disputes

📋 Overview Some customers have experienced automated Google Business Profile (GBP) posting stopping unexpectedly, or have noticed quota counts that did not reflect their actual active locations. Separately, customers who cancelled their subscription and expected a refund for charges made shortly after cancellation have raised billing disputes. This article explains what happened, what has been fixed, and what steps to take if you are still affected. 🛑 Why Did Automated GBP Posting Stop? Automated GBP posting may have paused for one or more of the following reasons: - Quota counted deleted locations: A bug caused deleted or disconnected GBP locations to remain counted toward your active posting quota. This inflated your quota usage and, in some cases, caused the system to treat your account as over-limit, preventing new posts from being generated for approval. - Posts not entering the approval queue: Even when a custom posting frequency was correctly configured, a pipeline issue prevented new posts from being created and surfaced for review. - Review replies posted despite quota being disabled: A separate issue allowed review reply automation to continue even when GBP automation quota was turned off at the admin level. This has also been resolved. ✅ What Has Been Fixed The Search Atlas engineering team has resolved the core issues that caused these problems. Here is a summary of completed fixes: - Quota counting corrected: Deleted and inactive locations are no longer counted toward your active GBP posting quota. Your quota should now accurately reflect only connected, active locations. - Post generation restored: The automated posting pipeline has been updated so that posts are generated and queued for approval according to your configured frequency. - Review reply automation scoped correctly: Review replies now respect quota settings. Automation will not run when GBP quota is disabled. - Pipeline reliability improvements: Additional work is in progress to ensure exact-minute publishing, eliminate stalled background jobs, drain any backlog of queued posts, and improve system observability so issues like these are caught earlier. 🔍 Check Your Current Posting Status After these fixes, your automated GBP posting should resume automatically. To verify everything is working correctly, follow these steps: 1. Log in to Search Atlas and navigate to Local → GBP Galactic (GBP Projects) in the left sidebar. 2. Confirm your locations are connected and show as Active. 3. Check your posting frequency settings to ensure your preferred schedule is still configured. 4. Review the Posts Pending Approval queue to see if new posts have been generated. 5. If the approval queue is empty and no posts have appeared within your expected posting window, proceed to contact support using the instructions at the bottom of this article. 💳 Billing Disputes and Refund Questions If you cancelled your subscription and were subsequently charged — for example, if you cancelled on July 7th but were billed on July 9th — here is how billing and cancellations work, and what to expect: - Cancellation effective date: Cancellations take effect at the end of your current billing period. A charge that occurs after a cancellation request but before the billing period ends may still be valid, depending on when in the cycle you cancelled. - Refund eligibility: If you believe a charge occurred in error — outside your billing period, or after your access was fully terminated — you may be eligible for a refund. Refund requests are reviewed on a case-by-case basis. - Documenting your request: To help our team validate your refund request as quickly as possible, have the following ready: your account email address, the exact cancellation date, the charge date and amount, and any confirmation emails you received. Our team cannot process refunds through this knowledge base. Please use the support chat described below so a human teammate can access your account history and confirm whether a refund was issued or is owed. 🛠️ Still Experiencing Issues? If automated posting has not resumed, your quota still appears incorrect, or you need a billing dispute reviewed, our support team can investigate your specific 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.

Last updated on Oct 26, 2026

🗺️ Fix Competitor Names Showing in Local SEO Heatmap

🔍 What Is Happening? When you open your Local SEO Heatmap, you expect to see your own business name tracking keyword rankings across your target area. If a competitor's business name is appearing in your heatmap configuration instead, this is not a normal setup state. It typically points to one of three root causes: a Google Business Profile (GBP) connection pulling in the wrong listing, a project configuration error where the wrong business was selected, or a data sync issue that associated your project with an incorrect GBP entry. This article walks you through each cause and tells you exactly how to fix it. ✅ Before You Begin Confirm the following before troubleshooting: - You are logged in to Search Atlas with the account that owns the Local project. - You have Admin or Editor access to the GBP Projects section. - You have access to the Google Business Profile that belongs to your business. 🛠️ Step 1 — Check Which Business Is Connected to Your Project Navigate to Left sidebar → Local → GBP Projects. You will land on the GBP Projects page at /gbp-galactic/gbp-projects. Locate the project linked to your Local SEO Heatmap and review the business name displayed on the project card. - If the project card already shows the competitor's name, the wrong GBP listing was connected at project creation. Continue to Step 2. - If the project card shows your correct business name but the heatmap still displays the competitor, this is a data sync issue. Skip to Step 3. ⚙️ Step 2 — Correct the GBP Connection If the wrong business is connected to the project, you need to disconnect the incorrect GBP listing and reconnect the correct one. 1. On the GBP Projects page, open the project settings for the affected project. 2. Locate the connected Google Business Profile and remove the incorrect listing. 3. Reconnect by selecting Connect GBP Account (on the Local → GBP Projects page) and choosing the correct business from the list of GBP accounts authorised under your Google account. 4. Save the project settings. 5. Return to the Local SEO Heatmap for that project and confirm your business name now appears correctly. Important: If you do not see your business listed when reconnecting, make sure the Google account you are using has Manager or Owner access to the correct GBP listing. A missing listing at this step means the Google account connected to Search Atlas does not have permission to access your business profile. 🔄 Step 3 — Force a Data Sync If your project card shows the correct business name but the heatmap configuration still displays the competitor's name, the issue is a data sync mismatch between your project settings and the heatmap data layer. 1. Open the affected Local project from the GBP Projects page. 2. Navigate to Left sidebar → Local → Overview to confirm your business details are displayed correctly at the overview level. 3. Return to your Local SEO Heatmap and refresh the page completely using a hard reload (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac). 4. Wait up to two minutes for the heatmap data to repopulate, then check whether your business name now appears correctly in the configuration. If the competitor's name is still present after a forced refresh, do not modify further settings. This confirms a backend data association error that requires engineering review. Proceed to Step 4. 🚩 Step 4 — Rule Out a Duplicate or Conflicting Project In some cases, a second Local project may have been created for the same target area using the competitor's GBP listing, and the heatmap is displaying data from that project rather than yours. - Go to Left sidebar → Local → GBP Projects and review all projects listed on the GBP Projects page. - Check whether any project is named after or connected to your competitor. - If a conflicting project exists, delete it or disconnect the competitor's GBP listing from it, then recheck your heatmap. If no conflicting project exists and the competitor's name is still appearing, this is confirmed as a platform-level data issue. 📋 What to Check if Nothing Works If you have completed all steps above and the competitor's business name is still appearing in your Local SEO Heatmap, collect the following information before contacting support. Having this ready will speed up the engineering review significantly: - The name of the affected Local project and the URL of the heatmap page showing the issue. - A screenshot clearly showing the competitor's name appearing in the heatmap configuration. - The name of the competitor business that is appearing incorrectly. - The GBP listing name and address of your own business as it appears in Google. - Confirmation of whether the issue appeared after a specific action, such as reconnecting a GBP account, creating a new project, or after a team member made changes. 💬 Still Seeing the Issue? If the competitor's name persists after following all steps above, this requires direct investigation by our engineering team to resolve the data association at the backend level. 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.

Last updated on Oct 26, 2026

📍 Fix Local SEO Quota Exhaustion Errors

🔍 What Is a Quota Exhaustion Error? A quota exhaustion error means your account has used all the allocated points or credits for a specific feature. In the context of Local SEO, this most commonly affects heatmap keyword tracking. When your heatmap keyword quota runs out, Search Atlas pauses new scans and displays a quota exhaustion notice until additional points are added. This is not a bug — it is expected behaviour when your plan's included quota has been fully consumed. 📊 How Heatmap Keywords and Local SEO Points Work Local SEO features in Search Atlas — including heatmap keyword scans — are powered by Local SEO points. Each heatmap keyword scan consumes a set number of points depending on the grid size and scan frequency you have configured. Once your points balance reaches zero: - Scheduled heatmap scans will not run. - Manual scan requests will be blocked. - You may see a quota exhaustion warning inside the Local section. Adding more Local SEO points restores full access immediately without any changes to your existing project settings or historical data. 🗺️ How to Check Your Current Local SEO Points Balance 1. In the left sidebar, click Local to open the Local SEO section. 2. Click Overview (Left sidebar → GBP Projects → Overview). 3. Your current Local SEO points balance and usage breakdown are displayed at the top of the Overview page. 4. Review which projects or heatmap keywords are consuming the most points to help you plan future usage. ➕ How to Purchase Additional Local SEO Points 1. Navigate to Avatar → Billing → Plans & Top-ups. 2. Locate the points balance section and click Top Up or the equivalent purchase button shown on screen. 3. Select the points package that fits your needs and complete the checkout process. 4. Your new points are added to your balance instantly upon successful payment. 5. Any previously paused heatmap scans will resume on their next scheduled run. 💡 Tips to Avoid Running Out of Points - Audit your heatmap grid sizes. Larger grids consume more points per scan. Reduce the grid size on lower-priority keywords to extend your quota. - Review scan frequency. Daily scans use points faster than weekly scans. Adjust frequency based on how competitive or time-sensitive each keyword is. - Remove unused keywords. If a heatmap keyword is no longer relevant, delete it from your project to stop ongoing point consumption. - Monitor usage regularly. Check your balance in Avatar → Billing → Plans & Top-ups at least once a month to catch low balances before scans are interrupted. ❓ Frequently Asked Questions Has the quota exhaustion problem been fixed? Quota exhaustion is not a platform bug — it means your account's included Local SEO points have been fully used. Purchasing additional points resolves the issue immediately. Do I lose my heatmap data when quota runs out? No. All historical heatmap data and project configurations are preserved. Only new scans are paused until points are replenished. Will my quota reset automatically? Depending on your subscription plan, a portion of Local SEO points may refresh on your monthly billing cycle. Check your plan details in your account settings for exact reset terms. Purchased top-up points do not expire within your active subscription period. Can I set up a low-balance alert? Notifications and alert settings can vary by plan. Check your account notification preferences or ask via the chat widget for guidance specific to your subscription. 🆘 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.

Last updated on Oct 26, 2026

🔍 GBP Accounts Not Appearing After Client Authorization

🧭 Overview When you share an authorization link with a client and they confirm they've signed in, their Google Business Profile (GBP) account should appear in your Integrations tab. If it doesn't, the issue usually comes down to one of five common causes: sync delays, incomplete authorization, account mismatch, permission gaps, or a cached browser session. Work through the steps below in order to identify and resolve the problem quickly. ⏱️ Step 1: Wait for the Sync Delay After a client completes authorization, Search Atlas needs a short period to sync the connection. Before troubleshooting further, confirm the following: - At least 5–10 minutes have passed since the client confirmed they logged in. - You have refreshed your Integrations tab after waiting. If the account still does not appear after 10 minutes, move to Step 2. ✅ Step 2: Confirm the Authorization Was Fully Completed Clients sometimes close the browser tab before the authorization process finishes. Ask your client to confirm they completed every screen in the sign-in flow, including any Google permission approval screens that appeared after entering their password. A fully completed authorization ends with a confirmation message or a redirect back to the Search Atlas page — not simply reaching the Google login screen. If they are unsure, ask them to complete the authorization again using the same link you sent. 👤 Step 3: Check for an Account Mismatch This is one of the most common causes of missing accounts. Your client may have signed in with a personal Google account instead of the account that manages their GBP listing. Ask your client to verify: - They signed in with the Google account that has Owner or Manager access to the GBP listing. - They did not accidentally use a secondary or personal Google account. If they signed in with the wrong account, send the authorization link again and ask them to sign out of all Google accounts in their browser first, then sign in with the correct one. 🔐 Step 4: Verify Google Account Permissions Even if the client signed in with the correct account, the GBP listing may not appear if their permission level is too low. Search Atlas requires at least Manager-level access to a GBP location to sync it. Ask your client to check their GBP access level by visiting business.google.com and confirming they can see and manage the relevant location. If they only have basic access, the GBP owner will need to upgrade their permission before re-authorizing. 🗑️ Step 5: Clear Browser Cache and Retry A cached Google session in the client's browser can cause the authorization to silently fail or connect the wrong account. Ask your client to do the following before attempting authorization again: 1. Clear browser cookies and cache, or open a private/incognito window. 2. Sign out of all Google accounts. 3. Open the authorization link you sent and sign in fresh with the correct Google account. 4. Complete all permission approval screens until they see a confirmation or redirect. After they finish, wait 5–10 minutes and refresh your Integrations tab. 🔄 Step 6: Re-send the Authorization Link If none of the steps above resolved the issue, generate a fresh authorization link by going to the top-right Avatar Menu (👤) → Settings → Integrations → Share links → Individual links, and copying the Google Business Profile link from the modal. Send it to your client again. Older links can occasionally expire or encounter session conflicts. A new link starts the process cleanly. 🚦 Quick Diagnostic Reference Use this reference to match your symptom to the most likely cause: - Account missing immediately after authorization — Likely an incomplete auth flow or sync delay. Wait 10 minutes and refresh. - Account missing after 10+ minutes — Likely an account mismatch or permission issue. Confirm the correct Google account was used. - Authorization appears to complete but nothing syncs — Likely a cached browser session. Ask client to retry in incognito mode. - Client sees no GBP locations after signing in — Likely wrong Google account or insufficient permissions on the GBP listing. - Issue repeats after multiple attempts — Re-send a fresh authorization link and contact support if the problem persists. 💬 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.

Last updated on Oct 26, 2026

🔗 Fix Google OAuth Error 400 in GBP Audit

🔍 Overview When running a Google Business Profile (GBP) audit in Search Atlas, you may encounter the following error: Error 400: invalid_request. This is a Google OAuth 2.0 authorization error that occurs when your Google account connection has expired or become invalid. Clearing your cache or signing out will not fix this — the solution is to disconnect and reconnect your Google account directly inside Search Atlas. ⚠️ Why This Happens Search Atlas uses OAuth 2.0 to securely connect to your Google account and access your GBP data. Over time, this authorization token can expire or be revoked — for example, if you changed your Google password, revoked app permissions, or the token simply timed out. Once the token is invalid, any attempt to run a GBP audit will trigger the Error 400: invalid_request message from Google. 🛠️ How to Fix It: Reconnect Your Google Account Follow these steps to disconnect and reconnect your Google account to restore GBP audit access. 1. Navigate to the GBP or Local section of Search Atlas where your Google Business Profile projects are listed. 2. Locate the GBP project that is showing the authorization error. 3. Find the Google account connection option for that project — it will indicate that the authorization has expired or is no longer valid. 4. Disconnect or remove the expired Google authorization from the project. 5. Once disconnected, initiate a new Google account connection for the same project. 6. A Google sign-in window will appear. Sign in with the Google account that has access to your GBP listing and grant the requested permissions when prompted. 7. After successfully authorizing, return to your GBP project and relaunch the audit. The Error 400: invalid_request message should no longer appear and your audit will proceed normally. ✅ Confirm the Connection Is Working After reconnecting, verify the fix was successful before running a full audit: - Confirm your GBP location data is loading correctly within the platform. - Check that your GBP project no longer displays an authorization warning or error status. - Try running the audit again — if it progresses past the authorization step, the reconnection was successful. 🚫 What Will Not Fix This Error The following steps are commonly suggested for Google errors but will not resolve Error 400: invalid_request caused by an expired OAuth token: - Clearing your browser cache or cookies - Signing out of and back into Search Atlas - Using a different browser or incognito mode - Disabling browser extensions 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.

Last updated on Oct 26, 2026

🛠️ Fix OTTO GBP Automated Posting Content Accuracy

🔍 Overview OTTO's Google Business Profile (GBP) automated posting feature generates and publishes posts on your behalf using AI. If your posts contain topics that are unrelated to your business — such as references to products or services you don't offer — this is almost always caused by missing, incomplete, or misconfigured prompt settings inside OTTO. This article explains why this happens and walks you through how to fix it. ⚙️ Why Irrelevant Content Appears in Your GBP Posts OTTO generates GBP post content based on the instructions and context you provide in its settings. If those instructions are vague, incomplete, or missing key details about your business, OTTO may fill in the gaps with content pulled from general AI training data — which can include unrelated industries or services. Common reasons this happens include: - No custom prompt configured: OTTO falls back to a generic prompt that lacks your business-specific context. - Prompt is too broad: A vague prompt like "write about cleaning services" may trigger content about services adjacent to your niche, including ones you don't offer. - Business description is missing or minimal: Without a clear description of what your business does and does not do, the AI has limited guidance. - Service exclusions not specified: If you haven't told OTTO what topics to avoid, it has no way to know what's off-limits. 🚀 How to Fix and Configure Your OTTO GBP Prompt Follow these steps to update your prompt settings and ensure OTTO only generates content relevant to your business: 1. Go to Left sidebar → OTTO SEO, then open All Sites (SEO Automation) (URL: /seo-automation-v3). 2. Locate your connected GBP property and open its OTTO settings. 3. Navigate to the GBP Posting section and find the Prompt or Content Instructions field. 4. Write a clear, specific prompt that includes the following: - Your exact business type (e.g., "exterior pressure washing business") - The specific services you offer (e.g., "house washing, driveway cleaning, roof soft washing") - Services or topics to explicitly exclude (e.g., "do not mention hot tubs, pools, or any indoor services") - Your target audience and location if relevant 5. Save your changes and allow OTTO to generate the next scheduled post using the updated prompt. 💡 Tips for Writing an Effective OTTO Prompt A well-structured prompt significantly reduces the chance of irrelevant content being generated. Keep the following best practices in mind: - Be specific, not general: Instead of "write about my cleaning business," try "write about my residential exterior pressure washing company serving homeowners in Austin, TX." - Use exclusion language: Explicitly state what the post should never mention. For example: "Never reference hot tubs, spas, pools, or interior cleaning." - Include a tone or style direction: For example, "Keep the tone professional and friendly, focused on outdoor property maintenance." - Add a call to action: Tell OTTO how you want posts to end, such as "End every post with a call to action to request a free quote." - Review after the first post: After saving your updated prompt, check the next generated post to confirm the content aligns with your expectations before it goes live. 🔄 What to Do If Incorrect Posts Have Already Been Published If OTTO has already published GBP posts with irrelevant content, take the following steps: 1. Log in to your Google Business Profile directly at business.google.com. 2. Navigate to Posts and locate any posts with incorrect content. 3. Delete or edit those posts directly in the GBP dashboard. 4. Return to OTTO in Search Atlas and update your prompt as described in the steps above to prevent recurrence. 🛠️ Still Seeing Irrelevant Content After Updating? If you've updated your prompt and OTTO is still generating off-topic content, there may be a configuration issue that requires a closer look. 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.

Last updated on Oct 26, 2026

📍 Google Business Profile Reliability Fixes

Recent updates to the Google Business Profile module resolve two issues affecting account management and Local SEO Tools usability, ensuring smoother workflows for connected GBP locations. ✨ What's New This release ships two bugfixes to the Google Business Profile experience: - Duplicate API calls on disconnect fixed: The GBP disconnect button was triggering multiple API calls simultaneously on a single click, which could cause unpredictable behavior when unlinking a profile. This has been resolved so disconnecting a GBP account now fires a single, clean request as intended, eliminating any duplicate request behavior. - Missing connected GBPs in Local SEO Tools fixed: The business selector within Local SEO Tools was failing to display GBP locations that were already connected to the platform. Affected users were unable to select their linked businesses from the dropdown. Connected profiles now appear correctly in the selector, ensuring you can access and manage them without interruption. 🛠️ How to Use It 1. Navigate to Local (GBP Projects) from the left-hand sidebar. 2. To disconnect a profile, open your connected GBP account settings and click the Disconnect button once — the action will now complete with a single API call, without duplicate requests. 3. To use Local SEO Tools, open the business selector and confirm your connected GBP locations appear in the dropdown list. 4. Proceed with your local SEO workflows as normal — no additional steps are required. 📋 What to Expect - These are backend-behavior and UI data fixes — no changes to the visual layout or feature set. - No action is required on your part — both fixes are applied automatically. - All previously connected GBP accounts remain linked; no reconnection is needed. - If a GBP location is still missing from the Local SEO Tools selector after this update, try refreshing the page to force the latest data to load. - The disconnect flow will behave normally on a single click; there is no longer a risk of unintended duplicate requests being sent. 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.

Last updated on Oct 26, 2026

🗺️ Fix a Local SEO Heatmap Stuck Fetching

🔍 Why Does This Happen? A Local SEO heatmap can get stuck on fetching data for several reasons: - The ranking data request timed out in the background before results were returned. - Your Google Business Profile (GBP) account hit its API quota limit, temporarily blocking new data pulls. - A one-time sync error caused the scan to stall without displaying an error message. - A slow polling cycle meant the system could not confirm whether data had arrived or not. In most cases your historical baseline data is safe — the issue is with the active scan, not stored results. ✅ Step-by-Step Resolution 1. Wait 10–15 minutes. Background ranking fetches can take longer than expected. If the spinner is still showing after 15 minutes, continue to the next step. 2. Refresh your browser. Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to do a hard refresh. This clears cached states that can falsely show a fetch in progress. 3. Navigate back to Local SEO Heatmaps. Go to Left sidebar → Local → Local SEO Heatmaps. Check whether the heatmap now shows data or a clear error message. 4. Check your GBP Project connection. Go to Left sidebar → Local → GBP Projects and confirm your GBP account is connected and the project status is active. A disconnected account will cause all heatmap scans to stall. 5. Re-import or refresh the heatmap. On the Local SEO Heatmaps page, use the Import from Google Business Profile button to re-sync your location data, or click Save to trigger a new scan cycle. This will not overwrite existing historical data. 6. Verify historical data is intact. After the page reloads, scroll through your heatmap results to confirm previous scans are still visible. Baseline data is stored separately from active scan results and is not affected by a stalled fetch. ⚠️ API Quota Limit If your heatmap gets stuck repeatedly, your GBP account may have reached its daily API quota. When quota is exhausted, new ranking fetches are queued but cannot complete until the quota resets — typically within 24 hours. - Avoid triggering multiple manual refreshes in quick succession, as each attempt consumes quota. - Wait until the following day and allow the heatmap to run its scheduled scan automatically. - If you manage multiple GBP locations, consider spacing out heatmap scans to reduce quota consumption. 🛠️ If the Heatmap Is Still Stuck If you have completed all the steps above and the heatmap remains on fetching data after more than an hour, collect the following details before contacting support: - The name of the affected heatmap or GBP project (e.g., Starstone Fellowship). - How long the heatmap has been stuck. - Whether the issue affects one location or multiple locations. - Any error messages you see on screen. 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.

Last updated on Oct 26, 2026

🗺️ GBP Changes Not Appearing on Live Listing

🔍 Overview After deploying changes to your Google Business Profile (GBP) through Search Atlas, you may notice that updates do not appear on your live listing — even after receiving a success message and waiting 24 hours or more. This article explains why this happens and walks you through the steps to resolve it. ⚠️ Why Changes May Not Appear There are several reasons a deployment can appear successful inside Search Atlas but fail to update on Google's side: - Google propagation delay: Most changes take up to 24–72 hours to appear on Google, even when deployed correctly. - Invalid or deprecated attribute values: If a field contains a value Google no longer supports (for example, a deprecated social media enum), Google silently rejects the update — even though Search Atlas returns a success message. - Pending state on Google's side: Certain field types, such as business hours or specific attributes, can enter a pending review state on Google and may take longer to go live. - Invalid argument errors: A deploy containing an unsupported value in any single field can cause the entire deployment to fail, leaving all other changes unapplied. - Service area updates: Service area changes are particularly prone to silent failures where Google accepts the request but does not apply the update to the live listing. 🛠️ Steps to Troubleshoot 1. Wait the full propagation window — and do not edit the field again while you wait. Allow at least 72 hours before concluding that a change has not applied. Google's review and propagation process varies by field type and location. Do not edit the same field again during this window: a second edit overwrites the in-flight change and restarts Google's 24–72 hour review clock from zero. Make your edit once, deploy it, then wait. 2. Check your live listing directly. Open Google Maps or Search and manually verify whether the specific field you updated has changed. Do not rely solely on the preview inside Search Atlas. 3. Review each changed field individually. If a batch deployment ("Deploy all changes") failed, try deploying each field one at a time. This helps identify which specific field is causing the rejection. 4. Remove or correct problematic attributes. If you recently added social media links, phone number types, or custom attributes, check whether those values are still supported by Google. Remove any that may be outdated and redeploy. 5. Check for yellow badge persistence. A yellow badge on a field inside Search Atlas may indicate the change is still pending or was not fully confirmed by Google, even if the deploy appeared successful. Try redeploying that specific field. 6. Refresh your GBP connection. Navigate to your GBP settings inside Search Atlas and confirm your Google account connection is active and authorised. A lapsed OAuth token can cause silent failures. 📋 Common Scenarios and Fixes - Hours not updating: Business hour changes can enter a Google-side pending state. Wait 72 hours and check again. If still not applied, remove the hours entry and redeploy. - "Deploy all changes" fails entirely: This is often caused by one invalid field blocking the entire batch. Deploy fields individually to isolate the issue, then correct and redeploy the problematic field. - Service areas show success but don't update: Service area changes are known to occasionally fail silently. Try removing the service area entries, saving, then re-adding and redeploying them. - Social or action links not saving: Google periodically deprecates supported link types. Remove any link that uses an older format (such as Facebook Messenger) and redeploy the remaining changes. ✅ What a Successful Deployment Looks Like A change is fully applied when: - The field in Search Atlas shows no yellow pending badge. - The update is visible on your live Google Business Profile on Google Maps or Search. - The change has been live for at least 24 hours without reverting. If the field still shows a pending badge after 72 hours, the deployment has likely encountered a silent rejection from Google and should be redeployed after reviewing the field value. 💬 Still Need Help? If you have followed the steps above and your changes are still not appearing on your live listing, our team can investigate the specific deployment logs for your location. 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.

Last updated on Oct 26, 2026

🤖 Fix Google Business Profile Auto-Reply Not Working

🔍 Overview If your Google Business Profile (GBP) is connected to Search Atlas but the AI Auto-Respond feature is not replying to new reviews, this article walks you through the most common causes and how to fix them step by step. ✅ Step 1: Confirm Your GBP Is Properly Connected A broken or expired GBP connection is the most common reason auto-replies stop working. To check your connection status: 1. In the left sidebar, click Local. 2. Select Overview. 3. Locate your GBP project and check that the connection status shows as active. If you see a warning, a disconnected badge, or a prompt to reconnect, your Google account needs to be re-authorised. 4. Follow the on-screen prompts to reconnect your Google account and grant the required permissions. After reconnecting, allow up to 15 minutes for the integration to refresh before testing again. ⚙️ Step 2: Verify Auto-Respond Is Enabled Even if your GBP is connected, the Auto-Respond toggle must be switched on at the project level. To confirm this: 1. In the left sidebar, click Local, then select Reviews. 2. Find the Auto-Respond setting at the top of the page. 3. Make sure the toggle is turned on. If it is off, enable it and save your changes. 4. Check that you have selected an AI response style or template if prompted — without this, the feature cannot generate replies. 🔄 Step 3: Check If Reviews Are Syncing Auto-replies can only be sent to reviews that have been successfully pulled into Search Atlas. If reviews are not syncing, the AI has nothing to respond to. To check review sync status: 1. Go to Local → Reviews in the left sidebar. 2. Look for your most recent Google reviews. Compare the dates shown in Search Atlas against your actual Google Business Profile to see if new reviews are missing. 3. If reviews are not up to date, try manually triggering a sync by refreshing the Reviews page or using any available Sync or Refresh button on the page. Note that Google can take up to 24 hours to surface new reviews through its API. A short delay is expected and does not always indicate an error. 🛠️ Step 4: Check for Reviews Already Responded To The Auto-Respond feature will not overwrite replies that already exist on a review — either from a previous manual response or a prior auto-reply attempt. If a review shows as responded inside Google but not inside Search Atlas, this may cause a sync mismatch. To resolve this: - Check the review inside Local → Reviews and confirm whether a response is already recorded. - If the response exists in Google but is missing in Search Atlas, reconnecting your GBP (Step 1) usually resolves the discrepancy. ⚠️ Common Reasons Auto-Replies Fail - Expired Google OAuth token: Your Google authorisation has timed out and needs to be renewed. - Insufficient Google permissions: The connected Google account may not have owner or manager access to the GBP listing. - Auto-Respond toggle turned off: The feature was disabled manually or reset after a platform update. - No AI response template selected: The feature requires a response style to be configured before it can generate replies. - Review sync delay: New reviews have not yet been pulled in from the Google API. 🚀 Quick Checklist Before Contacting Support 1. GBP connection is active with no warnings in Local → Overview. 2. Auto-Respond toggle is on in Local → Reviews. 3. An AI response style or template is selected. 4. New reviews are visible inside Local → Reviews. 5. The connected Google account has owner or manager access to the GBP listing. 6. You have waited at least 24 hours after a new review was posted. 💬 Still Need Help? If you have completed all the steps above and auto-replies are still not generating, 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.

Last updated on Oct 26, 2026

🏢 Fix SAB Address Removal and State Field Formatting

🔍 Overview If you manage a Service Area Business (SAB) on Google Business Profile, you may notice two common issues: Google periodically removes your business address from the profile, and the state field sometimes defaults to lowercase (for example, va instead of VA). This article explains why both happen and walks you through the steps to fix them. 📍 Why Google Removes SAB Addresses Google's guidelines for Service Area Businesses are strict: if your business serves customers at their location rather than at a physical storefront open to the public, Google requires that the address be hidden from the public-facing profile. This is by design, not a bug. Common reasons Google removes or hides a SAB address include: - Google's own enforcement: Google automatically detects profiles marked as SABs and removes any publicly displayed street address to comply with its own policies. - User-suggested edits: Anyone on Google Maps can suggest an edit to your profile. If a third party flags your address, Google may act on that suggestion. - Re-verification triggers: Certain profile changes, such as updating your service area or business category, can trigger a re-verification process that resets address visibility. - Duplicate profile detection: If Google finds a duplicate listing for your business, it may suppress or alter address data on one or both profiles. - Profile ownership or management changes: Transferring ownership or adding new managers can occasionally reset fields to their default states. ⚙️ How SAB Address Settings Work in Search Atlas Within Search Atlas, your GBP profile data is managed under Left sidebar → Local → Overview (GBP Profile Completion). From the Overview page you can review your profile's current address and service area configuration. Keep the following in mind: - If your profile is correctly categorised as an SAB, the address field in Search Atlas may appear blank or hidden — this reflects Google's live data, not a platform error. - Any address you enter for an SAB is stored as the internal business address for verification purposes only. It will not be displayed publicly on Google Maps. - Changes pushed from Search Atlas sync with Google's API. If Google removes the address on its end, the field in Search Atlas will update to reflect that removal on the next sync. 🔡 State Field Defaulting to Lowercase (e.g., "va" instead of "VA") The state field displaying as lowercase is a formatting issue that can occur when address data is imported, synced from a third-party source, or manually entered without capitalisation. Google's API accepts both cases but the United States Postal Service (USPS) standard requires two-letter state abbreviations to be uppercase. Displaying lowercase abbreviations can occasionally cause address validation mismatches or inconsistencies across platforms. To correct the state field capitalisation in Search Atlas: 1. Go to Left sidebar → GBP Projects and open the affected GBP project. 2. Navigate to Left sidebar → Local → Overview (GBP Profile Completion) and select the profile you want to edit. 3. Locate the Address section and click Edit. 4. In the state field, clear the existing lowercase value and re-enter the abbreviation in uppercase (for example, change va to VA). 5. Save your changes and allow up to 24 hours for the update to sync with Google. If the field reverts to lowercase after saving, the most likely cause is an upstream data source — such as a citation or data aggregator — feeding incorrect formatting back into your profile. Check your Left sidebar → Local → Local Citations to identify any citations listing the state in lowercase and update them individually. 🛠️ Troubleshooting Steps for Address Persistence If your SAB address keeps disappearing or resetting, work through the following steps in order: 1. Confirm your profile type: In your Google Business Profile dashboard, verify whether the profile is set as a Service Area Business or a storefront. If it is an SAB, address removal is expected Google behaviour and cannot be permanently reversed. 2. Check for suggested edits: Log in to your Google Business Profile Manager and review the Suggested Edits section. Reject any unauthorised changes to your address. 3. Review your service area settings: Overly broad or conflicting service areas can trigger automated Google audits. Narrow your service area to the regions you genuinely serve. 4. Inspect for duplicate listings: Search Google Maps for your business name and phone number to find any duplicate profiles. Request removal of duplicates through Google Business Profile support. 5. Audit your Local Citations: In Search Atlas, go to Left sidebar → Local → Local Citations and check that all citations carry consistent, correctly formatted address data. Inconsistent citations are a leading cause of repeated address removal. 6. Re-enter and re-save the address: After correcting any external data issues, return to Left sidebar → Local → Overview (GBP Profile Completion), edit the address fields, and save. Monitor the profile over the next 48–72 hours to confirm the data holds. 7. Document repeated removals: If the address is removed more than twice after following these steps, note the dates and times. This information is useful when escalating to Google Business Profile support directly. ✅ Best Practices for SAB Profile Stability - Always use uppercase, USPS-standard state abbreviations (e.g., VA, TX, NY) in every address field and citation. - Keep your business category, service area, and contact details consistent across all platforms and citations. - Avoid making multiple profile edits in quick succession, as this can trigger Google's automated review systems. - Regularly audit your citations via Left sidebar → Local → Local Citations to catch formatting inconsistencies early. 💬 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.

Last updated on Oct 26, 2026

⚠️ Local Heatmaps: 'Select All' in Bulk Edit May Miss Some Business Locations

A known bug in Local Heatmaps bulk edit mode causes Select All to skip business locations that have not yet been loaded — silently leaving them out of your bulk action. Use the workaround below to load all locations first; a fix is ready and will deploy shortly. 🔍 What's Happening In Local Heatmaps bulk edit mode, clicking Select All captures only the business locations already rendered in the dropdown at that moment. Any locations sitting behind a Load More prompt are excluded without any error or warning. As a result, bulk actions — such as updating settings or running grid scans — may apply to fewer locations than you intended. This affects any account that has more business locations than the initial dropdown load limit. 🛠️ Workaround Steps Until the fix is deployed, follow these steps before clicking Select All: 1. Open Local Heatmaps and enter bulk edit mode to display the business selector dropdown. 2. Scroll to the bottom of the dropdown and click Load More. 3. Continue clicking Load More until no further results appear — this confirms all your business locations are now fully loaded. 4. Click Select All. Every loaded location is now included in your bulk action. 📡 Engineering Status A fix has been completed and will deploy shortly. Once live, Select All will automatically include all business locations regardless of how many require loading — no manual Load More steps will be needed. The update applies automatically and requires no action from you. 📞 When to Contact Support Reach out to our support team if: - The Load More button does not appear even though you have more locations than are shown in the dropdown. - Clicking Load More repeatedly does not surface all your expected business locations. - The workaround above does not resolve the issue for your account. When contacting support, include your account name and a brief description of the behavior you're seeing so we can assist you quickly. 🎯 A fix is ready and will deploy shortly — no action needed on your end. In the meantime, the Load More workaround above ensures every bulk edit reaches all your intended locations. Contact support if you need further assistance before the fix goes live.

Last updated on Oct 26, 2026

🗺️ Fix Duplicate GBP Entries in Rank Tracker

🔍 Overview If you notice two entries for the same Google Business Profile (GBP) location inside Search Atlas Rank Tracker — for example, two listings named Michelle and Marcella — this guide explains why this happens and how to clean it up. Duplicate GBP entries can also cause report data to appear under the wrong company, so resolving them ensures your reporting stays accurate. 🤔 Why Duplicate GBP Entries Appear Duplicate GBP entries in Rank Tracker are usually caused by one of the following: - The same location was added more than once — either manually and via a Google Business Profile import, or added twice across different projects. - Multiple workspaces or projects share the same GBP location — if a location is connected to more than one project, it can appear separately in each context. - A previous GBP connection was not fully removed — disconnecting a profile without deleting the associated tracking entry leaves a ghost record behind. - The GBP account contains duplicate verified listings — Search Atlas reflects what exists in your Google account, so duplicate listings on Google's side will show up here too. 📊 Why Reports Show Data for the Wrong Company When two entries exist for the same GBP location, Search Atlas may pull ranking data into both entries independently. Because each entry can be associated with a different project or client workspace, keyword rankings and local map pack data can appear under the wrong company name on exported or scheduled reports. This is a data-source mismatch — the tracking entry and the report template are pointing to different project contexts. 🛠️ How to Find and Remove Duplicate Entries 1. In the left sidebar, click Keywords, then select Rank Tracker (Keyword Rank Tracker). 2. Review the list of tracked locations. Look for any GBP entries that share the same business name or address. 3. Click into each duplicate entry and note which project it is associated with and what keywords are being tracked. 4. Decide which entry is the correct one — typically the entry attached to the right client project with the most complete keyword list. 5. Select the duplicate entry you want to remove, open its settings, and delete or disconnect it from the project. 6. Confirm the remaining entry is linked to the correct project and that its report data source matches the intended client workspace. ✅ How to Verify Reports Are Using the Correct Data Source After removing the duplicate, check any affected reports to confirm they are pulling data from the correct GBP entry: - Open the report and review the data source or connected profile field in the report settings. - If the report was built against the deleted duplicate, reassign it to the correct remaining GBP entry. - Run a preview or refresh the report to confirm rankings and local data now reflect the right business. 🚫 How to Prevent This from Happening Again - Add each GBP location only once per project. Avoid importing a location that has already been added manually. - Audit your Google Business Profile account for duplicate verified listings before connecting them to Search Atlas. Merge or remove duplicates on Google's side first. - When removing a GBP connection, always delete the associated Rank Tracker entry at the same time to avoid ghost records. - Use clear, consistent project naming so it is easy to spot when the same location has been added to more than one project. 💬 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. Additional Notes Duplicate profiles created during heatmap setup: re-adding a business when configuring a heatmap instead of selecting the existing saved profile creates a second entry. Fix: remove the newer duplicate, then re-attach the heatmap to the original saved GBP profile by selecting it from saved locations rather than adding it anew.

Last updated on Oct 26, 2026

🗺️ Fix Local Citation Overlap Errors After Offering Changes

🔍 What Is a Local Citation Overlap Error? A local citation overlap error occurs when you attempt to submit a new citation campaign for a business location that is already covered by an existing active campaign. Search Atlas flags this conflict to protect data integrity and avoid contradictory signals across citation sources. This error commonly surfaces when a business updates its service offerings and tries to submit a new campaign without first resolving the existing one. ⚠️ Why This Happens When Offerings Change When your business updates its service offerings — for example, adding new service types, removing discontinued services, or shifting focus to a different area — your original citation campaign still holds the old directives. Submitting a new campaign without properly addressing the old one creates a conflict that triggers the overlap error. Common scenarios that cause this: - The original campaign is still active and targeting the same location or category. - New offering directives contradict the scope defined in the existing campaign. - A previous submission is still in progress and has not yet cleared the system. ✅ How to Resolve the Overlap Error Because resolving a local citation overlap error and reworking an affected campaign involves backend adjustments to your citation data, this issue requires assistance from the Search Atlas support team. When reaching out, please have the following ready to help the team resolve it as quickly as possible: - The business name and address associated with the conflicting campaign. - The exact error message you are seeing when attempting to submit. - A description of the offering changes you have made (e.g., services added, removed, or modified). - The date and time you first encountered the overlap error. - Any campaign names or IDs visible in your account related to the affected location. Having this information ready will allow the support team to identify the conflicting campaign, coordinate the necessary rework, and resubmit your citations with the correct updated directives. 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.

Last updated on Oct 26, 2026

🛠️ GBP Posts Not Generating Across Multiple Accounts

🔍 Overview Sometimes Google Business Profile (GBP) automated posts may stop generating across several accounts at once, while continuing to work for others. This is typically caused by a platform-level issue — not a problem with your individual settings — and requires our engineering team to resolve it. This article explains what happens during these incidents, how to check whether you are affected, and the fastest way to get your posts recovered. ⚠️ Signs You Are Affected - Automated GBP posts are generating for some accounts but not others. - Posts that were scheduled during a specific window were never published. - There is no error message visible — posts simply do not appear. 🧠 What Causes This Incidents like this are caused by background infrastructure failures that affect the automated post generation pipeline across multiple accounts at the same time. When this happens, the platform may silently skip posts for some accounts while continuing to process others normally. Our engineering team monitors for these failures and works to resolve them as quickly as possible, typically within a few hours of detection. ✅ What Our Team Does to Fix It When a fleet-wide post generation failure is identified, our specialized team takes the following steps: 1. Identifies the affected accounts — the team reviews which GBP automation configurations were impacted during the affected window. 2. Regenerates the missed posts — posts that were skipped are queued for regeneration. 3. Runs a publishing script — a script is initiated to ensure the recovered posts are published correctly to your Google Business Profiles. 4. Confirms completion — the team verifies that all affected posts have been successfully published before closing the incident. Resolution typically takes a few hours once the issue has been escalated to the specialized team. 🚀 What You Should Do Because this type of issue is caused by a platform-level failure, there are no settings changes or manual steps you can take to fix it yourself. The recommended course of action is: 1. Note the affected accounts — make a list of which GBP accounts are missing posts and the approximate dates or time window when posts stopped generating. 2. Check whether posts recover on their own — if an incident is already being resolved by our team, posts may begin appearing within a few hours without any action on your part. 3. Contact support if posts remain missing — if posts have not recovered after several hours, reach out so our team can escalate and apply the regeneration script to your specific accounts. 💡 Tips to Reduce Impact - Regularly review your GBP automation configurations to ensure they are active and correctly set up. - If you manage multiple GBP accounts, periodically spot-check that posts are appearing as expected, even during periods when you have not reported an issue. - Keep a note of which accounts and automation schedules are most critical so you can quickly identify gaps if a future incident occurs. 📞 Get Help If your GBP posts are still not generating after a few hours, or if you need help identifying which accounts were affected, our team is ready to escalate and apply the fix on your behalf. 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.

Last updated on Oct 26, 2026

GBP Local Heatmap iFrame Embed Not Loading

What This Article Covers Some customers using iFrame embeds for GBP Local Heatmaps have seen the embed become stuck on the Search Atlas loading screen, display a login prompt, or fail to render at all. The steps below will help you troubleshoot and resolve lingering browser or cache-related problems. Known Issue This is a confirmed platform issue where shared iFrame embeds for Local SEO Heatmaps can load indefinitely or redirect to a login screen instead of displaying the heatmap. If you are experiencing this behaviour, the steps below should help resolve it. Step-by-Step Troubleshooting 1. Clear your browser cache and cookies. Stale cache data is the most common reason an embed continues to misbehave. Clear your cache and cookies in your browser settings, then reload the page containing the iFrame. 2. Test in an incognito or private window. Open a fresh incognito or private browsing session and paste your iFrame embed URL directly into the address bar. This rules out any browser extensions or stored session data interfering with the load. 3. Try a different browser. If the embed still does not load, open it in a different browser entirely (for example, switch from Chrome to Firefox or Edge) to confirm whether the issue is browser-specific. 4. Regenerate the shareable iFrame embed. Log in to Search Atlas, navigate to the Local SEO Heatmaps section, and open the relevant heatmap. Generate a fresh iFrame embed code and replace the old embed code in your custom dashboard with the newly generated one. 5. Check that the heatmap data has loaded inside the platform. Before embedding, confirm that the heatmap renders correctly when you view it directly inside the platform. If it does not load there either, the underlying heatmap data may need to be refreshed first. 6. Test the updated embed. After replacing the embed code, reload your custom dashboard and confirm the heatmap now displays correctly. Still Need Help? If the iFrame embed is still loading indefinitely after completing all steps above, please contact our support team via the chat icon in the bottom-right corner of Search Atlas so we can investigate further for your account.

Last updated on Oct 26, 2026

🔌 Fix GSC and GBP Email Property Mismatch Errors

🧭 Overview When connecting Google Search Console (GSC) or Google Business Profile (GBP) to Search Atlas, you may encounter a frustrating situation: the connection reports success, but no properties or business locations appear. This happens when the Google account used to authenticate does not own or have verified access to any GSC properties or GBP listings. This article walks you through diagnosing the cause and resolving it step by step. ⚠️ What This Error Looks Like - GSC connects successfully but displays a message such as "This account doesn't have any site associated." - GBP connects successfully but the business location list is empty. - The integration screen shows your Google account email but no selectable properties or profiles. 🔍 Step 1 — Verify Which Google Account Is Connected The most common cause is authenticating with a personal or secondary Google account that has no GSC properties or GBP listings attached to it. 1. Inside Search Atlas, go to Settings → Integrations. 2. Check the email address shown under the GSC or GBP connection. Note it exactly. 3. Open a browser and go to search.google.com/search-console. Confirm you are signed in with that same email address. 4. Check whether any properties are listed. If the GSC dashboard is empty, this account has no associated sites. 5. Repeat for GBP by visiting business.google.com and confirming whether any business locations appear under that email. 🔄 Step 2 — Disconnect and Reconnect with the Correct Account If the authenticated email is not the owner or verified manager of your GSC properties or GBP listings, you must disconnect and reconnect using the correct account. 1. In Search Atlas, go to Settings → Integrations. 2. Click Disconnect next to the GSC or GBP integration. 3. Click Connect GSC Account (Site Metrics → GSC pages) or Connect GBP Account (Local → GBP Projects) again and sign in with the Google account that owns or has full access to the properties you want to pull in. 4. Grant all requested permissions when prompted by Google. 5. Return to Search Atlas and confirm that your properties or business locations now appear in the selection list. 👥 Step 3 — Check Property Permissions in Google Search Console If you must use a secondary or team Google account, that account needs to be added as a verified user inside GSC before it will surface any properties in Search Atlas. 1. Ask the GSC property owner to sign in to Google Search Console. 2. Select the relevant property from the left sidebar. 3. Go to Settings → Users and permissions. 4. Click Add user, enter the email address used in Search Atlas, and set the permission level to Full or Restricted depending on the access needed. 5. The invited user must accept the invitation via their Google account. 6. Once accepted, disconnect and reconnect GSC in Search Atlas using that email. The property should now appear. 🏢 Step 4 — Check Business Access in Google Business Profile For GBP, the connected email must be an owner or manager of the business location. 1. Ask the primary GBP owner to sign in to Google Business Profile. 2. Select the relevant business location. 3. Go to Business Profile settings → Managers. 4. Click Add and enter the email address used in Search Atlas. Assign the role of Manager or Owner. 5. The invited user must accept the invitation from their Google account. 6. Once accepted, disconnect and reconnect GBP in Search Atlas. The business location should now appear. 🧹 Step 5 — Clear Browser Cache and Re-authenticate Occasionally, browser-cached sessions cause Google to authenticate with an unintended account even after you attempt to switch. To rule this out: - Open an Incognito or Private browsing window. - Navigate to Search Atlas and attempt the GSC or GBP connection from there. - Sign in explicitly with the correct Google account when the Google authentication prompt appears. - This prevents cached credentials from interfering with the connection. ✅ Confirming a Successful Fix After completing the steps above, your integration is working correctly when: - The GSC connection shows a dropdown list of your verified properties for you to select. - The GBP connection shows your business name and location ready for selection. - Data begins populating in your Search Atlas dashboards within a few minutes. 🛠️ Quick Reference — Root Causes and Fixes - Wrong email authenticated: Disconnect and reconnect with the account that owns the properties. - Email has no GSC properties: Add it as a user inside GSC settings and re-authenticate. - Email has no GBP access: Add it as a manager inside GBP settings and re-authenticate. - Cached Google session: Use an Incognito window to force a clean sign-in. 💬 Still Need Help? If you have verified permissions on the correct account and properties still do not appear after following all steps above, 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.

Last updated on Oct 26, 2026

🔍 Fix GBP Automation, Posts & Whitelabel Reports

🗺️ Overview This article covers three common issues Search Atlas customers encounter when managing Google Business Profile (GBP) features and whitelabel reports: review reply automation pulling already-answered reviews, automated GBP posts not appearing for approval, and correctly linking GBP with whitelabel report configuration. Follow each section that applies to your situation. ⚠️ Why Is Review Reply Automation Flagging Already-Responded Reviews? Review reply automation scans your GBP for unanswered reviews. In some cases, reviews that already have a reply are incorrectly surfaced as tasks. This usually happens for one of the following reasons: - Sync delay: Search Atlas periodically syncs review data from Google. If a reply was posted recently — either manually or through another tool — the platform may not yet reflect the updated status, causing the review to appear unanswered. - Reply posted outside Search Atlas: Replies made directly in Google Business Manager or a third-party tool may not immediately update the review's status inside Search Atlas until the next sync cycle. - Duplicate automation rules: If multiple automation rules target the same review category or star rating, a review can be picked up by more than one rule and generate duplicate tasks. To resolve this: 1. Navigate to OTTO SEO → SEO Automation in the left sidebar (or go to /seo-automation-v3). 2. Open your active review reply automation and click Edit. 3. Check that no two rules share overlapping filters (e.g., the same star rating range). 4. Allow up to 24 hours for Google sync to complete and re-check whether the false tasks have cleared. 5. If a specific review continues to appear incorrectly, manually mark it as resolved inside the task list to remove it from the queue. 📝 Why Are Automated GBP Posts Not Generating for Approval? When automated GBP posts are configured but do not appear in your approval queue, the most common causes are a disconnected GBP account, an incomplete automation setup, or a scheduling conflict. Work through the following checks in order: 1. Confirm GBP is connected: Go to OTTO SEO → SEO Automation → select your project → open Settings. Under the Connections tab, verify that your Google Business Profile account shows a green Connected status. If it shows disconnected or an error, click Reconnect and complete the Google OAuth flow. 2. Check the automation rule status: In the left sidebar, go to Local (GBP Projects) and locate your GBP post rule. Confirm the toggle is set to Active. A paused or draft rule will not generate posts. 3. Review the posting schedule: Open the rule and confirm the frequency, time zone, and start date are set correctly. If the start date is in the future, no posts will be generated yet. 4. Verify approval workflow settings: If your rule requires manual approval before publishing, posts will appear in the Pending Approval queue — not auto-publish. Check that queue inside the automation panel to see if posts are waiting there. 5. Location-level permissions: For agency accounts managing multiple locations, ensure the specific location has GBP posting enabled and that the connected Google account has Manager or Owner permissions on that location in Google Business Manager. After confirming all settings, save the rule and allow up to one full scheduled cycle for a new post to generate. 🔗 How to Correctly Link Google Business Profile A properly linked GBP account is required for both review automation and post automation to function. Follow these steps to link or re-link your profile: 1. Go to OTTO SEO → SEO Automation in the left sidebar. 2. Select the project you want to configure. 3. Click Settings, then open the Connections tab. 4. Go to Local → GBP Projects and click Connect GBP Account. 5. Sign in with the Google account that has Manager or Owner access to the GBP location. 6. Select the correct Business Account and then the specific Location from the dropdown menus. 7. Click Save to confirm the connection. Important: If you manage multiple locations, repeat this process for each project. Each project should be linked to one GBP location. 📊 How to Configure Whitelabel Reports Whitelabel reports allow you to present Search Atlas data under your own brand. Here is how to set them up correctly: 1. Go to Reports → Report Builder in the left sidebar (or navigate to /report-builder/projects-list). 2. Select an existing report project or click + Create (Report Builder). 3. Open the Branding tab inside the report editor. 4. Upload your logo, set your brand colors, and enter your agency name. All Search Atlas branding will be replaced with yours in the final report. 5. To include GBP data (reviews, posts, insights) in the report, add a GBP module from the module library. The module will pull data from the GBP account linked to the selected project. 6. Confirm the correct project is selected at the top of the report builder so the GBP data source matches the intended location. 7. Click Save, then use the Share or Export options to deliver the whitelabeled report to your client. Tip: If GBP data is missing from the report module, verify that the GBP account is connected at the project level (see the section above) and that at least one sync has completed after the connection was made. ✅ Quick Troubleshooting Checklist - False review tasks: Check for overlapping automation rules and wait for the next sync cycle (up to 24 hours). - GBP posts not generating: Confirm GBP is connected, automation rule is active, and schedule/start date are correct. - GBP link issues: Reconnect via OTTO SEO → SEO Automation → Settings → Connections using an account with Manager or Owner permissions. - Whitelabel report missing GBP data: Ensure the report is linked to the correct project and GBP is connected at the project level. 💬 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.

Last updated on Oct 26, 2026

🛠️ GBP Place Action Links: Resolving a Timeout Save Error

Saving a Place Action Link in GBP Galactic Overview previously failed with a timeout error that prevented the link from being stored. This issue is resolved — if you still encounter the error, follow the steps below. ⚠️ What the Timeout Error Looks Like When you enter a URL in the Place Action Links modal on the GBP Galactic Overview page and click Save, an error modal appears and the link is not saved. The underlying cause is an HTTP 524 status — a Cloudflare gateway timeout indicating the save API did not respond before the connection expired. ✅ Fix Status: Issue Resolved The Search Atlas engineering team identified and resolved the root cause of this 524 timeout on the Place Action Links save endpoint. The fix is deployed — the save action now completes successfully for the vast majority of customers. 🛠️ Steps to Try If the Error Still Appears If you still see a save failure when adding or editing a Place Action Link, follow these steps in order: 1. Dismiss the error modal. 2. Wait approximately 30 seconds, then do a hard refresh of the GBP Galactic Overview page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). 3. Re-open the Place Action Links modal, re-enter your URL, and click Save. 4. If the error appears again after two retries, contact Search Atlas support and include a screenshot of the error modal along with the URL you are trying to save. Once the save completes without error, your Place Action Link is stored and the modal will close successfully. 🌀 This timeout error is resolved for most customers — if it persists on your account, a hard page refresh and retry typically clears it, or contact Search Atlas support for direct investigation.

Last updated on Oct 26, 2026

🌌 GBP Galactic Setup and Troubleshooting Guide

🗺️ Overview This guide covers three common setup and troubleshooting areas inside GBP Galactic: review reply automation filtering, automated GBP post generation, and whitelabeled report domain configuration. Work through each section that applies to your situation. ⭐ Part 1: Review Reply Automation — Filtering Old or Already-Responded Reviews Review reply automation is designed to respond only to new, unanswered reviews. If you are seeing tasks generated for reviews you have already responded to, or for older reviews that predate your automation setup, the steps below will resolve this. Why does this happen? When GBP Galactic first connects to your Google Business Profile, it performs an initial sync of all existing reviews. Without correct filtering, the automation can surface already-responded reviews as pending tasks. This is controlled by the deduplication logic and the hide filter. How to hide already-responded or unwanted reviews from automation: 1. Navigate to your GBP Galactic dashboard and open the Reviews section. 2. Locate the review that is incorrectly appearing as a task. 3. Click the eye icon next to the review. This marks the review as hidden and removes it from the active automation queue immediately. 4. Repeat for any other reviews that should not trigger automation tasks. Preventing this in future syncs: - After connecting a new GBP location, always audit the initial review list and hide any pre-existing responded reviews before enabling automation. - The deduplication system checks whether a reply already exists on the Google side. If a reply was posted outside of Search Atlas (for example, directly in Google Business Profile), allow up to 24 hours for the sync to detect it. Once detected, the review will no longer generate a task. - If tasks continue to appear for a review that has a confirmed reply on Google, use the eye icon to manually hide it and then contact support so the sync can be investigated. Key rule: The eye icon is your primary tool for removing any review from automation consideration. Hidden reviews are never deleted — they remain visible in your review history but are excluded from task generation. 📝 Part 2: Automated GBP Posts — Troubleshooting No-Generation Issues If automated GBP posts are not being generated for your approval, there are several prerequisites to check before assuming a platform error. Step 1 — Confirm automation is enabled for your location. 1. Go to your GBP Galactic dashboard and select the relevant business location. 2. Open Settings for that location and find the Automated Posts toggle. 3. Confirm the toggle is switched on. If it is off, enable it and allow up to 24 hours for the first post draft to appear. Step 2 — Check your approval workflow settings. - Automated posts are placed in an approval queue before publishing — they do not go live automatically unless you have explicitly enabled auto-publish. - Open the Posts tab inside GBP Galactic and check the Pending Approval filter. Posts may already be waiting there without triggering a notification if email alerts are disabled. - If auto-publish is enabled but posts are still not appearing on Google, confirm that your GBP connection has active write permissions (see Part 3 for reconnection steps). Step 3 — Verify your GBP location is correctly connected. - A disconnected or expired GBP OAuth token will silently prevent post generation. Go to Integrations inside your account settings and confirm the Google Business Profile connection shows a green Connected status. - If the status shows an error or expired state, click Reconnect and complete the Google authorisation flow. Posts should resume within 24 hours. Step 4 — Check post frequency limits. - If a post was generated recently, the system may be respecting a minimum interval between posts. Review your configured posting frequency in location settings and confirm the schedule aligns with your expectations. 🔗 Part 3: Whitelabeled Reports — Domain Configuration and URL Setup Whitelabeled reports allow you to share branded report links with clients using your own custom domain instead of a Search Atlas URL. Follow these steps to configure your domain correctly. Step 1 — Open Agency Settings. 1. Click your Avatar in the top navigation and select Agency Settings (White Label Setup). Step 2 — Open Whitelabel Settings. 1. Inside Agency Settings (White Label Setup), locate the white label configuration options (Upload Agency Logo / Brand Colors / Favicon / AI Assistant Branding). 2. Locate the Custom Domain field. Step 3 — Add your custom domain. 1. Enter the subdomain or domain you wish to use for report URLs, for example reports.youragency.com. 2. Save the domain entry. The platform will display the DNS records you need to add. Step 4 — Update your DNS settings. 1. Log in to your domain registrar or DNS provider. 2. Add the CNAME record exactly as shown in the platform. The record name will be your chosen subdomain and the value will point to the Search Atlas hosting address provided on screen. 3. DNS propagation typically takes between 15 minutes and 48 hours depending on your provider. Step 5 — Verify and activate. 1. Return to the whitelabel settings in Search Atlas and click Verify Domain. 2. Once verified, the status will change to Active and your report URLs will begin using your custom domain. 3. If verification fails after 48 hours, double-check that the CNAME record was entered without extra spaces and that no conflicting A records exist for the same subdomain. Linking your GBP to whitelabeled reports: - When creating a report that includes GBP data, ensure the GBP location is connected and authorised (see Part 2, Step 3). Without an active GBP connection, GBP widgets inside whitelabeled reports will display as empty or show a connection error to your client. - After reconnecting GBP, refresh the report and allow up to one hour for data to repopulate. ✅ Quick Checklist - Hide already-responded reviews using the eye icon to stop false automation tasks. - Confirm the Automated Posts toggle is on and check the left sidebar → Social → Pending Approvals queue before assuming posts are missing. - Reconnect your GBP OAuth token if it has expired — this affects both post generation and report data. - Add your CNAME record exactly as shown and use the Verify Domain button to activate your whitelabeled URL. 💬 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.

Last updated on Oct 26, 2026

🗺️ Fix GBP Profile Not Showing During Onboarding

🔍 Overview During Search Atlas onboarding, you may reach the step where you need to connect your Google Business Profile (GBP) — only to find that your profile does not appear in the list. This article explains the most common reasons this happens and walks you through how to fix it. ✅ Before You Begin Make sure you have the following ready before troubleshooting: - Access to the Google account that owns or manages your Google Business Profile - Your Search Atlas account credentials - A stable internet connection ⚠️ Common Reasons Your GBP Profile Does Not Appear There are several reasons why your profile may not show up during onboarding: - Wrong Google account connected: Search Atlas can only detect GBP profiles linked to the Google account you authorized during onboarding. If you have multiple Google accounts, you may have authenticated the wrong one. - Insufficient permissions: You must be listed as an Owner or Manager on the GBP profile. Profiles where you only have a pending invitation will not appear. - Profile not yet verified: Unverified Google Business Profiles are not returned by the Google API and will not appear in Search Atlas. - GBP account not connected to Google Search Console or Google Ads: In some cases, profiles that have never been accessed through the Google Business dashboard may not be fully active in the API. - Cache or session issue: Switching usernames or accounts mid-session — for example, during a support conversation — can cause the authorization token to become mismatched, preventing profiles from loading correctly. 🛠️ How to Fix the Issue 1. Sign out and reconnect your Google account. Go to Avatar Menu (👤) (avatar) → Settings → Integrations and disconnect the currently linked Google account. Then reconnect using the Google account that is the verified Owner or Manager of your GBP profile. 2. Confirm your GBP role. Open business.google.com and verify that your Google account appears as an Owner or Manager for the profile you expect to see. If your access is pending, accept the invitation first. 3. Check your profile's verification status. In the Google Business dashboard, confirm your profile shows as Verified. If it is not verified, complete Google's verification process before returning to Search Atlas onboarding. 4. Clear your browser cache and cookies, then reload Search Atlas and restart the onboarding flow. This resolves most session-related mismatches, including those caused by switching usernames mid-session. 5. Try a different browser or an incognito window. This rules out browser extensions or stored sessions interfering with the Google OAuth flow. 6. Restart the onboarding connection. Navigate to Left sidebar → GBP Projects (URL: /gbp-galactic/gbp-projects) and look for the option to add or reconnect a GBP project. Follow the prompts to re-authorize your Google account. 📋 If You Switched Usernames During a Support Session Changing your Search Atlas username while a support chat thread is active can cause your session token to reset. If this happened to you, follow these steps: 1. Log out of Search Atlas completely. 2. Clear your browser cache and cookies. 3. Log back in using your updated username and password. 4. Navigate to Left sidebar → GBP Projects and attempt to reconnect your GBP profile. Note that your previous chat thread may no longer be accessible after a username change. You can start a new support conversation at any time using the chat widget in the platform. 🗺️ Navigating to Your GBP Projects Once your profile is successfully connected, you can manage all your Google Business Profile activity from the GBP Projects section of Search Atlas: - Left sidebar → Local → Overview (GBP Profile Completion) — Summary of your GBP performance - Left sidebar → Local → Posts — Create and schedule GBP posts - Left sidebar → Local → Reviews — Monitor and respond to reviews - Left sidebar → Local → Media Library — Upload and manage photos - Left sidebar → Local → Local Citations — Track and manage local directory listings - Left sidebar → Local → My Tasks — View outstanding local SEO tasks 💬 Still Need Help? If your GBP profile still does not appear after following all the steps above, 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.

Last updated on Oct 26, 2026

🗺️ Fix Google Business Profile Verification Status Mismatch

🔍 Understanding the Mismatch Search Atlas pulls your Google Business Profile (GBP) verification status directly from the Google Business Profile API. If your profile shows as unverified inside Search Atlas but is confirmed verified in Google, the issue is not with your Google account — it is a data sync or permission problem between Search Atlas and your GBP connection. Standard steps like refreshing the page or waiting 24–48 hours will not fix this. Follow the diagnostic steps below to identify and resolve the root cause. ✅ Step 1: Confirm Your Profile Is Verified in Google Before troubleshooting the Search Atlas side, confirm the verification status directly in Google: 1. Go to business.google.com and sign in with the Google account connected to Search Atlas. 2. Locate the business profile in question. 3. Check that the profile displays a green checkmark or a Verified label. If it shows a pending or suspended status in Google, the mismatch originates in Google — resolve it there first before continuing. 🔗 Step 2: Check Which Google Account Is Connected Search Atlas can only read verification status from the Google account that was used during the GBP connection. A mismatch commonly occurs when the profile is verified under one Google account but Search Atlas is connected to a different one. 1. In Search Atlas, go to Left sidebar → GBP Projects. 2. Open the affected GBP project from your project list. 3. Note the Google account email displayed in the project settings or connection details. 4. Compare this email to the Google account that owns the verified profile at business.google.com. 5. If the emails do not match, the wrong account is connected. Proceed to Step 4 to reconnect with the correct account. 🔑 Step 3: Check Google Account Permissions Even if the correct Google account is connected, Search Atlas requires sufficient permissions to read your GBP data. A Owner or Manager role is required — a Site Manager role is not sufficient. 1. Sign in to business.google.com with the connected Google account. 2. Navigate to Business Profile settings → Managers. 3. Confirm the connected account holds an Owner or Manager role on the verified profile. 4. If the role is insufficient, have the profile Owner upgrade the permission level, then proceed to Step 5 to force a data refresh. 🔄 Step 4: Reconnect Your Google Business Profile If the wrong account is connected, or if permissions were recently changed, you need to reconnect the profile in Search Atlas. 1. Go to Left sidebar → GBP Projects and open the affected project. 2. Locate the option to disconnect or re-authenticate the Google account linked to this project. 3. Disconnect the existing connection. 4. Reconnect using the Google account that is the Owner or Manager of the verified profile. 5. Complete the Google authorization flow and grant all requested permissions. 6. Return to Left sidebar → GBP Projects → Overview and check whether the verification status now shows correctly. ⚡ Step 5: Force a Data Sync After fixing account or permission issues, the verification status may not update immediately. Trigger a manual sync to pull the latest data from Google: 1. Go to Left sidebar → GBP Projects → Overview. 2. Look for a Sync or Refresh Data option within the project dashboard and select it. 3. Wait up to 5 minutes for the sync to complete, then reload the page. 4. Confirm the verification status now displays correctly. ⚠️ Step 6: Check for a Suspended or Flagged Profile Google may mark a profile as unverified internally if it has been flagged, suspended, or has a pending reinstatement request — even if it previously showed as verified. Search Atlas will reflect this status accurately. - Sign in to business.google.com and look for any alerts, banners, or suspension notices on the profile. - If the profile is suspended or flagged, you must resolve the issue directly with Google before Search Atlas can show a verified status. - Visit the Google Business Profile Help Center for guidance on reinstating a suspended profile. 🆘 When to Contact Support If you have completed all steps above and the verification status still shows incorrectly in Search Atlas, the issue may require a manual review of your GBP connection at the account level. 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 you reach out, please have the following ready to speed up resolution: - The Google account email connected to Search Atlas for this project. - The Google account email that owns the verified GBP profile. - A screenshot of the verified status from business.google.com. - A screenshot of the unverified status shown inside Search Atlas.

Last updated on Oct 26, 2026

🗺️ Fix Google My Business Heatmap Not Generating

🔍 Overview If your Google My Business (GBP) location is connected in Search Atlas but the heatmap fails to generate — even after reconnecting your account or manually entering your address — the most common cause is missing keywords. The heatmap needs at least one keyword assigned to your location before it can fetch and display ranking data. This article walks you through the full troubleshooting process. ✅ Before You Start: Confirm Your Setup Before troubleshooting the heatmap itself, verify the following basics are in place: - Your GBP account is successfully connected to Search Atlas. - Your business location appears under Left sidebar → Local → GBP Projects. - Your business address is correct — either pulled automatically from Google or entered manually. If any of these are missing, resolve them first using the steps in the next section. 📍 Step 1 — Verify Your Location Is Connected and Configured 1. Go to Left sidebar → Local → GBP Projects. 2. Locate your business (for example, Power Within Chiropractic) in the project list. 3. Open the location and confirm that your business address is displayed correctly. - If the address is missing or incorrect, select the option to edit or manually enter your address and save your changes. 4. If your GBP account appears disconnected, use the reconnect option and follow the on-screen prompts to re-authorize your Google account. Once the address is confirmed and the account is connected, move on to Step 2. Note: a connected location with a valid address alone is not enough to generate a heatmap — keywords are also required. 🔑 Step 2 — Add Keywords to Your Location (Most Common Fix) This is the step most commonly missed. The heatmap uses keywords to determine which search terms to track and map local rankings for. Without at least one keyword, the heatmap has no data to display and will not generate. 1. Go to Left sidebar → GBP Projects and open your business location. 2. Navigate to the Overview tab (Left sidebar → GBP Projects → Overview). 3. Look for the keyword or heatmap settings section within your location project. 4. Add one or more relevant search keywords for your business — for example, chiropractor near me, chiropractic adjustment, or your primary service terms. 5. Save your changes. After adding keywords, allow a few minutes for the system to begin fetching data. Refresh the heatmap view to check if it has started generating. 🔄 Step 3 — If the Heatmap Still Does Not Appear If you have confirmed a valid address and added keywords but the heatmap is still not generating, try the following: - Wait and refresh: Heatmap data can take several minutes to populate after keywords are first added. Refresh the page after 5–10 minutes. - Check keyword relevance: Make sure the keywords you added match services your business is actually associated with on Google. Generic or unrelated terms may return no local ranking data. - Reconnect your GBP account: If the connection status appears unstable, disconnect and reconnect your Google account under Left sidebar → Local → GBP Projects, then re-add your keywords if they were cleared during the process. - Manually re-enter your address: If the address field is blank or auto-population failed, manually type and save your full business address, then confirm keywords are still assigned. ⚠️ Common Mistakes That Cause Heatmap Failures - Skipping keyword setup: Connecting your location and entering an address without adding keywords is the leading cause of heatmap generation failure. - Repeated reconnections without checking keywords: Reconnecting your GBP account will not fix a missing-keyword issue. Always verify keywords are assigned after any reconnection. - Incorrect or incomplete address: An address that does not match your verified Google Business Profile address can prevent accurate data fetching. 💬 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.

Last updated on Oct 26, 2026

🔄 Local SEO Points Monthly Rebill Not Processing

Overview Each billing cycle, your Local SEO points quota should automatically renew via a recurring charge. In some cases, this payment can fail silently — meaning your quota is not refreshed and you may not receive any notification. This article explains what to do if your Local SEO points monthly rebill or quota reset does not process correctly. What Causes This Issue A sync issue between the payment processor and the platform's quota system can cause a monthly rebill to fail without triggering an alert. When this happens, your Local SEO points are not replenished even though your subscription is active. What to Do Next Before contacting support, work through the following self-check steps — these steps may confirm the root cause and speed up resolution when you do reach out: 1. Check your billing history. Go to your account top-right avatar → Billing and review your recent charges. Look for the Local SEO rebill charge for the current billing cycle. If the charge is missing or shows a failed status, note the exact date and amount. 2. Verify your payment method. In the Avatar Menu (👤) → Billing section, confirm your card or payment method on file is not expired, has sufficient funds, and is set as your default payment method. If it is outdated, update it immediately — in some cases updating the payment method allows the next scheduled rebill to process correctly. 3. Check your email for payment failure notices. Search your inbox (including spam) for any failed payment notification from Search Atlas or Stripe. The email will confirm whether the charge was attempted and declined. 4. Wait up to 24 hours after updating your payment method. The platform may automatically retry a failed charge. If your quota replenishes within 24 hours, no further action is needed. If you have completed the steps above and your Local SEO points quota has still not been renewed, contact our support team. When you reach out, share the following so the team can act immediately: - Your account email address. - The billing date on which the rebill should have processed. - A screenshot or description of your billing history showing the missing or failed charge. Our team will confirm whether the payment failed on the billing side, escalate to engineering if a sync error is detected, and manually reset your Local SEO quota so you can continue working while the underlying issue is resolved. To reach support, 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. Tips to Prevent This in the Future - Keep your payment method up to date in your account billing settings. - Review your billing history at the start of each billing cycle to confirm your charge processed successfully. - If your Local SEO quota appears unchanged from the previous month, reach out to support promptly so the issue can be investigated and resolved quickly.

Last updated on Oct 26, 2026

📊 Why Citation Score Shows Google Listings Not Found

🔍 Overview If your Citation Score inside GBP Galactic shows Google or Google Maps as listing not found, you are not alone. This is a known display behaviour, and it does not mean your Google Business Profile is missing or broken. This article explains why it happens and what you can expect. 💡 Why Google and Google Maps Show as 'Listing Not Found' The Citation Score feature scans a wide network of third-party directories to detect and verify your business listings. However, Google and Google Maps are not accessible through the same automated scanning method used for other directories. Google restricts external tools from crawling and verifying Google Business Profile data in the same way. Because of this restriction, the Citation Score tool cannot automatically confirm the presence of your Google or Google Maps listing — even when your GBP profile is fully active, verified, and connected to GBP Galactic. The listing not found status for these two sources reflects a technical limitation of the scan, not an actual problem with your profile. ⚙️ Can I Manually Add Google and Google Maps Citations? At this time, Google and Google Maps cannot be manually added as citations within the Citation Score tool. Because these platforms fall outside the supported directory network, they are not available as sources you can submit or override manually. Your Citation Score will continue to reflect the status of all other supported directories, and your Google Business Profile remains fully functional and connected to GBP Galactic regardless of what the Citation Score displays for these two sources. ✅ How to Check Your Google Business Profile Is Working Correctly To confirm your GBP profile is active and properly connected, follow these steps: 1. Go to Left sidebar → Local → GBP Projects to open GBP Galactic. 2. Select the relevant GBP project from your project list. 3. Review the Overview page (Left sidebar → GBP Projects → Overview) to confirm your profile details, status, and connected account are displaying correctly. 4. Check Left sidebar → Local → Reviews (GBP Reviews) and Left sidebar → Local → Posts to confirm data is syncing from your live Google profile. If your Overview is loading profile data and your Reviews or Posts are syncing, your Google Business Profile is connected and working as expected. 📋 What the Citation Score Does Measure The Citation Score is still a valuable indicator of your broader local presence. It measures how consistently your business information appears across supported third-party directories, including platforms like Yelp, Bing Places, Apple Maps, and many others. A strong Citation Score on these platforms supports your overall local SEO health. To review your full citation status, navigate to Left sidebar → Local → Local Citations. Here you can see which directories have been found, which have inconsistencies, and where opportunities exist to build or fix listings. 🛠️ Summary - Google and Google Maps showing as listing not found in Citation Score is expected behaviour — it is a scan limitation, not a profile error. - Your GBP profile remains active and connected to GBP Galactic regardless of this display. - Manual citation submission for Google and Google Maps is not currently supported. - Use the Local Citations page to manage and improve citations across all other supported directories. 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.

Last updated on Oct 26, 2026

🛠️ Fix Failing Local SEO Heatmaps and Recover Credits

What Causes This Issue? If your Local SEO heatmaps are repeatedly failing and consuming credits without completing a scan, your keyword input or heatmap configuration may be contributing to the problem. Two commonly reported factors include: - Special characters in keywords — quotation marks (e.g. ") and other special characters in your keyword input may cause scans to fail while still deducting credits. - Stuck or unresponsive heatmap grids — some heatmap grids may become stuck in a broken state and cannot progress to a completed scan. Follow the steps below to attempt to resolve the problem yourself. How to Fix a Failing Heatmap 1. Navigate to the Local SEO Heatmaps section of your account. 2. Locate the heatmap that is failing or stuck. 3. Delete the failing heatmap. 4. Create a new heatmap with the same target location and keyword. 5. Before saving, review your keyword input and remove any quotation marks or special characters (e.g. ", ', &). Use plain text only. 6. Run the scan again. Once the keyword is free of special characters, the scan should complete successfully without consuming additional credits unexpectedly. Tips to Avoid This Problem in the Future - Always use plain-text keywords without quotation marks or symbols when setting up a heatmap. - If a scan appears stuck or shows no progress after a reasonable amount of time, do not re-run it repeatedly — each attempt may deduct credits even if the scan fails. - Check your available credit balance before running large batches of heatmaps. What If You Lost Credits Due to Failing Scans? If your credits were consumed by failed heatmap scans, our team can review your account and issue a refund where applicable. Credits have been successfully refunded for affected customers once the issue was confirmed. To request a credit refund, please contact our support team and describe the heatmaps that failed along with the approximate number of credits lost so the team can verify and restore your quota. Known Ongoing Improvements Our engineering team is actively working on additional improvements related to Local SEO Heatmaps, including better messaging when your quota is exhausted. These updates will make it easier to understand what is happening if a scan cannot proceed, so you can take action sooner and avoid unnecessary credit loss. Still Need Help? If you need further assistance, please use the chat widget on this page to reach our support team and we will be happy to help.

Last updated on Oct 26, 2026

🔗 Fix GBP Integration Not Showing After Client Auth

🔍 Overview When you send a client an authorization link to connect their Google account, it can sometimes appear as though nothing happened — their Google Business Profile (GBP) does not show up in your Integrations tab even after they confirm they've completed the login. This article explains the most common reasons this occurs and walks you through how to fix it. ⚙️ How the GBP Authorization Flow Works When you initiate a GBP integration for a client, Search Atlas generates a unique authorization link. Your client must: 1. Open the link in a browser where they are logged into the correct Google account — the one that owns or manages their GBP listing. 2. Grant the requested permissions on the Google consent screen. 3. Reach the confirmation page, which indicates the authorization was successful. Only after all three steps are completed will the connected account appear in your Integrations tab. If any step is skipped or completed incorrectly, the integration will not register. ⚠️ Common Reasons the Integration Does Not Appear - Wrong Google account used: The client was logged into a personal Gmail account instead of the Google account that manages their GBP. The authorization must be completed from the account that has Owner or Manager access to the listing. - Permissions not fully granted: The client clicked through the consent screen without accepting all requested permissions. Google requires full permission approval for the integration to activate. - Link opened while already logged into a different account: If the client's browser had a different Google account active, the authorization may have been granted to the wrong account. - Link expired or was reused: Authorization links are time-sensitive. If the client waited too long or tried to use the link more than once, it may no longer be valid. - Browser or cookie issue: Cached sessions or browser extensions can interfere with the Google consent flow, causing it to fail silently. 🛠️ Step-by-Step Troubleshooting 1. Confirm the correct Google account: Ask your client to verify which Google account manages their GBP. They can check this by visiting business.google.com and confirming they are logged in with the right account before clicking the authorization link. 2. Generate a new authorization link: Go to your Integrations tab in Search Atlas and revoke or remove the pending connection if one exists, then generate a fresh authorization link to send to your client. 3. Ask the client to use an Incognito or private window: This clears any cached Google sessions and ensures the browser is using only the account they actively log into during the process. 4. Walk through the consent screen together: If possible, have the client share their screen or confirm step by step that they clicked Allow (not Skip or Cancel) on every permission prompt. 5. Refresh your Integrations tab: After the client confirms completion, wait up to two minutes and then do a full page refresh. Newly authorized accounts can take a short moment to propagate. 6. Check for multiple Google accounts: If the client manages several Google accounts, make sure they are not switching between accounts mid-flow. The entire process should be completed within a single account session. ✅ How to Confirm the Integration Is Active Once the authorization is completed correctly, the connected Google account will appear in your Integrations tab with a green status indicator. You will then be able to select the associated GBP listing and attach it to the relevant project. If the account appears but no GBP listing is shown, the Google account used may not have access to any verified listings — confirm with your client that their listing is active and linked to that account. 💡 Tips to Prevent This Issue in the Future - Include clear instructions with the authorization link — let clients know they must use the specific Google account tied to their GBP, not their personal Gmail. - Recommend clients complete the authorization on a desktop browser in an Incognito window for the most reliable experience. - Follow up with clients promptly after sending the link, as links can expire if left unused. 🙋 Still Need Help? If you have followed all the steps above and the integration is still not appearing, 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.

Last updated on Oct 26, 2026

🔗 Fixing GBP and Project URL Mismatches

If you manage more than one website and Google Business Profile (GBP) inside Search Atlas, you may notice the AI Agent or other tools referencing a URL that does not match your active project. For example, your active project is ericrounds.com, but the system pulls data for a different business such as Total Service. This is especially common when you have two GBP profiles connected to two different domains under the same account. This article explains why this happens and how to correct it. 🤔 Why the Wrong URL Appears Search Atlas pulls data from the data source tied to your active project. When two GBP profiles are connected to two different domains, the platform can only align one GBP profile with one project at a time. A mismatch usually happens for one of these reasons: - The wrong GBP profile is linked to the current project. - Two projects share the same account, and the AI Agent is reading the default or most recently connected profile instead of the one you expect. - The project domain and the GBP profile point to different websites, so the system defaults to the connected GBP data. In short, the AI Agent uses whichever URL is stored as the data source for the project you are viewing. If that link is incorrect, the output will reference the wrong business. When more than one GBP profile is connected, the AI Agent does not always resolve the intended location automatically, so it can fall back to the wrong profile. Improvements to how the AI Agent auto-resolves the correct GBP location are actively in progress; in the meantime, manually confirming and correcting the connected profile is the reliable fix. 🔍 How to Confirm the Data Source Before making changes, check which GBP profile is currently attached to your project. 1. Open the project you want to review (for example, ericrounds.com). 2. Go to the project or GBP settings area. 3. Locate the connected Google Business Profile and note the business name and website listed. 4. Compare that URL to your active project domain. If the listed profile shows a different business or domain, that mismatch is the cause of the wrong URL. ⚙️ How to Fix the Mismatch Follow these steps to align the correct GBP profile with the correct project. 1. Open the affected project. 2. Go to the GBP or data source connection settings. 3. Disconnect the incorrect Google Business Profile if one is attached. 4. Select and connect the GBP profile that matches your project domain. 5. Save your changes and refresh the page. Once the correct profile is linked, the AI Agent and reports will begin using the matching URL. 💡 Tips for Managing Multiple GBP Profiles When you work with several websites and profiles, a few habits help prevent future mismatches: - One project per domain: Keep each website in its own project so data sources stay clean. - Match names carefully: Confirm the GBP business name and website match the project before connecting. - Check the active project: Always verify which project is selected before reviewing AI Agent output. - Reconnect after changes: If you switch domains or profiles, update the connection right away. 🔄 What to Do After Fixing the Link After connecting the correct profile, allow the platform a short time to sync the new data source. Then reopen the AI Agent and generate a fresh response. It should now reference your active project URL. If older reports still show the previous URL, they were created before the fix and will not update retroactively. 💬 Need More Help If the wrong URL continues to appear after reconnecting the correct GBP profile, our team can review your account setup. 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.

Last updated on Oct 26, 2026

🗺️ Fix Inaccurate GBP Galactic Post Content

🔍 Overview If OTTO is generating Google Business Profile (GBP) posts about topics completely unrelated to your business — for example, a pressure washing company receiving posts about hot tubs — the cause is almost always an incorrectly populated Galactic post prompt field. This article explains how that field works and how to fix it. ⚙️ How the Galactic Post Prompt Field Works When OTTO generates automated GBP posts, it can draw content from two sources: - Your Knowledge Graph — This is the recommended source. OTTO uses the business information, services, and details already stored in your OTTO settings to generate accurate, on-brand content automatically. - The Galactic post prompt field — This is an optional free-text field where you can provide a custom instruction or topic for OTTO to write about instead. If this field contains any text, OTTO will follow those instructions and may ignore your Knowledge Graph data entirely. The Galactic post prompt field is optional by design. Leaving it empty tells OTTO to rely on your Knowledge Graph, which produces the most relevant and accurate content for your business. 🚨 What Causes Off-Topic GBP Posts Off-topic posts are almost always caused by one of the following: - A previous prompt was entered in the Galactic post prompt field and was never removed. - A generic or unrelated instruction was accidentally saved in the field. - The field was populated during initial setup with placeholder or test content. Even a single word or leftover phrase in the prompt field is enough to steer OTTO away from your Knowledge Graph and generate irrelevant content. 🛠️ How to Fix It: Clear the Galactic Post Prompt Field 1. In the left sidebar, click OTTO SEO to open the OTTO dashboard. 2. In the left sidebar, go to Local → GBP Galactic (GBP Projects) and open Posts for your connected GBP property. 3. Find the post prompt field (sometimes labelled as a custom prompt or writing instruction box). 4. Check whether the field contains any text. If it does, delete all content from the field so it is completely empty. 5. Save your settings. 6. Allow OTTO to generate the next scheduled post. It will now pull content directly from your Knowledge Graph. You do not need to enter anything in the prompt field to get high-quality posts. An empty field is the correct configuration for most businesses. ✅ When Should You Use the Prompt Field? Leave the Galactic post prompt field empty in most cases. Only populate it if you have a specific, time-sensitive need — for example: - You are running a limited promotion and want posts to focus on a specific offer. - You want to highlight a new service that has not yet been added to your Knowledge Graph. - You are testing a particular content angle for a short period. If you do add a custom prompt, review it regularly and clear it once it is no longer needed. Leaving an outdated prompt in the field is the most common cause of inaccurate GBP posts. 🔎 Verify Your OTTO Settings and Knowledge Graph If clearing the prompt field does not resolve the issue, the next step is to confirm that your Knowledge Graph contains accurate business information. Incomplete or missing data in OTTO settings can sometimes cause OTTO to fill gaps with unrelated content. - Go to OTTO SEO in the left sidebar and open your OTTO settings for the affected property. - Confirm that your business name, category, services, and description are fully populated and accurate. - Make sure there are no placeholder entries or incorrect service categories listed. Once your Knowledge Graph is complete and the prompt field is empty, OTTO has everything it needs to generate relevant, accurate GBP posts without any manual input. 💬 Still Seeing Inaccurate Posts? If you have cleared the prompt field, verified your Knowledge Graph, and OTTO is still generating off-topic content, our team can investigate further. 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.

Last updated on Oct 26, 2026

🗂️ GBP Posts Count vs List View Discrepancy

🔍 Overview If your Search Atlas dashboard shows a total post count (for example, 19 posts) but only a smaller number of posts appear in the list view (for example, 1), this is a known UI display issue. It does not mean your posts are missing or were never published. The counter and the list view pull data from different parts of the system, and they can temporarily fall out of sync. This article explains what causes the discrepancy, how to confirm your Google Business Profile (GBP) posts were actually published, and what to do if the issue persists. ⚙️ Why This Happens The total post count shown in your dashboard reflects the number of posts recorded in the backend database. The list view, however, renders posts through a separate UI layer. When there is a sync delay or a rendering issue between these two layers, the counter may display the correct total while the list view shows fewer — or even just one — post. This means: - Your posts were created and stored correctly in the system. - The counter number is accurate — it reflects real records. - The list view has a display bug and is not rendering all posts at that moment. - Posts that are not visible in the list may still have been sent to Google Business Profile as scheduled. ✅ How to Confirm Your Posts Were Published to GBP Before assuming posts are missing, verify their status directly in Google Business Profile. Follow these steps: 1. Open your Google Business Profile account at business.google.com. 2. Navigate to the Posts section of your business listing. 3. Check whether the posts appear there with the correct dates and content. 4. If the posts are visible in GBP, they were successfully published by Search Atlas — the issue is limited to the dashboard display only. If the posts are not visible in GBP either, note the post titles or dates you expected to see and contact support so a teammate can review your account backend directly. 🛠️ Steps to Resolve the List View Display Issue Try the following steps in order to restore the full list view in your Search Atlas dashboard: 1. Refresh the page using a hard reload. On most browsers, press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac). This clears the local page cache and forces the list to reload. 2. Check your filters. Make sure no date range filter, status filter, or location filter is applied that could be hiding posts. Reset all filters to their default state. 3. Switch browsers. Open the dashboard in a different browser (for example, Chrome, Firefox, or Edge) to rule out a browser-specific rendering problem. 4. Log out and log back in. Sign out of Search Atlas, wait 30 seconds, then sign in again. This refreshes your session token and can resolve temporary sync issues. 5. Wait and revisit. If a backend sync is in progress, the list view may catch up within a few minutes. Return to the posts section after 5–10 minutes and check again. If the list view still does not show all posts after completing these steps, the issue requires a backend review by our support team. 🚫 Steps That Will NOT Fix This Issue The following actions are commonly suggested for UI problems but will not resolve a backend-to-UI sync discrepancy: - Clearing your browser cache and cookies — this affects locally stored files, not the backend data sync. - Reinstalling or resetting the browser — the issue is server-side, not browser-side. - Deleting and recreating posts — your original posts already exist in the system and may already be published to GBP. Avoid recreating posts until a support teammate confirms the originals were not published, as doing so could result in duplicate posts on your Google Business Profile. 📋 What to Have Ready When Contacting Support To help our team resolve the issue as quickly as possible, please gather the following before reaching out: - The total post count shown in your dashboard (for example, 19). - The number of posts visible in the list view (for example, 1). - The Google Business Profile location affected. - Any filters currently applied to the posts list (or confirmation that no filters are active). - A screenshot of the discrepancy if 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.

Last updated on Oct 26, 2026

⚠️ GBP Galactic API_UNSUPPORTED Error Explained

🔍 What This Error Means If you see an API_UNSUPPORTED error while using GBP Galactic inside Search Atlas, your account connection is not broken. This error is specific to the Q&A posting feature within GBP Galactic and reflects a known limitation with the underlying Google Business Profile API. Generic troubleshooting steps — such as reconnecting your account, re-verifying your location, or checking your GBP connection — will not resolve this error because the issue is not related to your account setup. 📋 Why This Happens Google's Business Profile API does not currently support posting or managing Q&A content through third-party platforms. When GBP Galactic attempts to perform a Q&A action via the API, Google returns an API_UNSUPPORTED response, which is then surfaced to you inside the platform. This is a limitation imposed by Google, not a bug or misconfiguration on your end or within Search Atlas. ✅ What Still Works in GBP Galactic Only Q&A functionality is affected. All other GBP Galactic features continue to work as expected, including: - Publishing and scheduling Google Posts - Updating business information such as hours, address, and contact details - Managing and responding to customer reviews - Uploading and managing photos - Viewing local performance insights and analytics - Managing products and services listed on your profile 🚫 What Is Currently Unsupported The following Q&A actions cannot be completed through GBP Galactic due to the API restriction: - Posting new questions to your Google Business Profile - Submitting answers to existing questions via the platform - Managing or moderating Q&A content from within Search Atlas 🛠️ What You Should Do Instead Until Google extends API support for Q&A functionality, you will need to manage your Q&A content directly through Google. Follow these steps: 1. Go to business.google.com and sign in with the Google account linked to your business profile. 2. Select the location you want to manage. 3. Navigate to the Q&A section from the left-hand menu or the profile overview. 4. Post new questions, submit answers, or flag inappropriate content directly from this interface. This workaround ensures your Q&A section stays active and up to date while the API limitation remains in place. 📌 Quick Summary - API_UNSUPPORTED error in GBP Galactic is caused by a Google API restriction, not an account or connection issue. - Only Q&A posting and management is affected — all other GBP Galactic features work normally. - Reconnecting your account or re-verifying your location will not fix this error. - Manage Q&A content directly at business.google.com until Google adds API 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.

Last updated on Oct 26, 2026

GBP Project Missing From Local Playbook

Overview When setting up a Local GBP Playbook, you may find that one or more of your Google Business Profile projects do not appear in the project selection dropdown — even though your GBP accounts are already connected. This article explains what to check on your end and what happens when the issue requires backend intervention from our team. Step 1: Verify Your GBP Project Is Connected Before anything else, confirm that the affected Google Business Profile is properly connected inside the platform. 1. Navigate to the GBP Projects section within the Local area of the platform. 2. Review the list of connected projects and confirm that the GBP you expect to appear in the Playbook is listed there. 3. If it is not listed, use the option to connect or add your Google Business Profile account and follow the on-screen prompts. 4. Once connected, return to the Local GBP Playbook and check whether the project now appears in the selector. Step 2: Confirm All Relevant GBPs Are Visible If you manage multiple locations or brands under the same account, make sure you are looking at the correct workspace and that all GBP accounts have been connected — not just some of them. It is possible for one location to appear while another does not if the connection step was only partially completed. - Check that each individual GBP location you need appears as its own entry in the GBP Projects section. - If a location is listed in GBP Projects but still missing from the Playbook selector, the issue is likely a backend configuration problem rather than a missing connection. Step 3: What to Do If the Project Is Connected but Still Missing Based on confirmed cases, a GBP project can be fully connected yet still fail to appear in the Local GBP Playbook selector due to a missing internal project link. This requires a backend fix applied by our support team and cannot be resolved by reconnecting the GBP or adjusting settings on your end. If you have completed Steps 1 and 2 and the project is still not appearing, contact our support team directly so a specialist can identify the missing internal link and apply the necessary backend fix. Once the fix is applied, the project will appear in the Playbook selector without any further action needed on your side. Tips to Avoid This Issue - Always connect a GBP account through the GBP Projects section before attempting to configure a Playbook for that location. - If you are setting up multiple locations, connect and verify each one individually before building out Playbooks. - After connecting a new GBP, allow a few moments for the platform to register the project before navigating to the Playbook selector. Still Not Resolved? If your GBP project is confirmed as connected in GBP Projects but still does not appear in the Local GBP Playbook selector, a backend fix is required. Please reach out to our support team via the chat widget so a specialist can resolve this for you as quickly as possible.

Last updated on Oct 26, 2026

🔶 Understanding Orange Triangle Warning Icons in GBP

🔶 What Is the Orange Triangle Icon? When reviewing your Google Business Profile (GBP) optimizations inside OTTO SEO, you may notice an orange triangle warning icon next to certain fields. This icon is a visual alert — it does not mean something is broken. It means OTTO has detected a conflict or mismatch between the data it recommends and the data currently present in your Google Business Profile or Knowledge Graph source. 📋 Why Does the Warning Appear? The orange triangle appears in the following situations: - Data conflict detected: The value OTTO wants to apply differs from what is already set in your GBP or pulled from another data source. - Override required: OTTO is flagging that applying its recommendation will overwrite existing information, and it wants you to confirm this intentionally. - Source mismatch: Information pulled from your Knowledge Graph or GBP does not match the optimized value OTTO has prepared for that field. These warnings are designed to protect you from accidentally overwriting correct business data without realising it. 🛠️ How to Resolve an Orange Triangle Warning 1. Click on the flagged field or the orange triangle icon to open the field detail panel. This will show you the current value versus the value OTTO recommends. 2. Review the conflict. Compare what is already set in your GBP with what OTTO is suggesting. Decide which value is accurate and up to date. 3. Choose your action: - Select Apply to accept OTTO's recommended value and push it to your GBP. - Select Keep existing to retain your current GBP value and dismiss the warning for that field. 4. Repeat for each field showing the orange triangle until all conflicts are resolved. 💡 Tips for Managing Warning Icons - Orange triangles are not errors — they are prompts for your review. Your profile is still active and visible while warnings are present. - If you have recently updated your GBP directly inside Google, OTTO may flag those fields until it re-syncs. Allow a short sync period and then refresh the page. - Prioritise warnings on high-impact fields such as business name, address, phone number, categories, and hours, as these affect local search ranking and customer trust. - Resolving all orange triangle warnings helps OTTO accurately track your optimization progress and score. ❓ Frequently Asked Questions Will ignoring the warnings affect my GBP listing? No. Your GBP listing remains live and functional. However, leaving conflicts unresolved means OTTO cannot apply its recommendations for those fields, which may limit your optimization improvements. Why does the same field keep showing a warning after I resolve it? This can happen if the data in your GBP is updated externally — for example, by Google's automated suggestions or edits from a third party. Re-open the field and review the new conflict. Can I bulk-resolve all warnings at once? Currently, each flagged field should be reviewed and resolved individually to ensure no important data is overwritten by mistake. 🆘 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.

Last updated on Oct 26, 2026

🛠️ GBP Automated Posts Stopped Publishing Across Profiles

🔍 What This Article Covers If your GBP automated posts suddenly stopped publishing across most or all of your connected profiles — even though your automation settings appear correct and are configured to post every few days — this article explains what happened, how it was resolved, and what steps to take if you experience this again. ⚠️ Recognising the Issue You may be affected by this type of outage if you notice the following: - Automated posts stopped publishing on a specific date with no changes made on your end. - The issue affects most or all of your GBP profiles, with only one or two continuing to post. - Your automation settings still appear active and correctly configured. - No error message is displayed inside the platform. This pattern — sudden, fleet-wide stoppage across many profiles simultaneously — is a strong indicator of a platform-level issue rather than a misconfiguration in your account. 🧩 What Caused This In the confirmed incident that prompted this article, our engineering team identified a backend platform issue that caused GBP post automation to stop working for all profiles. The issue was not caused by anything in customer accounts or settings — it was entirely internal to the platform. Engineering shipped a fix, and automated posting resumed for all affected profiles once the fix was deployed. ✅ Steps to Take When Automation Stops 1. Check that your automation settings are still active. Navigate to your GBP automation settings within the platform and confirm that automated posting is still enabled for your profiles and that your posting frequency settings are unchanged. 2. Note the date posting stopped. Record the exact date of the last successful post for each affected profile. This information helps our team diagnose the issue quickly. 3. Check how many profiles are affected. If only one profile is not posting, the cause is more likely a profile-specific setting, a Google Business Profile connection issue, or a content generation error. If the majority of your profiles stopped on the same date, it is likely a platform-level issue. 4. Wait briefly if a fix has already been announced. If our team has communicated an active incident or a recent fix, allow 24 hours for the queue to catch up and resume normal scheduling before contacting support. 5. Contact support if the issue persists. If posts have not resumed after 24 hours and no platform-wide incident has been announced, reach out to our support team with the date posting stopped and the number of affected profiles. We will investigate on your behalf.

Last updated on Oct 26, 2026

🔗 Fix GSC and GBP Integration Email Mismatch

🔍 Understanding the Problem When connecting Google Search Console (GSC) or Google Business Profile (GBP) to Search Atlas, the platform pulls data from the Google account you use to authenticate. If that account has no properties or businesses linked to it, Search Atlas will appear empty or show a "no data" state — even though your data exists in Google. This almost always happens because you authenticated with a different Google account than the one that owns or has access to your GSC properties or GBP listings. ⚠️ Common Causes - You have multiple Google accounts (e.g. a personal Gmail and a work Google Workspace account) and signed in with the wrong one. - Your GSC property or GBP listing is owned by a client or agency account, not your personal account. - You were granted access to GSC or GBP as a delegated user on a different email address. - You previously connected an account and recently switched primary Google accounts. 🛠️ How to Fix the Email Mismatch 1. Identify the correct Google account. Log in to Google Search Console (search.google.com/search-console) and note which email address is shown in the top-right corner when you can see your properties. Do the same in Google Business Profile (business.google.com). Write down the exact email address that has access. 2. Disconnect the current Google account in Search Atlas. Inside Search Atlas, navigate to Settings, then select Integrations. Locate the Google Search Console or Google Business Profile connection and click Disconnect. 3. Clear your browser's active Google session (recommended). Open a new browser tab and go to myaccount.google.com. Sign out of all Google accounts, or use an Incognito/Private window for the next step to avoid auto-selecting the wrong account. 4. Reconnect using the correct account. Back in Search Atlas Integrations, click Connect next to Google Search Console or Google Business Profile. When the Google authentication pop-up appears, select or sign in with the email address you identified in Step 1. 5. Grant all requested permissions. Make sure you check every permission checkbox Google presents. Search Atlas requires read access to your properties and location data to display results correctly. 6. Verify the connection. After authenticating, return to the relevant section of Search Atlas (e.g. the GSC dashboard or GBP manager). Your properties and business locations should now appear within a few minutes. 📋 Special Cases Agency or client-owned properties: If the GSC property or GBP listing belongs to a client, your client must add your Google account as a verified owner or full user in GSC, or as a manager in GBP, before Search Atlas can access that data. Service Account or delegated access: If you access GSC through a Google Workspace account where permissions are managed by an admin, contact your workspace administrator to confirm your account has the correct access level assigned directly to your email. Multiple properties across different accounts: Search Atlas connects to one Google account per integration at a time. If your properties are spread across multiple Google accounts, you will need to consolidate access — for example, by adding your primary email as an owner or manager on all relevant GSC properties and GBP listings. ✅ Quick Checklist Before Reconnecting - You can see your GSC properties when logged in with the target email at search.google.com/search-console. - You can see your GBP listings when logged in with the target email at business.google.com. - You have disconnected the old Google account inside Search Atlas Integrations. - You are connecting through an Incognito window or have signed out of other Google accounts. - You approved all permission scopes during the OAuth flow. 💬 Still Need Help? If you have followed all the steps above and your properties or business listings still do not appear, 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.

Last updated on Oct 26, 2026

🛠️ Fix 'Update Failed' Error Adding Social Profiles to GBP

🔍 Overview Some users have encountered an Update Failed error when attempting to add social media profile URLs to a Google Business Profile (GBP) inside Search Atlas. This issue can occur even after the GBP has been successfully connected. This article explains what the issue is, what you can try, and how to escalate if the problem persists. ⚠️ What Triggers This Error You may be affected by this issue if: - You have already connected your Google Business Profile in Search Atlas. - You navigate to your GBP project in Search Atlas and attempt to add social profile URLs. - After entering a social profile URL and attempting to save, the platform returns an Update Failed error. - The error repeats consistently, regardless of how many times you retry. ✅ Steps to Try Before Contacting Support 1. Confirm your GBP is properly connected. Verify that your Google Business Profile project is active and fully connected in Search Atlas. A profile that is not fully connected may produce save errors. 2. Check the URL format. Ensure the social profile URL you are entering is complete and correctly formatted (e.g., starts with https://). Malformed URLs can sometimes trigger a save failure. 3. Try a different social platform URL. Test whether a different platform's URL saves successfully. This helps confirm whether the issue is specific to a particular social network or is more general. 4. Clear your browser cache and retry. A stale browser session can occasionally interfere with form submissions. Clear your cache, reload the page, and attempt the update again. 🐛 Escalating the Issue If the steps above do not resolve the error, the issue may require investigation by the Search Atlas support team. When reaching out, please have the following ready: - The name of your GBP project in Search Atlas. - The exact error message you are seeing. - The social platform URL(s) you are attempting to add. - The approximate date and time when the error first occurred. 🙋 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.

Last updated on Oct 26, 2026

🛠️ Fix OTTO GBP Content Publishing Failed Errors

🔍 Overview If you are seeing Content Publishing Failed notifications for one or more of your OTTO-enabled Google Business Profiles (GBPs), you are not alone. This error typically means OTTO was unable to push content to your GBP on Google's side. This article explains the most common causes and walks you through the steps to fix them. ⚠️ Common Causes of Publishing Failures Before diving into fixes, it helps to understand what triggers this error. Publishing failures are almost always caused by one of the following: - Disconnected or expired Google account connection — The OAuth token linking your Google account to Search Atlas has expired or been revoked. - Insufficient Google account permissions — The connected Google account does not have Owner or Manager access to the GBP location. - GBP location suspended or unverified — Google has suspended or flagged the business listing, blocking third-party publishing. - Google API outage or rate limiting — Temporary issues on Google's end can cause batch publishing failures across multiple locations. - Duplicate or policy-violating content — Google rejects posts that contain content that violates its posting policies. 🛠️ Step-by-Step Troubleshooting 1. Check your Google account connection. Go to Left sidebar → OTTO SEO → SEO Automation (URL: /seo-automation-v3). Open OTTO settings and navigate to the connected accounts section. If your Google account shows a warning icon or a Reconnect prompt, click it and complete the OAuth flow to re-authorise the connection. 2. Verify account permissions on Google. Log in to business.google.com and confirm that the Google account connected to Search Atlas is listed as an Owner or Manager for every affected GBP location. Viewer-level access will cause publishing to fail silently. 3. Check the status of each GBP location. In your Google Business Profile dashboard, look for any locations marked as Suspended, Pending verification, or Disabled. OTTO cannot publish to listings that Google has restricted. Resolve any Google-side issues before retrying. 4. Retry the failed publications. After reconnecting your account or fixing permissions, return to Left sidebar → OTTO SEO → SEO Automation and locate the affected GBP tasks. Navigate to Content → Onpage Audit (Onpage Audit) and use the Retry option to trigger a fresh attempt for each failed item. 5. Review the content for policy violations. If only specific posts are failing while others succeed, open the flagged content and check for promotional language, URLs in disallowed fields, or restricted categories. Edit the content to align with Google's content policies and retry. 6. Wait and retry during a Google outage. If all GBPs failed at the same time and your connection looks healthy, the issue may be a temporary Google API disruption. Wait 30–60 minutes, then retry the publications. ✅ How to Confirm the Issue Is Resolved After completing the steps above, publishing is confirmed as working when: - The Content Publishing Failed notification no longer appears for the affected locations. - New OTTO-generated posts appear live on your GBP listings within the expected publishing window. - The OTTO task status in OTTO SEO shows Published or Completed rather than Failed. 🔄 Preventing Future Publishing Failures To minimise the chance of this error recurring, keep the following best practices in mind: - Re-authorise your Google account connection every time you change your Google password or revoke app permissions. - Ensure the connected Google account always retains Owner or Manager access to all GBP locations managed by OTTO. - Monitor your GBP listings in Google Business Profile regularly for verification or suspension notices. - Avoid bulk-scheduling large volumes of posts during known Google maintenance windows. 💬 Still Need Help? If you have followed all the steps above and are still seeing Content Publishing Failed errors, our team is ready to investigate further. 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. Additional Notes Image Validation Errors: Minimum size 400×300px, max 5MB, JPG/PNG only (no GIF/WebP/HEIC). Images must not contain watermarks or overlaid text covering >10% of image. Fix: open affected GBP content settings in Otto, remove/replace non-compliant image, re-trigger publishing.

Last updated on Oct 26, 2026

🔗 Fix Social Media Link Errors in Google Business Profile

🧭 Overview When adding social media links to your Google Business Profile (GBP), you may encounter a save error even if your URLs look correct. A common cause is a malformed URL — one that contains extra characters such as query parameters or locale codes that GBP does not accept. This article explains how to identify, clean, and successfully add your social media links to your GBP via Search Atlas. ⚠️ Why Social Media URLs Fail to Save Google Business Profile is strict about URL formatting. A URL that works fine in your browser may still be rejected by GBP if it contains any of the following: - Query parameters — extra text added after a ? or & symbol, such as &locale=en_GB, ?ref=homepage, or ?utm_source=share - Tracking codes — appended by social platforms or third-party tools when you copy a link - Locale or language suffixes — for example, Facebook sometimes appends &locale=en_GB or similar region codes - Redirect URLs — shortened or redirected links instead of the direct profile URL Even if only one of your social media URLs is malformed, GBP may block the entire save action — making it appear as though all your links are causing the error. 🔍 How to Identify a Malformed URL Before entering any social media URL into GBP, inspect it carefully. A clean URL should look simple and contain no extra characters after the main address. Use the examples below as a guide: - Facebook (clean): https://www.facebook.com/yourbusinessname - Facebook (malformed): https://www.facebook.com/yourbusinessname?locale=en_GB&ref=page_internal - LinkedIn (clean): https://www.linkedin.com/company/yourbusinessname - TikTok (clean): https://www.tiktok.com/@yourusername Everything after and including a ? or & character should be removed before you use the URL in GBP. 🛠️ How to Clean Up Your URLs 1. Open each social media profile in your browser. 2. Copy the URL from the address bar. 3. Paste it into a plain text editor (such as Notepad or TextEdit). 4. Find the first ? or & character in the URL. 5. Delete everything from that character to the end of the URL. 6. Double-check that the remaining URL still points to your correct profile page. 7. Use this cleaned URL when adding the link to your GBP. Example: If you copied https://www.facebook.com/mybusiness?locale=en_GB&ref=page_internal, the cleaned version would be https://www.facebook.com/mybusiness. 📍 How to Add Social Media Links in GBP via Search Atlas 1. Open your Search Atlas project and navigate to the Google Business Profile section for the relevant location. 2. Locate the social media links field within your GBP profile editor. 3. Paste each cleaned URL into the appropriate social media field (e.g. Facebook, LinkedIn, TikTok). 4. Review all entries to confirm no URL contains a ? or & character. 5. Save your changes. If the save succeeds, your social media links are now live on your GBP. 6. If you still encounter a save error after cleaning all URLs, remove each link one at a time to identify which specific URL is still causing the issue, then clean or replace that URL and try saving again. 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.

Last updated on Oct 26, 2026

🔧 Fix TOO_MANY_ENTRIES Google Business Profile Errors

What Is the TOO_MANY_ENTRIES Error? When deploying updates to your Google Business Profile (GBP) through Search Atlas, you may see a TOO_MANY_ENTRIES error. This error means Google's API rejected one or more of your updates. Because the specific causes and resolution steps for this error depend on your account configuration and the exact deployment that triggered it, our support team will need to investigate directly. This article explains what to expect and how to prepare for escalation so we can resolve it as quickly as possible. What to Do When You See This Error If you encounter a TOO_MANY_ENTRIES error during a GBP deployment in Search Atlas, please collect the following information before reaching out to our team: - The name of the GBP project where the error occurred. - The exact error message as it appears on screen (a screenshot is helpful). - The date and time the error first appeared. - A description of what you were attempting to deploy when the error occurred (for example, which fields or locations you were updating). - Whether the error appeared immediately or after a delay. - Whether you have attempted the deployment more than once and whether the error is consistent. What Happens Next Once you contact our support team with the above details, a teammate will review your deployment configuration and work with you to identify the cause of the error and the correct resolution path. Our team has visibility into deployment logs and API response data that can pinpoint exactly what triggered the rejection. 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.

Last updated on Oct 26, 2026

🔧 Fix GBP Deploy ATTRIBUTE_INVALID_ENUM_VALUE Error

🔍 Overview When you attempt to deploy all changes to your Google Business Profile (GBP) inside Search Atlas, you may see a Deployment Failed — ATTRIBUTE_INVALID_ENUM_VALUE error. The deploy does not complete, and refreshing or clearing your browser cache does not resolve the issue. This error is caused by a deprecated attribute value stored against your GBP location — specifically, Google's Business Profile API no longer accepts certain attribute values (for example, attributes/preferred_messaging_service set to facebook_messenger). Because Google rejects this value at the API level, all deploys for the affected location are blocked until the value is removed or corrected on the backend. ⚠️ What Causes This Error - One or more GBP attributes linked to your location contain a value that Google's API has deprecated and no longer accepts. - This is a backend data issue — it cannot be fixed by refreshing the page, clearing your browser cache, or using a different browser. - The problem affects the entire location, so all pending changes are blocked until the invalid attribute is resolved. ✅ What You Should Do 1. Confirm the error message. Make a note of the exact error text you see (e.g., Deployment Failed — ATTRIBUTE_INVALID_ENUM_VALUE) and the GBP location name it affects. 2. Check your GBP attributes in Google Business Profile directly. Log in to your Google Business Profile account at business.google.com and navigate to the affected location. Look for any messaging or communication-related attributes (such as a preferred messaging service). If you see Facebook Messenger or another deprecated messaging option listed, remove it and save the change. This may clear the deprecated value on Google's side and unblock your deploy. 3. Retry the deploy in Search Atlas. After removing any suspect attributes in Google Business Profile, return to Search Atlas and attempt to deploy your changes again. Wait a few minutes before retrying to allow Google's API to reflect the update. 4. If the deploy still fails, contact the Search Atlas support team using the chat widget (see below). Share the name of the affected GBP location and a screenshot or copy of the error message. Our engineering team will identify and remove the deprecated attribute value from the backend, which will unblock your deploys. 📊 What Happens After You Report It Once you reach out, our team will investigate the specific attribute causing the conflict on your location's profile. The fix involves removing or replacing the deprecated value on the backend — no action is required from you on the Google side beyond the steps above. After the fix is applied, your deploys will resume normally. If you need further help, please reach out to our support team via the chat widget in Search Atlas.

Last updated on Oct 26, 2026

🛠️ Fix the GBP TOO_MANY_ENTRIES Deployment Error

🔍 What Is the TOO_MANY_ENTRIES Error? When deploying updates to your Google Business Profile (GBP) through Search Atlas, you may encounter a TOO_MANY_ENTRIES error. This error is triggered by the Google Business Profile API when a deployment request contains more individual updates than Google allows in a single request. In practical terms, this means the number of fields or attribute changes bundled into one deployment exceeds Google's per-request limit. This is a restriction enforced on Google's side, not a Search Atlas platform issue. ⚠️ Why the Waiting Period Alone May Not Work You may have tried waiting before re-deploying, only to see the same error appear. If the underlying deployment contains too many entries, re-deploying the same batch without changes may cause the error to repeat. ✅ How to Resolve the Error Because the exact batch size limit and timing thresholds enforced by Google's API can vary and are not publicly documented, the recommended approach when you encounter this error is to contact the Search Atlas support team. A support agent will be able to review your specific deployment, identify the cause, and guide you through the correct resolution steps. When reaching out, please have the following ready so the team can assist you as quickly as possible: - The name of the GBP location or project affected - The exact error message you received (including any error codes shown) - The approximate date and time the error occurred - A description of the updates you were attempting to deploy (e.g., business hours, photos, attributes) 💡 General Best Practices - Avoid deploying large numbers of changes at once. If you have many GBP updates ready, consider grouping them into smaller, separate deployments rather than sending everything in a single batch. - Prioritise high-impact updates first. If you have many changes queued, deploy the most time-sensitive updates (such as holiday hours or address changes) before lower-priority ones. - Review attribute-heavy updates carefully. Profiles with many custom attributes (services, amenities, payment options) may be more prone to hitting API limits. Consider separating attribute updates into their own deployment. 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.

Last updated on Oct 26, 2026

🛠️ Fix Google Business Profile Verification in Report Builder

🔍 Overview When building a report in Report Builder, you may notice that your Google Business Profile (GBP) appears as not verified, even though it is verified inside the platform. This prevents you from selecting the profile and adding it to your report. This article explains why this happens and walks you through the steps to fix it. 💡 Why This Happens Report Builder checks the verification status of your GBP at the time the report is being built. If your profile was verified recently, or if there is a sync delay between the Local section and Report Builder, the verification status may not have updated yet. In some cases, the connection between your GBP project and Report Builder needs to be refreshed manually. ✅ Step 1 — Confirm Your GBP Is Verified in Local 1. In the left sidebar, click Local. 2. You will land on the GBP Projects page (/gbp-galactic/gbp-projects). 3. Locate the Google Business Profile you want to use in your report. 4. Confirm that the profile shows a verified status. If it does not, complete the GBP verification process before continuing. 🔄 Step 2 — Refresh the Profile Connection 1. While still in the GBP Projects section, click into the GBP project that is showing as unverified in Report Builder. 2. Navigate to GBP Projects → Overview for that project. 3. Allow the page to fully load so the platform can sync the latest verification data. 4. Wait 1–2 minutes, then proceed to Report Builder. 📊 Step 3 — Retry in Report Builder 1. In the left sidebar, click Reports. This opens the Report Builder projects list (/report-builder/projects-list). 2. Open the report you are working on, or create a new one. 3. Attempt to select your Google Business Profile again. 4. If the profile now shows as verified, you can proceed to add it to your report. 🛠️ Still Showing as Unverified? If your GBP is confirmed verified in the Local section but still appears unverified in Report Builder after following the steps above, try the following: - Hard refresh your browser by pressing Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to clear any cached page data. - Log out and log back in to force the platform to reload your account data and sync the latest verification status. - Try a different browser to rule out a browser-specific caching issue. ⚠️ Important Notes - Verification status syncs between Local and Report Builder may take a few minutes after a profile is first verified. - Only GBP profiles that are fully verified and connected to a Local project will be selectable in Report Builder. - If you have multiple GBP profiles, make sure you are selecting the correct one — profile names can look similar if you manage several locations. 🆘 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.

Last updated on Oct 26, 2026

📍 GBP Fixes and Improvements

We've shipped seven updates to Google Business Profile, resolving Media Library issues and refining navigation and preview behavior for a smoother experience. ✨ What's New This release includes three bug fixes and four improvements across GBP. - Media Library duplicate image fix: Uploaded images no longer show twice in the UI, and deleting no longer leaves a duplicate behind. - Sidebar navigation fix: GBP sidebar navigation items now enable correctly after connecting a new Google Business Profile account. - File size error fix: The Media Library no longer shows an incorrect 'File size too small' error — frontend and backend size limits are now aligned and communicated consistently. - New link badge: Added a "New link generated" badge indicator to the External Upload Link. - Name field sync: Updates to the GBP name field now reflect correctly in the preview panel and top business dropdown. - Audit out of beta: Removed the Beta tag from GBP Audit in the left navigation sidebar. - Streamlined Media Library access: Replaced the Media Library pop-up with an in-app redirect to the Media Library section, with the location pre-selected. 🛠️ How to Use It 1. Open Local (GBP Projects) from the left sidebar. 2. Connect or select a business account to access its profile tools. 3. Navigate to the Media Library to upload images, which now display and delete cleanly. 4. Use the External Upload Link and watch for the "New link generated" badge when a new link is created. 📋 What to Expect Media Library uploads, deletions, and error messaging now behave consistently, and navigation enables properly after connecting a new account. Clicking into the Media Library now redirects you in-app with the correct location pre-selected instead of opening a pop-up, and GBP Audit is now a fully released feature. 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.

Last updated on Oct 26, 2026

🔄 Fix GBP Locations Failing to Sync

🔍 Overview If you are seeing save errors when trying to add locations to your GBP Projects, or if your locations appear to have disappeared, this is almost always caused by a temporary Google API rate limit — not a problem with your Search Atlas account or data. This article explains what is happening, what to expect, and how to get your locations back without losing any project history or settings. ⚠️ What Is Causing This Error? Search Atlas connects to Google Business Profile (GBP) through Google's official API. Google places limits on how frequently tools like Search Atlas can make calls to that API. When those limits are reached, Google temporarily blocks new connection requests, which causes: - Save errors when trying to add or re-add locations to a GBP Project - Locations appearing to be missing or hidden inside the platform - Only being able to add one location at a time, with long waits between attempts This is an external restriction applied by Google — it is not a bug in Search Atlas, and it is not caused by disconnecting or reconnecting your Google account. 📋 What Happens to Your Existing Projects and Data? Your GBP Projects and all associated data are not deleted when this error occurs. Projects that appear to be missing are only temporarily hidden due to the sync issue. Once the API rate limit clears, your locations and projects will become accessible again with no loss of settings, history, or project data. 🛠️ What You Should Do 1. If you see a save error when adding locations, stop attempting to save repeatedly — multiple retries will not resolve a Google API rate limit and may extend the waiting period. 2. Wait a few hours before trying again. Google's rate limits are temporary and typically reset within hours. 3. After waiting, navigate to your GBP Projects area and attempt to add or view your locations again. 4. If your locations still do not appear after several hours, contact our support team so we can investigate further and assist you directly. ❓ Will Disconnecting and Reconnecting My Google Account Help? No. Disconnecting and reconnecting your Google account will not resolve an API rate limit error. The restriction is applied at the Google API level, not at the account authentication level. Reconnecting your account while the rate limit is active is unlikely to make a difference and is not necessary — your existing connection and all project data remain intact. ✅ When Everything Is Working Again Once Google's API rate limit has reset, you should be able to add and save multiple locations to your GBP Projects without errors. Your previously hidden projects and location data will be fully restored automatically. If you continue to experience issues or have any questions, please reach out to our support team and we will be happy to help.

Last updated on Oct 26, 2026

📅 GBP Automated Posts Not Appearing After Setup

🔍 Overview If you configured automated Google Business Profile (GBP) posts to start today but don't see any posts yet, there are a few common reasons this can happen. Posts may be held for review before publishing, or there may be a short delay after initial setup before the system begins generating content. The steps below will help you identify what to check. ⚙️ Why Posts May Not Appear After Configuration After setting up GBP post automation, posts may not appear publicly for one or more of the following reasons: - Posts require approval before publishing: Your automation settings may be configured to hold generated posts in a review queue. In this case, posts will not go live until they have been manually approved. - Initial setup delay: When you first configure automation, it may take some time — potentially up to a day — before the system begins generating and scheduling posts. This is expected behavior and not an error. - Automation settings may need review: If neither of the above applies, it is worth revisiting your automation configuration to confirm that it was saved correctly and is active for the intended GBP location. 🗂️ What to Check in Search Atlas To investigate why posts are not appearing, navigate to your GBP post automation settings within Search Atlas and look for any of the following: - Posts that are queued or awaiting review rather than published - An approval or review requirement that may be holding posts back from going live - Whether the automation is active and associated with the correct GBP location If you find posts in a pending or review state, approving them through your post management area should allow them to publish to your GBP listing. ⏱️ If You Just Completed Setup Today If you configured your automation settings today and no posts have appeared yet, this is likely normal. Allow up to 24 hours from the time of configuration, then return to your post management area to check whether posts have been generated or are queued for review. ✅ Quick Troubleshooting Checklist - Check for posts in a pending or review state in your GBP post automation area. - Confirm your automation is active and assigned to the correct GBP location. - Allow up to 24 hours if you only recently completed setup. - Review your automation configuration to ensure all settings were saved correctly. If you have checked all of the above and posts are still not appearing, reaching out to our support team with your project name, the GBP location affected, and the date you completed your configuration will help us 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.

Last updated on Oct 26, 2026

Automated GBP Posting Stopped After Image Bug

🔍 What Happened Some Google Business Profile (GBP) automated posts stopped publishing due to a bug in the AI image generation process. When image generation failed, the automation either skipped the post entirely or published it without an image. This issue has since been resolved on the backend, and automated posting should now be running normally across connected GBP locations. ⚙️ Why Some Locations Were Affected and Others Were Not The bug did not affect every account or location equally. Whether a specific location was impacted depended on how that location's automation was configured — in particular, whether it relied on automatic image generation as part of the posting process. Locations that were not using image generation in their automation were less likely to be affected. ✅ How to Confirm Your Automations Are Working Again Because the fix was applied on the backend, no configuration changes are required on your end. To confirm that automated posting has resumed for your locations, check whether new posts have appeared in your GBP locations after the fix was deployed. If new posts are showing up, your automation is running normally again. If you are not seeing new posts and believe your automation should have resumed, please reach out to the Search Atlas support team so they can investigate the specific location on your behalf. Provide the affected location name(s) and a description of what you are seeing. 💡 What to Do If Posting Has Not Resumed If automated posting is still not working for one or more locations, please contact the Search Atlas support team. You can reach support via the live chat widget in the bottom-right corner of the platform — type human teammate to be connected with a member of our team. Provide the affected location name(s) and a description of what you are seeing so the team can investigate directly.

Last updated on Oct 26, 2026

🛠️ GBP Auto Respond and Automated Posting Quota Issues

🔍 Overview Some users encounter two related issues inside the Google Business Profile (GBP) section of Search Atlas: - Auto Respond won't enable — the toggle stays off even after clicking to save changes. - Automated Posting shows a quota error — the platform reports you have hit a 10-account limit even though your actual number of connected listings is much lower. Both issues are caused by backend quota counting bugs, not by anything the user has misconfigured. Engineering has identified and resolved systemic quota-counting errors that allowed usage counters to become inflated or misaligned with the actual number of listings on an account. If you are experiencing either symptom, follow the steps below before contacting support. ✅ Step 1: Confirm Your Actual Listing Count Before reaching out, verify how many GBP listings are connected to your account. If the number shown in the Automated Posting quota error does not match your real listing count, this confirms the counter is inflated on the backend — which is a known bug that requires a support team correction. 🔄 Step 2: Try Disabling and Re-enabling the Feature For both Auto Respond and Automated Posting, try the following: 1. Turn the feature off completely. 2. Save or apply the change. 3. Wait a few seconds, then turn the feature back on. 4. Save again and refresh the page. In some cases, this clears a stale state and allows the setting to save correctly. If the toggle still reverts to off or the quota error reappears, proceed to the next step. 🔄 Step 3: Check for Recent Plan Changes If your account has recently been downgraded from a higher plan to a lower one, your Automated Posting quota may not have been correctly adjusted at the time of the change. This is a known issue where the quota counter is not properly enforced during plan transitions, which can leave your account in an inconsistent state. Make a note of any recent plan changes so you can share this context with the support team. 💬 Step 4: Contact Support for a Backend Quota Reset If the steps above do not resolve the issue, the quota counter on your account needs to be corrected manually by the support team — exactly as was done for the customer who reported this problem originally. This is not something you can fix from within the platform settings. When you contact support, include the following information to speed up the resolution: - Which feature is affected: Auto Respond, Automated Posting, or both. - The exact error message you see (e.g., "10-account limit reached"). - The actual number of GBP listings connected to your account. - Whether your plan has changed recently. 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. 📋 What to Expect After Support Intervenes Once the support team corrects the quota on the backend, both Automated Posting and Auto Respond should become available to enable without errors. You do not need to reconnect your listings or change any settings — the fix is applied on the account level. After confirmation from the support team, refresh the page and attempt to enable the features again. ⚠️ Known Background Context Engineering has shipped fixes for several quota-counting bugs in the GBP Automated Posting system, including cases where the usage counter allowed activity above the plan limit, and cases where the counter became inflated independently of actual usage. If you are seeing a quota error that clearly does not reflect your real usage, you are likely affected by a residual instance of one of these bugs. Reporting it through the chat widget helps the team identify and resolve any remaining cases.

Last updated on Oct 26, 2026

🛠️ GBP Auto-Posting and Auto-Review-Reply Not Working

🔍 Overview Some users have reported two related issues with Google Business Profile (GBP) automation in Search Atlas: automated posts requiring manual approval despite being set to post automatically, and the auto-reply to reviews toggle appearing active but not sending replies. Both issues were confirmed as platform bugs and have since been resolved by the engineering team. This article explains what happened, what was fixed, and what to do if you are still seeing unexpected behaviour. ⚙️ What Was Happening - Auto-posting not working: Posts that should have published automatically were being held for manual approval, even when the automatic posting setting was enabled. - Auto-review-reply not working: The toggle for automatic review replies appeared to be active and showed a confirmation, but replies were not actually being sent to reviews. ✅ What Was Fixed Both issues were escalated as high-priority bugs and resolved by the Search Atlas engineering team. 1. Auto-posting fix: A confirmed bug was causing automated posts to be skipped or held for approval incorrectly. The fix has been built and deployed to production. 2. Auto-review-reply fix: A separate issue was preventing review replies from being sent even when the automation appeared enabled. This has also been resolved and confirmed working in production. 🔎 Steps to Verify Your Settings Are Now Working If you are on the platform now and want to confirm automation is functioning correctly, follow these steps. 1. Navigate to your GBP automation settings and confirm that auto-posting is still set to publish without requiring manual approval. If the setting was changed during the issue period, re-apply your preferred setting and save. 2. Check your recent posts to confirm the latest scheduled content published automatically without requiring a manual approval step. 3. Review your GBP review reply settings and confirm the auto-reply option is enabled. 4. Check your recent reviews to see whether replies have been posted automatically. Keep in mind that any replies you sent manually before the fix will already appear — only reviews received after the fix was deployed should be used to confirm the automation is now working. ⚠️ Still Seeing the Problem? If you have verified your settings and automation is still not working as expected after the fix was deployed, this may indicate a separate configuration issue specific to your account or location. In particular, confirm the following before contacting support: - Your GBP location is connected and active in the platform. - No recent changes were made to your GBP location connection that may have interrupted automation. If the issue persists, please reach out to the Search Atlas support team so they can investigate your specific account configuration.

Last updated on Oct 26, 2026

🔧 Fix GBP 'Not Found' Error After Domain Transfer

What This Error Means After transferring a domain from an agency into OTTO, you may see a 'not found' or 'error not found' message when opening your Google Business Profile (GBP) Audit. This error prevents your location data from loading and is not related to the heatmap — it affects the GBP Audit section itself. This is a known backend issue that occurs after certain domain transfers to OTTO and cannot be resolved by browser-side actions alone. The steps below will help you confirm the scope of the problem, attempt the available self-serve actions, and — if the issue persists — provide our team with the information needed to fix it on the backend quickly. Step 1: Attempt a GBP Reconnection 1. In the left sidebar, navigate to Local (GBP Projects). 2. Locate the affected GBP location and disconnect it from your OTTO account by removing the GBP connection for that location. 3. Reconnect the same GBP location by re-authorising your Google account and selecting the correct business listing. This re-establishes the link between OTTO and your GBP location data and resolves the error in many cases. 4. Reload the GBP Audit and check whether the 'not found' error has cleared. If the data now loads correctly, no further action is needed. Step 2: If the Error Persists, Collect These Details If reconnecting the GBP location does not clear the error, the disconnect is at the backend level and requires our team to re-link the record directly. Before reaching out, gather the following so the fix can be applied as quickly as possible: 1. Check whether the error affects all GBP locations or only specific ones by navigating to each location within your GBP Audit. Note which locations are affected — this tells our team whether the issue is account-wide or tied to a specific location record. 2. Note the exact error message text displayed on screen (for example, 'not found' or 'error not found'). 3. Take a screenshot or record a short screen video showing the error. This allows our team to confirm the exact behaviour and prioritise the backend fix. 4. Note the domain name that was transferred and, if known, the agency account it was transferred from. Our team uses this to locate the affected record in the backend and re-link the GBP location data correctly. 5. Contact our support team through the platform and share the information collected above so the backend fix can be applied to your account without delay. What Our Team Will Do Once you reach out with the details above, our support team will investigate the affected account on the backend and re-link the GBP location data that became disconnected during the domain transfer. This fix is applied directly to your account — there is no action required from you after you submit the information. Most cases are resolved in the same support session once the affected domain and location are identified. If you need further assistance, reach out to our support team through the platform and a member of our team will be happy to help.

Last updated on Oct 26, 2026

🛠️ GBP Post Images Failing to Save

🔍 Overview Some customers have experienced an issue where adding an image to a Google Business Profile (GBP) post causes the post to fail to save. The post may remain in draft state without the image attached. This has been confirmed as a backend defect that Search Atlas engineering has investigated and resolved. ⚠️ Symptoms - You add an image to a GBP post, but the post will not save. - The issue occurs across multiple projects, not just one. - The post appears to be stuck in draft state with no image attached. - The image may appear as a placeholder or cloud icon in the post preview. 📋 What Caused This Issue This was a confirmed backend defect in the Search Atlas platform. Images failed to attach to posts because of missing internal media reference data that links uploaded images to their respective posts. Additionally, a separate issue caused a 403 error when uploading images in GBP Posts, and in some cases the UI could become frozen or unresponsive during post creation. Engineering has resolved these defects and applied fixes to affected posts. ✅ Steps to Take Right Now 1. Navigate to Left sidebar → Local → GBP Projects and open the affected project. 2. Locate the post or posts that failed to save with images. Check whether they are sitting in draft state. 3. Try re-opening each affected draft post and re-attaching your image, then attempt to save again. In many cases, the underlying fix allows the save to complete successfully now. 4. If the image still does not attach or the post remains stuck, do not delete the draft. Leave it in place so that our team can inspect the post data if needed. 5. Note which specific posts and projects are affected before reaching out — this helps our team investigate faster. 💡 Tips to Avoid Image Issues - Use images uploaded directly through the platform rather than external URLs where possible, as external URLs may not meet storage requirements. - If you see a placeholder or cloud icon instead of your image in the post preview, this is a sign the image did not attach correctly — do not publish the post until the image is confirmed. - If the post creation screen freezes or becomes unresponsive while uploading an image, refresh the page and check your drafts before attempting again to avoid creating duplicate posts. 🚀 Still Experiencing the Issue? If you re-attach your image and the post still will not save, this may indicate a new or unresolved instance of the defect. Please do not delete your draft posts, as our engineering team may need to inspect them 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.

Last updated on Oct 26, 2026

📅 Fix GBP Automated Posts Not Appearing

🔍 Overview After configuring automated posts for your Google Business Profile (GBP), you may notice that no posts appear — even when the start date is set to today. This guide walks you through the most common causes and how to fix them so your posts publish as expected. ⚙️ How Automated GBP Posts Work Search Atlas schedules and publishes GBP posts automatically based on the configuration you set. However, a few conditions must be met before posts will go live. If any step in the setup is incomplete, posts will not be created or published. ✅ Step 1: Verify Your GBP Project Is Connected Automated posts require an active, connected GBP project. To check this: 1. Go to Left sidebar → Local → GBP Projects to open your GBP projects dashboard. 2. Confirm your business location appears and shows a connected status. 3. If your location is disconnected or missing, reconnect your Google Business Profile account before proceeding. 📝 Step 2: Check Your Post Configuration Navigate to your post settings and review each field carefully: 1. Go to Left sidebar → GBP Projects → Posts. 2. Open the automated post series you configured. 3. Confirm the following are set correctly: - Start date: Make sure it is set to today or a past date — future dates will delay publishing. - Frequency: Ensure a posting interval (e.g., weekly, daily) has been selected. - Post content: At least one post template or content variation must be saved. - Location assigned: The post series must be linked to a specific GBP location. 4. Save any changes you make before leaving the page. ⏱️ Step 3: Allow Processing Time After saving your configuration, automated posts do not always publish instantly. The system may take up to a few hours to process and queue the first post, especially if the start date is set to the current day. Wait a few hours, then return to Left sidebar → Local → GBP Projects → Posts to check whether the first post has been created. 🔄 Step 4: Confirm Google Permissions Are Active Search Atlas needs ongoing permission to publish to your GBP listing. If your Google account credentials have expired or been revoked, posts will silently fail. To rule this out: 1. Go to Left sidebar → Local → GBP Projects and select your GBP project. 2. Check whether there is any warning or error message related to your Google account connection. 3. If you see a reconnect prompt, follow the on-screen steps to reauthorise access. 4. After reconnecting, return to Left sidebar → GBP Projects → Posts and confirm your automation is still enabled. 🛠️ Step 5: Review the Posts Feed for Errors Search Atlas logs post activity in your Posts dashboard. To check for errors: 1. Navigate to Left sidebar → GBP Projects → Posts. 2. Look for any posts marked with a failed or error status. 3. If errors are present, note the message shown — this will help identify whether the issue is with content formatting, image size, or an account permission problem. 4. Correct the flagged issue and re-enable the automation if it was paused. 💡 Common Reasons Automated Posts Are Not Created - Start date is in the future: Posts will not publish until the configured date is reached. - No content template saved: The system has nothing to publish if post content is empty. - GBP account disconnected: Expired Google permissions stop all publishing activity. - Location not assigned: A post series without a linked location will not run. - Automation toggled off: Double-check that the automated posting switch is turned on. 🆘 Still Not Seeing Posts? If you have followed all the steps above and automated posts are still not appearing, there may be an account-level or platform issue that requires investigation. 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.

Last updated on Oct 26, 2026

🛠️ GBP Posts Not Queuing for Scheduling

🔍 What Is This Issue? When creating a Google Business Profile (GBP) post in Search Atlas, the post should automatically enter a queue for scheduling. Some users have reported that posts stop queuing — even when switching to a different computer or browser. This is usually caused by a temporary platform issue or stale browser data interfering with the scheduling process. ⚙️ What Caused This? A known issue affecting GBP post creation was identified and resolved by the Search Atlas development team. If you are still experiencing this problem, leftover browser cache and cookies are the most likely culprit preventing the fix from taking effect on your end. ✅ How to Fix It Follow these steps to restore normal scheduling behaviour: 1. Clear your browser cache and cookies. In most browsers, open Settings and look for a privacy or history section where you can clear cached data and cookies. After clearing, close and reopen your browser. 2. Try again in an incognito or private window. Open a new incognito (Chrome) or private (Firefox/Safari/Edge) window, log back in to Search Atlas, and attempt to create the GBP post again. 3. Navigate to your GBP project. Open the relevant GBP project within Search Atlas. 4. Recreate the post. Attempt to create and schedule your GBP post as normal. It should now enter the scheduling queue correctly. 💡 Additional Tips - If you have multiple GBP locations, check whether the issue affects all of them or just one specific location. - Make sure you are using a supported, up-to-date browser for the best experience with Search Atlas. - If the post shows a Failed or stuck Scheduled status after attempting again, note the post details as this may help our team investigate further. 🆘 Still Having Trouble? If clearing your cache and using an incognito window does not resolve the issue, the problem may require a deeper look 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.

Last updated on Oct 26, 2026

📋 Fix Google Business Profile Social Media URL Errors

🔍 What This Error Means When you add social media links to your Google Business Profile, Google validates each URL against strict formatting rules. If a URL contains tracking parameters, session tokens, or extra fragments, Google rejects it with an INVALID_SOCIAL_MEDIA_PROFILE_URL error. This guide shows you exactly how to clean and format your TikTok, Facebook, and Instagram URLs so Google accepts them. ⚠️ Why URLs Fail Validation The most common reason URLs fail is the presence of extra characters appended by mobile apps, referral systems, or analytics tools. These are invisible to you when you copy a link from your phone or browser, but Google's validator rejects them immediately. Common culprits include: - ?_t= — TikTok session tracking parameter - &_r= — TikTok referral parameter - ?mibextid= — Facebook mobile referral token - ?igsh= — Instagram share tracking parameter - #fragments — Any hash fragment at the end of a URL All of these must be removed before submitting the URL to Google Business Profile. ✅ Platform-Specific Formatting Rules 🎵 TikTok TikTok URLs copied from the mobile app almost always include tracking parameters. Strip everything after and including the ? symbol. Incorrect: - https://www.tiktok.com/@yourbrand?_t=8hXkZ1234abc&_r=1 Correct: - https://www.tiktok.com/@yourbrand The accepted format is: https://www.tiktok.com/@[your-handle] 📘 Facebook Facebook links shared from mobile devices append a ?mibextid= token. Remove everything from the ? onward. Also avoid using /profile.php?id= numeric URLs — use your vanity URL instead. Incorrect: - https://www.facebook.com/yourbrand?mibextid=ZbWKwL - https://www.facebook.com/profile.php?id=100063712345678 Correct: - https://www.facebook.com/yourbrand The accepted format is: https://www.facebook.com/[your-page-name] If you have not yet set a custom Facebook username, go to your Facebook Page settings and create one before adding the URL to Google Business Profile. 📸 Instagram Instagram share links include a ?igsh= parameter. Remove everything from the ? onward. Trailing slashes are optional but do not cause errors. Incorrect: - https://www.instagram.com/yourbrand?igsh=dGVzdDEyMzQ= Correct: - https://www.instagram.com/yourbrand The accepted format is: https://www.instagram.com/[your-handle] 🛠️ How to Update Your GBP Social Links in Search Atlas Once you have your cleaned URL, navigate to your GBP management section in Search Atlas, locate the social media links fields, and paste the correctly formatted URL. Save your changes and allow Google a short time to revalidate the profile. 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.

Last updated on Oct 26, 2026

🔧 Fix a Stuck GBP Data Lock Toggle

What This Article Covers Some users have found that the GBP Data Lock toggle for a location appears stuck in the on position and does not respond when clicked. This is a known issue that our team has resolved for affected users. Follow the steps below in order — many users are able to resolve this without contacting support. What to Do Work through the following steps in order. Each step has resolved the issue for some users, so try all of them before reaching out to our team. 1. Hard refresh the page. Press Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac to clear the cached page state. Once the page reloads, click the GBP Data Lock toggle again to attempt to disable it. 2. Open an incognito or private browsing window. Copy the URL of your Local SEO location settings page, paste it into a new incognito/private window, log in to Search Atlas, and try clicking the toggle there. This rules out a browser extension or cached session token interfering with the toggle's state. 3. Try a different browser entirely. If the incognito window did not work, open Search Atlas in a completely different browser (for example, if you normally use Chrome, try Firefox or Edge), navigate to the affected location's settings, and attempt to disable the toggle again. 4. Clear your browser's cookies and site data for Search Atlas. In your browser settings, clear cookies and cached data specifically for the Search Atlas domain, then log back in and retry the toggle. Stale session data can cause the toggle to display an incorrect locked state. 5. Check whether the issue is location-specific. Navigate to another location in your account and verify whether its GBP Data Lock toggle responds normally. If other locations are unaffected, note the name of the stuck location — this information will help our team identify the backend state mismatch quickly. If you have completed all five steps and the toggle is still unresponsive, the toggle state needs to be corrected on the backend by our team. Please do not attempt additional workarounds beyond what is listed here. Still Need Help? If the GBP Data Lock toggle remains stuck after trying all the steps above, our team can investigate and correct the backend toggle state 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.

Last updated on Oct 26, 2026

✍️ Content Genius GBP Address Mismatch Fix

A bug causing a false address mismatch warning when selecting GBP locations in Brand Vault has been fixed by our engineering team, ensuring location data displays accurately without misleading alerts. ✨ What Was Fixed Content Genius was incorrectly triggering an address mismatch warning during GBP location selection within Brand Vault, even when the address data was valid and consistent. This could cause confusion and interrupt workflows that rely on selecting the correct GBP location. The fix ensures that the mismatch warning only appears when a genuine discrepancy exists between addresses. 🛠️ What to Do If You Are Still Seeing the Warning This fix has been deployed to all accounts. If you are still experiencing a false address mismatch warning when selecting your GBP location in Brand Vault, try the following steps: 1. Hard-refresh your browser (Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac) to ensure you are running the latest version of the platform. 2. Clear your browser cache and cookies, then log back in and retry selecting your GBP location in Brand Vault. 3. Try the steps in a different supported browser to rule out a browser-specific issue. 4. If the warning still appears after the above steps, note the exact warning message, the GBP location name, and the timestamp, as our support team will need these details to investigate further. 📋 What to Expect GBP location selection in Brand Vault should now behave correctly — address mismatch warnings will only display when there is an actual discrepancy in your location data. No changes to your existing settings or configurations are required as a result of this fix. 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.

Last updated on Oct 26, 2026

Heatmap Public Share Link Stuck Loading

Overview When you share a Local SEO Heatmap via a public link or embed it as an iframe (for example, inside a GoHighLevel dashboard), the page may display an infinite loading spinner and never show your heatmap data. This article explains why this happens and what steps to take to resolve it. What Causes This Issue This is a known platform bug that has been reported and investigated by our team. The public share page fails to load heatmap data, resulting in an infinite loading spinner. The issue can affect: - Public share links opened directly in a browser - Public share links opened in incognito mode or a different browser - Heatmap iframes embedded in third-party dashboards such as GoHighLevel - Cases where the shared link appears to show stale or outdated heatmap data If you are experiencing this issue, our support team can investigate and escalate it on your behalf. Steps to Try Before Contacting Support In some cases, a cached version of the old link may cause loading problems. Try these steps first: - Hard refresh the page — press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to bypass the browser cache. - Clear your browser cache and reload the shared URL. - Test the link in a fresh incognito window to rule out locally cached data. - Re-generate the public share link from the Local SEO Heatmaps section of your Search Atlas account, then test the new link in a browser where you are not logged in to Search Atlas. - Re-embed the iframe — if the iframe URL was set previously, remove the old embed code and replace it with the newly generated share link from your account. - Check that the heatmap has run at least one scan — a heatmap with no completed scan data will not display any results on the public share page. If the Loading Spinner Still Appears If the steps above do not resolve the issue, please reach out to our support team directly so we can investigate and escalate as needed. Gathering the following details before contacting us will help our team investigate faster: - The full public share URL that is not loading - The name of the heatmap and the Search Atlas account email address - Whether the issue occurs in a direct browser link, an incognito window, or an iframe embed - A screenshot or screen recording of the loading spinner - The name of any third-party platform where the iframe is embedded (for example, GoHighLevel) If you need further assistance, please contact our support team via the chat widget in your Search Atlas dashboard and we will be happy to help.

Last updated on Oct 26, 2026

🔧 Fix GBP Post Count and Visibility Discrepancies

Overview If your Search Atlas dashboard shows a total post count (for example, 19 posts) but only a smaller number appear in your visible post list, this can be confusing. This article explains why this happens and how to confirm that your Google Business Profile (GBP) posts were successfully published. Why the Post Count and Visible List Differ The total post count displayed in your dashboard reflects all posts ever created or scheduled for your Google Business Profile — including posts that have already expired, been removed by Google, or are no longer active. The visible list, by contrast, shows only your currently active and live posts. Google automatically expires certain GBP post types after a set period. This is a Google platform behaviour, not a Search Atlas issue. Common reasons for the discrepancy include: - Expired posts: Some GBP post types expire after a set period and are removed from the live view automatically by Google. - Google content policies: Occasionally, Google may not publish or may remove a post that conflicts with its content guidelines. - Scheduled vs. published posts: Posts that are queued for a future date are counted in the total but are not yet visible on your profile. - Post rollover: As new posts are added, older posts may no longer appear in the active visible list on your profile. How to Confirm Search Atlas Published Your Posts Search Atlas automatically publishes posts to your connected Google Business Profile on the scheduled date and time. To verify that a post was successfully sent: 1. Log in to your Search Atlas dashboard and navigate to the GBP posting area. 2. Locate the post in question and review any status or indicator information shown for that post to determine whether it has been submitted to Google. 3. Cross-check directly in your Google Business Profile manager at business.google.com to see which posts are currently live on your profile. If a post appears there, it was successfully published. 4. If a post you expected to be live does not appear in your GBP manager, note the post details (title, scheduled date and time) so you can report them to the support team. What to Do If a Post Did Not Publish as Expected If you believe a post was not published correctly, try the following steps: 1. Go to your account settings and verify that your Google Business Profile is still connected and authorised under your integrations. 2. If the authorisation appears to have expired, reconnect the integration and attempt to republish the post. 3. Check your GBP manager at business.google.com to confirm whether the post appears there. 4. If the post is still missing after reconnecting and republishing, contact our support team with the post details (title, scheduled date and time) for further investigation. 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.

Last updated on Oct 26, 2026

🗺️ Fix a GBP Audit Showing the Wrong Location

🔍 What This Article Covers If your business has moved to a new location and your GBP audit still shows the old address, an empty heatmap, or no competitor data, this article explains why it happens and what steps to take to get accurate results. ⚠️ Why This Happens When a business changes its address in Google Business Profile, the audit inside Search Atlas may still be linked to the previous, now-inactive GBP listing. Because that old listing no longer has an active location, the heatmap and competitor data cannot load — they require a valid, active GBP location to generate results. There are two separate issues that can occur together: - Old address still showing: The audit has not yet synced the updated address from Google Business Profile. - Heatmap and competitors missing: The audit is pulling data from the inactive listing with the old address, which has no heatmap coverage. ✅ Step 1 — Refresh Your GBP Audit Data Before creating a new audit, check whether refreshing the audit data resolves the address discrepancy. Navigate to your GBP audit in Search Atlas and use the available option to sync or refresh data from your Google Business Profile. Wait for the sync to complete, then check whether the updated address now appears. If the address updates correctly and the heatmap loads, no further action is needed. 🛠️ Step 2 — Create a New Audit Manually If refreshing the data does not fix the heatmap or competitor data — or if the audit is still linked to the old inactive listing — you need to create a brand-new audit and make sure it is connected to your current, active GBP location: 1. In Search Atlas, navigate to your GBP Projects area. 2. Locate the project associated with your business. 3. Start a new audit from within that project. 4. When selecting the GBP profile to audit, carefully confirm you are selecting the active listing with the new address — not the old or inactive one. Both listings may appear in the selection if the previous location was not fully removed from your Google account. 5. Complete the audit setup and allow it to run. The heatmap and competitor data should now populate correctly because the audit is tied to an active location. Important: Do not continue running audits on the old report if the linked GBP listing is inactive. Results will remain incomplete regardless of how many times you refresh. 💡 Tips to Avoid This Issue in the Future - Whenever your business changes its address in Google Business Profile, verify which GBP listing is connected to each audit in Search Atlas before running new reports. - If you have multiple GBP listings (for example, the old location and the new one), make sure t

Last updated on Oct 26, 2026

🔧 Fix GBP Deployment Failed Category Error

🧭 Overview If your Google Business Profile (GBP) deployment keeps failing with a Deployment Failed error — even after multiple retries — the cause is likely not a platform issue. Google occasionally invalidates or removes a profile's primary category on their side, which prevents Search Atlas from completing the sync. Generic fixes like refreshing or waiting will not resolve this. You need to manually reset the primary category directly in Google Business Profile before attempting another deployment. ⚠️ What Causes This Error Google Business Profile enforces strict category validation during any data sync. If your primary category has been removed, changed, or flagged by Google — even without any action on your part — Search Atlas cannot push updates to your profile. The deployment fails because the required category reference no longer exists on Google's side. Common signs this is your issue: - The Deployment Failed error appears consistently across multiple retry attempts. - The error occurs shortly after a previous successful sync. - Your GBP primary category appears blank, changed, or missing when you log in to Google Business Profile directly. - No other profile fields appear to be causing conflicts. ✅ Step 1 — Confirm the Category Issue in Google Business Profile 1. Log in to your Google Business Profile account at business.google.com. 2. Select the affected business location. 3. Locate the Primary category field in your profile settings. 4. Check whether the field is blank, shows an unexpected value, or displays a category that differs from what you originally set. 5. If the field is empty or incorrect, the category has been invalidated and must be reset before you can deploy. 🛠️ Step 2 — Reset the Primary Category in Google Business Profile 1. In your Google Business Profile settings, locate the primary category field. 2. Clear any existing value and set your correct primary category. 3. Save your changes and allow Google time to process the update on their side before proceeding. 🔄 Step 3 — Retry the Deployment in Search Atlas 1. Return to Search Atlas and open the affected GBP project. 2. Once you are in the project, retry the deployment. The updated category from Google's side should now allow the sync to complete successfully. 3. If the deployment fails again after resetting the category, note the exact error message displayed and the timestamp of the failure — you will need these details if you need to escalate. 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.

Last updated on Oct 26, 2026

🔍 Fix Greyed-Out GBP Auto Review Responses

🔍 What This Article Covers If you turn on automated review responses for your Google Business Profile (GBP) locations, select AI auto-reply for each star rating, and press the update button — but the toggle stays greyed out and nothing saves — your account has likely hit a location automation quota limit. This article explains what causes it and how to get it resolved quickly. ⚙️ What Is the Automation Location Quota? Every Search Atlas plan includes a limit on how many GBP locations can have automation features active at the same time. If the number of locations you are trying to automate exceeds the limit allowed on your current plan, the platform blocks the change silently — the toggle appears to do nothing, and no error message is shown. For example: if your plan allows automation on 55 locations but you have 76 locations with automation active, any attempt to enable additional features like automated review responses will fail without explanation. 🛠️ How to Identify If This Is Your Issue You are likely hitting a quota limit if all of the following apply: - You navigated to the Reviews section, enabled auto response, and selected AI auto-reply for one or more star ratings. - You pressed the update button to save your settings. - The toggle remained greyed out or inactive after pressing update, with no error message displayed. - You manage a large number of GBP locations — particularly if that number is close to or exceeds any plan-based limits. 📊 Why This Happens When the number of locations with active automation on your account exceeds your plan's allowed limit, the backend raises a quota error. Currently, this error is not surfaced visibly in the platform interface — the update appears to fail silently, leaving the toggle greyed out. A fix to improve this workflow is in progress by the engineering team. 🚀 How to Resolve It Because the quota limit is set at the account level, you cannot increase it yourself from within the platform. To resolve this, you need a member of the Search Atlas team to update your automation location limit to match the number of locations you are actively managing. 1. Before reaching out, count the total number of GBP locations you currently have with automation active in your account. This helps the team process your request faster. 2. Note the specific feature you are trying to enable — in this case, automated AI review responses — and which locations or star ratings are affected. 3. Contact the Search Atlas team using the live chat widget (see below). Share your total active location count and confirm you need your automation location limit increased to match. 4. Once the team updates your limit, return to the Reviews section, re-enable auto response, select your preferred AI auto-reply settings for each star rating, and press update. The toggle should activate and save successfully.

Last updated on Oct 26, 2026

📊 Fix Missing GBP Metrics in Report Builder

🔍 Common Causes for Missing GBP Metrics If Google Business Profile (GBP) metrics are not displaying in your Report Builder configuration, the issue typically stems from one of three sources: disconnected GBP accounts, insufficient permissions, or report configuration errors. ⚙️ Verify GBP Account Connection Ensure your Google Business Profile is properly connected to Search Atlas: 1. Navigate to Reports in the left sidebar 2. Open your report project or create a new one 3. In the report editor, locate the GBP Metrics section 4. Confirm the correct GBP location is selected and shows a green connection status 5. If disconnected, click Reconnect GBP and complete the OAuth flow with a Google account that has Manager or Owner access to the profile 🔐 Check Google Account Permissions Metrics require specific access levels on the Google Business Profile: - The connected Google account must have Manager or Owner role (not just Site Manager) - Verify permissions in Google Business Profile Manager: Users → locate your email → confirm role - If using a shared agency account, ensure it has been granted access to the specific location 📅 Validate Date Range and Data Availability GBP metrics may not appear if: - The selected date range exceeds available data (new profiles have limited historical data) - The range includes future dates - Google has not yet processed insights for recent days (allow 48–72 hours for fresh data) Adjust the date filter in the report builder to a range where data is confirmed available. 🛠️ Refresh Report Configuration If metrics were previously working but disappeared after saving: 1. Open the report in the Report Builder 2. Remove the GBP metrics section using the Delete icon 3. Re-add it via Add Section → GBP Metrics 4. Reconfigure metrics, layout, and date range 5. Save the report again This resolves a known issue where saved configurations occasionally lose metric bindings. 🧪 Test with a Minimal Report To isolate the issue: 1. Create a new report project 2. Add only a GBP Metrics section 3. Select one metric (e.g., Total Searches) 4. Set a recent 7-day date range 5. Preview the report If metrics appear here but not in your main report, the issue is configuration-specific. 💡 Known Platform Fixes Recent updates have resolved: - GBP metric cards now display proper arrow indicators for delta values (not plain text) - Total Searches and Maps Views summary bar renders correctly - Shared report URLs now match the editor layout and metrics Ensure you are on the latest platform version by hard-refreshing (Ctrl+Shift+R / Cmd+Shift+R). 🆘 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.

Last updated on Oct 26, 2026

🔧 Fix Google Account Reconnection and Auto-Posting Errors

Overview Some users see a 'Google account needs to be reconnected' error even when their account appears connected, and notice that scheduled auto-posts have stopped publishing. This is a known issue where Google Business Profile (GBP) accounts can silently disconnect from the platform, causing scheduled posts to fail without any notification. Step 1: Reconnect Your Google Account Manually reconnecting your Google account clears the broken authentication token and re-establishes a fresh connection. This is the primary fix for both the reconnection error and auto-posting failures. 1. Navigate to your GBP projects area within the platform. 2. Locate the affected account and follow the on-screen option to reconnect or connect your GBP account. 3. Complete the Google authorisation flow when prompted. 4. Once reconnected, confirm that the account status no longer shows an error. Step 2: Verify That Scheduled Posts Resume After reconnecting your Google account, allow a few minutes and check whether your scheduled posts begin publishing again. If posts were queued during the disconnection period, they may take a short time to process once the connection is restored. Why This Happens Google occasionally revokes or expires the access tokens that connect your account to third-party platforms. When this happens, the platform may not immediately surface a clear warning, so scheduled posts silently fail. If you have followed the steps above and the error persists or posts are still not publishing, please contact our support team via the chat icon in the bottom-right corner of the platform so we can investigate further.

Last updated on Oct 26, 2026

🔄 GBP Locations Missing From Galactic Import List

Overview If you have verified Google Business Profile (GBP) locations with Manager or Owner access and they appear correctly in Google Business Profile Manager but are missing from the import list inside GBP Galactic, an integration refresh is usually all that is needed to bring them back. This article walks you through what to check on your end and the steps to trigger a refresh. If the locations still do not appear after following these steps, our team can perform a backend refresh to resolve it. Why This Happens GBP Galactic pulls your locations through a live integration with your connected Google account. Occasionally, this sync can fall out of step — meaning Google shows the locations correctly on their side, but the integration layer inside Search Atlas has not picked up the latest data. This is a known sync issue and does not affect your actual GBP listings or rankings. What to Check First - Confirm your access level: Make sure the Google account connected to Search Atlas has Manager or Owner access for the missing locations in Google Business Profile Manager. - Confirm the locations are published: Locations that are pending verification or suspended in Google may not be importable. - Check you are using the correct Google account: If you manage multiple Google accounts, ensure the one connected to Search Atlas is the same one that owns the missing locations. Steps to Resolve 1. Disconnect your Google account from Search Atlas: Go to your Avatar Menu (👤) (avatar) → Settings → Integrations and locate the connected Google Business Profile account. Disconnect it. 2. Reconnect your Google account: Re-authorize the same Google account that has Manager or Owner access to the missing locations. Complete the full OAuth flow so Search Atlas can re-query your account. 3. Return to GBP Galactic and open the import list: After reconnecting, navigate back to GBP Galactic and check the import list again. The missing locations should now appear. 4. If locations are still missing after reconnecting: Contact our support team. Provide the following so we can trigger a backend re-sync as quickly as possible: - The exact names of the missing GBP locations - The Google account email connected to Search Atlas - Confirmation that you have Manager or Owner access in Google Business Profile Manager for those locations If the Issue Persists If your locations are still missing after reconnecting your Google account, our team can perform a backend re-sync of your connected Google account, which causes the platform to re-query your account and register all eligible locations. Please reach out to our support team through the chat in the platform and we will resolve it for you.

Last updated on Oct 26, 2026

🔧 Fix GBP Auto-Review-Reply Not Responding

Overview If your Google Business Profile (GBP) is connected and auto-respond is enabled, but reviews are not receiving AI-generated replies, this is a known issue that our team investigates on a case-by-case basis. Because the root cause can vary depending on your account configuration, there is no single self-serve fix that applies universally. What to Check Before Escalating Before reaching out, review the following common factors that can contribute to auto-replies not generating: - GBP connection status: Confirm that your Google Business Profile is still actively connected to Search Atlas. An expired or partial connection can prevent replies from being generated. - Auto-respond setting: Verify that the auto-respond feature is enabled for the specific GBP location experiencing the issue. If you manage multiple locations, this setting may need to be confirmed per location. - Review sync status: Auto-replies can only be generated for reviews that have successfully synced into Search Atlas. If new reviews are not appearing in the platform, the AI cannot respond to them. - Existing responses: The system will not generate an AI reply for a review that already has a response, including replies posted manually outside of Search Atlas. How to Get Help Because this issue requires investigation of your specific account and GBP connection, please escalate to our support team. To help us resolve this quickly, have the following ready: - The name and URL of the affected Google Business Profile location - The approximate date when auto-replies stopped generating - Any error messages you have seen in the platform - Whether the issue affects one location or multiple 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.

Last updated on Oct 26, 2026

🛠️ Local Citation Submissions Stuck in Submitting Status

🔍 Overview If your local citation campaign remains stuck in a Submitting status beyond the expected completion window, this is a known display bug that has been identified and resolved by our development team. This article explains how to confirm whether your campaign is affected and what steps to take if you are still seeing an incorrect status. 📋 What Caused This Issue Our engineering team identified and fixed a display bug affecting local citation campaign statuses. Citation campaigns were showing a Submitting status even after the underlying submissions had completed. This was a frontend display issue, not a problem with the submissions themselves. The fix has been deployed to production. ✅ How to Check Your Citation Campaign Status 1. Navigate to Local → Local Citations (Local Citations) within the platform. 2. Locate the affected campaign and review the status currently displayed. 3. If the status still shows Submitting and your campaign has been running longer than expected, proceed with the troubleshooting steps below. ⚙️ What to Do If Your Status Is Still Stuck Because the bug fix has been deployed, most affected campaigns should now display the correct status. However, if your campaign continues to show Submitting well beyond the expected window, follow these steps: 1. Perform a hard refresh of your browser (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) to ensure you are loading the latest version of the platform. 2. Navigate away from the current page and return to your Local Citation campaign to allow the status to reload cleanly. 3. Log out of your account and log back in, then navigate back to your citation campaigns and recheck the status. 4. Note the purchase date of the affected citation pack and how long it has been showing the incorrect status — you will need this information if you contact support. 5. If the status remains incorrect after these steps, reach out to our team using the instructions below. 💡 Key Things to Know - The Submitting status bug is a display issue only — your actual citation submissions are not necessarily delayed or incomplete because of this. - If you are unsure whether your submissions have completed, our support team can look into the status on your behalf. 📬 Still Need Help? If your citation campaign status remains stuck after following the steps above, please open the chat widget in the bottom-right corner of the platform and type human teammate. Include your account details and the name of the affected campaign so we can investigate promptly. Additional Notes This affected multiple campaigns simultaneously and was unrelated to account settings, subscription level, or the number of businesses in a project. The status display logic has been corrected so campaigns accurately reflect their completed state; an update was applied to prevent mismatched statuses in future submissions. Orders normally complete within 50 days. A related issue caused the status in list view to differ from the status inside the submission details modal. Some accounts may need a manual status refresh applied by the team — there is no self-serve action that forces a status recalculation for historical orders.

Last updated on Oct 26, 2026

🔓 Disable the GBP Project Lock in Search Atlas

🧩 Overview When you try to update a field inside a Google Business Profile (GBP) project and see the message "To edit a field you have to disable the lock on", it means the project-level lock is active. This lock is controlled by a single lock icon in the GBP Projects Overview menu — not at the individual field level. Disabling it takes only a few seconds and immediately allows editing across the project. 🗺️ Where to Find the Lock The lock icon lives at the top of the GBP Projects Overview menu. Follow this exact navigation path: 1. In the left sidebar, click Local. 2. Click GBP Projects (GBP Projects) — this opens the GBP projects list. 3. Locate and select the GBP project you need to edit. 4. Inside the project, open the GBP Projects Overview menu panel on the left side of the screen. 5. At the top of that menu, look for the lock icon. 🔓 How to Disable the Lock 1. Navigate to Left sidebar → Local → GBP Projects (GBP Projects). 2. Select the client's GBP project from the list. 3. In the GBP Projects Overview menu, find the lock icon at the top. 4. Click the lock icon to toggle it from locked to unlocked. The icon will change state to confirm the lock has been removed. 5. Return to the field you were trying to edit and make your changes as normal. Note: The lock icon is a project-level control. Disabling it affects the entire project, so re-enable it after you finish editing if you want to protect the project data from accidental changes. ⚠️ Common Mistakes to Avoid - Looking for field-level locks: The error message may suggest the lock is on a specific field, but the fix is always at the project level in the Overview menu. - Checking permissions or deployment settings: This error is not related to user permissions or deployment status — it is only caused by the project lock being active. - Editing without unlocking: Any field inside a locked project will block edits until the project-level lock is removed. Unlock first, then edit. 🔁 Re-Locking the Project After Editing Once you have finished making updates, it is good practice to re-enable the lock to prevent unintended changes to the project. Return to Local → Overview (Overview) → select the project → GBP Projects Overview menu and click the lock icon again to restore it to the locked state. 💬 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.

Last updated on Oct 26, 2026

🗓️ Fix Local SEO Heatmap Auto-Refresh Scheduling Issues

Overview Local SEO Heatmaps in Search Atlas can be configured to refresh automatically on a set schedule. However, certain actions or misconfigurations can silently disrupt that schedule — causing heatmaps to stop updating or failing to appear correctly in reporting. This article explains what to check and how to escalate if the issue persists. Why Your Heatmap May Stop Auto-Refreshing Auto-refresh scheduling issues on Local SEO Heatmaps are typically caused by a misconfiguration in the heatmap's refresh or scheduling settings. Common scenarios include: - The crawl frequency being unintentionally changed or reset after editing other heatmap settings. - The heatmap being set to run only once rather than on a recurring schedule. - A manual refresh completing successfully but no further automatic refreshes being scheduled afterward. What to Check in Your Heatmap Settings If your heatmap has stopped refreshing automatically, review the scheduling or crawl frequency settings within that heatmap's configuration panel. Verify that a recurring schedule (such as weekly or monthly) is still selected and save any changes you make to confirm they are applied. If you are unsure where to locate these settings or the options appear different from what you expect, our support team can walk you through the correct steps for your account. Why Manually Refreshed Heatmaps May Not Appear in Reporting If you triggered a manual refresh but the updated data is not showing in your reports, possible reasons include: - Processing delay: Manual refreshes can take time to complete depending on grid size and current platform load. Wait a few minutes and then reload the heatmap view. - Scheduling reset: If the crawl frequency was reset to a one-time run, a manual refresh will complete but no further automatic refreshes will be scheduled, creating gaps in reporting over time. When to Contact Support If you have reviewed your heatmap settings and auto-refresh is still not working as expected, please reach out to our team with the following information ready: - The name of the affected heatmap and the project it belongs to. - The schedule you expected (e.g. weekly or monthly) and when refreshes last occurred. - Any recent changes you made to the heatmap before the issue started. - Screenshots of the current scheduling settings if 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.

Last updated on Oct 26, 2026

Local SEO Heatmaps Embed Fix for Monday.com

Overview Some customers found that Local SEO Heatmap reports would not render when embedded as an iframe or shared via a public URL inside Monday.com. In some cases the map loaded partially but heatmap data and map pins never appeared. Current Status: Known Issue The Search Atlas team is aware that Local SEO Heatmap iframes and public shared URLs may not render correctly inside Monday.com. If you are experiencing this symptom, please reach out to the Search Atlas support team so we can review your specific case and assist you further. Steps to Try 1. In Search Atlas, navigate to the Local SEO Heatmaps section. 2. Open the heatmap report you were trying to embed. 3. Copy the public share link or iframe embed code from the report. 4. Paste the link or embed code into your Monday.com board and reload the view. 5. Verify whether the map renders fully and that your heatmap data is visible. Tips for a Smooth Embed Experience - Use a freshly copied link. If you saved an older embed code, remove it and generate a new one to ensure you have the latest version. - Clear your browser cache. Cached versions of the embed may still show a broken state. A hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) or clearing your cache can help. - Test the public URL directly first. Before embedding, open the public share link in a new browser tab to confirm the heatmap renders correctly on its own. If it works standalone, any remaining display issue is likely related to how Monday.com is handling the embed rather than Search Atlas itself. When to Contact Support If you are experiencing this issue or have followed the steps above and your heatmap embed is still not rendering correctly, please reach out to the Search Atlas support team via the chat icon in your dashboard so we can investigate further.

Last updated on Oct 26, 2026

Fix GBP Lock Errors and Missing Social Fields

🔍 Overview Two common issues can interrupt your GBP Golden Loop progress in Search Atlas: a lock error that prevents your profile from staying locked, and a validation blocker when a client does not have every social media account or optional attribute listed in the checklist. This article explains why these happen and what to do next. ⚠️ Understanding the GBP Lock Error When you attempt to lock a GBP project in Search Atlas, you may encounter errors or find that the lock does not hold as expected. These issues can be caused by Google-side restrictions on certain address fields or by platform-level behaviour affecting how location data is saved. Because the exact cause can vary by account and location, our team will need to investigate your specific project. 🛠️ What to Do When the GBP Lock Fails If you are experiencing a GBP lock error or the lock is not persisting on your project, please escalate to our support team so we can investigate. To help us resolve this as quickly as possible, have the following ready before reaching out: - The name of the affected GBP project in Search Atlas. - The exact error message you are seeing (copy it word for word if possible). - The timestamp or approximate time when the error first occurred. - Whether the lock appears to save initially but then resets, or whether it fails immediately. - Any recent changes made to the address or profile fields before the error appeared. 📋 Handling Missing Social Media Accounts The Golden Loop checklist may include social media profile URLs (such as Facebook, Instagram, X, LinkedIn, or others) as required fields. If a client does not have one or more of these accounts, the checklist item may block you from marking the profile as complete. Because the available options for handling missing fields depend on how your specific checklist is configured, our team can advise on the correct approach for your account. When escalating, please include: - The name of the GBP project and the specific checklist field that is causing the blocker. - Whether the client has confirmed they will not be creating the missing social account. - A screenshot of the checklist item and any options currently visible to you. 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.

Last updated on Oct 26, 2026

🛠️ GBP AI Image Generation Not Working Correctly

What This Article Covers Some users noticed that AI-generated images for Google Business Profile (GBP) automated posts stopped reflecting their actual business — for example, a pool or landscaping company receiving random, unrelated scene photos instead of relevant visuals. This was accompanied by empty or blank image prompts. This article explains what happened and confirms the fix is live. What Caused the Issue A regression in the GBP automated posting feature caused AI image generation to stop using your business context when creating images for scheduled posts. As a result: - Images no longer matched your business type or industry. - Image prompts appeared empty or blank in the post preview. - Scheduled posts occasionally showed incorrect statuses or failed to generate images at all. This was confirmed as a platform bug and escalated to the engineering team as a priority issue. The Fix Is Now Live The engineering team investigated and resolved the underlying issue. The fix has been fully deployed to production. You do not need to take any technical action to receive this fix — it is applied automatically to your account. If you created automated posts during the affected period and they produced incorrect or unrelated images, those posts should now generate correctly when you create new ones. What to Do If You Are Still Affected If you are still seeing unrelated images or empty prompts after the fix, please reach out to our support team so we can investigate 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.

Last updated on Oct 26, 2026

🔧 Fix OTTO Pixel and GBP Dashboard Sync Issues

🔍 Overview Some customers notice that their Search Atlas dashboard shows no connected Google Business Profile (GBP), missing heat maps, or no reviews — even when active GBP profiles and pixel installations are already in place. In some cases, a pixel may appear connected on an account where it should not be. Because resolving these issues requires backend investigation by our team, this article explains what is happening and what information to have ready when you contact us. ⚙️ Why This Happens These display issues are typically related to one or more of the following: - Pixel ID mismatch: The OTTO pixel installed on your site may be using an incorrect or outdated ID that the platform cannot associate with your account, preventing it from being recognised as active. - GBP not linked to the correct OTTO project: If your GBP profile was connected after the OTTO project was created, the association between the two may not have been established correctly. - Pixel appearing on the wrong account: A known display issue can cause a pixel to appear connected on an account it does not belong to. This is a cosmetic problem and does not affect your actual tracking data. 🚀 What to Do Because these issues involve backend account configuration and pixel detection logic, they cannot be fully resolved through the dashboard alone. Our support team will need to investigate your account directly. To help us resolve your issue as quickly as possible, please have the following ready before reaching out: - The domain name affected (e.g., example.com) - The OTTO project name associated with that domain - Your pixel ID if you can locate it in your project settings - A description of what is missing or incorrect — for example, whether it is the GBP profile, heat maps, reviews, or the pixel connection status - Any screenshots of the dashboard showing the issue - The approximate date and time you first noticed the problem 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.

Last updated on Oct 26, 2026

GBP Score Stuck on Calculating

📋 Overview If one or more of your Google Business Profile (GBP) locations shows all other metrics correctly but the overall GBP score remains stuck on Calculating for more than 24–48 hours, this article explains what causes the issue and how to resolve it. 🔎 What Causes This Issue? The GBP score is generated by a background process that runs on a scheduled cycle. In some cases, this process does not correctly pick up newly connected or recently updated locations, leaving the score indefinitely in a Calculating state. This is a platform-level issue — it cannot be fixed by refreshing the page alone. ✅ Steps to Resolve This Issue Follow these steps in order to get your GBP score unstuck as quickly as possible: 1. Wait 48 hours after first connecting a location. The GBP score calculation can take up to 48 hours for newly connected profiles. If the score updates within this window, no further action is needed. 2. Check all affected locations. Note how many of your GBP locations are showing the Calculating status and whether they are newly connected or have been active for some time. 3. Disconnect and reconnect the affected GBP location. If the score is still stuck after 48 hours, try removing the affected GBP location from your account and reconnecting it. This can prompt the background calculation process to re-run for that location. After reconnecting, allow another 24–48 hours for the score to generate. 4. Verify your GBP connection is active and authorized. Go to Left sidebar → Local → GBP Projects (GBP Projects | searchatlas.com) and confirm the location is connected with a valid, authorized Google account. An expired or revoked authorization can prevent the scoring process from completing. Re-authorize if needed. 5. Contact support if the score remains stuck beyond 48 hours after reconnecting. If the score has still not updated after attempting the steps above, reach out to our team. A server-level fix may need to be applied to your account by engineering. Provide the details listed in the next section so the team can escalate your case quickly. 📝 Information to Have Ready When Contacting Support To help our team escalate your case quickly, please have the following ready before opening a chat: - The names or URLs of the GBP locations affected - How long the score has been stuck on Calculating - Whether the locations are newly connected or were previously showing a score - Any troubleshooting steps you have already attempted If you need help, please reach out to our support team and we'll be happy to assist.

Last updated on Oct 26, 2026

Google Business Profile UI & Heatmap Fixes

The Google Business Profile release on 2026-07-21 shipped 3 tickets — 1 bugfix and 2 improvements — targeting the GBP tool's search fields, heatmap date loading, and local business search functionality. All changes apply automatically; no action is required on your end. ✨ What's New - Bugfix — GBP search fields: A known issue affecting GBP search field behavior has been resolved, restoring correct input and display functionality. - Improvement — Heatmap date loading: Heatmap date selection and data loading in the GBP tool now performs more reliably and consistently. - Improvement — Local business search: Local business search within the GBP tool has been enhanced for improved accuracy and performance. 🛠️ What to Do 1. Navigate to Local (GBP Projects) in the left sidebar of your Search Atlas dashboard to use the updated tool. 2. If you still see unexpected behavior in search fields, heatmap date loading, or local business search after this release, try refreshing the page first. 3. If the issue persists, note your project name, a clear description of the behavior, and the exact timestamp when it occurred before reaching out — this helps the team investigate quickly. 📋 What to Expect - All updates apply automatically — no configuration changes are required. - If you experience behavior that does not match the fixes described above, the support team can confirm whether your issue falls within the scope of this release and advise on next steps. 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.

Last updated on Oct 26, 2026

🛠️ Fix GBP Post Generation Stuck on Preview

🔍 Overview Some customers experience GBP (Google Business Profile) post generation getting stuck at the preview stage — the post editor never populates, the preview shows No data, or the process simply stops without an error message. This can happen even after refreshing the page or clearing your browser cache. This article explains what you can try right now and what information to have ready if you need to escalate. ⚠️ What Causes This Behaviour GBP post generation can stall at the preview stage for a number of reasons, including intermittent failures during content generation, network interruptions that cut off a request mid-process, or a temporary issue on the platform side. Because the failure often occurs silently — with no error message displayed — it can be difficult to tell exactly what went wrong. 🛠️ Steps to Try First 1. Wait a moment and watch the spinner. Content generation can sometimes take longer than expected. If the spinner is still running, give it additional time before assuming it has failed. 2. Refresh and retry. Once the wait has passed, refresh the page and attempt post generation again. Intermittent failures often succeed on a second attempt. 3. Try a different browser. Use an up-to-date version of Google Chrome or Microsoft Edge and ensure no browser extensions are blocking network requests. 4. Check your internet connection. A dropped or unstable connection can interrupt the generation process and cause a silent failure. 5. Clear your browser cache. Stale cached data can occasionally interfere with the post editor loading correctly. Clear your cache, then retry. 📋 What to Have Ready Before Contacting Support If the steps above do not resolve the issue, gather the following information before reaching out so our team can investigate as quickly as possible: - The name of the GBP project or location where the issue is occurring - The exact step at which generation stalls (e.g., immediately after starting, or after appearing to load briefly) - Any error message displayed, or confirmation that no message appeared - The time and date when the issue occurred - A screenshot or screen recording of the stuck state if 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.

Last updated on Oct 26, 2026

🗺️ GBP Galactic Citation Score: Google Listings Not Found

🔍 Overview If your Citation Score in GBP Galactic displays listing not found for Google or Google Maps — even though your profile is actively linked to GBP Galactic — you are not alone. This is a common source of confusion because linking your Google Business Profile and discovering that profile as a citation are two separate processes. This article explains why this happens and what to do next. ⚙️ Why 'Listing Not Found' Appears for Google and Google Maps Connecting your Google Business Profile to GBP Galactic gives the platform permission to manage and sync your profile data. However, the Citation Score tool works differently — it independently scans public directories and data sources across the web to detect whether your business listing exists and is consistent on each platform. Google and Google Maps are scanned the same way as any other directory. A listing not found result can appear even when your GBP account is connected, because the Citation Score reflects what an independent scan finds in the public web, not what is connected inside the platform. ✅ What to Do When You See 'Listing Not Found' for Google Because the source of this issue requires investigation on the backend, please have the following information ready when you reach out to our team: - The exact business name, address, and phone number stored in GBP Galactic. - The exact business name, address, and phone number currently shown on your Google Business Profile. - The current verification status of your Google Business Profile (verified, pending, or suspended). - The date of any recent changes made to your business name, address, or phone number on Google. - A screenshot of the Citation Score result showing the 'listing not found' status for Google or Google Maps. Our team will review your account and Citation Score scan results to identify the cause and advise on next steps. 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.

Last updated on Oct 26, 2026

Fix GBP Placeholders on Public Report Links

🔍 What Is This Issue? When you share a public report link with a client or colleague, the report may display generic placeholders instead of the actual business names associated with your Google Business Profile locations. This is a known platform bug that requires investigation by our support team. If you are seeing placeholders on a public report link, please reach out so this can be reviewed and resolved for your account. ⚙️ Why Does This Happen? Public report links are designed to be accessible without requiring the viewer to log in. However, a platform-level issue can cause Google Business Profile location names to display as generic placeholder labels instead of real business names when the link is opened. The report content itself may load correctly, but the business identity information may not display as expected. This is a backend issue and cannot be resolved through settings changes on your end. Our team will need to investigate it directly for your account. 🛠️ Steps to Take Before Contacting Support 1. Open your shared report link. Navigate to the report you previously shared within your Search Atlas account. 2. Check whether placeholder names appear where real business names should be displayed. 3. If placeholders appear, collect the following details before contacting support: the full public report link URL, the affected business or project name, the placeholder text displayed, and any timestamps or notes on when the issue first appeared. 💡 Tips for Sharing Reports with Clients - If placeholders appear consistently across multiple links or projects, note all affected report names and project details before reaching out to support. 📋 Still Seeing Placeholders? This issue requires backend investigation. Please contact our support team with the following information ready: the full public report link, the affected business or project name, the exact placeholder text shown, and a description of when the issue began. Having these details ready will help the team resolve this as quickly 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.

Last updated on Oct 26, 2026

🔗 Connect Client GBP Authorization

🔗 Before You Begin Use the authorization link generated in Search Atlas to let your client securely connect their Google Business Profile (GBP). The client must sign in with a Google account that has permission to manage the correct profile. - Confirm the client has Manager or Owner access to the GBP. - Ask the client to use the Google account connected to that profile. - Send the complete link without editing, shortening, or adding characters. 🚀 Connect a Client Through the Link 1. Open the GBP connection flow in Search Atlas and generate the authorization link. 2. Copy the full link and send it to your client. 3. Ask the client to open the link in a current browser. 4. The client should sign in to Google, choose the correct Business Profile, and approve the requested permissions. 5. After authorization, the client should wait for the confirmation page before closing the browser. 6. Return to Search Atlas and confirm that the GBP is connected to the correct client or site. ⚠️ Fix the “Malformed Request” Error This message usually means the authorization link was changed, copied incompletely, expired, or opened in a session that could not complete the request. Do not repeatedly retry the same link. 1. Generate a new authorization link in Search Atlas. 2. Copy it again from the platform and send it as plain text. 3. Ask the client to open the new link in a private window or a different current browser. 4. Have the client sign in with the Google account that manages the intended GBP. 5. Ask the client to complete the process in one session without using the browser Back button. 🛠️ Resolve Other Connection Problems - Wrong profile appears: Sign out of other Google accounts or use a private window, then select the correct account and profile. - Access is denied: Add the client’s Google account as a Manager or Owner of the GBP, then generate a fresh link. - Authorization was blocked: Check that the client is using the official link from Search Atlas and has not modified it. - The link says it was already used: Create and send a new link. Authorization links may be single-use or expire. - Search Atlas still shows disconnected: Refresh the page and verify that the authorized Google account matches the client’s GBP access. ✅ Best Practices - Send each client a newly generated link. - Do not paste the link into documents or tools that may alter its characters. - Connect one client profile at a time to avoid selecting the wrong GBP. - Ask the client to tell you which Google account and profile they authorized. 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.

Last updated on Oct 26, 2026

🗺️ SAB Hidden Address and GBP Map Display

🔍 Overview If your Google Business Profile (GBP) is set up as a Service Area Business (SAB) with a hidden address, you may notice a "No Address Found" notice on the map card inside the GBP Galactic dashboard. This article explains exactly what that message means, why it appears, and whether it affects any of your SEO or rank-tracking capabilities. 📍 What Is a Service Area Business (SAB)? A Service Area Business is a business type in Google Business Profile where the owner serves customers at their location rather than a fixed storefront. Examples include plumbers, cleaners, and delivery services. Google allows SAB owners to hide their physical address from public view — a common and recommended practice for home-based businesses. When you hide your address in GBP, Search Atlas reflects that same privacy setting inside the platform. 🗺️ Why Does "No Address Found" Appear on the Map Card? The "No Address Found" notice on the GBP Galactic dashboard map card is a cosmetic display message only. It appears because: - Your GBP listing has a hidden address, so Google does not return address data via the API. - Search Atlas accurately mirrors your public GBP data — since no address is publicly available, none is shown on the map card. - This is the expected and correct behaviour for any SAB with address privacy enabled. There is no error, misconfiguration, or missing data on your account. The notice is purely informational. ✅ Does This Affect Backend Sync or Rank Tracking? No. The "No Address Found" display state has zero impact on any backend functionality. Specifically: - GBP sync: Your profile data continues to sync normally. All edits, posts, reviews, and tasks propagate to Google as expected. - Rank tracking: Local SEO Heatmaps and all rank-tracking features operate at full capability. Tracking is based on your defined service area and target keywords, not your physical address. - Profile completion score: Search Atlas has been updated so that SAB listings are no longer incorrectly prompted to "Add Business Address." If you previously saw that suggestion, it has been resolved and will not count against your profile completion. - All other features: Posts, Reviews, Media Library, My Tasks, and Local SEO Heatmaps all function normally regardless of address visibility. ⚙️ How to Confirm Your SAB Settings in Search Atlas 1. In the left sidebar, go to Local → GBP Projects. 2. Select the GBP profile in question. 3. Review the map card — if your address is hidden in Google, you will see "No Address Found." This confirms your privacy setting is being respected. 4. Navigate to Local → Local SEO Heatmaps to verify that heatmap tracking is running normally for your target locations. 💡 Best Practices for SAB Listings - Keep your address hidden in GBP if you operate from a private or home address — this is Google's recommended approach for SABs. - Define your service areas clearly inside your GBP profile so Google and Search Atlas can accurately reflect your coverage zone. - Use Local SEO Heatmaps to track ranking performance across your entire service area rather than relying on a single address pin. - Regularly check Local → My Tasks for any recommended profile optimisations specific to SABs. 🛠️ Still Seeing Unexpected Behaviour? If the "No Address Found" message appears on a listing that should have a visible address, or if you notice any disruption to sync or rank tracking, follow these steps: 1. Go to Local → GBP Projects and confirm the correct GBP account is connected. 2. Check your address visibility setting directly inside Google Business Profile to ensure it matches your intended configuration. 3. Refresh the dashboard and allow a few minutes for data to sync. If the issue persists, 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.

Last updated on Oct 26, 2026

🔗 Fix Recurring Google Business Profile Disconnections

🔍 Overview If your Google Business Profile (GBP) integration keeps disconnecting — even after you successfully reconnect it — you are likely experiencing a Google OAuth token revocation issue. This article explains why this happens, how to identify it, and the steps to resolve it for good. ⚠️ Why Does This Keep Happening? Search Atlas connects to your Google Business Profile using a secure authentication method called OAuth. Google issues a token (a kind of digital key) that allows the platform to read and write data on your behalf. This token can become invalid for several reasons: - You revoked platform access in your Google Account security settings — either intentionally or accidentally. - Your Google password changed, which automatically invalidates all connected app tokens. - Too many connected apps caused Google to cycle out older tokens. - Your Google Account was used to connect multiple Search Atlas workspaces, causing token conflicts across accounts. - Inactivity or a Google-side security review expired the token without warning. When a token is revoked, Search Atlas loses access silently in some cases, which means scheduled posts and data syncs can fail without an obvious error message. The platform is being updated to display a reconnect banner when this occurs, but in the meantime this article will help you get ahead of the issue. 🛠️ How to Permanently Fix the Disconnection Follow these steps in order. Skipping steps — especially the Google security cleanup — is the most common reason the problem keeps coming back. 1. Remove Search Atlas from your Google Account permissions. Go to myaccount.google.com → Security → Third-party apps with account access. Find Search Atlas and click Remove Access. This clears any corrupted or partial token before you reconnect. 2. Sign out of all Google accounts in your browser. If you are signed into multiple Google accounts, token conflicts are common. Use a clean browser session or an incognito window for the next step. 3. Sign back in to Search Atlas and navigate to the GBP integration settings. Go to Local → GBP Projects and click Connect GBP Account. 4. Authenticate with one Google Account only. When the Google sign-in prompt appears, choose the single Google Account that owns or manages your GBP locations. Do not connect multiple Google Accounts to the same workspace. 5. Grant all requested permissions. Search Atlas requires specific scopes to manage your GBP listings and scheduled posts. Declining any permission will result in a partial connection that breaks later. 6. Verify the connection status. After reconnecting, confirm that your GBP locations appear in the platform and that their status shows as active. If any location shows a warning or is missing, repeat the steps above using the correct Google Account for that location. 🔄 Consolidating Multiple Google Accounts A very common cause of recurring disconnections is having GBP locations spread across different Google Accounts while connecting them all to one Search Atlas workspace. Here is how to consolidate cleanly: - Identify which Google Account is the primary owner of each GBP location you want to manage in Search Atlas. - If locations are owned by different Google Accounts, use Google Business Profile Manager to add a single shared Google Account as a manager across all locations. - Once all locations are accessible from one Google Account, reconnect Search Atlas using that single account. - Remove any old or duplicate Google connections from the Search Atlas integrations settings page before reconnecting. Using one Google Account as the connection point significantly reduces token conflicts and prevents future disconnections. 📋 How to Check If Your Connection Is Healthy After reconnecting, use these checks to confirm everything is working correctly: - Navigate to Local → GBP Projects and confirm each location shows a green active status. - Create a test scheduled post for one GBP location and verify it publishes at the scheduled time. - Check your GBP dashboard in Search Atlas to confirm location data is syncing correctly. - Revisit myaccount.google.com → Security → Third-party apps and confirm Search Atlas appears with full access. 🚫 What to Avoid - Do not reconnect without first revoking old access in your Google Account. Reconnecting on top of a broken token rarely fixes the underlying issue. - Do not use a Google Account that has two-factor authentication set up on a device you no longer have access to — this can block the OAuth flow mid-connection. - Do not connect the same Google Account across multiple Search Atlas workspaces simultaneously, as this can cause tokens to override each other. 💬 Still Experiencing Disconnections? If you have followed all the steps above and the integration continues to disconnect, our team can review your account's token status and OAuth logs 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.

Last updated on Oct 26, 2026

🔧 Troubleshooting Otto GBP Content Publishing Failed Errors

🧭 Overview When Otto is enabled on your Google Business Profiles (GBPs), it automatically schedules and publishes content such as posts, updates, and offers. If you see a content publishing failed notification for one or more GBPs, it means Otto attempted to publish but encountered an error before completion. This article walks you through the most common root causes and the steps to resolve each one. 🔍 Step 1: Identify How Many GBPs Are Affected Before troubleshooting, determine the scope of the problem. This helps narrow down whether the issue is isolated to a single profile or systemic across your account. - Go to Left sidebar → OTTO SEO → All Sites (SEO Automation) (URL: /seo-automation-v3). - Review your Otto-enabled GBPs and note which ones show the content publishing failed status. - If only one GBP is failing, the issue is likely profile-specific (permissions or data). If multiple GBPs are failing simultaneously, the issue is more likely API-level or account-level. ⚠️ Step 2: Check the Four Root Cause Categories Most publishing failures fall into one of four categories. Work through each one in order. 1. Image Validation Errors Google enforces strict image requirements for GBP posts. Otto will fail to publish if an image does not meet these standards. - Minimum size: 400 × 300 pixels. Maximum file size: 5 MB. - Accepted formats: JPG and PNG only. GIF, WebP, and HEIC files are not supported. - Images must not contain watermarks, overlaid text that covers more than 10% of the image, or prohibited content under Google's policies. - To fix: open the affected GBP's content settings in Otto, remove or replace the non-compliant image, and re-trigger publishing. 2. API Connection Errors Otto connects to Google Business Profile via the Google My Business API. A broken or expired connection will cause all publishing attempts to fail. - In Left sidebar → Local (GBP Projects), locate the affected GBP and check its connection status indicator. - If the connection shows as disconnected or expired, click Reconnect and complete the Google OAuth flow. - After reconnecting, wait up to five minutes and check whether queued posts publish successfully. 3. Permissions Errors Otto requires Owner or Manager level access to a GBP in order to publish content. If your role was changed, or the Google account used to connect the profile was removed from the GBP, publishing will fail. - Log in to Google Business Profile Manager (business.google.com) and confirm the connected Google account has Manager or Owner access to the affected profile. - If the account was downgraded to Site Manager or removed entirely, restore the correct permission level and then reconnect the profile inside Otto. 4. Data Format Errors GBP posts have content rules that Otto must follow. Publishing fails when post content exceeds limits or uses unsupported characters. - Post text must not exceed 1,500 characters. - Offer posts require a valid start date and end date; missing or past-dated offers will be rejected by Google. - URLs attached to posts must be fully qualified (beginning with https://) and must resolve without redirect errors. - To fix: review the scheduled post content in Otto, correct any field that violates these rules, and save the changes before re-publishing. ✅ Step 3: Confirm the Fix With Resolution Checkpoints After applying a fix, use these checkpoints to confirm the issue is fully resolved before moving on. 1. Return to Left sidebar → OTTO SEO → All Sites (SEO Automation) and open the affected GBP. 2. Verify the profile's connection status shows Connected with a green indicator. 3. Check that the previously failed post now shows a status of Published or Scheduled, not Failed. You can verify this in Left sidebar → Local → Posts (GBP Posts). You can verify this in Left sidebar → Local → Posts (GBP Posts). 4. If the post was published, confirm it is visible on the live GBP listing by visiting the Google Business Profile directly. 5. If failures persist after completing all steps above, note the exact error message displayed in Otto and proceed to the next section. 🔁 Step 4: If Errors Continue After Troubleshooting If you have worked through all four root cause categories and the publishing failure persists, the issue may require account-level investigation. Before reaching out, collect the following information to speed up resolution: - The name and location of the affected GBP(s). - The exact error message shown in the Otto dashboard. - The date and time of the most recent failed publishing attempt. - A screenshot of the connection status screen for the affected profile. 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.

Last updated on Oct 26, 2026

🗺️ SAB Hidden Address and GBP Galactic Map Display

🔍 Overview If your Google Business Profile (GBP) is set up as a Service Area Business (SAB), you may notice the map card on your GBP Galactic dashboard displays a "No Address Found" notice. This article explains exactly what that message means, why it appears, and confirms that it has no effect on your rank-tracking or backend data sync. 📍 What Is a Service Area Business? A Service Area Business is a business type that travels to or serves customers at their location rather than hosting customers at a fixed address. Common examples include plumbers, cleaners, landscapers, and delivery services. When you choose to hide your address on Google Business Profile — which Google recommends for most SABs — no physical address is made publicly visible on your listing. 🗺️ Why Does "No Address Found" Appear on the Map Card? The map card inside GBP Galactic (Left sidebar → Local → GBP Projects) pulls the publicly available address field from your Google Business Profile. Because your address is intentionally hidden at the GBP level, the platform has no public address to display or pin on the map. As a result, it shows "No Address Found" in place of a map pin. This is a purely cosmetic notice. It reflects the deliberate privacy setting on your GBP listing and is the expected, correct behaviour for SAB accounts with a hidden address. It does not indicate a configuration error or a problem with your account. ✅ Does This Affect Rank Tracking or Backend Sync? No — and this is the most important point. The "No Address Found" display state has zero impact on the following capabilities: - Rank tracking: Local keyword rankings are tracked using your service area and target location settings, not your physical address. Tracking continues to run normally. - Backend data sync: Search Atlas syncs GBP data — including posts, reviews, insights, and pending tasks — directly through the Google Business Profile API. A hidden address does not interrupt or degrade any of these sync processes. - GBP Galactic features: All features within GBP Galactic, including the Overview tab, Reviews tab, About tab, Local SEO Heatmaps, and Pending Tasks, remain fully functional regardless of the map card display state. - Profile completion scoring: Search Atlas correctly recognises SAB listings. You will not receive an inaccurate suggestion to "Add Business Address" as part of your profile completion tasks. This has been resolved to ensure SAB accounts are assessed accurately. 🛠️ How to Confirm Your SAB Settings Are Correct 1. Navigate to Left sidebar → Local → GBP Projects and open your project. 2. Go to Left sidebar → Local → Overview → About tab. 3. Confirm that your service area (cities, regions, or postal codes) is correctly defined. 4. Verify that no physical address is listed publicly — this is intentional for SABs. 5. Return to GBP Projects and confirm that Pending Tasks do not incorrectly prompt you to add a business address. If they do, use the chat widget to let our team know. 💡 Key Takeaways - "No Address Found" on the map card is a cosmetic display notice only — it is expected behaviour for SABs with a hidden address. - No internal backend sync, rank-tracking, or GBP Galactic functionality is degraded by this display state. - Your service area settings — not a physical address — drive local rank tracking for SAB listings. - Profile completion tasks are calibrated to recognise SAB accounts correctly so you are not prompted to add an address you have intentionally hidden. 💬 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.

Last updated on Oct 26, 2026

🗺️ How to Disable Heatmaps on the PRO Plan

📋 Overview Heatmaps are a PRO plan feature in Search Atlas that visualize how your Google Business Profile (GBP) ranks across a geographic grid for your target keywords. They are a powerful tool for Local SEO, but not every account needs them running continuously. If you would prefer to stop heatmap tracking, remove existing heatmap data, or ensure you are not billed for this functionality, this guide walks you through your options. 🤔 Why You Might Want to Disable Heatmaps There are several common reasons customers choose to turn off heatmap tracking: - You are not actively running Local SEO campaigns and do not need geo-grid rank tracking. - You want to reduce or control the scope of your PRO plan usage. - You no longer manage the Google Business Profile the heatmaps were created for. - You want to clear out historical heatmap data you no longer reference. 🛑 How to Stop Heatmap Tracking To stop new heatmap scans from being generated, follow these steps: 1. Log in to your Search Atlas platform account. 2. Navigate to Local → Local SEO Heatmaps from the left-hand menu. 3. Locate the specific heatmap campaign or scheduled scan you want to stop. 4. Open the campaign settings and disable or delete the scheduled recurring scan so no further scans run automatically. Disabling the scheduled scan prevents new heatmap data from being collected going forward. This is the key step to ensure the functionality is no longer actively running on your account. 🗑️ How to Remove Existing Heatmap Data If you also want existing heatmap results removed, you can delete individual heatmap campaigns and their historical scans directly from the Heatmap page: 1. Go to Local → Local SEO Heatmaps from the left sidebar. 2. Select the heatmap campaign you wish to remove. 3. Use the delete option to remove the campaign and its associated scan history. If you need all heatmap data permanently removed from our servers across your entire account, our team can process a complete data removal request for you. Because this is a permanent action, it must be handled directly by our support team so we can confirm the scope with you before proceeding. 💳 Heatmaps and Your PRO Plan Billing It is important to understand how heatmaps relate to your subscription: - Heatmaps are included as part of the PRO plan feature set rather than billed as a separate standalone product. - Disabling heatmap tracking stops the functionality from running, but on its own it does not change the price of your PRO plan, since the plan bundles multiple PRO-level features together. - If your goal is to avoid being charged for functionality you are not using, you may want to review your overall plan tier rather than only the heatmap feature. If you would like to change your plan, downgrade, or discuss billing adjustments related to features you are not using, our team can review your account and walk you through the best option for your needs. ✅ Quick Recap - Stop future scans by disabling the scheduled heatmap scan in the Local → Local SEO Heatmaps page. - Remove past results by deleting the heatmap campaign and its scan history. - For a complete server-side data removal or billing/plan changes, reach out to our team so we can confirm and process the request. 💬 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.

Last updated on Oct 26, 2026

🔧 Fix Broken GBP Notification Redirect Links

What Is This Issue? If you are using Search Atlas under a white-label agency setup, you may notice that clicking the View button inside a Google Business Profile (GBP) notification redirects you to a blank page instead of opening the review inside your Search Atlas dashboard. This is a known platform-side configuration issue affecting white-label agency accounts. It does not affect the reviews themselves — all review data is still being captured and stored correctly inside your dashboard. Why This Happens GBP review notifications are sent automatically when a new review is posted on a connected Google Business Profile location. For some white-label agency accounts, the redirect URL embedded in those notifications points to an outdated endpoint, causing the browser to display a blank screen. This is a backend configuration issue that requires a fix on the platform side. No action on your end will resolve the broken link itself. How to View Your GBP Reviews Right Now While the redirect link in the notification email is broken, you can still access all of your GBP reviews directly inside the platform: 1. Log in to your Search Atlas dashboard at dashboard.searchatlas.com. 2. In the left sidebar, navigate to Local (GBP Projects). 3. Select the relevant business location from your list of connected profiles in the Local (GBP Projects) section. 4. From there you can view, respond to, and manage all incoming reviews. No review data is lost. Everything referenced in the notification is also available inside the dashboard through the steps above. What You Should Do About the Broken Links There is no action required on your end to fix the redirect links themselves. However, there are a few things you can do in the meantime: - Ignore the View button in existing notification emails and access reviews directly via the dashboard as described above. - Bookmark your GBP Reviews page inside the dashboard for faster access when new notifications arrive. - Inform your team members or sub-users about this workaround so they are not blocked when a notification arrives. Does This Affect All Notifications? This issue specifically affects white-label agency accounts whose notification links point to an outdated domain. Standard accounts using the default Search Atlas domain are not affected. If you are unsure whether your account is impacted, check whether the View button in your GBP notification emails leads to a blank page. Escalating This Issue Because this is a backend configuration issue, it must be resolved by our support team. When reaching out, please have the following ready: - Your agency account name or workspace URL - The exact URL the broken notification link redirects to - A screenshot or description of the blank page behavior 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.

Last updated on Oct 26, 2026

🔧 Fix Yellow Pages Citations, Billing & Campaign Issues

Overview This article addresses three related issues that can occur together when managing local citations in Search Atlas: a Yellow Pages listing that has not updated to your new business name, an unexpected charge appearing on your account, and an inability to create new campaigns due to free trial restrictions. Because these are backend issues, our support team will need to investigate and resolve them on your behalf. Follow the steps below to prepare the information needed when you reach out. Issue 1: Yellow Pages Listing Not Updated After 2+ Months Citation updates — including business name changes — are submitted to directory publishers like Yellow Pages on your behalf. However, propagation to the live directory can take time, and in some cases a sync or submission error may have prevented the update from going through. This type of issue requires investigation by our support team. When contacting support, please have the following ready: - The name of the affected project or account - The old and new business name you expected to see reflected on Yellow Pages - The approximate date the citation update was originally submitted - A screenshot or link showing the Yellow Pages listing still displaying the outdated information Note: After a successful re-submission by our team, allow several weeks for Yellow Pages to reflect the change on their platform. Directory propagation timelines are controlled by the publisher. Issue 2: Unexpected or Incorrect Charge If you have been charged an amount that does not match your expected plan cost, this may be the result of a billing error tied to citation campaign creation. Search Atlas processes refunds for verified incorrect charges. This type of issue requires review by our support team. When contacting support, please have the following ready: - The charge amount and the date it appeared on your account - A description of why you believe the charge is incorrect (e.g., you did not authorize a campaign, or the amount does not match your plan) - Any relevant screenshots from your billing history Important: Do not attempt to re-submit any campaigns or payment information before speaking with the support team, as this could result in a duplicate charge. Issue 3: Cannot Create Campaigns Due to Free Trial Restrictions If your account is unable to create new campaigns because of free trial restrictions, this is a backend account state that our support team can investigate and restore. When contacting support, please have the following ready: - Your account or project name - The exact error message or restriction notice you are seeing - A screenshot of the restriction if 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.

Last updated on Oct 26, 2026

🔍 GBP Audit Stuck in Pending Status

🧭 Overview When you run a GBP audit, processing usually begins immediately and the audit status is tracked on screen. If the status has not updated after several minutes, the audit is likely stuck in a pending state. This is typically caused by a temporary background worker outage on Search Atlas's infrastructure — not by anything wrong with your account or your Google Business Profile. ⚠️ How to Recognise This Issue - You triggered a GBP audit and the status appeared but has not advanced for 5 or more minutes. - The audit status remains Pending with no error message displayed. - Other parts of the platform continue to work normally. 🛠️ What Causes It GBP audits are processed by a dedicated background worker. If that worker goes offline or becomes overloaded, audit tasks queue up and cannot progress until the worker is restarted by our engineering team. This is an infrastructure-level issue that cannot be resolved by changing settings inside your account. ✅ Steps to Take 1. Wait 10–15 minutes. Our monitoring systems detect worker outages automatically, and engineering teams are alerted to restart the worker as quickly as possible. In most cases the audit resumes on its own once the worker is back online. 2. Refresh the page. After waiting, navigate back to your GBP project and check whether the audit status has updated. 3. Do not submit the audit again. Triggering a second audit for the same profile while the first is pending can create duplicate tasks and delay resolution further. 4. Check back after 30 minutes. Once engineering restarts the worker, queued audits are automatically re-dispatched and should complete in the normal timeframe. 5. If the audit is still stuck after 30 minutes, contact our support team so they can escalate to engineering directly (see below). 📋 Information to Have Ready When Contacting Support To help our team investigate quickly, please have the following details available before reaching out: - The name of the GBP profile or project you were auditing. - The approximate time you triggered the audit. - A confirmation that the audit status has not changed for more than 30 minutes. 💡 What Happens Behind the Scenes When our engineering team is alerted, they restart the background worker responsible for processing GBP audit tasks. Once the worker is online, a recovery process automatically re-dispatches any audits that were stuck in the queue. You do not need to do anything for the audit to resume — it will pick up and complete without you having to retrigger it. 💬 Need Further Help? If the audit remains stuck after 30 minutes, please reach out to our support team and we will escalate to engineering on your behalf.

Last updated on Oct 26, 2026

🗺️ Local SEO Heatmap Grid Bug & Credit Refund

🔍 What Happened A platform-side bug caused a number of Local SEO heatmaps to generate incomplete grids rather than the expected full grid layout. This affected projects across multiple accounts running heatmap refreshes. The root cause was a bug in the heatmap grid generation and quota handling process. Rather than failing gracefully when an error occurred, the system consumed credits and returned a malformed or incomplete grid output. Both issues have since been identified and resolved by our engineering team. ✅ What Has Been Fixed - Grid generation bug: The underlying issue that caused incomplete heatmap grids to be produced has been corrected. New refreshes will produce full grids as expected. - Quota handling: The error in how quota was tracked and applied during heatmap refreshes has been resolved. 💳 Credit Refunds for Affected Refreshes If your account consumed credits for heatmap refreshes that returned incomplete grids, those credits may be eligible for a refund. Refunds are being reviewed and processed for confirmed affected accounts. To check the status of your refund or verify whether your account is included: 1. Navigate to the Local SEO section of the platform and review your current heatmap and quota status. 2. Check your credit balance to confirm whether the refund has already been applied. 3. If you do not see the expected credit restoration, contact our support team using the details below so we can investigate your specific account. 🛠️ How to Refresh Affected Heatmaps Once the fix is confirmed on your account, you can re-run heatmap refreshes to generate complete grids. Follow these steps: 1. Navigate to the Local SEO section of the platform and select the relevant project. 2. Open the heatmap you want to refresh and confirm whether it is showing an incomplete grid. 3. Trigger a manual refresh. The system will now process the full grid correctly using your available quota. 4. Allow a few minutes for the grid to fully render, then reload the page to confirm the complete grid is displayed. When reaching out to support, please have your project name, the approximate time the affected refresh occurred, and a screenshot of the incomplete grid ready so our team can investigate efficiently. 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.

Last updated on Oct 26, 2026

📋 Fix Business Description Word Count Rejection Errors

🔎 Overview When submitting your business description through the Data Aggregator and Network Submissions section in Local Citations, Search Atlas validates that your description falls within a strict 50–500 word count range. If your submission is rejected with a word count error, the most common cause is a miscalculation of your actual word count — not a formatting issue, character limit, or browser cache problem. This article explains exactly how word count is measured, why your count may differ from what you expect, and how to correct your description so it passes validation. 🗺️ How to Access Data Aggregator Network Submissions 1. Log in to Search Atlas. 2. In the left sidebar, click Local. 3. Select Local Citations from the sub-menu. 4. Open your target project and navigate to the Data Aggregator and Network Submissions section. 5. Locate the Business Description field to review or edit your current entry. 📏 How Word Count Validation Works Search Atlas counts words using standard whitespace-based tokenisation. Every sequence of characters separated by a space, tab, or line break is counted as one word. The rules below are the most important ones to understand: - Minimum: Your description must contain at least 50 words. - Maximum: Your description must contain no more than 500 words. - Hyphenated compounds (e.g., award-winning) are counted as one word. - Numbers and symbols (e.g., 24/7, $50) each count as one word. - Punctuation attached to a word (e.g., a trailing comma or period) does not create an extra word. - Extra blank lines or multiple consecutive spaces do not add to the word count. This means word processor tools such as Microsoft Word, Google Docs, or browser extensions may report a slightly different count depending on how they handle hyphens, numbers, and punctuation. Always verify your count using a plain-text method before resubmitting. ⚠️ Common Reasons Your Count May Be Wrong - Word processor inflation: Some tools count hyphenated words as two words. Search Atlas counts them as one, so your processor may show a higher number than the platform records. - Copied content with hidden characters: Text pasted from a PDF, website, or formatted document can contain invisible characters or non-breaking spaces that word processors count but the platform does not recognise as word separators. - Contractions and possessives: Words like don't or company's are always counted as a single word. - Bullet points or list formatting: If you paste bulleted text, the bullet symbols may be stripped during submission, which can reduce your word count below 50. ✅ How to Accurately Check Your Word Count 1. Copy your business description text. 2. Paste it into a plain-text editor (Notepad on Windows, TextEdit in plain-text mode on Mac, or an online word counter tool that counts by whitespace). 3. Remove any leading or trailing blank lines. 4. Count the words. Confirm the total is between 50 and 500. 5. If you are close to the boundary, add or remove a few words to create a comfortable buffer — aim for at least 55–495 words to avoid edge-case discrepancies. ✍️ How to Update Your Business Description 1. Navigate to Local → Local Citations in the left sidebar. 2. Open the relevant project and go to Data Aggregator and Network Submissions. 3. Click Edit next to the Business Description field. 4. Paste your corrected description, confirm the word count is within range, and click Save. 5. Resubmit the form. The validation error should no longer appear once your word count is compliant. 🚫 What This Error Is NOT About If you received guidance suggesting the rejection is caused by a character limit, special characters, or a browser cache issue, that guidance does not apply to this specific error. The Data Aggregator business description field uses word count validation only. Clearing your cache or removing special characters will not resolve a word count rejection. Focus solely on adjusting the number of words in your description. 💡 Writing Tips for a Compliant Description - Aim for a natural length of 100–300 words — enough to be informative without padding. - Describe your core services, location, unique value, and who you serve. - Avoid keyword stuffing or repetitive phrases used solely to inflate word count, as these can affect how your listing is received by aggregator networks. - Write in full sentences rather than fragmented bullet points to ensure an accurate and consistent word count. 🆘 Still Seeing the Rejection Error? If you have confirmed your word count is between 50 and 500 and the error persists, there may be an underlying technical issue with your submission. 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.

Last updated on Oct 26, 2026

🗺️ GBP & Local SEO Bug Fixes August 2026

🔧 What Was Fixed The following issues affecting GBP & Local SEO tools have been resolved in the August 26, 2026 platform release. 📌 Strategic Priorities - Broken card sentences: Some Strategic Priorities cards displayed incomplete sentences that were missing a predicate. The copy on all affected cards now reads correctly. 🌡️ Heat Map - Top-ranked pin hover state: The top-ranked pin on the Heat Map did not respond to hover interactions. It now highlights correctly when you move your cursor over it. - Pin click not working: Clicking pins on the Heat Map had no effect. Clicking a pin now opens its associated details as expected. 🖼️ Media Library - Tag filter chips not updating: Adding or removing a tag from a media item did not refresh the tag filter chips in the UI. The filter chips now update immediately to reflect any tag changes. - Empty-state icon: The icon shown when the Media Library contained no items was inconsistent with the rest of the platform. It has been replaced with the standard shared empty-state component. - Video upload not working: No video files could be uploaded through the Videos section of the Media Library. Video uploads now complete successfully. 🏢 GBP Details - Locked profile fields editable in UI: Profile fields that are locked by Google appeared editable in the GBP Details form, even though any attempted save would fail. Locked fields are now correctly displayed as read-only, preventing confusion before you reach the save step. ✅ Do I Need to Do Anything? No action is required. All fixes are live and apply automatically to your account. If you were affected by any of the issues listed above, revisit the relevant area of the platform to confirm everything is now working as expected. 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.

Last updated on Oct 26, 2026

🧊 Unfreeze OTTO Projects to Fix GBP Posting

🔍 Overview When an OTTO project is frozen, all connected features — including Google Business Profile (GBP) automated posting and profile management — are locked. You cannot disconnect a GBP profile, update posting settings, or make any edits to the project until it is unfrozen. This article explains why this happens and the steps you can take to resolve it. ❄️ Why Projects Get Frozen OTTO projects are frozen when your account does not have enough active OTTO plan slots to keep all projects running. Frozen projects continue to hold their slot in your quota but cannot be edited or managed. Common reasons this occurs include: - Your subscription plan was downgraded and you now have fewer OTTO slots available. - You activated new projects that pushed you over your plan limit. - Billing changes temporarily reduced your available slots. A frozen project still counts against your quota but is fully inactive — meaning GBP automated posting stops and you cannot disconnect the linked GBP profile without first resolving the frozen state. 🛠️ How to Unfreeze a Project To regain control of the GBP profile connected to a frozen project, you must first unfreeze it. Follow these steps: 1. In the left sidebar, click OTTO SEO, then select All Sites. 2. Locate the frozen project. Frozen projects are clearly labelled in the project list. 3. Check your current OTTO slot availability at the top of the page. If you have a free slot, click the frozen project and select Unfreeze. 4. Once unfrozen, the project becomes fully editable. You can now disconnect the GBP profile, update automated posting settings, or make any other changes needed. ⚠️ What to Do If You Have No Free Slots If all of your OTTO slots are in use, you will need to free up a slot before you can unfreeze the project you need to edit. You have two options: - Freeze a different active project — Navigate to OTTO SEO → All Sites, select a project you do not currently need active, and click Freeze. This frees up a slot you can use to unfreeze the project blocking your GBP work. - Upgrade your OTTO plan — If you need all current projects to remain active, consider upgrading to a plan with more OTTO slots. Contact our team via the chat widget for guidance on plan options. Once a slot is available, return to the frozen project, unfreeze it, complete your GBP edits or disconnections, and then re-freeze the project if you no longer need it active. 🔗 How to Disconnect a GBP Profile from a Project After the project is unfrozen, follow these steps to disconnect the Google Business Profile: 1. Go to OTTO SEO → All Sites and open the newly unfrozen project. 2. Navigate to the Overview tab for that project. 3. Locate the connected GBP profile under the Local SEO or GBP section. 4. Click the disconnect or remove option next to the GBP profile. 5. Confirm the disconnection when prompted. Once disconnected, the GBP profile is no longer linked to that OTTO project and can be connected to a different project or managed independently. 📋 Managing Multiple Frozen Projects with GBP Profiles If you have several frozen projects that all have GBP profiles attached, the most efficient approach is to work through them one at a time: - Unfreeze one project, disconnect its GBP profile, then re-freeze or delete that project if it is no longer needed. - Repeat for each remaining frozen project. - This approach avoids the need to upgrade your plan if your goal is simply to clean up and disconnect profiles. If you need to disconnect GBP profiles from a large number of frozen projects at once and do not have enough slots to work through them individually, reach out to our support team for assistance. 💡 Tips to Avoid This Issue in the Future - Before freezing a project, disconnect any GBP profiles you no longer need linked to it. - Regularly review your OTTO SEO → All Sites page to keep your active project list aligned with your plan's slot limit. - If you are approaching your slot limit, consider archiving or removing projects that are no longer in use rather than allowing them to be auto-frozen. 🙋 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.

Last updated on Oct 26, 2026

📧 Fix GMB Alerts and Reassign Rejected Guest Posts

📋 Overview This article covers two common questions: why you may not be receiving email alerts for Google Business Profile (GMB) post authorizations, and what happens to your guest post submission after a publisher in Link Laboratory rejects it. Both issues have straightforward solutions explained below. 📬 Why Am I Not Receiving GMB Email Alerts? Search Atlas sends email alerts when activity is detected on your Google Business Profile, including post authorization updates. If you are not receiving these emails, the most common reasons are: - Emails landing in spam or promotions: Check your spam, junk, and promotions folders. Add the Search Atlas sending address to your safe-senders list to prevent this going forward. - Alert threshold behavior: GMB alerts are triggered by any ranking position gain greater than zero on the Local SEO heatmap — including small movements such as a +0.1 position change. If you expected an alert for a larger movement only, be aware that the system is intentionally sensitive and will fire on any positive change. - Notification preferences not enabled: Confirm that email notifications are turned on for your account. Navigate to the top-right corner avatar, then review your profile and notification settings to ensure alerts are active. - Incorrect email address on file: Verify that the email address associated with your account is correct. Go to the top-right corner avatar → Settings → Profile (or Email Settings) to check your account email. If emails are reaching your inbox inconsistently, the most reliable fix is to whitelist Search Atlas in your email client and ensure your account email is up to date. 🔗 What Happens After a Publisher Rejects My Guest Post? When you submit a guest post through Link Laboratory (accessible via the top-right corner avatar → App Ecosystem → Publisher Exchange tab → Go to Link Laboratory) and the publisher rejects your placement, you are not left without options. Search Atlas has an automated reassignment system that works as follows: 1. Rejection is detected automatically: Once a publisher rejects your submission, the placement enters a 72-hour Pending Action window. During this window, you have the opportunity to take action or let the system handle it. 2. Daily auto-assigner runs: Every day, the auto-assigner reviews all publisher-rejected placements that are still within the 72-hour window and reassigns them to a suitable alternative publisher. 3. New placement is confirmed: Once reassigned, your guest post moves forward with the new publisher. You will be notified of the updated placement status. This means your campaign is not stalled by a single publisher's decision. The system automatically finds a replacement so your link-building timeline stays on track. ✅ What Should I Do After a Rejection? While the auto-assigner handles most cases automatically, here are the steps we recommend: 1. Log in to Search Atlas and navigate to Link Laboratory via the top-right corner avatar → App Ecosystem → Publisher Exchange tab → Go to Link Laboratory. 2. Locate your rejected placement and check its current status in the dashboard. 3. If the placement is still within the 72-hour Pending Action window, you may also manually request reassignment or adjust your submission details before the auto-assigner runs. 4. After the window closes, confirm that a new publisher has been assigned and review the updated placement details. If the placement does not appear to have been reassigned after 72 hours, contact our team using the live chat widget for a manual review. 💡 Quick Tips to Avoid Future Issues - Keep your account email address up to date so you never miss an alert. - Whitelist Search Atlas emails to ensure delivery to your primary inbox. - Monitor Link Laboratory regularly during the 72-hour window after a submission, especially for time-sensitive campaigns. - Review your guest post content against publisher guidelines before submission to reduce the likelihood of rejection in the first place. 🆘 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.

Last updated on Oct 26, 2026

🔧 Fix Google Business Profile Mapping in Brand Vault

🔍 Overview After mapping a Google Business Profile (GBP) location inside Brand Vault, some customers find that the mapping reverts to a Needs profile status — even when the address appears to match and the save action reports success. This article explains what is happening and what to expect while our team works to resolve it. ⚠️ Why This Happens This behaviour is caused by a known issue currently being investigated by our engineering team. The GBP mapping does not always persist correctly after saving inside Brand Vault, causing the status to revert to Needs profile on subsequent page loads. The issue is tracked internally and a fix is actively in development. 🛠️ What to Do Right Now Because this is a confirmed bug, there is no reliable self-serve workaround at this time. To get your mapping corrected, please escalate to our support team. When you reach out, have the following information ready so we can act quickly: - The name of the Brand Vault brand or location showing Needs profile. - The Google Business Profile name and address you are trying to map. - A brief description of what you did when the revert occurred (e.g. saved the mapping, refreshed the page). - Any screenshots showing the Needs profile status after saving. ✅ What a Resolved Mapping Looks Like Once the mapping is correctly saved, the Needs profile label will be replaced by your business name and address. GBP data such as address, phone, or hours will also pre-fill correctly into Brand Vault fields, confirming the connection is live. 📋 Known Limitation This issue is under active development. We will update this article when a fix has been released. Thank you for your patience. 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.

Last updated on Oct 26, 2026

🔗 Fix GBP Linking Issues and Schedule Onboarding

🔍 Overview Some customers complete the Google Business Profile (GBP) connection process in Brand Vault without errors, yet the status does not update to Connected. This article explains why this happens, how to fix it, and how to schedule a personalised onboarding session to get the most out of Search Atlas. ⚠️ Why Your GBP Status May Show as Disconnected A known issue can cause GBP connection status to display incorrectly after the authorisation flow completes. This typically occurs in one of the following situations: - The Google account used to connect GBP was accessed via a shared link during Step 2 of the onboarding flow, rather than a direct login. - The connection completed successfully in the background, but the status indicator did not refresh automatically. - The Google account has multiple Business Profiles and the correct location was not selected during the linking step. 🛠️ Steps to Resolve the GBP Connection Issue 1. Refresh the page after completing the authorisation flow. The status indicator sometimes requires a manual page reload to reflect the updated connection state. 2. Avoid shared links. If you were invited to connect via a shared or forwarded URL, navigate directly to Local → GBP Projects (and click the Connect GBP Account button) and start the connection process from there instead. 3. Check your Google account permissions. Make sure you are logged in to the Google account that has Owner or Manager access to the Business Profile you want to link. 4. Select the correct Business Profile location. During the authorisation screen, confirm you are selecting the specific location you want to connect—not a different profile associated with the same Google account. 5. Disconnect and reconnect. If the status still shows as disconnected after following the steps above, click Disconnect next to the location in Local → GBP Projects, wait 30 seconds, then go through the connection flow again using a direct login. 6. Clear browser cache or try a different browser. Cached session data can sometimes interfere with OAuth flows. Use an incognito window or a different browser as a quick test. ✅ How to Confirm Your GBP Is Successfully Connected Once the connection is established correctly, you will see the following indicators in Brand Vault: - The location card displays a green Connected badge next to the Business Profile name. - GBP data—including reviews, Q&A, and local listing details—begins populating within the location dashboard. - The OTTO SEO agent can access GBP signals for that location when running local SEO tasks. If the badge remains grey or shows Disconnected after completing all steps above, this may indicate an account-level permission issue on the Google side. Double-check that your Google account has not had its GBP access revoked or transferred. 📅 How to Schedule a 1-on-1 Onboarding Session Search Atlas offers personalised onboarding sessions to help new customers set up their account correctly and get the most value from the platform. To schedule your session: 1. Log in to your Search Atlas account. 2. Open the chat widget in the bottom-right corner of the platform. 3. Type onboarding session to trigger the scheduling flow, or type human teammate to speak directly with a team member who can book a time that works for you. During your onboarding session, a Search Atlas specialist can walk you through GBP linking, OTTO SEO configuration, keyword tracking setup, and any other areas where you need guidance. 💡 Tips for a Smooth GBP Connection - Always use a direct browser session—not a shared or forwarded link—when authorising Google integrations. - Connect GBP using the Google account that is the primary owner of the Business Profile wherever possible. - If you manage multiple locations, connect them one at a time and confirm each status before moving to the next. - Keep your browser up to date to avoid OAuth compatibility issues. 🙋 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.

Last updated on Oct 26, 2026

📊 Troubleshooting GBP Metrics Not Displaying in Report Builder

📋 Overview If you have added a Google Business Profile (GBP) section to your report but the metrics are not displaying, this article will walk you through the most common causes and their fixes. This applies even if you have already tried standard troubleshooting steps such as a hard refresh or adjusting your date filters. GBP metrics rely on an active integration and a properly saved report configuration. When one of these elements is disrupted, the section may appear empty, disappear entirely, or display inconsistently between the editor and the shared view. 🔍 Why Your GBP Metrics Are Not Showing There are several reasons GBP stats may fail to populate in the Report Builder, including: - The GBP section was removed automatically after saving the report configuration. - The connected Google Business Profile location has not synced enough data for the selected date range. - The date range falls outside the window where Google provides GBP insights (Google typically limits historical data availability). - The report was opened via a shared URL that displays a different layout or metric set than the editor. - The GBP integration disconnected or lost authorization since the report was created. 🛠️ Step-by-Step Fixes Work through the following steps in order. Most GBP display issues are resolved by re-verifying the integration and re-adding the section. 1. Navigate to Reports in the left sidebar to open your Report Builder projects list. 2. Open the affected report and confirm that a GBP section is still present in the layout. If it disappeared after saving, add it again from the section menu. 3. Confirm the correct Google Business Profile location is selected for the report. If no location is connected, reconnect your GBP account before proceeding. 4. Set the date range to a period within the last few months, as Google limits how far back GBP insights are available. Very recent dates (the last 2–3 days) may also lack data because Google reports insights with a delay. 5. After adjusting the section and date range, save the report configuration again to lock in your changes. 6. Perform a hard refresh of the page to load the updated metric cards. 🔗 Checking the Shared Report View If your GBP metrics appear correctly in the editor but are missing or look different in the shared report URL, this is often a layout-sync issue between the editor and the published version. - Return to the editor and confirm the GBP section displays as expected. - Re-save the report to force the shared URL to regenerate with the current layout. - Reopen the shared link in a fresh browser tab or incognito window to confirm the metrics now match the editor. 📈 Understanding GBP Metric Cards When your GBP metrics do load, you may notice several summary elements, including a Total Searches versus Maps Views summary bar and individual metric cards showing change deltas. Each metric card includes an arrow indicator that reflects whether a value increased or decreased compared to the prior period. If a card shows a delta but seems visually inconsistent, re-saving and refreshing the report will typically restore the correct display. ✅ When to Reconnect Your GBP Integration If the GBP section continues to show empty metrics after completing the steps above, the underlying integration may need to be reconnected: 1. Verify your Google Business Profile account is still authorized within the platform. 2. If authorization has lapsed, reconnect the account and grant all requested permissions. 3. Return to your report, re-add or refresh the GBP section, save, and reload. 💬 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.

Last updated on Oct 26, 2026

🔔 GMB Post Alerts and Rejected Post Resubmission

📌 Overview If you are not receiving email alerts when a Google Business Profile (GMB) post requires your authorization, or if you need to resubmit a rejected guest post to a different publisher, this article explains what to expect and what information to have ready when reaching out to our team. ⚠️ About GMB Post Authorization Alerts Some users have reported not receiving email alerts when a GMB post is pending authorization or has been rejected. If you are experiencing this, our team will need to investigate your specific account configuration and post history to identify the cause and apply a resolution on the backend. 🔄 Resubmitting a Rejected Guest Post If a guest post has been rejected and you need to resubmit it to a different publisher, this action currently requires backend assistance from our team. There is no self-serve workflow available in the platform at this time for reassigning a rejected post to a new publisher. 📋 What to Have Ready When You Contact Support To help our team resolve your issue as quickly as possible, please have the following information available before reaching out: - The name of the project or business profile affected - The exact post title or content snippet for the rejected or undelivered post - The date and approximate time the post was submitted - Any rejection reason or error message you have observed - Confirmation of whether the authorization alert email was expected but not received, or whether the post rejection itself is the primary concern 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.

Last updated on Oct 26, 2026

🛑 Stop Unwanted GBP Posts After Cancellation

🔍 Why This Happens When a Search Atlas subscription is canceled, automated Google Business Profile (GBP) posting configurations may not be deactivated immediately. This can cause scheduled or automation-driven posts to continue publishing to your Google Business Profile even after your account is no longer active. We take this seriously — unwanted posts containing inaccurate information can harm your business reputation, and stopping them quickly is our priority. ⚙️ What Needs to Happen Stopping unwanted GBP posts on a canceled account requires our team to investigate and deactivate the automation on the backend. This is not something that can be resolved through the platform interface alone, as the posting configuration can persist after account cancellation. 🛠️ Information to Provide When Contacting Us To help our team resolve this as quickly as possible, please have the following information ready: - The name of the affected Google Business Profile location - Your Search Atlas account name or ID associated with the canceled subscription - Examples of recent unwanted posts (including approximate dates and times) - Any GBP listing URLs that are affected ✅ What to Expect Once our team receives your report, we will investigate the source of the automated posts on the backend and ensure all posting configurations are fully deactivated. We will confirm with you once the automation has been stopped and no further posts will be published. 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.

Last updated on Oct 26, 2026

🔄 Google Business Profile Reviews Showing Late in Search Atlas

🔍 What Is Happening Some Search Atlas users have noticed that new reviews posted on Google Business Profile (GBP) do not appear in their Search Atlas dashboard until 7–8 days after the review was published. This delay is not caused by a settings error on your account — it is a known platform issue currently under active investigation by our engineering team. ⚙️ Why the Delay Occurs Search Atlas uses two syncing processes to pull new GBP reviews into your dashboard: - Real-time / daily sync: Designed to check for new reviews every 12 hours using Google's pub/sub notification system. - Weekly full sync: A comprehensive sync that runs every Saturday and catches anything the daily sync missed. For a significant portion of connected locations, Google's pub/sub notifications are not being delivered reliably to Search Atlas. This means the daily 12-hour sync does not detect new reviews, and those reviews only surface when the weekly Saturday sync runs — resulting in a 7–8 day gap. Our engineering team has confirmed this affects approximately 75% of active GBP locations and is not isolated to a single account or region. 📊 How to Check Your Reviews in Search Atlas While our team works on a fix, you can manually check for newly synced reviews by navigating to Left sidebar → Local → Reviews (GBP Reviews). Reviews that have completed the weekly sync will appear here. If a review you are expecting is not visible, it is likely waiting for the next Saturday full sync to complete. 🛠️ What Our Engineering Team Is Doing This is being actively worked on. Here is the current status of related fixes: - Real-time sync fix (In Progress): Engineers are investigating why Google pub/sub notifications are not delivering for the majority of locations and are working to restore reliable daily syncing. - 7-Day no-sync alert (In Development): A health monitoring feature is being built that will automatically alert you if a location has not synced within 7 days, so you are never left wondering about a delay. - Edited reviews not updating (Under Investigation): A separate but related issue has been identified where reviews that are edited on Google after their initial posting are not being updated in the Search Atlas dashboard. This is also being tracked and investigated. ✅ What You Should Do Right Now 1. Be aware that new reviews may not appear in Search Atlas for up to 7–8 days if your location is affected by this sync issue. 2. To verify a review exists, check directly on your Google Business Profile in Google Maps or Google Search. 3. Check your Left sidebar → Local → Reviews (GBP Reviews) after each Saturday to confirm recently synced reviews have appeared. 4. If a review has not appeared after more than 8 days, contact our support team so we can investigate your specific location. 💡 Important Notes - This is a backend sync issue — there is nothing wrong with how your GBP account is connected to Search Atlas. - Reviews are not lost; they will sync on the next full Saturday sync at the latest. - Edited reviews (reviews that were changed after being originally posted on Google) are subject to a separate known issue and may not update in the dashboard even after a full sync. Report these individually to support so they can be tracked. 💬 Still Need Help? If your reviews have not appeared after more than 8 days, or if you suspect your location may have a different issue, we want to hear from you. 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.

Last updated on Oct 26, 2026

⚡ Fix GBP/NAP Mismatches and Citation Scan Delays

📋 Overview NAP stands for Name, Address, and Phone Number — the three core data points used to verify your business identity across the web. When your Google Business Profile (GBP) and website show different NAP data, or when recent updates do not appear immediately in Search Atlas citation scans, it can affect your local SEO rankings and create confusion for customers. This article explains the most common causes and how to resolve them. 🔍 Why Your GBP and Website NAP May Not Match Even small formatting differences count as mismatches. Search engines and citation tools compare NAP data character by character, so inconsistencies that look minor to a human eye can cause real SEO issues. Common causes of NAP mismatches include: - Phone number formatting: Your GBP may store your number as +1 (555) 123-4567 while your website displays 555-123-4567 or (555) 123-4567. These are treated as different values by citation scanners. - Country code handling (+1): Some platforms automatically prepend +1 to US numbers pulled from GBP. If your website omits the country code, a mismatch is flagged even though the number is functionally identical. - **Address abbreviations:**St. vs Street, Ave vs Avenue, or a missing suite number can all register as mismatches. - Business name variations: Using LLC, Inc., or shortened names inconsistently across your GBP, website, and directories will trigger citation errors. - Outdated website footer or contact page: A GBP update does not automatically update your website. Both must be edited separately. ✅ How to Audit and Fix Your NAP Data 1. Log in to your Google Business Profile dashboard and note your exact business name, address, and phone number as they currently appear. 2. Compare this data exactly — character by character — against what appears on your website's contact page, footer, and any schema markup. 3. Correct any discrepancies directly in Google Business Profile (via your GBP dashboard) and update your website to match. Use one consistent format for your phone number across all locations, for example: (555) 123-4567 with no country code, or +1 (555) 123-4567 with the country code — choose one and apply it everywhere. 4. Check all major directories (Yelp, Bing Places, Apple Maps, etc.) and update any outdated or inconsistent NAP data there as well. 5. Once all sources are corrected, allow time for Search Atlas to re-scan your citations and reflect the updated data. Citation scans do not update in real time — propagation can take time depending on the scan schedule. ⏱️ Why Citation Scans Take Time to Update Citation scans are not performed in real time. After you make changes to your GBP or website NAP data, Search Atlas will reflect those changes on its next scheduled scan cycle. This is expected behavior and not an error. If a significant amount of time has passed and data still appears outdated, try triggering a manual re-scan from within the platform if that option is available for your project. 🛠️ When to Escalate If you have corrected your NAP data across all sources and the mismatch persists in Search Atlas after a full scan cycle, escalate to the support team. When you do, have the following ready: your project name, the specific field showing the mismatch (name, address, or phone), the exact values shown in Search Atlas vs. your GBP, and an approximate timestamp of when you made your corrections. 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.

Last updated on Oct 26, 2026

💳 Fix Payment Failures Blocking Local SEO Quota

🔍 Overview You may notice that your Local SEO Generation quota still shows remaining points — for example, 3,515 out of 5,400 — yet you receive an out-of-quota error when attempting to generate a review reply or other Local SEO content. Refreshing the page or logging out does not resolve the issue. In most cases, this is caused by a payment failure on your account, which temporarily suspends access to quota-based features even when points appear to be available. ⚙️ Why This Happens Search Atlas links quota access to your account's billing status. When a payment attempt fails — due to an expired card, insufficient funds, or a bank-side decline — the platform places a hold on feature usage to protect your account. The quota counter continues to display your remaining points, but the system blocks new generations until the billing issue is resolved. This is expected behavior designed to keep your account in a consistent state. 🛠️ How to Fix the Issue 1. Check your billing status. Navigate to your account settings and open the Billing or Subscription section. Look for any alerts, failed payment notices, or past-due invoices. 2. Update your payment method. If your card has expired or was declined, add a new card or update the existing one. Make sure the billing address matches what your bank has on file. 3. Retry the payment. Once your payment details are updated, use the option to retry or pay the outstanding balance. Your account will return to active status as soon as the payment is successfully processed. 4. Verify quota access is restored. Go to Left sidebar → Local → Reviews (GBP Reviews) and attempt to generate a review reply again. The out-of-quota error should no longer appear if the payment was successful. ✅ Confirming Everything Is Working After resolving the payment issue, confirm that your Local SEO features are fully accessible: - Navigate to Left sidebar → GBP Projects → Overview to check your project dashboard loads correctly. - Go to Left sidebar → Local → Reviews (GBP Reviews) and attempt to generate a review reply using your remaining points. - Verify your quota counter reflects the correct remaining balance and that no error messages appear. If your quota balance looks incorrect after the payment is resolved, allow a few minutes for the system to sync, then refresh your browser. 🚫 What Does Not Fix This Issue The following steps will not resolve an out-of-quota error caused by a payment failure: - Refreshing the page or clearing your browser cache - Logging out and back in - Switching browsers or devices - Waiting for the quota to reset These actions do not change your account's billing status, so the block remains in place until the payment issue is addressed. 💡 Tips to Prevent This in the Future - Keep your payment method up to date. Update your card details before the expiry date to avoid automatic payment failures. - Enable billing notifications. Make sure the email address on your account is active so you receive payment failure alerts promptly. - Check your account status regularly. A quick visit to the Billing section each month can help you catch issues before they affect your workflow. 🙋 Still Seeing the Error? If your payment has been successfully processed but you are still seeing the out-of-quota error, or if you are unable to locate the billing settings on your account, our team is ready to 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.

Last updated on Oct 26, 2026

🛠️ Resolving GBP Audit Quota Exhaustion Errors

The GBP Audit quota exhaustion error appears when your account has used all of the Google Business Profile audits included in your current plan for the billing period. This article explains what the error means, how to check your remaining allowance, and the fastest ways to get audits running again. 🤔 What the Quota Exhaustion Error Means Each Search Atlas plan includes a fixed number of GBP Audit runs per billing cycle, tracked as your allowed GBP audits. When you try to start a new audit after using your full allowance, the audit stops and the platform displays a quota exhaustion message instead of a report. - Quota message: you have used every audit in your current allowance. - Technical error message: the audit failed for another reason, such as an invalid profile or a data issue. These are separate states with distinct messages, so read the on-screen text carefully before acting. GBP Audits draw from their own dedicated quota. They do not consume Heatmap credits or Local SEO Points, so topping up those balances will not resolve this error. 🔍 How to Check Your Remaining Quota 1. Click your avatar in the top-right corner of the platform. 2. Select Billing. 3. Open the Plans & Top-ups tab. 4. Review the quota model details to see your plan's included GBP Audit allowance and current usage. The quota panel shows how many audits remain in your current billing cycle, so you can plan your runs before reaching the limit. 🔄 When Your Quota Resets Your GBP Audit allowance resets at the start of each billing cycle. If your error is caused purely by quota exhaustion and you do not need audits urgently, the simplest fix is to wait for the reset and re-run the audit afterwards. Your saved profiles and previously generated reports are not affected — nothing is deleted when you hit the limit. 💳 How to Top Up or Increase Your Allowance If you need additional audits before your reset date, all options are handled from the Billing area: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing. 3. Open the Plans & Top-ups tab. From there, choose the option that fits your situation: - Buy a top-up: purchase additional GBP Audit runs that become available immediately. - Upgrade your plan: higher-tier plans include a larger monthly allowance of allowed GBP audits. - Redeem a promo code: if you have a promotional code, apply it from the Plans & Top-ups tab to add extra quota. If you do not have a payment method on file yet, use the Add Payment Method action on the same tab before purchasing a top-up or upgrading your plan. ✅ Best Practices to Avoid Exhausting Quota - Check your remaining audits under Billing → Plans & Top-ups before launching batch audits. - Run audits only for profiles you actively manage, and remove unused ones from your queue. - Space audits across your billing cycle instead of running them all at once. - Remember that audits which fail with a technical (non-quota) error message can be re-run and do not count toward your successful audit allowance. 💬 Still Seeing the Error After a Top-Up? If you have confirmed available quota or completed a top-up and the quota error still appears, refresh the page and re-run the audit once. If the error persists, our team can review your account's quota usage 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.

Last updated on Oct 26, 2026

🛠️ Fix a Stuck Local SEO Post Generation

🔍 Overview When creating a Local SEO post, the workflow moves through a series of steps before your content is ready. Occasionally, the process stalls at Step 2 – Generating Your Posts and does not advance, even after refreshing the page or clearing your browser cache. This article explains why this happens and what you can do to get your posts generated successfully. ⚠️ Why Posts Get Stuck at the Generating Step The post generation process relies on a background task queue. If a task in that queue stalls or encounters an error, your post can appear frozen indefinitely. Common reasons this occurs include: - A background processing task became stuck or timed out before completing. - One or more linked business locations encountered an error during content creation, causing the entire batch to pause. - A temporary platform-side issue disrupted the generation queue at the time you submitted your post. - The post entered a silent Failed state with no visible error message or retry option shown in the UI. Refreshing the page, restarting the workflow, or clearing your browser cache will not resolve these issues because the problem occurs in the background, not in your browser. ✅ Steps to Resolve a Stuck Post 1. Wait up to 10 minutes. Background tasks can occasionally be delayed under high load. If the post is still stuck after 10 minutes, move to the next step. 2. Navigate to your Posts list. Go to Left sidebar → Local → Posts. Check whether the post appears with a Failed or Draft status. 3. Delete the stuck post and start a new one. If the post shows no option to retry or resume, delete it and create a new post from scratch. This clears the stalled background task and starts a clean generation request. 4. Check your connected locations. Before re-creating the post, confirm that the Google Business Profile locations you are targeting are properly connected. Go to Left sidebar → Local → Overview and verify each location shows an active status. A disconnected or misconfigured location can silently cause generation to fail. 5. Recreate the post for a single location first. If you are generating posts in bulk across multiple locations, try creating the post for one location only. This helps identify whether a specific location is causing the failure before you run a full batch. 💡 Tips to Prevent This Issue - Keep your Google Business Profile locations connected and authorised at all times before running post generation. - Avoid navigating away from the generation step immediately after submitting — allow the UI to confirm the task has been accepted before leaving the page. - If you run bulk post generation across many locations, monitor the Posts list after submission to catch any locations that did not receive content. - Note that when bulk generation partially succeeds, the platform may show a lower number of created posts than expected. Review your Posts list to confirm which locations received content and which did not. 🆘 Still Stuck? Contact Support If your post remains stuck after following the steps above, or if you see a Failed status with no way to retry, our team can investigate the background task queue and resolve it for you. 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.

Last updated on Oct 26, 2026

🛠️ Resolving GBP Audit Quota Errors

This guide explains what the GBP Audit quota is, why you may see an error when running an audit, and how to top up your quota so you can get back to work. 🔍 What the GBP Audit Quota Error Means Every Search Atlas plan includes a set number of Google Business Profile (GBP) audits you can run in each billing cycle. This number is your audit quota. Each time you generate a new GBP Audit report, one audit is deducted from that quota. If you see an error when starting a GBP Audit that mentions your quota, running out of audits, or being out of points, it means you have used all the audits available on your plan for the current billing cycle. The audit did not run, and your existing reports have not changed. Good to know: GBP Audits draw from a dedicated per-plan audit quota. Running audits does not reduce the Local SEO Points or heatmap credits available for your other tools. 📊 How to Check Your Remaining Audit Quota To see how many audits you have left in your billing cycle: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing. 3. Open the Plans & Top-ups tab. 4. Review the quota details to see how many GBP audits remain for this cycle. 💳 How to Top Up Your GBP Audit Quota Yes, there is a way to top up. If you run out of audits before your quota resets, you can purchase additional audits in a few steps: 1. Click your avatar in the top-right corner of the platform. 2. Select Billing. 3. Open the Plans & Top-ups tab. 4. Choose a top-up option that includes GBP audits and complete the checkout. 5. Return to the GBP Audit tool and run your audit again. If you do not have a payment method saved yet, use the Add Payment Method button on the same tab before purchasing your top-up. Have a promo code? Use the Redeem Promo Code option in the Billing section to add extra quota to your account at no cost. If you regularly run out of audits, upgrading to a higher plan gives you a larger included audit quota every billing cycle. ♻️ When Your Quota Resets Your audit quota refreshes automatically at the start of each new billing cycle. If you prefer not to top up, simply wait for the reset and run your audit then. Audits that never started because of the quota error did not consume any of your quota. 🚫 If the Error Is Not Quota-Related Not every GBP Audit error means you are out of quota. The platform shows a distinct message for quota exhaustion, separate from other failure types. If your error mentions something else, such as an invalid Business Profile, a connection problem, or a data issue, try these quick checks: - Confirm the Google Business Profile you are auditing is live and publicly visible. - Double-check the business name and location details you entered. - Refresh the page and run the audit again. - Verify your account and billing are active in the Billing section. If the audit still fails after these checks, reach out using the chat option below and include the name of the business you were auditing so we can investigate faster. 💬 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.

Last updated on Oct 26, 2026

🛠️ Local Citation Status Stuck in 'Submitting' Fix

🔍 Overview After purchasing a local citation pack, orders normally complete within 50 days. If your order still shows a Submitting status beyond that window, you are likely experiencing a known display bug where the platform's interface does not correctly reflect the actual backend submission status. This article explains what causes the issue, how to confirm it, and what steps to take. ⚙️ What Causes This Issue Our engineering team identified and resolved a backend discrepancy affecting local citation campaigns. In some cases, citations were fully submitted to directories — including the Foursquare and GPS network — but the status visible in the platform did not update to reflect completion. This mismatch caused orders to appear permanently stuck in Submitting even though the underlying work was finished. A related issue also caused the status shown in the list view to differ from the status shown inside the submission details modal. Both of these bugs have been fixed and deployed to production. ✅ How to Check Your Citation Order Status 1. In the left sidebar, go to Local → Local Citations. 2. Open the relevant project and navigate to your local citations section. 3. Review the current status displayed for each citation pack order. 4. If an order was placed more than 50 days ago and still shows Submitting, the status may not have refreshed automatically following the bug fix deployment. 💡 What to Do If the Status Has Not Updated Because this was a UI and backend synchronisation bug, some accounts may need a manual status refresh applied by our team after the fix was deployed. There is no self-serve action inside the platform that forces a status recalculation for historical orders affected by this bug. If your citation order is still showing Submitting after the fix has been live for at least 48 hours, the next step is to contact our support team so an agent can verify your specific order records, confirm whether submissions were completed on the backend, and apply any necessary corrections to your account. 📋 Information to Have Ready Before Contacting Support - The dates your citation pack orders were purchased (for example, the order from September 2 or March 11) - The name of the GBP project or business location associated with the orders - A screenshot of the current status shown in the platform, if possible - Confirmation of how many days have passed since each order was placed 🚀 What Our Team Will Do When you reach out, a support agent will look up your citation order records on the backend to confirm whether submissions were actually completed despite the status display. If the fix has been deployed and your status still has not updated, the agent will escalate to the engineering team with your account details and track the correction through to resolution. You will be given a feedback window to confirm the status displays correctly after any fix is applied. 📞 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.

Last updated on Oct 26, 2026

🔍 Investigate Google Connection Drops

🔎 What causes recurring disconnections? Search Atlas connects to Google using authorization tokens. A connection may appear valid but stop working when Google expires or revokes a token, permissions change, access is removed, or Google temporarily returns an authentication error. GBP connections can be affected by profile ownership, manager permissions, duplicate locations, or intermittent Google API responses. These issues may occur at any time, including weekends, and do not necessarily mean your credentials are incorrect. ✅ Check the connection status 1. For Google Search Console, open the relevant project in Search Atlas and review its integration or connection status. 2. For Google Business Profile, open the affected GBP project in Search Atlas. 3. Note which property or location is disconnected, the time it happened, and any displayed error message. 4. Check whether the issue affects one property or multiple properties connected to the same Google account. 🔐 Confirm Google access - Sign in to the Google account that owns or manages the affected property. - Confirm that the account still has the required Search Console or Business Profile permissions. - Check that the property or location has not been deleted, transferred, renamed, or duplicated in Google. - For GBP, verify that the account has appropriate access to each affected location, not only to the business group. 🔄 Reconnect the affected service 1. Disconnect only the affected Google connection when the platform provides that option. 2. Reconnect it using the Google account with confirmed access. 3. Approve all requested permissions and select the correct properties or locations. 4. Return to the project and confirm that data loads successfully. Reconnect only once when possible. Repeated reconnect attempts can make it harder to identify whether the issue is caused by permissions, a specific property, or a temporary Google response. 🧪 Collect details for investigation If the connection disconnects again, record the exact time, your time zone, affected properties or locations, Google account used, and the full error message. Screenshots of the connection status and any failed synchronization are also useful. Also note whether the issue happens after a password change, permission update, account switch, location transfer, or other Google Business Profile change. This information helps determine whether the failure is token-related, property-specific, or part of a broader service issue. 🛠️ How recurring issues are handled Some disconnections are caused by recoverable Google authentication responses rather than a permanent loss of access. Search Atlas may need to investigate server logs, token handling, affected profile types, and synchronization behavior to identify the underlying cause. When escalating, please have your project name, affected Google account, exact error message, and the timestamp of the disconnection ready. 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.

Last updated on Oct 26, 2026

🔧 Fix Wrong Phone Numbers on YP Network Citations

Overview When you submit a phone number correction through Search Atlas, the update is sent to the YP Network (and other citation sources) on your behalf. However, YP Network citations can take longer to reflect changes than other directories — this is normal and not a sign that something has gone wrong. This article explains why delays happen, what the correction process looks like, and what you can do while you wait. Why Does the YP Network Take So Long to Update? Unlike some directories that accept automated data pushes instantly, the YP Network applies its own internal review and publishing process. This means: - Updates are submitted promptly by Search Atlas, but YP Network controls when the change goes live on their side. - Processing times vary depending on the type of correction and YP Network's current queue. - Phone number corrections may take longer than address or name changes because YP Network may conduct additional verification steps. - Cached versions of your listing can appear on third-party sites that pull from YP data, which adds another layer of delay. This delay does not mean your correction was lost or ignored — it means it is in YP Network's publishing pipeline. How to Check the Status of Your Citation Update You can monitor the progress of your citation correction inside Search Atlas by navigating to your citations management area and locating the YP Network listing. The listing will reflect its current update status so you can confirm whether the correction has been submitted. If the update shows as submitted, the correction has been sent to YP Network and is waiting on their end to be published. No further action is required from you at this stage. What You Should Do Right Now While waiting for the YP Network to publish the corrected phone number, we recommend the following steps: - Verify the correct number is live on other directories. Check Google Business Profile, Bing Places, Yelp, and other major citations to confirm the right number appears there. - Ensure your website displays the correct phone number. Search engines use your website as a trusted source, so consistency there matters. - Do not resubmit the correction multiple times. Duplicate submissions can cause conflicts in YP Network's system and may delay the update further. - Document the discrepancy. Keep a note of when the correction was submitted so you have a reference point if escalation is needed later. When to Escalate If your YP Network listing has not updated after an extended period and you believe something may have gone wrong, please reach out to our support team. When escalating, have the following ready: - Your project name or business name as it appears in Search Atlas - The incorrect phone number currently showing on YP Network - The correct phone number that should appear - The date the correction was originally submitted 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.

Last updated on Oct 26, 2026

🛠️ Local Citation Submissions Stuck on 'Submitting' Status

🔍 Overview Some Local Citation campaigns displayed a Submitting to Sites status that never updated — even after the campaigns had already been successfully submitted and passed to publishing channels. This was a confirmed UI display bug, not a failure in the underlying submission process. Our engineering team has identified the root cause and deployed a fix. If you are still seeing a stuck status, the information below explains what happened and what steps to take. 📋 What Caused This Issue The problem was a front-end status display error. While your campaign data was actually submitted and handed off to the relevant citation networks correctly, the platform's status display did not update to reflect the completed state. As a result, campaigns showed an incorrect status indefinitely, even though the work had finished on the back end. This affected multiple campaigns simultaneously and was unrelated to account settings, subscription level, or the number of businesses in a project. ✅ What Has Been Resolved The engineering and QA teams have deployed fixes addressing this issue. Specifically: - The status display logic has been corrected so that campaigns accurately reflect their completed state after submission. - An update was applied to prevent mismatched statuses from appearing in future submissions. These fixes cover campaigns that were stuck due to the UI glitch and ensure new submissions display the correct status as they progress. 🚀 Steps to Take If You Still See a Stuck Status 1. Perform a hard refresh of your browser (press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac). This clears cached page data and loads the latest status from the server. 2. Navigate away from the current page and return to your Local Citation campaign to allow the status to reload cleanly. 3. If the status still appears stuck after refreshing, note the campaign name(s) and the date they were originally submitted, then contact our support team using the instructions below. 💡 How to Check Whether Your Submission Actually Completed Because this was a display-only bug, your citations may have been successfully submitted even while the status appeared stuck. A few things to keep in mind: - Submission to citation networks and aggregators can take time to propagate and appear live on individual directories — this is normal and does not indicate a problem. - If the fix has been applied and your status no longer appears stuck, your submission was processed correctly and no further action is needed on your end. 📞 Still Need Help? If your campaign status remains stuck after following the steps above, please reach out to our support team via the chat widget in your Search Atlas dashboard. Have your campaign name(s) and original submission date ready so we can investigate promptly.

Last updated on Oct 26, 2026

🛠️ Troubleshooting Cloud Stack Generation Failed Error

This article helps you fix the "Cloud stack generation failed. Please try generating again" error that can appear when uploading images inside your GBP Project. This error is typically triggered by an issue with the image file itself or a temporary platform hiccup — not always the number of images selected. The steps below give you the specific checks and actions needed to resolve it and confirm the upload succeeded. 📍 Where to Find It Navigate to Left sidebar → Local → GBP Projects, then open the relevant project. The cloud stack image upload option is available within the project's posting or overview area. 🛠️ Step-by-Step 1. Refresh and retry immediately. The error is sometimes caused by a momentary connection issue with the cloud service. Close the dialog, wait 30 seconds, and attempt the generation again before making any other changes. 2. Check your image file format. Only use widely supported formats such as JPG, JPEG, PNG, or WebP. Files in HEIC, TIFF, BMP, or other formats can trigger this error even if the image count is within the limit. 3. Verify image file size. Each image should be under 5 MB. Large files may cause the cloud stack process to fail silently. Compress or resize any image that exceeds this threshold before re-uploading. 4. Confirm you are selecting fewer than 4 images. Even if you believe you have selected fewer than 4, deselect all images and reselect them one at a time to rule out a selection state error in the UI. 5. Check image dimensions. Very small images (under 250 × 250 px) or unusually large canvases can cause processing failures. Use images with standard dimensions appropriate for Google Business Profile posts. 6. Try a different browser or clear your cache. Open your GBP Project in an incognito window or a different browser. Clear cached data if the error persists in your usual browser, as stale cache can interfere with upload processing. 7. Re-upload with a single image first. If multi-image uploads continue to fail, test with one image only to isolate whether the issue is file-specific or affects all uploads in this project. ✅ How to Confirm It Worked After retrying the generation, you should see the cloud stack preview render successfully within the project view — the error banner will disappear and your uploaded image(s) will display in the posting queue or overview area. Navigate to Left sidebar → Local → Overview and confirm the post or image appears under the relevant tab. If the preview loads without any error message and the image is visible in the project, the cloud stack was generated successfully. 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.

Last updated on Oct 26, 2026

📍 Fix 'No Address Found' in GBP Projects

🔍 What This Article Covers If your Google Business Profile (GBP) address appears correctly in Local SEO Heatmaps but shows No address found inside GBP Projects, your project is working from a stale data snapshot. This is not a connection problem — it means GBP Projects needs to pull a fresh copy of your profile data. The fix is a manual data refresh from within the project. ⚠️ Why This Happens Search Atlas stores a local snapshot of your GBP data when a project is first created or last synced. If your address was added, edited, or verified in Google after that snapshot was taken, GBP Projects will not reflect the change automatically. Local SEO Heatmaps pulls data independently, which is why your address can appear there but remain missing in GBP Projects. ✅ How to Fix It: Refresh Your GBP Data 1. Log in to Search Atlas and navigate to Local → GBP Projects from the left sidebar. 2. Open the project that is showing No address found. 3. Locate the option to trigger a manual data refresh or sync with your connected Google Business Profile. 4. Initiate the refresh to pull the latest data from your Google Business Profile. 5. Wait a few moments for the refresh to complete, then check whether your address now appears correctly. In most cases, this single action resolves the No address found message immediately by replacing the outdated snapshot with your current GBP information. 🔗 Before You Refresh: Confirm Your GBP Is Connected The data refresh will only work if your Google Business Profile is properly linked to your Search Atlas account. Before running the refresh, quickly confirm the following: - Your Google account is connected under your Search Atlas workspace settings. - The correct GBP location is associated with this project — especially important if you manage multiple locations or accounts. - Your GBP listing is active and not suspended inside Google Business Profile Manager. If any of these conditions are not met, resolve the connection issue first, then run the refresh. 🗺️ Address Shows in Heatmaps but Not in GBP Projects This specific mismatch — address visible in Local SEO Heatmaps but missing in GBP Projects — is a reliable indicator that the issue is a stale data snapshot, not a connection or permissions problem. You do not need to reconnect your account or recreate the project. Triggering a manual data refresh is the correct and only step required to resolve this discrepancy. 🔄 Still Showing 'No Address Found' After Refreshing? If the address remains missing after refreshing your GBP data, consider the following: - Wa

Last updated on Oct 26, 2026

📍 Fix Incorrect GBP Heatmap Pins

📌 What a heatmap pin represents A heatmap pin shows the location used as the starting point for a local search scan. It is separate from your keyword rankings and does not change your Google Business Profile (GBP) address. If a pin moves to the wrong location, the scan may be using an incorrect map center or saved latitude and longitude. Refreshing the page may not restore the original pin because the scan location is stored with the project or scan data. 🔎 Check your GBP project 1. Open Local from the left sidebar. 2. Go to Overview and select the affected GBP project or location. 3. Confirm that the business name and address match the correct GBP listing. 4. Review the map position and verify that the marker is placed at the intended business location. 🗺️ Check the affected heatmap 1. Open the heatmap containing the affected keywords. 2. Compare the pin with the business address shown in your GBP project. 3. Check whether only older scans are incorrect or whether new scans also use the wrong location. 4. Refresh the page once after confirming the project details. Avoid repeatedly refreshing while the location data is being updated. 🔄 Why refreshing may not fix the pin A refresh reloads the saved scan data; it does not recalculate the scan origin. If the wrong coordinates were stored when the scan ran, the existing keyword pins may continue to display at that position. New scans should use the corrected project location after the GBP address and map data are synchronized. Historical scans may continue to show their original pin because they preserve the location used at the time of scanning. ✅ Recommended next steps - Confirm the GBP address and map marker are correct. - Check that the affected keywords belong to the correct GBP project. - Run a new scan after the location is corrected and compare its pin with the business location. - If the new scan still places the pin incorrectly, record the project name, affected keywords, scan date, and incorrect location. 💬 Get help with a persistent issue If new scans continue to use the wrong location after you verify the GBP project, the issue may require a data correction. 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.

Last updated on Oct 26, 2026

📍 Fix Missing Local Heatmap Pins

📌 Why pins may be missing Missing pins are usually a display issue rather than a change to your local SEO data. Common causes include an incorrect map zoom level, older scan dates that do not display the center point correctly, or a temporary issue while heatmap results are loading. In some cases, the heatmap may show blank spaces in the platform or in a generated report even though ranking data is available. A pin can also appear differently between the heatmap list, scan details, and Google results when data has refreshed at different times. 🔍 Check the heatmap view 1. In the left sidebar, go to Local → Local SEO Heatmaps. 2. Open the affected heatmap. 3. Check whether the map is zoomed too far in or out. Adjust the zoom level so the full grid and its location pins are visible. 4. Review the scan date and compare it with the date shown in the heatmap list or scan details. 5. Refresh the page and reopen the heatmap. 📅 Check older scans and reports Older scans may not show the center point or pins correctly in every view. If the pins are missing only for an older date, compare that scan with a newer scan before drawing conclusions about ranking performance. If pins are missing in a report but visible in the heatmap, the issue may be limited to report display. Reopen the heatmap, confirm the correct scan is selected, and generate the report again if needed. 🛠️ Try a new scan 1. Confirm that the heatmap uses the correct business location and search term. 2. Run a new scan from the Local SEO Heatmaps area. 3. Wait for the scan to finish, then check the new result at several zoom levels. 4. Compare the new scan with the affected scan to determine whether the problem is limited to one date. Do not assume that missing pins mean rankings are missing. Check the scan status and ranking values separately from the map markers. ✅ When to request help Contact support if pins remain missing across multiple heatmaps or clients, appear only at certain zoom levels, or are missing in both the platform and generated reports. Include the affected heatmap names, scan dates, location, search term, and a screenshot showing the missing pins. 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.

Last updated on Oct 26, 2026

📍 Local Citation Stuck in Submitted Status

📋 What “Submitted” means A citation marked Submitted has been sent to the directory or network for processing. Some publishers take time to review, publish, or sync listings, so the status may not change immediately. In some cases, a citation can remain displayed as Submitted even after the underlying submission is complete. This is especially possible with aggregator networks and their connected directories. 🔎 Check your citation campaign 1. Open Local from the left sidebar. 2. Select GBP Projects. 3. Open the relevant project and review the local citation campaign. 4. Check whether individual directories show a current status, completion date, or live listing link. Review the business name, address, phone number, and website URL for accuracy. Incorrect or incomplete business information can delay directory processing. ⏳ When a citation stays submitted If a citation has remained Submitted for several weeks, especially for more than two months, do not create duplicate campaigns. Duplicate submissions can create conflicting listings and make tracking more difficult. Some completed citation rows may continue to show Submitted because the directory does not return a final status or the platform has not received a status update. A Submitted label does not always mean that the citation failed. 💳 Credit refunds and reviews Credits are reviewed based on the citation’s actual processing result, the directory’s response, and whether the submission was completed by the provider. A refund is not automatic solely because the display remains Submitted. When a citation appears stuck, our team can review the campaign, confirm whether the submission completed, and determine whether a credit adjustment is appropriate. Keep the project name, business name, affected directories, and approximate submission date available for review. 🛠️ Get help with a stuck citation If the status has not changed after an extended period or you believe the citation was not processed, contact support from inside Search Atlas. Include the affected business, campaign, directory names, and a screenshot or export of the Submitted rows. 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.

Last updated on Oct 26, 2026

📍 Fix Local Citation Updates and Billing

📋 Understand citation updates Local citation changes may take time to process across third-party directories. Search Atlas can submit and track the campaign, but each directory controls when an update becomes visible. A campaign that remains unchanged after the expected processing period should be reviewed by our team. 🔎 Check your campaign 1. Open Local → GBP Projects from the left sidebar. 2. Find the relevant project and select View project. 3. Review the citation campaign status, submitted business details, and any available directory results. 4. Confirm that the business name, address, phone number, and website match your approved Google Business Profile information. For example, include the campaign ID when reviewing a delayed campaign, such as campaign id-8275 for Pedder Hyundai of Moreno Valley. 💳 Understand billing corrections Local citations are billed per aggregator. The current price is 40 credits per aggregator. Older citation records may show the amount originally paid, even when the current price has changed. This does not mean that an old campaign was charged again. If the credits shown do not match the campaign’s purchase details, record the campaign ID, affected business, number of aggregators, and the credits displayed. This information helps the team compare the original transaction with the current campaign record. 🛠️ Prepare a support request - Business name and location - Campaign ID - Date the citation campaign was submitted - Directories that still show incorrect information - Expected details and the details currently displayed - Credits charged and credits you expected to be charged - Screenshots of the campaign or directory listing, if available Do not create a duplicate campaign while an existing submission is being reviewed. Duplicate submissions can make billing and directory status harder to reconcile. 💬 Get a status review If a citation has not updated after 15 days, or if the billing amount appears incorrect, share the details above through the platform chat so the team can review the campaign and billing record together. 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.

Last updated on Oct 26, 2026

📍 Fix Missing Local SEO Heatmap Pins

📍 Why pins may be missing Missing pins on a Local SEO Heatmap can result from the map zoom level, an incomplete or outdated scan, delayed ranking data, or a temporary display issue. This can affect multiple clients without any settings being changed. 🔎 Check the heatmap view 1. Open Local from the left sidebar. 2. Select Local SEO Heatmaps. 3. Open the affected client and scan. 4. Zoom out slightly to display the full grid. Pins may not appear when the map is zoomed in too far. 5. Refresh the page and check whether the center point and surrounding pins load. 🗓️ Verify the scan and date Confirm that you are viewing the intended scan date. Older scans may show incomplete center-point or pin data, and the date shown in scan details may not always match the date shown in the scan list during a display issue. < - Compare the scan date in the list with the date in its details. - Check whether the scan has finished processing. - Review the rank shown for each pin instead of relying only on the summary count. 🔄 Run a fresh scan If pins are still missing, create or run a new scan using the same location, keyword, and grid settings. Allow the scan to finish, then reopen Local → Local SEO Heatmaps and refresh the page. A new scan can replace incomplete or stale map data. 👥 Check other client projects If pins are missing across several clients, this is more likely to be a platform-wide display or processing issue than a project configuration problem. Avoid changing locations, keywords, or grid settings until you have recorded the affected scans. 📝 What to include when reporting If the issue continues, record the client or project name, scan date, keyword, search location, grid settings, browser, and whether the issue affects one client or multiple clients. Include screenshots showing the map, scan list, and scan details if 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.

Last updated on Oct 26, 2026

📊 Fix Google Business Profile Names in Shared Reports

🔍 Overview When you share a Search Atlas report via a public link, Google Business Profile (GBP) locations may appear as generic placeholders — such as Google Business Profile 1 — instead of your actual brand names and addresses. This also affects how tracked keywords display in the Local Pack tab of shared reports. This article explains why this happens and what to have ready when contacting support so the issue can be resolved as quickly as possible. 🧩 Why This Happens Shared report links are accessible without requiring the viewer to log in to Search Atlas. In some cases, the system that fetches GBP location details — including business names and addresses — does not correctly serve that data to unauthenticated (logged-out) viewers. As a result, the report falls back to placeholder text instead of your real location data. 🛠️ Steps to Take If You See Placeholder Names If you are seeing Google Business Profile 1 or similar placeholder text in a shared report, this is a backend issue that requires investigation by our support team. To help us resolve it quickly, please have the following ready when you reach out: - The exact shared report link that is displaying placeholder names. - The name of the GBP project or projects affected. - A screenshot showing the placeholder text as it appears in the shared report. - The approximate date and time when you first noticed the issue. 📍 What to Expect Once our team investigates your specific shared report link and GBP project configuration, we will confirm the root cause and apply the appropriate fix on the backend. You do not need to delete or recreate your report — our team will advise on any steps needed on your end after reviewing 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.

Last updated on Oct 26, 2026

🔗 Fix GBP Authorization Link Errors

🔗 What the error means The “malformed request” message usually means the Google authorization URL is expired, incomplete, altered, or being reused in an unsupported session. Do not retry the same link. 🛠️ Generate a fresh connection link 1. Return to the Search Atlas GBP connection flow. 2. Start a new authorization request and copy the newly generated Google URL exactly as provided. 3. Do not edit, shorten, bookmark, reuse, or share the URL as a permanent connection link. It is temporary and intended for the current authorization attempt. 🌐 Use a compatible browser session 1. Open the fresh URL in a current version of Chrome, Edge, Safari, or Firefox. 2. Use a private or clean browser window if another Google account is already signed in. 3. Sign in with the Google account that has permission to manage the client’s Business Profile. 4. Complete the authorization without switching browsers, devices, or Google accounts. ✅ Complete the connection After Google approval, return to the Search Atlas tab and wait for the connection status to update. If the client manages several profiles, select the correct Business Profile or location when prompted. 🚫 If the error appears again - Close the failed Google tab and discard the old URL. - Generate another link from the Search Atlas connection flow. - Paste the complete URL without extra spaces or quotation marks. - Disable extensions that may block redirects, or try a clean private window. - Confirm that the Google account has the required Business Profile access. Never ask a client to keep or reuse a pasted Google OAuth URL. Generate a new link for each connection attempt and share it only through the intended authorization process. 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.

Last updated on Oct 26, 2026

📍 Local Citation Campaign Stuck on Submitted Status

🔍 Overview Local citation campaigns in Search Atlas sometimes appear stuck under Local → Local Citations (Local Citations) with a status of Incomplete or Warning instead of Complete for an extended period. This is a known issue that our internal team can investigate and resolve on the backend. There is currently no self-serve option to force a status update from within the platform. ⚠️ Why This Happens A citation campaign may remain in an Incomplete or Warning state without progressing to Complete due to a backend processing issue. The exact root cause can vary by campaign and requires investigation by our support team. ✅ Steps to Take Before Contacting Support 1. Locate the affected citation campaign in the platform and note its current status. 2. Record your campaign name or ID — you will need this when contacting support. 3. Note approximately when the campaign was submitted, so our team can assess how long it has been stuck. 🛠️ What Our Team Does to Fix It When our support team investigates a stuck citation campaign, we will look into the backend status of your submission and take the appropriate action to resolve it. These actions can only be performed by our internal team. 📋 Information to Have Ready To help our team resolve your issue as quickly as possible, please have the following on hand when you reach out: - Your campaign name or ID - The approximate date the campaign was submitted - A screenshot of the current stuck status, if 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.

Last updated on Oct 26, 2026

📅 Fix GBP Scheduled Posts Failing Across Locations

🔍 Overview If your Google Business Profile (GBP) posts are stuck in Scheduled status and never publish — especially across multiple store or franchise locations — this article explains what to do when this happens and how to get it resolved. ⚠️ Common Symptoms - Posts remain in Scheduled status past their intended publish date and time. - Multiple location posts fail at the same time with no error message. - Posts appear stuck with no confirmation that they went live on Google. 🧠 Why This Happens Scheduled GBP posts failing to publish across multiple locations is a known issue that can affect franchise or multi-location accounts. The exact root cause may vary and typically requires investigation by the Search Atlas support team to diagnose and resolve. ✅ What To Do 1. Check directly in Google Business Profile. Log in to your Google Business Profile dashboard and verify whether the posts actually published on Google's side. If they did, the issue may only be a display lag inside Search Atlas — no further action is needed. 2. Gather key details before escalating. To help the support team investigate quickly, have the following ready: the names of the affected locations, the exact scheduled date and time of the failing posts, and any error messages you see (if applicable). 3. Contact support. If posts are confirmed stuck and not published on Google's side, reach out to the Search Atlas support team with the details above so the issue can be investigated and resolved on the backend. 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.

Last updated on Oct 26, 2026

🛠️ GBP Re-Verification After Services Playbook Changes

🔍 What Happened? You deployed the services playbook to add service descriptions, and now your Google Business Profile (GBP) says it needs verification. This is more common than most people expect, and it does not mean something is broken in your Search Atlas account. Google decides when a profile must be re-verified. Search Atlas sends your approved changes to Google, and Google's automated systems review every update. When they see edits they consider sensitive, they may temporarily suspend the profile or ask the owner to prove they still control the business. Your profile data has not been deleted. The profile is usually just waiting for you to confirm ownership. 🤔 Why Would Service Changes Trigger Verification? Google does not publish exact rules, and they change over time. These are the most common reasons a profile is flagged: - Many edits at once: Adding several services and descriptions in one update can look like a big change to the profile. - Changes to core details: Edits to the business name, address, service area, categories, or hours are watched more closely than minor text edits. - Category and service mismatches: Services that do not fit the profile's main category can raise a flag. - Description content: Text that looks promotional, includes links, phone numbers, or special characters, or repeats keywords may be reviewed more strictly. - Existing profile risk: Profiles that are new, recently edited, or previously flagged are more likely to be asked to verify again. Sometimes the verification request would have appeared anyway, and the timing just lined up with your deploy. Search Atlas cannot see or control Google's internal decision. ✅ How to Re-Verify Your Profile 1. Open Google Search or Google Maps while signed in to the Google account that manages the profile. 2. Search for your business name, or search my business, to open your profile management view. 3. Look for a button or banner such as Get verified or Verify now. 4. Select the verification method Google offers. Options vary by business and may include a video recording, a phone call, a text message, an email, or a postcard. 5. Follow the on-screen instructions and submit the request. 6. Wait for Google's confirmation. Timing depends on the method. Instant methods may finish in minutes, while postcards and manual reviews can take several days. Use the Google account that owns or manages the profile. If you are not sure which one that is, check inside the Search Atlas platform to see which account was connected to your GBP. 🎥 Tips for Video Verification If Google asks for a video, it is checking that you really operate the business. A few tips can help you pass the first time: - Show clear outdoor signage, your storefront, and the street or surroundings if you have a physical location. - Show your work tools, vehicles, or equipment if you are a service-area business. - Show proof that you manage the business, such as an office, a work area, or business documents. - Record in one continuous take without cuts or edits. - Make sure the business name and address in the video match what is listed on your profile. ⏸️ What to Do While Verification Is Pending - Pause further edits. Extra changes can reset or slow down Google's review. - Do not create a new profile. A duplicate listing can cause bigger problems and make recovery harder. - Do not re-run the playbook yet. Wait until your profile is verified and showing normally. - Keep your business details consistent. Your name, address, and phone should match your website and other listings. While the profile is unverified, some information may be hidden from Google Search and Maps, and you may not be able to manage reviews or posts until verification finishes. 🛡️ How to Avoid This in the Future - Deploy in smaller batches. Add a few services at a time instead of everything at once. - Avoid changing core details at the same time. Do not edit your name, address, or categories on the same day you deploy service changes. - Keep descriptions natural. Write clear, factual descriptions of the service. Avoid keyword stuffing, links, phone numbers, and promotional claims. - Match services to your category. Only add services that truly belong to your primary business category. - Check your profile first. Before deploying, confirm that your profile is verified and has no warnings or pending edits in Google. - Review changes before approving. Make sure every service and description is accurate for your business. ❓ Frequently Asked Questions Did Search Atlas break my profile? No. The playbook sends your approved updates to Google, but Google controls verification and suspensions. Will my service descriptions be lost? In most cases they are not lost. They may stay hidden or pending until the profile is verified. Check your profile after verification to confirm they appear. Can Search Atlas verify the profile for me? No. Verification must be completed by the business owner or an authorized manager directly with Google. How long will it take? It depends on the method. Instant methods can finish within minutes, while manual reviews or postcards can take several days. What if my verification is rejected? Review Google's feedback, make sure your business details are accurate, and try the verification method again. Do not make extra edits until you have a result. 💬 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 instantly connected with a member of our team. Tell us which business profile is affected, when you deployed the playbook, and what message Google is showing, so we can help you faster.

Last updated on Oct 26, 2026

🔍 Team Members: Buying Citations with Hyperdrive Credits

📌 Overview Local citations are online listings of your business name, address, and phone number on directories and other websites. They help search engines trust your business details. In Search Atlas, you pay for citations with Hyperdrive credits. This article explains how Team Members can buy citations and what to check if the credit balance on screen is not what you expected. 👥 How Credits Work for Team Members Hyperdrive credits belong to the main account, not to individual users. Team Members spend from the same shared pool as the account owner. Keep these points in mind: - Your credit balance reflects what is available to the account you are currently working in. - The balance goes down whenever anyone on the team uses credits, including the owner and other Team Members. - What you can do depends on the role and permissions the account owner gave you. 🛒 How to Buy Local Citations 1. Log in to Search Atlas and make sure you are in the correct account or workspace. 2. Open the project for the business you are building citations for. 3. Go to the local citations area of the platform. 4. Check that the business name, address, and phone number are correct. Citations work best when these details match your other listings exactly. 5. Choose the citations or package you want to purchase. 6. Review the credit cost shown before you confirm. 7. Confirm the purchase and wait for the order to be processed. Once the order is placed, the credits are deducted and the citations are queued for submission. Submissions can take some time to appear live on each directory. 💳 If Your Credit Balance Looks Wrong Sometimes the balance on the screen differs from what you expected. For example, you may believe you should have 115,050 credits but see a different number, or a message that you cannot complete the purchase. Work through these checks first: - Check the account. If you belong to more than one account or workspace, each has its own credit balance. Confirm you are in the account that holds the credits. - Refresh the page. Log out and back in, or do a hard refresh, to clear an out-of-date display. - Check the cost of your order. Large citation orders can use many credits. Compare the cost shown at checkout with your available balance. - Look for recent usage. Other team members may have used credits on citations or other Hyperdrive features. - Check your permissions. If a purchase is blocked, your role may not allow spending credits. Ask the account owner to review your access. - Confirm the plan status. If a plan was recently renewed, changed, or paused, the balance may take a short time to update. 🧾 What to Share If You Need Help If the checks above do not solve the problem, gather these details so our team can look into it quickly: - The balance you see on screen and the balance you expected. - The account or workspace name and the project you were working in. - Your role on the account (for example, Team Member). - A screenshot of the message or balance shown. - The citations or package you tried to buy and the approximate time you tried. 💡 Tips to Avoid Problems - Ask the account owner to confirm your role before you start a large citation order. - Agree with your team on who purchases citations so credits are not spent twice on the same listings. - Check the cost before you confirm any purchase. - Keep your business details consistent across every listing. 🙋 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 instantly connected with a member of our team.

Last updated on Oct 26, 2026

📝 Fix Paragraph Spacing in Automated Blog-to-GBP Posts

🔍 Overview When Search Atlas automatically publishes blog content to your Google Business Profile (GBP), you may notice that paragraph breaks disappear — leaving all your text merged into one unbroken block. This is a known formatting issue that affects readability on your GBP listing. ⚙️ Why This Happens When a blog post is converted and published automatically to GBP, paragraph spacing that looks correct during content generation can collapse at the point of publishing. The result is that sentences and paragraphs are run together into a single continuous block of text, with no visible spacing between them. Our engineering team is actively tracking this issue (CG-1301) and working on a permanent fix. In the meantime, you can use the workaround below to ensure your GBP posts display with proper spacing. 🛠️ Workaround: Manually Edit the Post Before Publishing You can review and adjust automated GBP posts before they go live, or edit them immediately after publishing. Follow these steps: 1. In the left sidebar, click Local, then select Posts. 2. Locate the automated post generated from your blog content. 3. Open the post to enter the editor. 4. Review the text and identify where paragraph breaks are missing. 5. Place your cursor at the end of each paragraph and add a blank line to restore spacing. 6. Save and republish the post to apply your changes. 💡 Tips for Better Readability - Keep paragraphs short. Aim for 2–4 sentences per paragraph so your GBP post is easy to scan. - Review before publishing. If your workflow allows, check every automated post in the Posts section before it goes live. - Use clear sentence breaks. Strong punctuation and varied sentence length help readability even when spacing is limited. 📊 Current Status This formatting issue is a confirmed bug being addressed by the Search Atlas engineering team. Once the fix is deployed, paragraph spacing in automated blog-to-GBP posts will be preserved correctly from generation through to publishing — no manual editing required. 🙋 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 instantly connected with a member of our team.

Last updated on Oct 26, 2026

📍 Fix Missing Business Names in Heatmaps

📌 Why the business name may be missing Local SEO Heatmaps display the business name stored for the selected project. In some cases, Google Places returns an address or location name instead of a registered business name. When this happens, the address or location name may appear in the box above the keyword field, or the business name may not appear as expected. This is linked to the Google result selected for the project, rather than a problem with the heatmap list display. Address-only locations are also prevented from being added as new heatmaps. 🔎 Check the selected heatmap project 1. Open Local from the left sidebar. 2. Select Local SEO Heatmaps. 3. Open the affected project. 4. Review the business details and the Google result selected for the project. Confirm that the selected result represents the correct registered business and that its Google listing uses the expected business name. If the result is an address, landmark, or other location without a business name, the heatmap may continue to display that information. 🛠️ What to do next - Check that the correct Google Business Profile was selected when the heatmap was created. - Use a Google result that clearly shows the registered business name and location. - Refresh the heatmap after confirming the project details. - If the name has been missing for several days, review whether the selected Google result is an address-only location rather than a business listing. 💬 Need more help? If the correct business listing is selected but the name is still missing, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.

Last updated on Oct 26, 2026

🔍 Local Citations Quota Error: Insufficient Hyperdrive Credits

📌 Overview When you set up Local Citations, you may see a message saying you have reached your quota limit, even though you have not hit any plan limit that you can see. In many cases, this happens because your account does not have enough Hyperdrive credits to complete the Local Citations order or setup. This article explains why it happens, how to check your balance, and what to do next. ❓ Why You See a Quota Limit Message Local Citations submissions use Hyperdrive credits. If your available credits are lower than what the action requires, the platform may block the setup and display a general quota error instead of a specific credit message. This means: - The error does not always mean you have used up a plan-level limit, such as the number of projects or locations. - It can mean your Hyperdrive credit balance is too low to start the setup. - It can appear even if other tools in your account are working normally. 🧭 How to Confirm Your Hyperdrive Credit Balance 1. Log in to your Search Atlas account. 2. Open your account or billing area and look for your plan and usage details. 3. Find your Hyperdrive credits balance and compare it with the credits needed for the Local Citations action you are trying to run. 4. Check whether your credits have been used by other Hyperdrive-powered actions in the same billing period. If your remaining balance is zero or very low, that is the likely cause of the error. 🛠️ How to Resolve the Error 1. Add more Hyperdrive credits. If your plan allows it, purchase additional credits or upgrade to a plan with a larger credit allowance. 2. Wait for your credits to renew. If your credits refresh each billing cycle, you can retry the Local Citations setup after the renewal date. 3. Review recent credit usage. If your balance is lower than expected, check which actions used credits recently so you can plan future usage. 4. Retry the setup. After your balance is updated, return to Local Citations and start the setup again. Refresh the page first if the error is still displayed. ✅ Tips to Avoid This Error - Check your Hyperdrive credit balance before starting a new Local Citations setup. - Plan credit usage across projects or client accounts, especially if you manage several locations. - Keep your billing details up to date so renewals and purchases are not interrupted. 🔄 If the Error Continues If you have enough Hyperdrive credits and still see the quota message, try these steps: - Log out and back in, then retry the setup. - Make sure you are working in the correct account and project. - Take note of the exact error text and the project or location you were setting up, so our team can investigate faster. 💬 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 instantly connected with a member of our team.

Last updated on Oct 26, 2026