> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-zh/action-shi-yong-zhi-nan/navigation/go-to-url.md).

# Go to URL

此操作指示浏览器直接跳转到您指定的网页路径(URL)。

* 作用:这是工具开始工作的第一步。您只需输入网站地址,浏览器就会自动进入该页面,以便您执行后续步骤。

🎥 观看更多教程视频:[点击这里](https://youtu.be/a9qNt96X1SM)。

#### 配置参数:

* URL:您想要打开的网站的确切地址。

  > ⚠️ 必须注意:填入此栏的路径必须在开头包含完整的网络协议 `https://` 或 `http://`(例如:`https://24h.com.vn`)。如果您只填写简写形式如 `24h.com.vn`,系统将无法识别路由结构并报出操作错误。
* Timeout (s):脚本等待网页完整加载所有数据的限制时间(以秒为单位)。如果留空,系统默认为 `60` 秒。

#### 实际示例:使用慢速 Proxy 时调整等待时间

当您通过带有 Proxy 的 Profile 运行营销脚本或抓取数据时,有时会遇到连接速度非常慢、响应时间长的 Proxy 套餐,或者目标网站的服务器正遭遇网络拥堵。如果保持默认的等待时间,脚本可能会因超时而中途断开连接:

* 配置方法:
  * URL:`https://pinterest.com`
  * Timeout:从 `60` 改为 `120`(2 分钟)。
* 结果:浏览器将耐心等待最多 120 秒,以便网页能够及时加载完数据。相反,如果您的网络非常稳定,并且希望优化速度,使脚本在遇到失效(die)网页时不会卡住,您可以主动将该数值降低到 `20` 或 `30` 秒,以便系统更快地中断错误流程并切换到其他账户。


---

# 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.gpmautomate.com/automate-zh/action-shi-yong-zhi-nan/navigation/go-to-url.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.