White-/Blacklist for sitemap parameters

[KreativeKrise]

Would it be possible to add a constant where we can set a white- or blacklist for GET parameters? Often there are URLs with tracking parameters like "utm_source".

It would be nice to exclude URLs with such parameters from the sitemap generation.

Or is that already possible? I didn't find any information..

Thank you in advance!

[thomaszbz]

Which version of metaseo, TYPO3 and PHP are you using? Do you have realurl enabled and which version do you use?

I get the idea: These parameters can lead to duplicate content (multiple URLs with same content). For instance, you can also exclude these parameters at e.g. google search console and e.g. piwik analytics (while the latter does not use metaseo's sitemap).

How exactly do you create these get parameters? Using an extension? Does TYPO3 know something about these parameters or do you just add them outside of the scope of TYPO3?

I need to reproduce this issue first, to see if it really happens and if it creates new entries with 2.0.0. Did you try this out already?

What happens with your canonical tag when you use such parameters?

[KreativeKrise]

Metaseo 1.0.8
TYPO3 6.2.25
PHP 5.4.41

Realurl is enabled.

These parameters are created by an external newsletter service. It adds the tracking parameters for Google Analytics to the links inside the newsletter.

I will try version 2.0.0 on Monday if it maybe fixes the problem!
The canonical tag I have to check also on Monday because I don't use the functionality of metaseo.
So I will response on Monday!

Have a great weekend :)

[thomaszbz]

I'm not sure if 2.0.0 fixes the problem, but we fixed many many bugs since 1.0.8. 1.0.x is not supported any more (We still support 6.2 with 2.0.0).

But there's one regression which is not yet fixed in 2.0.0: #233 in case you have a full-blown hoster's environment, together with TYPO3 6.2. A fix is available in metaseo's develop branch, however.

[KreativeKrise]

I tried 2.0.0 and URLs with "wrong" GET-parameter generate an entry inside the sitemap.xml.
An option similar to metaTags.canonicalUrl.strict = 1 for the sitemap.xml would be great. Even better would be a whitelist for GET-parameters :)

[thomaszbz]

What happens if you use a parameter which is new to TYPO3 (not configured somewhere)?

E.g. http://www.example.com/some-page.html?thisisnew=1

• Is this parameter still added to the sitemap
• What does your canonical tag look like in the html source code in that case?

[KreativeKrise]

If I add a parameter like ?thisisnew=1 then it generates a new sitemap entry.
The canonical tag is fine, as long as I use metaTags.canonicalUrl.strict = 1.

[thomaszbz]

I've been able to reproduce this issue in the meantime, at least with parameters which are new to TYPO3. The entries originate from a live instance with metaseo 2.0.0, TYPO3 >= 6.2.26, before upgrading to 6.2.27

This is misbehaviour in respect to SEO. Maybe there is a way to mitigate this via configuration. If not, it could still be considered buggy somehow, while supporting external parameters still might be a feature which is new to metaseo.

Related: #268 potentially (partly) fixes this issue. We need to see if TYPO3 6.2.27+/7.6.11+ still have this issue.