## **🔍 Overview**

If you see two entries for the same business name — for example, two listings for **Michelle** or **Marcella** — inside the Google Business Profile (GBP) section of Search Atlas Rank Tracker, this is almost always caused by one of three Search Atlas-specific issues: a duplicate profile created during heatmap setup, a report data source mismatch, or a caching and sync delay. This article walks you through each cause and how to resolve it.

## **🗺️ Cause 1: Duplicate Profiles Created During Heatmap Setup**

The most common reason for duplicate GBP entries is re-adding a business when configuring a heatmap instead of selecting the existing saved profile. When you set up a new heatmap grid in Rank Tracker, the platform prompts you to connect a GBP location. If the business was added from scratch at that point — rather than chosen from your already-saved locations — Search Atlas creates a second, separate profile entry for the same business.

Each entry then generates its own data trail, so both appear in your location list and can be attached to different reports or projects independently.

**How to check for this:**

1. Go to **Left sidebar → Keywords → Rank Tracker**.
2. Open the project that contains the duplicate business names.
3. Navigate to the **GBP / Local** or **Heatmap** section of that project.
4. Compare the two entries: look at the address, place ID, and the date each was added. If both share the same address but have different creation dates or slightly different name formatting, a duplicate was created during heatmap setup.

**How to fix it:**

1. Identify the newer duplicate entry (typically the one added most recently).
2. Remove it from the heatmap or project configuration.
3. Re-attach the heatmap to the original, pre-existing GBP profile by selecting it from your saved locations list rather than adding it anew.
4. Save the project. Future heatmap data will now consolidate under the single correct profile.

## **📊 Cause 2: Report Data Source Mismatch**

A duplicate can also appear to exist when the same physical GBP profile is pulled as a data source in two different company or project contexts inside Search Atlas. This means the profile itself is not truly duplicated in Google — it is the same listing — but because it has been connected to more than one Search Atlas project or client workspace, it surfaces in reports under different company names.

This is common in agency accounts where the same location (for example, a practitioner with multiple client records) has been linked to more than one project during onboarding.

**How to check for this:**

1. In **Left sidebar → Keywords → Rank Tracker**, open each project that shows the duplicate name.
2. Check the **data source** assigned to the GBP entry in each project — look at the connected Google account, the place ID, or the business URL.
3. If the place ID or business URL is identical across both projects, you are looking at a data source mismatch rather than a true duplicate profile.

**How to fix it:**

1. Decide which project should be the canonical home for that GBP location.
2. In the secondary project, disconnect or remove the GBP data source.
3. If rank tracking is still needed for that business in the second project, create a keyword-only tracking setup without re-linking the GBP location, or consolidate both projects into one.
4. Update any scheduled reports to pull from the single, correct data source so the business name no longer appears under two company contexts.

## **⏳ Cause 3: Caching and Sync Delays**

Occasionally, a GBP entry that was recently deleted or renamed inside Search Atlas continues to appear in the Rank Tracker list or in exported reports due to a caching delay. This can make it look like a duplicate is still present even after you have taken corrective action.

**How to check for this:**

- Confirm the deletion or rename was saved successfully inside the project settings.
- Check whether the ghost entry still appears after a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac).
- Wait up to 24 hours after making changes, as GBP sync cycles can take time to propagate across all report views.

**How to fix it:**

1. Force a manual data refresh on the affected project if the option is available in your Rank Tracker project settings.
2. Clear your browser cache and log back into Search Atlas.
3. If the entry still appears after 24 hours, escalate to support (see below) and include the project name, the business names showing as duplicates, and a screenshot.

## **🛠️ Systematic Troubleshooting Checklist**

Before escalating, work through these steps in order:

1. **Confirm it is a Search Atlas issue, not a Google issue.** Log in to Google Business Profile directly at business.google.com and verify how many listings exist there for the business name in question. If there is only one listing in Google, the duplication is entirely within Search Atlas.
2. **Check creation dates.** In Rank Tracker, view the details of both entries. Different creation dates with the same address point to Cause 1 (heatmap re-add).
3. **Check place IDs or business URLs.** Matching place IDs across two projects point to Cause 2 (data source mismatch).
4. **Check if entries disappear after a refresh.** If a refresh resolves it, the issue was a cache delay (Cause 3).
5. **Review report data sources.** Open each affected report, confirm which GBP profile it is pulling from, and update mismatched sources.
6. **Document before making changes.** Take a screenshot of both entries including their addresses, project names, and any visible IDs before editing or deleting anything. This helps if escalation is needed.

## **🚫 What This Issue Is Not**

This is not the same as a standard Google Business Profile duplication problem (such as two separate listings on Google Maps for the same address). You do not need to request a GBP merge through Google Search Console or Google support to resolve this. The fix lives entirely inside your Search Atlas account configuration.

## **💬 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.