> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/integration-and-extensions/internal-url-handling.md).

# Internal URL Handling

### Do web links open internally or externally in my app?

All URLs open internally within the app using a web-view interface. This ensures a seamless user experience without exiting the app.

{% hint style="success" %}
A URL is the web address you type in your browser to open a website or a specific page on the internet.
{% endhint %}

#### **How does URL opening work?**

* **Internal Opening**:
  * When users click on a URL in your app, it opens directly in the app’s Web View interface.
  * This keeps users within the app environment, maintaining a consistent and uninterrupted experience.
* **No Default Browser Redirection**:
  * URLs do not redirect users to the device’s default browser (e.g., Chrome or Safari).
  * The Web View interface allows users to view the content without leaving the app.

{% hint style="success" %}
Benefits of keeping URLs in-app

* Consistent Experience: Users stay within the app, which provides a cohesive interface.
* Branding: Keeps the app's look and feel intact, even when displaying external content.
* Ease of Use: Users don’t need to switch between the app and a browser.
  {% 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.appmysite.com/frequently-asked-questions/integration-and-extensions/internal-url-handling.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.