Domains, URLs und Slugs

In the following we explain the most important terms and contexts of a Uniform Resource Locator (URL) in the context of search engine optimisation in TYPO3.

 

Structure of a URL

A URL defines where a resource (e.g. a web page, a PDF, an image, a video, etc.) can be found. It can consist of the following components:

 

What should I keep in mind when using URLs?

  • URLs should be as simple, understandable and clear as possible. Based on a URL, visitors should already know as precisely as possible what to expect.
  • Put relevant keywords in the entire URL path in a meaningful way. Keep in mind: The longer the URL, the less effective the keywords it contains.
  • Separate keywords with hyphens

Slugs

When it comes to the exact designation of a URL for a single web page, the so-called slugs play the most important role (protocol, domain, etc. are constant).

 

In the page properties of a page, you can set slugs individually via the URL Segment field:

If the URL segment field is left empty, TYPO3 automatically determines the slug based on the page structure (see page tree in the middle column of the TYPO3 backend) and the page name. Spaces are replaced by a hyphen and all letters are written in lower case.

 

Example:

If a page called "SEO with TYPO3" is in the page tree under "Our services" -> "Search engine optimisation" the slug reads:

usere-services/search-engine-optimisation/seo-with-typo3

The URL would then be (for an https-encrypted website with the domain example.de):

example.co.uk/our-services/search-engine-optimisation/seo-with-typo3

As a rule, you should not change the slug manually, as this will eventually become too confusing. Since the page tree also represents the structure of your website, the automatic generation by TYPO3 also follows the Google Guidelines for Webmaster.


Notes on a domain

With regard to a domain the following should be noted:

 

  • Select a main domain (recommendation without "www") and have all other domains forwarded to it
  • Avoid redirects of the start page. The call xyz.de, for example, should not forward to an address xyz.de/ueber_uns, as this increases the loading time (another connection must be established for the forwarding)
  • Avoid the use of parameters as much as possible
  • Offer all your content under a subdomain (e.g. "xyz.de/shop" is preferable to the domain "shop.xyz.de").