> For the complete documentation index, see [llms.txt](https://docs.legitimate.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.net/user-guide/legitimate-tags.md).
# Legitimate Tags
There are a number of methods that Legitimate can use to gather information for displaying your links on our site.
The default method is Legitimate Tags. These tags are a type of meta data that are placed in the \ section of web pages you want Legitimate to index.
Legitimate tags offer a quick and easy way for you to personalise exactly how your article will look when displayed on our site.
There are 7 Legitimate tags that we use
1. lg:title
2. lg:description
3. lg:tags
4. lg:url
5. lg:image
6. lg:creator
7. lg:index
The below code is an example of how Legitimate tags may look in a webpages \ section.
```markup
```
{% hint style="info" %}
Remember, all content on Legitimate is tied back to a profile. Before your content will be indexed on our site you must have a creator profile and creator tag.
{% 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 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.legitimate.net/user-guide/legitimate-tags.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.