Allow users to add <meta rel="canonical"> tags to site pages

[mlocati]

Currently, a single page may have multiple URLs:

• www.example.com/test
• www.example.com/index.php/test
• www.example.com/?cID=123
• www.example.com/index.php?cID=123

That's not good for search engines: they see duplicated contents at different URLs.
Let's tell them that all these URLs are for the same page (www.example.com/test)

[KorvinSzanto]

This looks good to me, @aembler what do you think?

[KorvinSzanto]

@mlocati resolve conflicts and I think this is good to merge.

[mlocati]

resolve conflicts

Done

[biplobice]

@mlocati Thank you for this feature. We're facing a different issue.
For example, we have the following URL.
https://example.com/action/param
But when there is a reference link from facebook/twitter/google it adds some parameters like-
https://example.com/action/param?utm_content=buffer539cd3&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

So, the canonical URL also get the same value. Our client wants to remove this get parameters from the canonical URL. I know you already have added an option excluded_querystring_parameters. But I think it would be a long list for our client. What could be the best solution for it then?

[mlocati]

The only solution I see is to add utm_content, utm_medium, utm_source, utm_campaign and so on to the value of the seo.canonical_tag.excluded_querystring_parameters site configuration key...

[biplobice]

Thank you.

[hissy]

The only solution I see is to add utm_content, utm_medium, utm_source, utm_campaign and so on to the value of the seo.canonical_tag.excluded_querystring_parameters site configuration key...

Thank you @mlocati , but if so, we should add some get parameters from popular search engines and social networking sites into the default config file, didn't it?

[mlocati]

@hissy what about creating a file located at /application/config/site.php with this contents?

<?php

return [
    'sites' => [
        'default' => [
            'seo' => [
                'canonical_tag' => [
                    'excluded_querystring_parameters' => [
                        'cID',
                        'ccm_token',
                        'utm_content',
                        'utm_medium',
                        'utm_source',
                        'utm_campaign',
                    ],
                ],
            ],
        ],
    ],
];

[hissy]

@mlocati Yeah, I can do that because I know about concrete5 config system well, but most of the beginners are not.

[mlocati]

I agree.
I'd collect the various querystring parameters defined by the different search engines/ads systems (Google, Bing, Facebook Pixel, ...) and add them to the default list.

[hissy]

We should ignore query and search_paths too. Search block uses these parameters, so it will be attached to the canonical URL on the search result. It's annoying.

[hissy]

I'd collect the various querystring parameters defined by the different search engines/ads systems (Google, Bing, Facebook Pixel, ...) and add them to the default list.

@mlocati Any updates on this issue? Should I create a new open issue about this?

[mlocati]

Should I create a new open issue about this?

I think it's a good idea: comments in merged pull requests aren't a great place to write about new issues, since they are somehow "hidden"