> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/menu/options-menu/search-engines.md).

# Search Engines

**Options>TV Show Search Engines** and **Options>Movie Search Engines** each open a *Modify Search Engines* window, one for TV shows and one for movies. These control TV Rename’s outgoing interface with the world (other than its data sources). Here, you can configure how and where TV Rename points a web browser searching for files.

<figure><img src="https://3508557057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx0gPeIfHpbgTioNust1M%2Fuploads%2FIW9izNvHluVVGSrkcvyN%2Fimage.png?alt=media&amp;token=b3527fe5-01c1-4f0a-9e8d-a32ca98081e9" alt=""><figcaption></figcaption></figure>

Using the `Add` and `Delete` buttons you can create or remove records at will, and the `Tags...` button pops up a list of supported tags to remind you what's available. (The tags supported are the same as those listed in the [Filename Template Editor](https://www.tvrename.com/menu/options-menu/filename-template-editor.md).)

TV Rename starts with three entries in each list: Google, YouTube and Vimeo. As an example, here is the TV show URL entry for Google.

> <https://www.google.com/search?q={ShowName}+S{Season:2}E{Episode}>

The list of URLs can be used from the ***Scan*** and ***Schedule*** tabs. The last used entry becomes the default, and its name appears on a search button on the toolbar (to the right of the `Refresh` button on the Schedule tab). It can be changed by clicking the `▼` button next to it and selecting another entry.

With a little ingenuity you can get really creative with these entries and pass your search to its specific target through a web proxy.


---

# 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://www.tvrename.com/menu/options-menu/search-engines.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.
