Whenever a URL on your board changes (you rename a job's slug, retire a page, or migrate from another platform), every existing link to the old URL starts returning a 404. That loses visitors and, over time, the search ranking the old URL had earned. A redirect fixes both: visitors and search engines that hit the old path are sent to the new one, and a permanent (301) redirect tells search engines to transfer the old URL's ranking to the new one.
Plan availability
SEO redirects are available on the Advanced and Enterprise plans. On other plans the tab shows an upgrade prompt instead of the tool. See Your easyboard subscription.
Add a redirect
At the bottom of the sidebar, click Settings, open the SEO card, then click the Redirects tab.
Click Add redirect.
In Old path, enter the path that should stop 404ing, like
/jobs/old-slug. You can paste the full URL from your browser; the domain part is stripped automatically and the path is stored lowercase.In Redirect to, enter the destination, like
/jobs/new-slug. It must be a path on this board (starting with "/"); external URLs are rejected, so a redirect can never send your visitors off-board. It must also differ from the old path.Choose the Type: Permanent (301) (the default) tells search engines the move is final and transfers ranking; Temporary (302) keeps the old URL's ranking in place, for short-lived situations only.
Leave Active on and click Create.
You should see a "Redirect created" confirmation and the rule appears in the table with its old path, destination, type and an Active switch. Open the old URL on your board in a new tab: it should land on the destination. Redirects can take up to a minute to go live, so if it doesn't fire instantly, wait a moment and reload.
Edit, pause, or remove a rule
Edit: open the rule from the table to change any field; click Save.
Pause: flip the rule's Active switch off. The rule is kept but stops redirecting, handy while testing or when you temporarily bring an old page back.
Delete: remove the rule entirely from the row actions. The old path immediately returns to whatever it resolves to naturally (usually a 404).
How matching works
Matching is by exact path. A rule for
/jobs/old-slugdoes not catch/jobs/old-slug-2; create a rule per URL.Paths are matched case-insensitively, and a trailing slash is ignored, so
/Jobs/Old-Slug/still matches.Anything after
?or#in the old path is ignored for matching, but a query string on the destination is preserved, so you can redirect into a filtered page like/jobs?remote=true.Each old path can have only one rule. Creating a second shows "A redirect for this path already exists"; edit the existing rule instead.
When to reach for redirects
Migrating from another platform: map your top old URLs (from your previous board's analytics) to their new homes here before you switch DNS. This is the single biggest ranking-saver in a migration.
Renamed content: changed a blog post's path or a job's slug? Add a redirect from the old path the moment you save the rename. See Write blog posts on your board.
Retired pages: rather than letting a deleted page 404, redirect it to the closest surviving page, like a related search page or your jobs list.
A worked migration example
Suppose your old board had a job at /positions/1234-senior-designer and the same job now lives at /jobs/senior-designer-acme:
Click Add redirect.
Old path:
/positions/1234-senior-designerRedirect to:
/jobs/senior-designer-acmeKeep Permanent (301) and Active, click Create.
Open the old URL on your live board and confirm it lands on the new job page.
Repeat for each URL worth keeping. Prioritize by traffic: the top 20 to 50 URLs from your old analytics usually carry the large majority of your link equity. For pages with no good one-to-one match, redirect to the nearest useful list page rather than the home page; a relevant destination keeps more of the ranking signal.
Tip: prefer Permanent (301) unless you truly plan to bring the old URL back. A 302 left in place for months sends search engines mixed signals about which URL to rank.