> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements/site-quality/robots.txt.md).

# Robots.txt

How to add a robots.txt file to your Elements project

A robots.txt file tells search engine crawlers which parts of your website they can or can’t access. It sits at the root of your domain (e.g. <https://example.com/robots.txt>).

{% hint style="info" %}
A robots.txt file is a *request*, not a guarantee. Well-behaved bots obey it, but malicious ones may ignore it. It also does not prevent indexing of pages if they’re linked to elsewhere, use noindex meta tags for that.
{% endhint %}

### To add a robots.txt file in Elements:

1. Right-click in the Page List area of your project window and choose New File.
2. A new file named untitled.html will appear — rename it to robots.txt.
3. Double-click the file to edit its contents, and add any robots.txt directives you need.

This file will be published to the root of your website, making it accessible to search engines at <https://yourdomain.com/robots.txt>.

<figure><img src="https://3876014504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy6AECEVH2p4eFDicpM1%2Fuploads%2FvljSGJeNkPk4xUi81EyS%2FCleanShot%202025-05-09%20at%2012%E2%80%AF.58.24%402x.png?alt=media&amp;token=89825bfa-fde2-472d-a913-c1f34af2a1df" alt="A robots.txt file open in the Elements code editor at the project root"><figcaption></figcaption></figure>

### Example robots.txt file:

You can use this on your own site, just don’t forget to change the domain name to ensure you're pointing to your own sitemap.

```
User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml
```


---

# 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.realmacsoftware.com/elements/site-quality/robots.txt.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.