Skip to main content

Managing redirects is an important task for keeping your website's SEO rating high, and avoiding "page not found" issues.

Ryan Marshall avatar
Written by Ryan Marshall
Updated over a week ago

Introduction to Redirects

Syngency allows you to manage the various URLs on your website – whether they are Divisions, Talent Portfolios, Pages, or Posts. Read more about Syngency's URL structure here, or see below for where you can edit the URLs for different types of pages.

In some cases, you may want to change the URL of a page (such as a division), but search engines like Google will still be indexing the old URL, and if you change it, you may risk search engines pointing to "dead links". This will often have a negative effect on your site's SEO (Search Engine Optimisation).

To avoid this, you will want to create a Redirect. This will redirect the old URL to the new URL, and instruct any search engines with an existing index of your site's pages, that the URL has changed, and that the new URL should be indexed.

It also avoids the common "Page Not Found" error which will be displayed when the URL no longer exists, and there is no redirect to a new one.

Managing your redirects

Syngency provides a simple interface for managing your website redirects under Website > Redirects:

Here you will see a list all of the redirects which are currently active for your site:

You can click on an existing redirect to edit it, or click the + icon to add a new one:

In the example below, you may have renamed a division from Social Media Influencers to Influencers, and will want to add a redirect so search engines can follow the new URL:

Important: Syngency redirects should only be relative URLs. Don't add any TLDs (Top Level Domains – such as here).

Where to find your website URLs

You will find the URL field for each of these in different places:


In the Types modal of Settings > Types > Divisions:


In the Website URL field of the Details tab in the talent's profile:


In the URL field of the page settings:


In the URL field of the post settings:

Did this answer your question?