> For the complete documentation index, see [llms.txt](https://docs.frase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frase.io/troubleshooting-and-faqs/citations-internal-and-external-linking.md).

# Control Internal and External Links

Frase adds internal and external links while it writes your article. Here's what to expect, and how to add, change, or block links yourself.

## Set your linking rules

{% stepper %}
{% step %}

### Go to Brand Hub → Brand Voice

{% endstep %}

{% step %}

### Add your instructions under *Links & CTAs*

Frase follows these every time it writes.
{% endstep %}
{% endstepper %}

## Internal links

{% hint style="warning" %}
Internal linking needs a site audit. Without one, Frase has no map of your pages to link to, so [run an audit](https://docs.frase.io/core-workflows/audit-my-site) first.
{% endhint %}

What to expect when Frase writes:

* **5 to 8 internal links per article**, spread across sections. Frase never links the same URL twice in one article, and it uses fewer links rather than forcing them in.
* **Links go in as Frase writes.** They're added during generation, so they read like part of the content.
* **Frase picks pages by relevance.** You can't choose specific pages ahead of time.

### Add or change internal links

Edit any link in the editor after the article is generated. It's worth doing when:

* You want to link a new page that wasn't in your last audit
* A priority page (like a pillar page or key product page) has to be linked
* The anchor text could be more specific

## External links

What to expect when Frase writes:

* **Links come from research.** Frase cites the sources it found during [Research](https://docs.frase.io/feature-reference/deep-research), placed where they support a point. It doesn't make links up.
* **Only authoritative sources.** Sources below a minimum authority threshold are filtered out, and government, education, and established industry sources come first. Frase pulls from high-value primary sources before supporting ones.
* **No competitor links.** Frase never links to competitor domains on your account, no matter how authoritative they are.
* **No over-citing.** Frase tracks what it has already cited and doesn't repeat the same source throughout the article.
* **Links back up facts.** External links usually sit next to statistics and specific claims. That fact density helps your GEO score and makes AI systems more likely to [cite your content](https://docs.frase.io/core-workflows/ai-visibility-and-geo).

### Block sites from being cited

Add domains to your *Blocked Domains* in **Site Settings**. Frase won't cite them in any article for that site, whatever their authority.&#x20;

<figure><img src="https://3311323497-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fm4GQuvaZPL4j5tqamFyy%2Fuploads%2FNLOK12A4rebcM2cyr9H7%2Fimage.png?alt=media&amp;token=30a35bc9-90dd-4e11-acc6-80ddf02fc21d" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Use these for competitors, low-quality sites, or anything you don't want referenced.
{% endhint %}

### Add or change external links

Edit any link in the editor after the article is generated. A few rules of thumb:

* Cite a credible source for every major claim or statistic. A 2,000 word article might have 6 to 8 external links, and that's fine.
* Link to the original study or report itself, rather than an article that mentions it.
* If you add a statistic yourself, link to where it came from.
* Skip competitor domains, even when the content is relevant.


---

# 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.frase.io/troubleshooting-and-faqs/citations-internal-and-external-linking.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.
