Set Up 301 Redirects
Preserve SEO equity when migrating to Cavuno by redirecting old URLs to new ones.
A 301 redirect permanently sends visitors and search engines from an old URL to a new one. If you're migrating an existing job board to Cavuno, redirects ensure your existing links, bookmarks, and search rankings continue to work. Without them, every inbound link to your old URL structure returns a 404, and you lose the SEO equity those pages have built up over time.
When to use redirects
Redirects are most important during platform migrations where your old job board used different URL patterns (for example, /careers/engineer instead of /jobs/senior-engineer). They're also useful after URL restructuring or when other websites link to paths on your domain that have changed.
Add a redirect
- Go to Board settings in the sidebar and click the Domains tab
- Click Add redirect
- Enter the Source path (the old URL path, starting with
/) - Enter the Destination (the new URL path or a full external URL)
- Click Add redirect
The redirect takes effect immediately. You can use the source path hint (.*) for wildcard patterns, and the destination hint %1, %2 for capture group replacements.
Redirect types
Exact redirects
An exact redirect matches a single path. For example, source /careers/engineer redirecting to destination /jobs/senior-engineer-at-acme. The table shows these as "Static" type.
Wildcard redirects
Wildcard redirects use regex capture groups to match patterns. Use (.*) to capture any text, then reference it with %1, %2, etc. in the destination.
For example, source /blog/(.*) with destination /articles/%1 redirects /blog/my-post to /articles/my-post. For multiple capture groups, source /archive/(.*)/(.*) with destination /content/%1/%2 redirects /archive/2024/my-post to /content/2024/my-post.
Bulk import with CSV
For large migrations, upload a CSV file instead of adding redirects one at a time. The CSV needs two columns: old_path and new_path. Maximum 1,000 redirects per import.
1234old_path,new_path/old-page,/new-page/blog/(.*),/articles/%1/about,https://example.com/about
- Click the three-dot menu next to the Add redirect button
- Click Import CSV
- Upload your CSV file
- Review the preview and click Import
You can also export your existing redirects as CSV using Export CSV from the same menu.
Reserved paths
You cannot create redirects for paths already used by Cavuno, including /jobs, /companies, /blog, /post, /password, /auth, /home, /admin, /api, /boards, /_next, /images, /assets, /locales, /sitemap.xml, /robots.txt, /favicon.ico, and /rss.xml. This prevents accidentally overriding working pages.
How redirects work
Redirects only apply to paths that don't match any existing Cavuno route. When a visitor lands on an unrecognized path, Cavuno checks your redirect rules. Exact matches are checked first, then wildcard rules in priority order. If a match is found, the visitor is permanently redirected (HTTP 301/308). If no match is found, a 404 page is shown.
Setting up redirects during migration is one of the most important steps for preserving your search rankings. Search engines follow 301 redirects and transfer most of the original page's ranking signals to the new URL. For more on migration SEO, see Technical SEO.