IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
Allowing users to submit comments for your website content can be a valuable source of feedback and also promote discussions. Comments, however, should be treated carefully to avoid undesired content appearing on your website or spam attacks generating extra cleanup work for content editors and forum moderators.
One important aspect where Sitefinity CMS lets you control comments behavior is in determining whether search engines should crawl hyperlinks in untrusted content. Untrusted content represents comments posted by site visitors. For example, comments for News, Blogs, Forum posts and so on. This can help you prevent any undesired SEO ranking "leak" from your domain to other domains.
To control this behavior you go to Administration » Settings » Advanced. In the left pane, expand System and click SEO and OpenGraph properties. There are 2 properties that you can configure:
NOTE: Projects created with Sitefinity CMS versions older than 11.1 will have the Append "nofollow" attribute to links in untrusted content property set to true after an upgrade to 11.1 or newer version. New comments posted on the site will get screened for untrusted links. If any comments already exist in such projects prior to the upgrade, their content will not be automatically processed. You need to republish the comments to have rel="nofollow" applied to the links from untrusted domains. You can do that through the Sitefinity CMS administrative UI by going to Content » Comments.
For more information about the mechanisms Sitefinity CMS exposes to control the behavior of user comments see Administration: Enable comments and ratings. Developers can also refer to For developers: Comments events for a list of extensibility points allowing custom implementation and integration with spam protection services.
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