> 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-en/action-guide/navigation/back-url.md). # Back URL Back URL is the action that instructs the browser to return to the previously visited webpage in the browsing history, similar to clicking the back arrow button in the top left corner of the Chrome or Firefox browser. This action works automatically and does not have any accompanying configuration parameters. 🎥 Watch the tutorial video: [Here](https://youtu.be/a9qNt96X1SM). #### Practical example: Go back to the product list after checking details When you script data scraping or enhance interaction (buff follow/like), the usual flow will be: from the summary list page, you click on a detail link to check information or press the follow button. After completing the task on that detail page, instead of using the Go to URL action to re-enter the address of the list page from the beginning (which requires the website to reload all data from the server, taking a lot of time): * How to apply: You just need to insert the Back URL action. * Result: The browser immediately goes back one step to the previous list page instantly, helping the script run smoothly, saving network bandwidth, and optimizing the processing speed of the flow. --- # 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.gpmautomate.com/automate-en/action-guide/navigation/back-url.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.