Do Google Posts affect Google Maps ranking, and what can I measure?

Google says local results are mainly based on relevance, distance, and popularity. Its explanation of prominence also mentions links, reviews, and positive ratings, while the same guidance says Google keeps search-algorithm details confidential. That guidance is a bounded description, not a complete or permanent ranking formula.¹

For the wider context, see Google’s local ranking factors. The answer there and this page should not be read as a promise that any single profile action guarantees a position.

For profile fundamentals, see the Google Business Profile guide, which is separate from the Post and performance references used here.

Google’s Business Profile post guidance says current updates help customers decide whether to visit. That describes the purpose of Posts, not a documented mechanism for changing organic Maps ranking.²

Google also ties visibility to the Post status. A Live Post is public and shows on Search and Maps. Pending and Not approved Posts do not show there. Posts older than 6 months are archived unless a date range is set.²

The broader guide to publishing photos and Posts on a Google Business Profile covers the content workflow. Use a Post for a real customer update, offer, or event, not as a ranking promise.

Keep these observations separate when you record them:

Google’s September 10, 2026 Google Small Business Bulletin, “Google Small Business Bulletin 📈 Track your Google Post views” says dashboard Post Reporting is rolling out globally. It reports rolling 18-month view counts for regular updates, offers, and events, aggregates views from Google Search and Google Maps, and shows the count on each Post card. The bulletin says this reporting is not yet available in the API.⁷ Keep this current dashboard reporting separate from the legacy API fields in the table above.

Profile performance data can combine organic Search and Google Ads, and daily metrics can cover both Search and Maps across devices. Those scopes describe where an interaction was recorded. They do not isolate a Post as the cause of a ranking change.

Google’s local-ranking guidance also says relevance and distance matter.¹ A before-and-after comparison for one business or one query can therefore move for several reasons. Treat a change as an association during the observation window unless a source establishes a causal test.

1. Set the observation window. Record each Post’s publication date, type, and status. Count only Live Posts, exclude Pending and Not approved Posts, and record the 6-month archive rule or any date range that changes it.
2. Record Post-level measures separately. If the current account or API exposes them, log LOCAL_POST_VIEWS_SEARCH and LOCAL_POST_ACTIONS_CALL_TO_ACTION. Verify the current access path because the older local-post insights endpoint was removed.^4,6
3. When dashboard Post Reporting is available, record the view count shown on each Post card as a separate dashboard measure. Preserve its scope: rolling 18 months, regular updates, offers, and events, aggregated across Google Search and Google Maps, with global rollout still in progress and no API availability stated in the bulletin.⁷ This measure is an observation, not proof of ranking impact.
4. Record profile-level measures in a separate row or sheet. Keep views, searches, calls, website clicks, offers, and daily metrics separate, and preserve whether a measure covers organic Search, Google Ads, Google Search, Google Maps, desktop, or mobile. Business Profile performance metrics explains the owner-facing labels.
5. If you also check Maps visibility, record the query, searcher location, device, date, and time. Keep those conditions stable enough to compare, and label the result as an observation rather than a Google ranking rule.
6. Report only what the records show. “Post views increased during the window” is an observation. “Posts raised Maps ranking” is a causal claim that a correlated change does not support.

This protocol helps you avoid assigning a profile-wide total to one Post. It also keeps a visibility check distinct from the performance data Google documents.