Local SEO / measurement

Google Business Profile Post View Counts: What the Metric Actually Tells You

Google has restored per-post visibility reporting inside Business Profile. The number is useful, but it is not a click, a lead, or evidence that posting improved local rankings.

Local business storefront displaying a Business Profile post and its view count

Direct answer: use the new Google Business Profile post view count as a visibility signal for individual updates, offers, and events. Compare similar posts over a consistent time window, add tagged links when a post has a website CTA, and keep calls, directions, bookings, and sales as separate outcome metrics. Google says reporting covers posts from the rolling previous 18 months, combines views from Search and Maps, is rolling out globally, and is not yet available through the API.

This guide is narrowly about measuring Google Posts. It does not replace a complete local SEO plan, prove a ranking effect, or turn a view into an attributable customer action.

The useful question is not “Which post has the biggest number?” It is “Which comparable post earned visibility, produced a measurable next action, and taught us what to publish next?”

What Google added

Google announced the return of post-level view reporting in its September 2026 Small Business Bulletin. A view count appears on post cards in the Business Profile dashboard. The announcement covers regular updates, offers, and events published during a rolling 18-month window and combines visibility from Google Search and Google Maps.

The change restores a basic signal that disappeared when older post insights were retired in 2023. Google's Business Profile API deprecation schedule records the February 20, 2023 sunset of accounts.locations.localPosts.reportInsights, LOCAL_POST_VIEWS_SEARCH, and LOCAL_POST_ACTIONS_CALL_TO_ACTION. The new counter is still a dashboard feature rather than an API metric. That distinction matters: a single-location owner can inspect posts directly, while an agency managing many locations cannot yet pull the numbers into a normal reporting pipeline.

Confirmed characteristicWhat it enablesWhat it does not provideMeasurement consequence
Count on each post cardCompare visibility between individual postsA separate click or conversion countKeep outcomes in a separate reporting field
Rolling 18-month historyReview recent seasonal and recurring contentA permanent lifetime archiveExport or snapshot counts periodically before older posts fall outside the window
Search and Maps combinedSee total exposure across the two surfacesA Search-versus-Maps splitDo not compare the number directly with Search-only visibility data
All post typesCompare updates, offers, and eventsProof that unlike post types had equal placementCompare like with like instead of ranking every post in one list
Dashboard onlyManual review by owners and managersAPI export or automated multi-location reportingUse controlled manual sampling until Google documents API support

What a post view means—and what remains undefined

The launch language describes how many times local customers viewed a post. Google has not published a detailed counting methodology for this new number. The current documentation does not say whether repeat exposures are deduplicated, how long a post must be visible, or whether an expanded post is treated differently from a card shown inside a profile.

Do not import the definition of the separate Business Profile Views metric. Google documents that profile-level metric as unique visitors counted in a limited way, but that does not establish the methodology for post-level reporting. Until Google documents the new counter, call it a post view and preserve the uncertainty.

Do not confuse the new per-post counter with the existing Offers performance metric, which Google separately describes as views and clicks on offers in a Business Profile.

Where to find the view count

  1. Sign in with an owner or manager account for the verified Business Profile.
  2. Open the profile management interface and select Posts.
  3. Review the count displayed on each eligible post card.
  4. Record the date and age of the post when you copy the number.
  5. If the field is missing, treat the account as not yet reached by the rollout; do not infer zero views.

Google describes the feature as a global rollout, not an instantaneous switch for every account. A missing counter during rollout is an availability state, while a displayed zero is a measurement value.

A measurement workflow that produces useful decisions

FloxoLab measurement framework: 24h → 7d → 28d. These are fixed comparison points proposed by FloxoLab, not observation intervals recommended by Google.

  1. Group comparable posts. Separate offers, events, operational updates, and general news. Placement and intent differ.
  2. Choose fixed observation points. Record views after 24 hours, 7 days, and 28 days instead of comparing one new post with one six-month-old post.
  3. Tag website CTAs. Use a specific landing page and UTM parameters such as utm_source=google, utm_medium=organic, and a stable campaign name.
  4. Record the business outcome separately. Track visits, calls, bookings, coupon use, or enquiries in the system that receives them.
  5. Write one next action. Repeat a useful offer, change the timing, improve the landing page, or stop a format that earns exposure without action.
Field to recordWhy it mattersExample
Location and post URL or internal labelPrevents records from being mixedQuezon City / September consultation offer
Post type and publish timeKeeps comparisons like-for-likeOffer / Monday 09:00
Views at fixed agesSeparates reach from time online24h, 7d, 28d
CTA and tagged destinationConnects exposure to measurable site activityBook / service landing page
OutcomeKeeps the report tied to the businessQualified form submissions
DecisionTurns reporting into actionRepeat next month with clearer offer

What you should export now

At minimum, preserve Post, Publish date, Current views, and Snapshot date. The rolling 18-month window means an older post will eventually leave the available history, so a dated snapshot is more useful than an undated copied number.

How to interpret the number without overclaiming

A high view count with no tagged visits may mean the post was visible but the offer, CTA, or destination did not earn action. A lower-view post with qualified bookings may be more valuable. A post can also influence a call or visit without producing a trackable website session, so attribution remains incomplete.

Do not report that posts increased rankings because views rose. The counter measures post exposure, not map-pack position. To evaluate local visibility, keep post reporting beside profile views, discovery queries, calls, directions, website clicks, and the actual leads or sales the business records. The broader distinction is explained in the zero-click search measurement guide.

The API gap is the main multi-location limit

Google says the new post reporting is not yet available through the Business Profile API. For a small group of locations, use a controlled manual sample. Record the same post types at the same ages and keep a screenshot or dated dashboard note as the source. For hundreds of locations, do not build scraping or fragile automation around an undocumented dashboard field.

A practical interim report can sample representative locations by market, store type, or offer. Label it as a sample rather than pretending it covers the estate. If Google later exposes an API field, map it into the existing record only after its definition and dimensions are documented.

A sensible first 30 days

Sources checked

The feature and its limits were checked on September 14, 2026. Because rollout and documentation can change, confirm the live field in the profile you manage before promising it in a client report.

Need a local measurement plan that reaches the business outcome?

FloxoLab can separate profile visibility, website activity, and real enquiries, then build a reporting routine your team can maintain.

Explore local SEO