> For the complete documentation index, see [llms.txt](https://unofficial-logseq-docs.gitbook.io/unofficial-logseq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unofficial-logseq-docs.gitbook.io/unofficial-logseq-docs/beginner-to-advance-features/aliases.md).

# Aliases

An **Alias** indicates an additional / alternative name for a note. Aliases are great when referring to acronyms, nicknames, notes in a different language, or even people. &#x20;

When you search or reference Franch / Francais, AI / Artificial Intelligence, PKM / Personal Knowledge Management, or Al Capone / Scarface, Aliases help you through the ability to use multiple terms to reference the same underlying note.

### How to Create an Alias

1. Create a new page and call it `Artificial Intelligence`.
2. In the **first block** of this pag&#x65;**,** type `alias:: AI`
3. Navigate to a different page and create the AI link `[[AI]]`
4. Clicking \[\[AI]] will navigate you to the  `Artificial Intelligence` page.

You can add multiple aliases by changing Step 2 to the following: `alias:: AI, Aliens Are Here, Chat-GPT`. When you reference each term, it will link to the original Artificial Intelligence page.

### Alias Negatives

&#x20;The main negative of using aliases is overlapping.&#x20;

For example, we use AI as an alias for Artificial Intelligence. However, AI could also stand for many other terms, such as Adobe Illustrator, Amnesty International or Air India etc. You need to be careful when setting aliases up to ensure it does not cause issues down the line as your knowledge base grows.

{% embed url="<https://www.youtube.com/watch?v=k9gMElbbJhU>" %}


---

# 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://unofficial-logseq-docs.gitbook.io/unofficial-logseq-docs/beginner-to-advance-features/aliases.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.
