> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/search/googlesearch.md).

# Google Search

###

To establish a connection to Google Search provide a CustomSearchId and APIKey.

### Creating a Custom Search Engine

To start searching websites through the provider, follow the steps below:

1. Sign into the Google Custom Search Engine site.
2. Click New Search Engine and add a site to focus the search on.
3. Click Edit Seach Engine, select your search engine in the menu, and then click Setup.
4. In the Details section, click Search Engine Id to retrieve the search engine Id used as the CustomSearchId in the connection string.
5. In the Sites to Search section, you can additionally select the Search the Entire Web but Emphasize Included Sites option in the menu.

### Getting the API Key

To authenticate requests to the Custom Search API, follow the steps below:

1. Log into the Google API console and select a project.
2. In the side bar under APIs & Services, click Library and then select the Custom Search API. Click Enable.
3. In the side bar, click APIs & Services -> Credentials.
4. Click Create Credentials -> API Key.
5. Select the API Key to restrict the key to your platform.

You can now search the Web using the Google Custom Search engine.

 

 


---

# 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.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/search/googlesearch.md?ask=<question>&goal=<user_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.