Trailing Slash Normalization

Gruxi normalizes trailing slashes so URLs resolve to a predictable format. This helps avoid duplicate content issues and keeps links consistent for both users and search engines.

The normalization behavior in Gruxi works like this:

• If a request is made without a trailing slash (for example, http://example.com/path) and the path matches a directory on the filesystem, Gruxi returns an HTTP 301 redirect to the URL with a trailing slash (for example, http://example.com/path/).
• If a request is made to a file URL with a trailing slash (for example, http://example.com/path/myfile.html/), Gruxi returns HTTP 404 Not Found, because a trailing slash is not valid for a file resource.

Other SEO-related features

• Canonical hostname: Gruxi can be configured with canonical hostnames for sites, helping search engines understand the preferred URL for your content and avoid duplicate content issues across multiple hostnames. See Hostnames for more details.