> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/marketing/link-from-the-app/book-with-google-links.md).

# Book With Google Links

#### Overview

Google Business Profile lets you attach action links to a location, so Customers can book straight from Google Search and Maps. Google requires each link you register to be a **different URL** — and the page each one opens must show the Club's name and street address, so Google can confirm the link belongs to that business.

The `bwg` query parameter does both jobs. Adding it to a normal PodPlay link makes the landing page display the location's full name and address, and gives you three distinct URLs to register.

#### The Three URLs

A location usually has one Book link and two Services links in Google Business Profile. Use one of these per slot so no two are identical:

| Google slot      | URL                                                                              |
| ---------------- | -------------------------------------------------------------------------------- |
| Book             | `https://[clubname].podplay.app/book/[location]?bwg=book`                        |
| Reservation      | `https://[clubname].podplay.app/book/[location]?bwg=reservation`                 |
| Community Events | `https://[clubname].podplay.app/community/events?location=[location]&bwg=events` |

Replace `[clubname]` with your Club's PodPlay subdomain and `[location]` with the location's name.

Note where `[location]` sits in each URL — it is **not** the same in all three:

* On the two **booking** links it is part of the **path**: `/book/brooklyn?bwg=book`. Booking pages read the location from the path only. Adding `?location=brooklyn` to a booking link does nothing.
* On the **Community Events** link it is a **query parameter**: `?location=brooklyn`. This is the same filter described in [Create Event Deep Links](/marketing/link-from-the-app/create-event-deep-links.md), and it accepts either the location's name or its ID.

#### What Changes on the Page

With `bwg` in the URL, the header shows the location's name with its street address underneath. Everything else behaves exactly as normal — Customers book the same way they always do.

Without the parameter, nothing changes. The address only appears on Book With Google links, so your existing marketing links are unaffected.

The value has to be exactly `book`, `reservation`, or `events`, all lowercase. Any other value — `?bwg=true`, `?bwg=Events`, a typo — is ignored, and the page loads without the address.

#### Notes

* **The Community Events link must include `location`.** Book With Google links point at one specific location, and the address only appears when the Events list is filtered to a single one.
* **Keep the parameter on the link you register.** If it is stripped, mistyped, or edited, the page loads normally but no longer shows the address, and Google may reject the link.
* **Changing the parameter later means re-registering every link** in Google Business Profile, so set these up once and leave them alone.
* The address shown is the one on the location's record. If it looks wrong, correct it in **Venues → the location → Address**, and the link will pick up the change.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/marketing/link-from-the-app/book-with-google-links.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.