Add Location Check-ins to BuddyPress

BuddyPress has no concept of place. Members can say where they are in an activity post, but nothing stores it, maps it or lets anyone search by it. Adding location check-ins fixes that with one plugin, a map provider and about half an hour of configuration. This guide walks through the setup, the privacy decisions you need to make before launch, and the cases where check-ins are worth the effort.

What a check-in adds to a community

A check-in attaches a named place, with coordinates, to an activity post. On the front end that means a small map card under the update, a “Check-ins” tab on the member’s profile showing every place they have shared, and the option to filter the activity stream to check-ins only.

This matters for some communities far more than others. Running clubs, travel groups, alumni networks, local business directories and event-driven communities get a lot from it because members genuinely want to know who is nearby or who was at the same place. A remote-first professional network or a course community gets almost nothing, and the extra composer button becomes clutter. Be honest about which kind you are before installing anything.

We have also seen check-ins work as a content prompt. “Where are you working from today?” is an easy post for a member who would otherwise say nothing, and easy posts are how quiet members become active ones.

What you need before you start

• WordPress 6.1 or later and BuddyPress 14.x (14.5.2 is current as of July 2026), or the BuddyBoss Platform.
• The BuddyPress Check-ins plugin, free on WordPress.org (version 2.5.0, July 2026, tested up to the current WordPress release).
• A map provider. The free plugin uses Google Maps, so you need a Google Cloud project with the Maps JavaScript API and Places API enabled and billing attached. The Pro version adds OpenStreetMap as a keyless alternative (more on that below).
• A privacy policy page that mentions location data. In the EU and UK, precise location is personal data and your policy should say what you store and for how long.

Google Maps billing after March 2025

Google retired the pooled $200 monthly credit on 1 March 2025 and replaced it with a free allowance per SKU. The Essentials tier, which covers Maps JavaScript API loads, Geocoding and Places Autocomplete, gives 10,000 free calls per SKU per month. A community with a few hundred active members posting check-ins will stay inside that. A community with ten thousand members typing into the location box on every post can exceed it, and Autocomplete is billed per session, so set a budget alert in the Google Cloud console before go-live. Details are in Google’s March 2025 pricing notes.

If you would rather avoid a billing account entirely, Check-ins Pro can use OpenStreetMap rendered through Leaflet with Nominatim for geocoding. There is no key and no invoice, but Nominatim’s public service has a usage policy of roughly one request per second, so very large sites should self-host a geocoder or stick with Google.

Setting up the free plugin

1. Install from Plugins → Add New, search “BuddyPress Check-ins”, activate.
2. In Google Cloud, create or open a project, enable Maps JavaScript API and Places API, create an API key, and restrict it to your domain under Application restrictions → Websites. An unrestricted key will be scraped and used by someone else within days.
3. Go to Dashboard → BuddyPress Check-ins → General Settings and paste the key. The settings page validates it; if validation fails, the composer marker stays hidden and nothing saves, which is the most common “it does not work” report we get.
4. On the same tab, enable the check-ins tab on member profiles and rename it if “Check-ins” does not fit your community (“Places”, “Been there”, “Visits”).
5. Enable the activity filter so members can switch the stream to check-ins only.
6. Optionally turn on the location field for member profiles. This adds Google autocomplete to a text field so members enter a real, geocodable place rather than “somewhere sunny”.
7. Log in as a test member, click the map marker in the activity composer, start typing a place, pick a suggestion, post. Check that the map card renders and that the profile tab lists the place.

If you use BuddyX or Reign the composer marker inherits the theme’s icon styling. On other themes you may need a line of CSS to align the marker with the media buttons.

Privacy settings worth changing on day one

Location is the one community feature where the defaults should not be trusted blindly. Decide these before members start posting, because changing them later does not retroactively fix what has already been shared.

Setting	Our recommendation	Why
Address precision (Pro)	City and state for public communities; full address only for closed groups	A full street address on a public activity stream tells strangers where a member lives or works.
Coordinate obfuscation (Pro)	On	Adds a small random offset so the map pin does not land on a member’s front door.
Check-in expiry (Pro)	24 hours for “I am here now” communities; permanent for travel logs	A live location should not stay live forever.
Member and group exclusions (Pro)	Exclude staff accounts and any group for minors	Some members should never appear on a map.
Profile tab visibility	Follow your activity privacy; if the stream is members-only, the tab should be too	Keeps logged-out crawlers from indexing place histories.

Also give members an exit. The free plugin includes bulk delete of saved places from the profile tab, so a member who regrets sharing can clear their history without asking an admin. Mention it in your onboarding.

Going further with Check-ins Pro

The free plugin covers posting and the profile map. Check-ins Pro (version 2.4.0, June 2026, from $49 a year) is about discovery: finding members and groups by where they are.

Members Near Me

A widget and a members directory filter that sorts by distance from the viewer. On a running club site this is the feature people actually sign up for. It needs members to have a geocoded profile location, so turn on the profile location field first and give it a few weeks to fill.

Group locations

Groups get a location field and appear on a map in the groups directory. For chapter-based organisations (a national charity with regional branches, a franchise with local owners) this replaces a static “find your branch” page with something members can keep current themselves.

Proximity search on the members directory

Adds a radius search to the members page, optionally alongside Profile Search filters. Pair it with a profile field such as “Skills” or “Role” and you get “designers within 25 km”, which is a genuinely useful query for a professional network.

OpenStreetMap instead of Google

Select the provider under the Map provider tab. Everything else works the same. Maps look different (OSM tiles are plainer) and autocomplete suggestions are less polished for business names, but for city and town lookups it is fine and costs nothing.

A worked example: a cycling club with 1,200 members

A club we worked with wanted members to log rides and find riding partners. Here is what the setup looked like in practice.

1. Free plugin plus Pro, Google Maps as provider because members wanted to tag cafes and trailheads by name.
2. Profile location field mandatory at signup, city-level precision, coordinate obfuscation on.
3. Check-in expiry set to permanent because ride logs were the point, but address precision locked to city and state so the public stream never showed a start point at someone’s house.
4. Members Near Me widget on the activity sidebar with a 30 km default radius.
5. Groups created per region, each with a location, so the groups directory map doubled as a “find your local ride” page.

Google usage settled at around 3,000 Autocomplete sessions and 6,000 map loads a month, well inside the free allowance. The unexpected win was the profile tab: members started treating their check-in map as a ride diary and linking it from their Strava bios.

Troubleshooting

• Marker missing from the composer. Nine times out of ten the API key failed validation. Check that both Maps JavaScript API and Places API are enabled, that billing is attached, and that the HTTP referrer restriction includes your domain with and without www.
• Map renders grey with “For development purposes only”. Billing is not enabled on the Google Cloud project.
• Check-ins save but the profile tab is empty. Re-save permalinks under Settings → Permalinks. If you have BuddyPress set to a custom members slug, confirm the tab was registered after that change.
• Autocomplete stops working after a caching plugin update. Exclude the Google Maps script and the plugin’s JS from minification and combination. Deferring the Maps script breaks the callback.
• Members outside your country get no suggestions. Autocomplete has no country restriction by default; if someone added one in a customisation, remove it. Conversely, if you want to restrict to one country to cut costs, that is where to do it.

Frequently asked questions

Does this work with BuddyBoss Platform?

Yes. Both the free and Pro versions support BuddyBoss Platform as well as BuddyPress, including the BuddyBoss activity composer.

Can members check in from the mobile app?

The plugin is web-based. It works in a mobile browser and in any app that wraps the website in a web view. It does not add endpoints to the BuddyBoss native app.

Is the location stored as coordinates or text?

Both. The place name, formatted address and latitude/longitude are saved as activity meta, which is what makes filtering and distance search possible.

Can I import existing location data from a profile field?

Not automatically. If you already have a free-text “Location” xProfile field, the quickest route is to ask members to re-enter it once the autocomplete field is on, so the value is geocoded.

What about communities built on BuddyNext?

BuddyNext has its own activity system and this plugin targets BuddyPress and BuddyBoss, so check BuddyNext’s own feature list for location support before combining them.

What we would do

Install the free plugin, restrict the Google key to your domain, turn on the profile tab and the activity filter, and post three check-ins yourself so the feature is not empty when members find it. Leave it for a month. If members use it, buy Pro for the privacy controls and Members Near Me, and set precision to city level before you announce the map. If they do not use it, deactivate it and put the half hour into something your community actually asked for.