---
title: Links
description: Write and format links in documentation.
image: https://developers.cloudflare.com/cf-twitter-card.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/style-guide/llms.txt  
> Use this file to discover all available pages before exploring further.

[Skip to content](#%5Ftop) 

# Links

Follow these guidelines for link text.

## Create links

Use the path to the product when creating a link.

* **Do**:  
   * `This is a link for Cloudflare WAN's [Get started](/cloudflare-wan/get-started/)`
* **Don't:**  
   * `This is a link for Cloudflare WAN's [Get started](https://developers.cloudflare.com/cloudflare-wan/get-started/)`

**Also not supported:**

* Relative links: `` A link to [`DurableObjectNamespace::get`](./namespace) ``
* Using the file extension in links: `This is a link for Cloudflare WAN's [Get started](/cloudflare-wan/get-started.mdx/)`

## Standard text

As much as possible, use text that follows one of these patterns:

* `For more information, refer to [<PAGE_TITLE>](LINK).`
* `To <DO_SOMETHING>, refer to [<SECTION_TITLE>](LINK).`

Do not use the following constructions:

* `Learn more about...`
* `To read more....`
* `For more information, refer the [Merge requests](LINK) page.`
* `For more information, refer the [Merge requests](LINK) documentation.`

## Descriptive link text

The more descriptive your link text, the easier it is for people to navigate your site and for Google to understand what you are linking to.

Practically, this means you should avoid link text like `here`, `this page`, or `read more`.

For example, instead of:

* `For more information, refer to [this page](LINK).`
* `For more information, go [here](LINK).`

Use:

* `For more information, refer to [set up Cloudflare](LINK).`

## Dashboard link text

When directing users to the Cloudflare dashboard, use the following convention:

```

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.

2. Go to **DNS** > **Records**.


```

```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/style-guide/","name":"Style Guide"}},{"@type":"ListItem","position":3,"item":{"@id":"/style-guide/formatting/","name":"Formatting"}},{"@type":"ListItem","position":4,"item":{"@id":"/style-guide/formatting/structure/","name":"Structure"}},{"@type":"ListItem","position":5,"item":{"@id":"/style-guide/formatting/structure/links/","name":"Links"}}]}
```