Redirects in Composer route visitors from outdated or alternate URLs to the correct page without 404 errors, including options for wildcard matching, 301 (permanent) or 302 (temporary) redirect types, and bulk import. This article covers adding redirects, when to add them, and managing vanity URLs.
đź’ˇQuick answers
- Where is the Redirects feature located? In Composer's left-hand navigation, under the Composer section.
- Adding a new redirect? Click +New Redirect in the top right. Enter the From URL (full URL with protocol and hostname), enable Wildcard if needed, choose Redirect to Page (Page Picker) or Redirect to URL, pick 301 or 302, and save.
- 301 vs 302: which redirect type to use? 301 (Permanent) for permanent URL changes; preserves SEO value and analytics. 302 (Temporary) for short-term redirects (seasonal pages, maintenance); does not preserve analytics tracking.
- What does Wildcard matching do? Redirects any URL that begins with the specified path to a single destination. For example, enabling wildcard on /blog redirects /blog/summer, /blog/winter/dec/old, and any other /blog/* path to the same target.
- Can redirects be added before launch? Yes for new clients. Use the final domain (not the staging domain); redirects automatically activate after launch. Redesign clients should NOT add redirects before launch since they affect the existing live site.
- Why use the Page Picker for redirect destinations? The redirect binds to the page ID, not to the domain or page name. The redirect keeps working even if the domain or page name changes later.
The Redirects area is Finalsite’s built-in tool for managing URL redirects across your site. It helps ensure that visitors who use outdated, shortened, or alternate URLs are seamlessly directed to the correct page, without encountering 404 errors.
Redirects are especially important during site launches, redesigns, and content restructuring. They also support accessibility, SEO, and user experience by preserving link equity and reducing confusion.
This article will show you how it works!
In this Article
This feature is found in Composer’s left-hand navigation.
Why use Redirects?
Redirects aren’t just a technical fix. They’re a powerful way to preserve trust and continuity.
- Keep users on track: Redirects automatically guide visitors from outdated links to the correct Composer page, preserving user experience and avoiding confusion.
- Streamline your workflow: Skip manually creating a Redirects branch and set redirects directly.
- Search and filter with ease: Redirects are searchable and can be filtered by columns for quick management.
- Import in bulk: Add multiple redirects at once in bulk to save time and reduce manual entry. Reach out to your implementation team or Finalsite Support for assistance with bulk import.
- Scale effortlessly: Built to support large sites and frequent updates with minimal effort.
It’s a small step that makes a big difference in keeping your digital presence strong and connected.
Add a new redirect
+ New Redirect: Add redirects by clicking the + New Redirect button in the top right corner.
-
From URL: Enter a full URL with protocol (http:// or https://), and hostname.
- For example: https://www.finalsite.com/about/team.
-
Enable wildcard matching: This option allows you to redirect any URL that begins with a specified path to a single destination page.
- For example: Enabling wildcard matching for https://www.finalsite.com/blog will redirect all URLs that start with that path, such as https://www.finalsite.com/blog/summer or https://www.finalsite.com/blog/winter/dec/old, to redirect to the same target page.
- Useful for managing dynamic or seasonal content under a shared directory.
- Simplifies redirect management and ensures consistent user experience across related content paths.
- Redirect to Page: Select a page from the Page Picker.
Use Page Picker to bind redirects
When selecting a destination page using the Page Picker, the redirect binds to the page ID, not to the domain or page name. This ensures the redirect continues to work even if the domain or page name changes (e.g., during a redesign or domain migration).
-
Redirect to URL: Enter a full URL with protocol (http:// or https://), and hostname.Â
- For example: https://www.finalsite.com/about/team.
-
Select 301 or 302: Choosing the correct redirect type helps preserve search engine optimization (SEO) and ensures the right behavior for users and crawlers.
-
301 (Permanent):
- Use when the original URL has been permanently replaced
- Tells browsers and search engines to update their records
- Transfers SEO value (e.g., page rankings) to the new URL
- Preserves site analytics tracking
- Ideal for retired pages, restructured content, or long-term changes
-
302 (Temporary):
- Use when the redirect is only needed for a short time
- Tells browsers and search engines not to update their records
- Does not preserve site analytics tracking
- May be handled inconsistently by different search engines
- Best for seasonal pages, temporary campaigns, or maintenance windows
-
301 (Permanent):
Use full URLs for redirect accuracy
When setting up a redirect, the From URL must include the full protocol (http:// or https://) and a domain that matches one of the verified hostnames associated with your site.
For example:
If you're redirecting to a page on the same domain as the To URL, simplify the From URL by using just the path.
For example:
/about/team
Always use full URLs with https:// in both the From and To fields to ensure proper redirect behavior and avoid issues with domain mismatches or incorrect hierarchy.
When to add redirects
Before launch
Add redirects manually or via upload before your site goes live.
- Always use the final domain (e.g., www.bedford.k12.mi.us)—not the staging domain (e.g., bedfordk12mius.finalsite.com)
- Redirects added pre-launch will automatically update to reflect the live domain after launch
- The Redirects Manager interface will show the staging domain pre-launch but will switch to the live domain post-launch.
Redesign clients should not add redirects before launch
If you're a redesign client, do not add new redirects before launch. Doing so will affect your current live site and may disrupt existing traffic. Only new clients (without a live site) should add redirects prior to launch.
After launch
Once your site is live, redirects go into effect immediately and begin routing traffic from old URLs to the new destinations.
- You can continue to add, edit, or remove redirects at any time
- Redirects are searchable and filterable, making it easy to manage large sets of vanity URLs or legacy paths
Manage vanity URLs in Redirects feature
A vanity URL is a short, memorable link that redirects users from a longer or harder-to-remember address. Use the Redirects feature to manage these URLs easily. You can add them one at a time or import in bulk (with the help of your implementation team or Finalsite support), helping your community find what they need faster without creating a separate Composer branch.
After adding redirects, you will see all of your current redirects listed in the following columns where you can manage your data.
- From URL: This is the original location of a redirect.
- To Page: This link shows where the page is redirected to.
- Type: Is this link a 301 or 302? (link to above spot)
- Wildcard: A green checkmark in this column tells you if Wildcard matching has been enabled.
- Edit/Delete: Edit each redirect’s settings or delete it from your list.
Comments
Please Sign in to leave a comment if you don't see the comment box below.