Basker Docs

Redirects

Add redirects, and keep old URLs working when a page's address changes

A redirect sends a visitor from one URL to another. Add one manually from the Redirects screen, or create one automatically when you change a page's URL.

When to add a redirect manually

  • A page on your old website (before Basker) needs to point to its new home on your Basker site.
  • A campaign URL that doesn't correspond to any page (example.com/winter-2026) should land on a specific event or page.
  • A typo in your domain or printed materials needs to redirect to the correct URL.
  • An event or page has been removed but its old URL is still being shared.

Redirects when a URL changes

Moving a page in the site tree does not create a redirect: the old URL stops working as soon as the move is published.

Changing a page's slug is different. When you edit the slug, including by renaming the page if its slug is set to generate from the title, Basker offers a Create a URL redirect option next to the slug field. Tick it before publishing to keep the old URL working. If the page has descendants, ticking it also redirects their old URLs.

Redirects created this way appear in your site's redirect list alongside the ones you add manually.

Add a redirect

Open Redirects under Website in Basker. The screen is subtitled Set up URL redirects for moved or renamed pages.

Click Create New

Click CREATE NEW to open the redirect editor.

Set the From URL

Enter the From URL (required): the path being redirected, starting with /. For example, /winter-2026. Don't include your domain.

Choose how the From URL is matched

Set the Match type to control which incoming URLs the redirect applies to:

  • Exact (default): only the exact From URL is redirected. /winter-2026 matches /winter-2026 and nothing else.
  • Starts with: any URL beginning with the From URL is redirected. /archive also catches /archive/2024 and /archive/2025/spring.
  • Contains: any URL that includes the From URL anywhere in its path is redirected.

Use Exact for one-to-one redirects; it's the default and what the Create a URL redirect option uses. Reach for Starts with or Contains to retire a whole group of old URLs with a single rule.

Pick the To URL Type

Choose the To URL Type:

  • Internal link (default): point at one of your existing pages, events, posts, or other published records via the Document to redirect to picker. The destination updates automatically if the target page is moved or renamed.
  • Custom URL: enter a free-form URL the redirect lands on. Use this for redirects that point outside your Basker site or to a path that doesn't correspond to a record.

Save

Click Save. The redirect takes effect immediately: visitors hitting the From URL are now sent to the destination.

A worked example

A common case: a print campaign sends visitors to /winter-2026 and you want everyone hitting that URL to land on the season-opener event page.

  • From URL/winter-2026
  • To URL Type → Internal link
  • Document to redirect to → the season opener event

Save and the redirect is live. Visitors typing or clicking /winter-2026 are sent straight to the event. Because it's an internal link, if you later rename the event or move it in the tree, the redirect destination keeps pointing at the right page automatically.

Permanent versus temporary

Most redirects in Basker are permanent (HTTP 301). Permanent redirects are how you preserve search rankings when content moves. Use them by default.

Temporary redirects exist for specific cases: a campaign URL that should stop redirecting after the campaign ends, or a redirect during a maintenance window. Use them sparingly.

Query parameters and tracking

Query parameters in the incoming URL (including UTM tags and promo codes) are preserved and forwarded to the destination.

Example: a redirect from /tickets to /events/summer-show will forward /tickets?promo=12345&utm_source=instagram as /events/summer-show?promo=12345&utm_source=instagram. You don't need to do anything extra to make this work.

If the destination URL already contains a parameter with the same name as one in the incoming URL, the destination's value takes priority.

Where to go next

On this page