We're currently in the process of building a new site in Umbraco 7. Our old site has 10,000's of pages which will need redirecting to the new url structure.
Is it acceptable to redirect to a node id (eg example.com/56789) if a "pretty" url has been set in the rel=canonical tag?
for example:
old url: example.com/news/truncated-headline-goes-here/12345
Redirecting (301 Permanent) to a page with a canonical meta tag describing the preferred URL should be fine for solving the problem, you describe.
However, make sure to provide absolute URLs for the canonical meta tags, e.g. http://example.com/news/truncated-headline-goes-here/12345 as opposed to example.com/news/truncated-headline-goes-here/12345 or/news/truncated-headline-goes-here/12345.
Note that you must also include the canonical meta tag on the canonical page itself.
Best practice for page redirects
Hi All,
We're currently in the process of building a new site in Umbraco 7. Our old site has 10,000's of pages which will need redirecting to the new url structure.
Is it acceptable to redirect to a node id (eg
example.com/56789) if a "pretty" url has been set in the rel=canonical tag?for example:
old url:
example.com/news/truncated-headline-goes-here/12345redirects to:
example.com/56789canonical:
example.com/news/year/month/day/full-headline-goes-hereThanks.
Redirecting (301 Permanent) to a page with a canonical meta tag describing the preferred URL should be fine for solving the problem, you describe.
However, make sure to provide absolute URLs for the canonical meta tags, e.g.
http://example.com/news/truncated-headline-goes-here/12345as opposed toexample.com/news/truncated-headline-goes-here/12345or/news/truncated-headline-goes-here/12345.Note that you must also include the canonical meta tag on the canonical page itself.
Source: Google Search Console Help > Content guidelines
is working on a reply...