TYPO3 Core

Richard Haeser wrote:

Why do you want to remove the page parameter? Paginated pages shouldn’t have a canocial to the first page and that is what happens when you remove the parameter.

You are right, Google said that the canonical tag should also include paginated pages.
But most seo tools complain about duplicate titles of the news list and paginated pages. So I would prefer to remove them from canonical tag.

But I can give you another example:
If you use news with categories (article can be related to multiple categories) and use them for filtering, you have to remove the category parameter from canonical tag to prevent duplicate content.

Example use case, where parameters shouldn't be added to canonical tag¶

There is an element that displays individually share-able content blocks. Therefore parameters are attached to the page url the content block is displayed on. If such a content block is shared, the og-tags fetched from the parametric url contain information of the content block and not of the page it's on, but the canonical tag should be the same as the target page still displays the same content.

Example code:

<f:for each="{ContentBlocks}" as="ContentBlock">
   <div id="content-block-1">
      <!-- content block content here -->
      <a href="https://www.facebook.com/sharer/sharer.php?u={f:uri.action(
          pluginName: 'ContentBlockSlider',
          controller: 'ContentBlock',
          action: 'ContentBlockSlider',
          arguments: '{contentBlock: contentBlock}', absolute: 1
       )}">Share me</a>
   </div>
</f:for>

The controller action then overrides the according meta tags. if a $contentBlock argument was provided.

There were several use cases where we had to use this approach to share different contents on one page.

Try to add your get Vars to:

$GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['excludedParameters']

list, worked in my case (v10 and v11).