> For the complete documentation index, see [llms.txt](https://help.getglinks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getglinks.com/introduction/create-a-go-link.md).
# Create a go link
Follow these simple steps to create a new go link.
**Step 1: Click on Create link**
1. From the [Glinks homepage](https://getglinks.com), click the **“+ Create go link”** button at the top right of the screen (see red arrow).
2. You will be taken to the “Create new go link” form.
**Step 2: Fill Out the Form**
1. **Destination URL**:\
Enter the full URL of the webpage or document you want to link to. For example, you might input a Google Doc link here.
2. **Link name**:\
Choose a short, memorable link name. For example, for a weekly meeting document, you can use “go/weekly.”
3. **Description**:\
Provide a brief description of the link's purpose. This will help others in your team understand the content. For example: "Weekly meeting document."
4. **Unlisted** (optional):\
Check this box if you want the go link to be hidden from your team and workspace.
Once all fields are filled, click **Create** to finalize your go link.
---
# 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://help.getglinks.com/introduction/create-a-go-link.md?ask=&goal=
```
`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.