> For the complete documentation index, see [llms.txt](https://docs.booknorder.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.booknorder.co.nz/how-to-guides/how-to-claim-your-business-on-google.md).
# How to claim your Business on Google
If you wish to drive more traffic to your restaurant as well as your online store, setting up your Google business listing is one of the most important steps, since Google is the first place people go to when searching for anything.
1. Log in to your Google Business account with your restaurant's email address. If you don't have a Google business account, create one.
2. Open [Google Maps](https://booknorder.freshdesk.com/support/solutions/articles/https%3Amaps.google.com)
3. Search for your restaurant in the search bar
4. Click "**Claim this business**"\\
5. Click "**Manage Now**"\\
6. You will be asked to verify that you manage this business. The verification will be through one of the following methods:
* Business email
* Phone call
* Text message
* Physical postcard mailed to store address\\
7. Once you're verified, you will be able to make edits to the listing
{% hint style="info" %}
You can also take a look at Google's support article about claiming your business
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.booknorder.co.nz/how-to-guides/how-to-claim-your-business-on-google.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
