Sitefinity’s canonical URLs implementation, addresses the following issues:
Inserting Canonical URL meta tag handles these cases. This tag tells the search engine what is the page where the item opens by default. It can be inserted either in the <head> tag of the page HTML or in the HTTP request. Sitefinity CMS adds the tag inside the <head> tag of the page.
For example, <link rel="canonical" href="http://www.example.com/dresses/greendress.html">
For more information about canonical URLs, see About rel="canonical" and The Canonical Link Relation.
To configure Sitefinity CMS to use canonical URLs, perform the following:
In Sitefinity CMS, there are static and dynamic pages. The static pages are the pages in the Pages grid in Sitefinity CMS backend. The dynamic pages are static pages with some appendix in their URL that changes their output. For example, if a static page is http://mysite.com/home the dynamic page could be http://mysite.com/home/myNews and it will display the news item myNews in its detail mode.
You can turn on and off the canonical links for a static and for dynamic pages separately. You can enable and disable canonical URLs for static pages on site level and on page level. The page-level setting overrides the site-level setting. You control dynamic pages canonical URLs by setting canonical URLs on widget level.
For static pages, you have an option to have query string parameters in the canonical URL. As the canonical URL is generated using the current request, by filtering the query string parameters, you can specify a list of the parameters that must always be preserved. You must add only parameters that lead to modification of the page content – for example, paging parameters. The rest of the parameters will be ignored, if they do not change the page content –for example, they could be some referral information, tracking info etc.
To define query string parameters, click Administration » Settings » Advanced » System » Content Locations » Page Default Canonical Url Settings » Allowed Canonical Url Query String Parameters and use the Create New button.
By default, a Sitefinity CMS parameter for paging is predefined in order to be preserved in canonical URL when paging that uses QueryString parameters is used.
Each widget has a property named SetPaginationUrls, which controls weather to add the pagination URLs in the head of the page, if the content is paginated. The widget generates the previous and next links of the paginated series in the following way:
<link rel=”next” href=”http://localhost/next/page/of/paginated/series?with=parameters” />
<link rel=”prev” href=”http://localhost/previous/page/of/paginated/series?with=parameters” />
To property is enabled, by default. To disable it, open the widget for editing, click its Advanced button, and in SetPaginationUrls enter true or false. First, you must have enables canonical URLs.
After you have configured the canonical URLs for the entire site, you can switch on and off canonical URLs for particular widgets.
It makes sense to do this only on pages where items are displayed in detailed view. For example, in order for an image to have canonical URL generated and inserted, you must publish a page with the Image gallery widget on it. When you browse this page, it does not create a canonical URL for the image until you click the image and display it in details view.
You can manage canonical URLs individually for the following widgets:
To configure canonical URLs on widget level, perform the following:
NOTE: If a canonical meta tag is already added to the <head> tag of a page and the widget on the page is set to open content items in auto-generated page, you must delete the meta tag added to the page, by clicking the Actions link of the page, opening Titles & Properties and then expanding the Advanced settings.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity