Pro plan

Vanity slugs

Create readable custom URLs for your documents using vanity slugs instead of random short IDs.

A vanity slug is a custom name you assign to a document, replacing its auto-generated short ID with a readable URL. Slugs are Pro-only and only resolve on your verified custom domain—they have no effect on everypage.co.

Setting a vanity slug

To name a document, open its sharing settings and look for the "Custom Link" field. Type your preferred name (lowercase letters, digits, and single hyphens only; up to 64 characters). When you have an active, verified custom domain, the preview shows you the full URL on your domain—for example, https://documents.example.com/annual-report.

If you don't yet have a verified custom domain, the field is disabled. Add and verify one in your Account settings first; slugs depend on it.

Character rules and validation

Slugs accept lowercase letters (a–z), digits (0–9), and hyphens. The following rules are enforced:

  • Must start and end with a letter or digit (no leading or trailing hyphens)
  • Hyphens must be single—no double or consecutive hyphens
  • Maximum 64 characters
  • Anything you type is lowercased before it is saved, so My-Report and my-report are the same slug
  • Unique per owner: you cannot assign the same slug to two different documents on your account
  • A slug shaped like a UUID is rejected, because UUID-shaped paths resolve as UUIDs first and the slug would never be reached

If you try to use a reserved word (such as api, docs, pricing, or login), the save is rejected because those paths belong to EveryPage itself.

Slug resolution and custom domains

This is the critical constraint: a slug only resolves to its document when accessed on your active, verified custom domain. Accessing the same slug on everypage.co returns 404. This is by design—slugs are guessable, so they only work on a host that is bound to one owner (your custom domain), never the public canonical host where thousands of files live.

If your custom domain is not yet verified, or becomes inactive because verification is removed or the account is no longer Pro, slug URLs stop working. Nothing redirects: the slug URL simply stops resolving, and the document remains reachable through its short ID or full UUID, which resolve on every host.

Renaming and consequences

You can change a document's slug at any time. A renamed slug breaks any link already shared under the old name—visitors who click the old URL get 404. Inform recipients if you rename a link after sharing.

Because of this, slugs are poor choices for permanent shared links. If you need a link that never changes, use the document's short ID instead, which is immutable. Frozen artifacts (QR codes, embedded viewers, and oEmbed) always use the short ID or UUID, never the slug, to ensure those links stay valid even if you rename the document later.

Clashes and per-owner uniqueness

Each slug you create must be unique within your account. If you try to assign a slug that is already in use on another of your files, the save is rejected (HTTP 409). Rename one of the conflicting slugs and try again.

A document you have moved to trash keeps its slug reserved until it is purged, so the name is not immediately free for another document.

Different owners can use the same slug name on their own custom domains—the uniqueness constraint is per owner, not global.

See also