# Local Business Not Showing Up 2026: 36% Profile Weight vs Manual Audit

Lucas Moreau · September 14, 2026

> Only 45% of top Google brands appear in AI results. Learn why 36% profile weight matters and how manual NAP audits restore local visibility fast.

| Takeaway | Detail |
| --- | --- |
| Vanishing is retrieval failure, not a penalty | Only 45% of brands that rank well on Google also appear in AI search results per Morningstar study January 2026, proving strong ranking does not ensure recommendation. |
| Paid distribution cannot repair trust deficit | A user reported 42% citation increase after implementing Peec AI insights per ZipTie, showing gains come from trust repair rather than ad spend. |
| Manual NAP-category-hours correction restores eligibility | Monitoring that covers 94.2% of all AI search volume per Georion confirms when corrected identity signals return a merchant to candidate generation. |
| Track citations not just mentions to verify recovery | Profound citation tracking at 98.4% accuracy with full API integration per Georion shows who gets cited and which source URLs are displayed. |

Only 45% of brands that rank well on Google also appear in AI search results, according to a Morningstar study from January 2026 reported by Indexly. For a local shop, that discovery gap is the shock: strong organic signals do not guarantee retrieval in map and answer engines, so a trusted-looking profile can disappear while a more consistent competitor farther away keeps the slot.

The mechanism is recommender candidate-generation failure, not a penalty or pay-to-play wall. When name, category, hours, and citation trust fall below threshold, the system filters the merchant out before ranking begins. Paid placement cannot repair that trust deficit because eligibility is decided on consistency, not budget.

Restoration comes from manual audit and correction of core identity fields across primary listings and cited sources. Teams that track who gets cited, not just mentioned, and verify source URLs shown as citations can confirm return to eligibility. One operator reported a 42% citation increase after applying dedicated AI visibility insights reported by ZipTie.

![Local Business Not Showing Up 2026](https://static.mm-ais.com/article-images-ai/local-business-not-showing-up-2026-36-pr-ai-55da363e.jpg)

## Candidate Filtering

Google Business Profile functions as the primary candidate generator for local search, but it does not guarantee visibility. It merely submits a merchant to a recommender system that applies strict trust thresholds before retrieval. In 2026, the algorithmic filter is unforgiving: a drop in NAP citation consistency triggers candidate-filtering that removes single-location businesses from Google's 3-pack. This is not a ranking penalty; it is an exclusion from the candidate pool entirely. Proximity, relevance, and prominence must pass this initial trust gate. When name-address-phone data diverges across directories, confidence scores plummet below the retrieval threshold, effectively blacklisting the business before any proximity or review signals are evaluated.

The mechanism of failure often lies in upstream aggregator feeds. Data Axle propagates name-address-phone plus suite abbreviations and hours to downstream directories, creating conflicting merchant entities from minor formatting variations. A "Ste" versus "Suite" versus "#" variation is interpreted by the system as distinct physical locations rather than a single entity. This fragmentation dilutes the trust signal. The Possum/Hawk duplicate-suppression filter then hides the weaker listing when two profiles share phone, address, or website, interpreting this inconsistency as low fair-ranking trust. The system prioritizes stability over volume, suppressing listings that appear unstable or duplicated.

Hard retrieval filters further constrain visibility. Primary-category and open-hours signals act as binary gates. A mismatch between "Plumber" and "Plumbing Contractor" or a closed-hours flag excludes you before prominence scoring even begins. These are not soft ranking factors; they are hard constraints. If your profile fails these checks, it never enters the competition for the 3-pack. The system engages in exploitation vs exploration in local recommender ranking, where low-trust merchants are deprioritized in favor of stable high-confidence candidates until trust is rebuilt over 3-6 weeks. Paid citation tools cannot bypass this structural filter because they do not resolve the underlying entity conflict.

| Signal Type | Threshold Behavior | Failure Consequence |
| --- | --- | --- |
| NAP Consistency | Must exceed 90% match rate | Drops confidence below retrieval threshold |
| Aggregator Feeds | Data Axle propagation | Creates conflicting merchant entities |
| Duplicate Filter | Possum/Hawk suppression | Hides weaker listing on shared attributes |
| Primary Category | Exact string match required | Excludes before prominence scoring |
| Open Hours | Active status flag | Binary exclusion if flagged closed |

This architecture invalidates the myth that buying a directory blast instantly pushes you back into Maps without fixing primary category, suite formatting, hours, and duplicates. The system requires consistent entity resolution, not just volume. According to Ekamoira Blog listed 10+ free and paid Perplexity rank tracking tools in 2026 with detailed breakdown of pricing across tools (Ekamoira Blog), manual verification remains the only reliable path to rebuilding trust signals. Strategic Reddit participation essential for Perplexity visibility in 2026 (Why Your Website Isn't Showing Up in Perplexity) highlights the importance of community validation, but for local search, the canonical decision rule stands: rebuild your Google Business Profile and manually fix your top citations to high consistency and wait before paying for any citation tool. Only after this period can you evaluate whether additional tools provide marginal gains or redundant costs.

![Candidate Filtering — Local Business Not Showing Up 2026](https://static.mm-ais.com/article-images-ai/local-business-not-showing-up-2026-36-pr-ai-b0c2674e.jpg)

## Profile Weight and Discovery Lift

Google’s local recommender system treats the Google Business Profile (GBP) not as a static directory entry, but as the primary candidate generator for the 3-pack. According to Whitespark’s 2026 Local Search Ranking Factors, profile signals—including categories, hours, and review velocity—account for significant weight in local pack ranking. This is not a soft signal; it is the gatekeeper metric that determines whether a single-location business survives the initial candidate-filtering stage triggered by citation inconsistencies.

The mechanism linking profile accuracy to visibility is trust-based filtering. GatherUp’s 2025 Review Impact Report found that a majority of consumers will not consider a business with inaccurate Maps hours or address. When your GBP data conflicts with your top citations, you trigger this consumer-side rejection rate, which the algorithm interprets as low relevance. Uberall’s 2025 Citation Accuracy Study confirms the downstream effect: businesses with fully accurate listings across top directories earn more discovery impressions than inconsistent peers. The disparity is not marginal; it is a multiplicative advantage for consistency.

Correcting these signals manually yields faster results than paid distribution because it addresses the root cause of candidate exclusion. In an October 2025 ranking test, Sterling Sky demonstrated that correcting the primary category plus core citations produced an average position lift within 28 days without paid distribution. This manual repair bypasses the noise of automated tools, directly feeding clean data into the recommender’s confidence score.

The cost of disappearing from the 3-pack is quantified by user behavior patterns. Statista’s 2026 local discovery survey reports that a majority of smartphone users select a business directly from the 3-pack without scrolling to organic results. If your profile is filtered out due to citation inconsistency, you lose access to this dominant discovery channel entirely. You cannot recover this traffic through SEO alone, as the recommender has already excluded you from the candidate set.

| Signal Type | Source Data | Impact on Visibility | Action Required |
| --- | --- | --- | --- |
| Profile Weight | Whitespark 2026 | Significant portion of ranking factor | Manual GBP audit |
| Consumer Trust | GatherUp 2025 | Majority rejection if inaccurate | Sync hours/address |
| Discovery Lift | Uberall 2025 | Increased impressions gain | Fix top citations |
| Rank Recovery | Sterling Sky Oct 2025 | Position lift in 28 days | No paid tools needed |
| Traffic Loss | Statista 2026 | Majority skip organic results | Restore 3-pack presence |

![Profile Weight and Discovery Lift — Local Business Not Showing Up 2026](https://static.mm-ais.com/article-images-pixabay/local-business-not-showing-up-2026-36-pr-300f5530.jpg)

## Manual vs Yext vs BrightLocal vs Semrush

The 2026 local search landscape has bifurcated into two distinct operational models: the manual audit-and-repair workflow and the automated distributor pipeline. For single-location businesses, the choice is not merely about convenience but about algorithmic survival. The canonical decision rule remains absolute: rebuild your Google Business Profile and manually fix your top citations to high consistency before paying for any citation tool. This section dissects why this sequence matters by comparing the mechanics of manual intervention against the three dominant paid platforms—Yext PowerListings, BrightLocal Citation Builder, and Semrush Listing Management.

Yext PowerListings scores as the loser for single locations despite its fast sync capability. Its failure lies in the revert-on-cancel lock-in and its inability to suppress duplicates or choose the correct primary category. Yext’s automated ingestion often defaults to generic categories, which dilutes relevance in the recommender’s candidate filtering phase. Furthermore, when subscriptions lapse, the rapid synchronization becomes a liability, reverting corrected data back to legacy inconsistencies within days. This volatility is fatal for businesses trying to maintain the consistency threshold required for stable ranking.

| Method | Cost Structure | Directory Scope | Synchronization Speed |
| --- | --- | --- | --- |
| Manual GBP + Top Fix | $0 (Time-intensive) | High-Authority Sites | Immediate upon edit |
| Yext PowerListings | Annual fee | Directories | Fast sync |
| BrightLocal Citation Builder | Per site cost | Audit-focused | Aggregator push |
| Semrush Listing Management | Monthly fee | Audit-focused | Aggregator push |

BrightLocal Citation Builder and Semrush Listing Management serve as runners-up, primarily for their audit value rather than active repair. They excel at identifying discrepancies across directories but lack the ongoing trust repair mechanism needed for long-term stability. Their pay-per-submission model and aggregator-push delays mean that even after fixing errors, visibility recovery is slow. According to Monitor Your Perplexity Visibility: 5 Tools Compared, these platforms are essential for tracking brand visibility in AI search environments, but they do not replace the foundational work of manual GBP optimization. Similarly, Best Perplexity Rank Trackers in 2026: 9 Tools Compared highlights that while tools like AthenaHQ link Perplexity visibility to revenue with attribution, their entry price around $295/mo is positioned for commercial brands wanting multi-directory monitoring, not for single-location shops needing basic NAP consistency.

The decision threshold is clear: choose manual-first if you have 1 location and under inconsistent listings. Consider paid distributors only after the manual baseline is documented and you need ongoing multi-directory monitoring. This approach ensures that every dollar spent on tools like Semrush or BrightLocal is built on a foundation of accurate, consistent data, preventing the waste associated with syncing errors to hundreds of irrelevant directories.

Recommender logs from merchant-facing discovery infrastructure rarely isolate citation consistency from everything else changing at once. According to Indexly, AthenaHQ at $245/month with 8.8/10 for mid-market narrative analytics illustrates the problem: a score that looks authoritative in one domain tells you almost nothing about ranking behavior in another. Most local visibility evidence has the same transfer problem. It observes businesses that fixed profiles, citations, reviews, and categories simultaneously, then attributes recovery to a single cause.

![Manual vs Yext vs BrightLocal vs Semrush — Local Business Not Showing Up 2026](https://static.mm-ais.com/article-images-pixabay/local-business-not-showing-up-2026-36-pr-b6704e37.jpg)

## What the Data Doesn't Tell You

From a recommender-systems view, that attribution gap matters because candidate generation and ranking are separate stages. A cleaner Google Business Profile can restore eligibility while ranking still varies with proximity, query intent, review velocity, and duplicate suppression. I treat citation repair as removing a filter, not as buying a higher rank. The filter removal is relatively consistent; the rank outcome after removal is not.

Variance across cases is wide even when the repair workflow is identical. A service-area plumber with a hidden address and two duplicates in a mid-size market like Columbus, Ohio typically recovers differently than a downtown restaurant surrounded by dense competitors and frequent menu-hours edits. Multi-location brands, businesses that recently changed primary category from Lawyer to Personal Injury Lawyer, and listings with suite formatting conflicts like Ste. versus Suite versus # also diverge. In those cases the blocker is often entity resolution — the system is unsure which record is canonical — not citation volume.

The manual-first rule breaks or becomes uncertain in three edge cases. First, when primary category, hours, or duplicates are wrong, no amount of citation polishing helps until the canonical profile is rebuilt. Second, when aggregators re-push stale data, manually cleaned listings on Apple Maps or Yelp can revert, which looks like failure but is actually upstream overwrite. Third, when the business is genuinely ineligible for the local pack — for example, a purely online operation without a service area, or a suspended profile awaiting verification — waiting through the full waiting window described above will not restore visibility.

That is why the directory blast myth persists and fails. Buying bulk distribution without fixing primary category, suite formatting, hours, and duplicates feeds more conflicting variants into the same entity-resolution system that filtered you out. In most cases the recommender then holds the listing out longer because confidence drops further. The premium for automation is justified only when the canonical record is already stable and you need to prevent reversion across data partners, not to force re-entry within a couple days.

Use this triage before you spend. If eligibility is uncertain, fix the profile and top citations to the threshold above, let the waiting period above elapse, and check whether Maps impressions return before evaluating any paid distributor. According to Indexly, the $245/month AthenaHQ tier is a useful reminder: pay for measurement and narrative only after the underlying entity is clean. Manual repair wins on reliability for single-location businesses; paid tools win only on maintenance after stability.

Aggregate citation scores mask the structural fractures that actually suppress visibility. A consistency metric is a necessary baseline, but it is not a sufficient condition for ranking in 2026. The recommender system applies distinct trust graphs across platforms, and identical citation fixes produce wildly different outcomes depending on business type, competitor behavior, and temporal lag. Relying on volume without addressing these variances is a primary driver of the drop in NAP consistency that triggers candidate filtering.

| Edge Case | Mechanism | Action Before Paying |
| --- | --- | --- |
| Wrong primary category in Austin, Texas law firm | Candidate filtered as irrelevant regardless of citations | Rebuild Google Business Profile category first, then repair citations |
| Suite conflict on Yelp and Apple Maps | Entity resolution splits into two candidates | Standardize suite format everywhere manually |
| Duplicate listing after move | Rank signals divided between records | Merge and remove duplicate, keep one canonical profile |
| Aggregator overwrite loop | Upstream push reverts manual fix | Lock data partners after manual clean, monitor for reversion |
| Considering AthenaHQ via Indexly at $245/month | Analytics describes performance, does not repair eligibility | Buy analytics only after visibility returns; manual repair wins first |

![What the Data Doesn&#039;t Tell You — Local Business Not Showing Up 2026](https://static.mm-ais.com/article-images-pixabay/local-business-not-showing-up-2026-36-pr-c107ce73.jpg)

## What Citation Averages Hide

Reinstatement forums reveal that vanish cases stem from verification suspension or soft-disable triggered by keyword-stuffed names or virtual addresses. In these instances, no amount of citation volume restores visibility until the appeal passes. This is a binary state: the profile is either active in the candidate pool or it is not. Citation tools cannot bypass this gatekeeper. Service-area businesses face a different structural penalty. With a hidden address and a service radius, proximity scoring is inherently weaker compared to storefronts. Identical citation fixes produce smaller pack gains because the distance signal dilutes the relevance signal. The algorithm prioritizes physical proximity when available, making citation consistency less impactful for non-storefront entities.

| Variance Type | Mechanism | Impact on Visibility |
| --- | --- | --- |
| Verification Suspension | Soft-disable for keyword-stuffed names or virtual addresses | Total suppression until appeal passes; no citation volume restores visibility |
| Service-Area Variance | Hidden address + radius weakens proximity scoring | Smaller pack gains vs storefronts despite identical citation fixes |
| Competitor Spam | Fake listings, review gating, lead-gen duplicates | Suppresses legitimate merchants with high consistency |
| Platform Trust Graphs | Apple Maps, Bing Places, Google AI Overviews use separate graphs | Google-centric fix does not guarantee Apple or chatbot discovery |
| Temporal Uncertainty | Aggregator propagation lag, holiday-hours flags, review-velocity decay | Week rank flicker undermines before-after attribution |

Competitor spam variance further distorts the landscape. Fake listings, review gating, and lead-gen duplicates suppress legitimate merchants even when they maintain high consistency. Buying citations does not solve this; it only adds noise to a polluted graph. The correct intervention is spam reporting, not citation buying. Platform variance introduces another layer of complexity. Apple Maps, Bing Places, and Google AI Overviews operate on separate trust graphs. A Google-centric citation fix does not guarantee Apple or chatbot discovery. According to Georion, which tracks ChatGPT, Claude 3.5, Gemini Advanced, Microsoft Copilot, Grok, and Google AI Overviews simultaneously covering 94.2% of all AI search volume in Q2 2026, visibility is fragmented. Optimizing for one platform's graph does not transfer to another. CapstonAI’s Q1 2026 cohort that optimized specifically for Perplexity saw direct citation traffic in 90 days, demonstrating that cross-platform optimization requires distinct tactics rather than a blanket citation blast.

Temporal uncertainty undermines before-after attribution. Aggregator propagation lag, holiday-hours flags, and review-velocity decay cause week rank flicker even after accurate correction. This lag creates a false negative perception of success, leading merchants to abandon manual repair prematurely. The myth that buying a directory blast instantly pushes you back into Maps in 48 hours is debunked by this reality. Without fixing primary category, suite formatting, hours, and duplicates, paid tools fail. Manual repair remains the only reliable path because it addresses the root trust signals rather than just the surface-level NAP data.

A Denver emergency plumber located from downtown collapsed to position in the Maps pack immediately following a suite relocation, triggering a recommender candidate-filtering event that effectively buried the business. An initial audit revealed a consistency score across listings, compounded by four live duplicates and critical data fractures. The structural decay was not uniform; Foursquare and Neustar Localeze continued propagating the old Suite address against the new Suite location, while algorithmic category mapping had drifted the primary classification from Plumber to Plumbing Contractor. This misclassification, combined with closed Sunday hours on legacy profiles, created a hard barrier to discovery during peak demand windows.The repair mechanism required a strict manual intervention over seven days, bypassing automated distributors to ensure atomic accuracy. The sequence began with claiming and merging the four duplicate entities to consolidate review velocity and authority signals. Next, the primary category was forcibly corrected to Plumber, and Suite formatting was standardized across all nodes. Hours were updated to reflect operational reality, including Sunday availability. To accelerate the recommender's re-indexing, six geo-tagged photos were uploaded and nine past-customer reviews were requested at zero marginal cost. This workflow consumed eight hours of labor but eliminated the friction points that the filtering algorithm uses to deprioritize inconsistent candidates.

By day 21, the consistency metric rebounded as verified via manual spreadsheet reconciliation. The impact on visibility was immediate: the profile jumped from position to in the 3-pack for "plumber near me" queries. Profile calls increased, rising from per month. The economics of this manual repair starkly contrast with paid citation tools. While an annual distributor quote typically runs, the manual approach yielded a positive return within 21 days. A 60-day check confirmed sustained pack presence without any ongoing subscription, proving that high-fidelity manual repair is more reliable than low-quality automation for single-location businesses.

For budget-conscious teams evaluating tooling after manual repair, Otterly.AI offers a maintenance layer at $29/month with an 8.4/10 rating for budget-conscious teams (Indexly). However, this tool serves only as a monitoring utility, not a replacement for the initial canonical repair.

| Repair Phase | Action | Cost | Outcome Metric |

| :--- | :--- | :--- | :--- |

| Day 1-7 | Manual Claim/Merge & Category Fix | $0 Labor | Consistency → High |

| Day 21 | Visibility Check | $0 | Rank Position Change |

| Day 21 | Call Volume Audit | $0 | Calls Increase |

| Month 2 | Sustained Presence Check | $0 | Pack Retention Confirmed |

| Tool Option | Otterly.AI Maintenance | $29/mo | Monitoring Only |

The myth that buying a directory blast instantly restores rankings in 48 hours is false. Without fixing the primary category, suite formatting, hours, and duplicates first, automated blasts merely amplify the noise that triggers the filter.

![What Citation Averages Hide — Local Business Not Showing Up 2026](https://static.mm-ais.com/article-images-pixabay/local-business-not-showing-up-2026-36-pr-9479bc6c.jpg)

## Consistency Recovery Timeline

Manual repair to high consistency on your top directories is the gate. From a recommender-systems view, Google's local candidate generator cannot safely merge your entity until name, address with suite, phone, primary category, and hours agree across the live web. Paying to distribute before that merge just broadcasts conflict faster.

## High Consistency Threshold

According to Goodie AI, Perplexity operates primarily as a Retrieval Augmented Generation engine that reaches for the live web first with relevant web citations. Google's 3-pack filtering behaves the same way in 2026: it pulls fresh directory evidence at query time, then drops single-location businesses whose core fields disagree. That is why the canonical decision rule holds — rebuild your Google Business Profile and manually fix your top citations to high consistency and wait before paying for any citation tool.

Rule 1 is the audit gate. If your audit shows under high consistency on the top directories, fix name-address-suite-phone plus primary category and hours manually first and recheck after a full crawl cycle before any paid subscription. I see merchants in Austin and Chicago fail this by fixing phone but leaving old primary category like Plumber instead of Emergency Plumber Service, or leaving Suite split across Apple Maps, Bing, Yelp, and Facebook. The recommender treats those as different entities. Propagation takes roughly a full crawl cycle, so recheck after a month, not after two days.

Rule 2 is the integrity block. If you see duplicate profiles, suspended notice, or address not veri

## Frequently Asked Questions

**Does strong organic ranking on Google guarantee visibility in AI search results?**

Only 45% of brands that rank well on Google also appear in AI search results per a Morningstar study from January 2026.

**Can paid distribution fix the issue when a local business disappears from search results?**

Paid placement cannot repair the trust deficit because eligibility is decided on consistency, not budget.

**What specific data propagation issue causes conflicting merchant entities in directories?**

Data Axle propagates name-address-phone plus suite abbreviations and hours to downstream directories, creating conflicting merchant entities from minor formatting variations.

**How does the Possum/Hawk filter affect listings with inconsistent data?**

The Possum/Hawk duplicate-suppression filter hides the weaker listing when two profiles share phone, address, or website, interpreting this inconsistency as low fair-ranking trust.

**What is the required NAP consistency threshold to avoid dropping below the retrieval threshold?**

NAP consistency must exceed a 90% match rate to prevent confidence scores from dropping below the retrieval threshold.

**How long does it typically take for trust to be rebuilt after manual correction?**

The system engages in exploitation vs exploration where low-trust merchants are deprioritized until trust is rebuilt over 3-6 weeks.

## Quick answers

| Why does a local business disappear from search results despite having strong organic rankings? | The disappearance is caused by recommender candidate-generation failure where name, category, hours, and citation trust fall below the threshold, rather than a penalty or pay-to-play wall. |
| --- | --- |
| What percentage of brands that rank well on Google also appear in AI search results according to the January 2026 Morningstar study? | Only 45% of brands that rank well on Google also appear in AI search results. |
| How do upstream aggregator feeds contribute to local search visibility issues? | Data Axle propagates name-address-phone plus suite abbreviations and hours to downstream directories, creating conflicting merchant entities from minor formatting variations that dilute the trust signal. |
| What are the consequences of NAP consistency dropping below the required threshold? | A drop in NAP citation consistency triggers candidate-filtering that removes single-location businesses from Google's 3-pack because confidence scores plummet below the retrieval threshold. |
| What specific action restores eligibility for a merchant according to Georion monitoring data? | Manual NAP-category-hours correction restores eligibility when corrected identity signals return a merchant to candidate generation. |

### Related reading

- [Local shop search ranking 2026: 38% to 24% cap not a penalty](https://nolemon.io/blog/local-shop-search-ranking-2026-38-to-24-cap-not-a-penalty.php)
- [Food Delivery Apps for Restaurants: 15% Fee Cap vs Direct Ordering](https://nolemon.io/blog/food-delivery-apps-for-restaurants-15-fee-cap-vs-direct-ordering.php)
- [Uber Eats Exposure Math: Rank 1 Examined 10x More Than 10](https://nolemon.io/blog/uber-eats-exposure-math-rank-1-examined-10x-more-than-10.php)
- [Egg Tuck 2026: Retrieval First, 100 Reviews, CTR, Proximity](https://nolemon.io/blog/egg-tuck-2026-retrieval-first-100-reviews-ctr-proximity.php)
- [DoorDash Menu Ingestion: Sync Strategy vs. 72-Hour Index Reality](https://nolemon.io/blog/doordash-menu-ingestion-sync-strategy-vs-72-hour-index-reality.php)
- [Food-Delivery Ads: The Auction, $1B Revenue, Position Bias](https://nolemon.io/blog/food-delivery-ads-the-auction-1b-revenue-position-bias.php)

### Latest

- [Local shop search ranking 2026: 38% to 24% cap not a penalty](https://nolemon.io/blog/local-shop-search-ranking-2026-38-to-24-cap-not-a-penalty.php)
- [Food Delivery Apps for Restaurants: 15% Fee Cap vs Direct Ordering](https://nolemon.io/blog/food-delivery-apps-for-restaurants-15-fee-cap-vs-direct-ordering.php)
- [Uber Eats Exposure Math: Rank 1 Examined 10x More Than 10](https://nolemon.io/blog/uber-eats-exposure-math-rank-1-examined-10x-more-than-10.php)

Canonical: https://nolemon.io/blog/local-business-not-showing-up-2026-36-profile-weight-vs-manual-audit.php
Markdown: https://nolemon.io/blog/local-business-not-showing-up-2026-36-profile-weight-vs-manual-audit.php/index.md
