> For the complete documentation index, see [llms.txt](https://www.information-architecture.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.information-architecture.world/wiad-organizer-guide/your-local-website/findability-information-architecture-and-seo/page-naming-and-url-conventions.md).

# Page naming and URL conventions

## Editing an Event page’s title, link title, tag title, and slug

Every page in your GitBook  microsite has a few names, and each one shows up in a different place. You can change all of them from the **Edit page** dialog.

**To open it:** hover over the page in the left-hand page tree, select the **⋯** menu, and choose **Edit title and slug**.&#x20;

### The four fields at a glance

<table><thead><tr><th width="122.21484375">Field</th><th>Where people see it</th><th width="140.921875">Required?</th><th>Example</th></tr></thead><tbody><tr><td><strong>Title</strong></td><td>At the top of the page, and by default in search results</td><td>Yes</td><td>World IA Day Seattle 2027</td></tr><tr><td><strong>Link title</strong></td><td>The left-hand navigation and links to the page</td><td>Optional</td><td>Seattle 2027</td></tr><tr><td><strong>Tag title</strong></td><td>The browser tab and search engine results</td><td>Optional</td><td>World IA Day Seattle 2027 | Seattle Design Guild</td></tr><tr><td><strong>Slug</strong></td><td>The page’s web address (URL)</td><td>Yes</td><td>events/2027</td></tr></tbody></table>

<figure><img src="https://508943019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LbaXiKk_kXFzqhBjzTM-1703796690%2Fuploads%2FAP3Erl2fb8zjdxvmG3bm%2Fimage.png?alt=media&amp;token=42b6e843-86db-4882-9b81-76066487c6ac" alt="The GitBook Edit page dialog, showing the Title, Link title, Tag title, and Edit slug fields. The title reads “World IA Day Seattle 2027,” the link title reads “Seattle 2027,” and the slug reads “events/2027.”"><figcaption></figcaption></figure>

### **Title**

{% columns %}
{% column %}
The title is the main heading of the page. Write it so someone who has never visited your site understands what the page is about. GitBook also uses the title to help with search, so be specific.
{% endcolumn %}

{% column %}
**Examples**

* **Do:** “World IA Day Seattle 2027”
* **Don’t:** “2027” or “Event page”

{% endcolumn %}
{% endcolumns %}

### Link title (optional)

{% columns %}
{% column %}
The link title is a shorter version of the title that appears in the left navigation and in links to the page. Turn it on when the full title is too long for the sidebar.

In the example, the full title is “World IA Day Seattle 2027,” but the navigation shows “Seattle 2027.” Because the site is already for World IA Day Seattle, we just want to indicate that this is for the "Seattle 2027" event.&#x20;

This is also helpful for country-based microsites where you might have multiple locations in a country. For example, the Germany microsite will have "Cologne 2027" and "Berlin 2015."&#x20;
{% endcolumn %}

{% column %}
**Tips**

* Keep it recognizable. Someone scanning the sidebar should know where the link goes.
* Keep link titles consistent across similar pages.

**Examples**

* **Do:** "Seattle 2027"
* **Don't:** "World IA Day Seattle 2027"
  {% endcolumn %}
  {% endcolumns %}

### Tag title (optional)

{% columns %}
{% column %}
The tag title is what appears on the browser tab and as the headline in search results. When it’s off, GitBook uses the page title.&#x20;

Turn it on when you want search results to show something different from the on-page title, for example to add your city or organization name.&#x20;

If you aren’t sure, leave it off. It defaults to whatever you have in the title field.&#x20;
{% endcolumn %}

{% column %}
**Best practices**

* Aim for **under about 60 characters** so search engines don’t cut it off.
  {% endcolumn %}
  {% endcolumns %}

### Slug

{% columns %}
{% column %}
The slug is the last part of the page’s web address.&#x20;

In the example, the slug is `2027` inside the `events/` group, so the full address ends in `/events/2027`. This keeps the full URL short without repeating the title.&#x20;

**Example**

* seattle.worldiaday.org/events/2027

**URL structure**

* `location`.worldiaday.org/`group`/`slug`
  {% endcolumn %}

{% column %}
**Best practices**

* Lowercase, with hyphens between words (`call-for-speakers`)
* Short and descriptive
* Free of spaces, accents, and special characters. GitBook converts non-Latin characters into romanization.
  {% endcolumn %}
  {% endcolumns %}

**Be careful when changing a slug on a published page.** Anyone who saved or shared the old link may reach a “page not found” error. Be sure to set up a URL redirect when changing slugs. See *Handling renamed or removed pages (redirects)*.
