-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Canonical Tags for Pagination on PLP #334
Comments
Hi @sja-dS |
hi @sja-dS Is page parameter the only one we should take into account? What about different parameters that also manipulates the content of the page like sorting or filtering? |
Hey @a-laurowski |
Hey @a-laurowski |
hi @sja-dS Please check the following PR if its suitable for you #338 My concern is that according to an article https://www.searchenginejournal.com/technical-seo/url-parameter-handling/#close any parameter which changes page content should be contained in the canonical link. I think this is something we need to discuss internally. The goal of the module is always to provide the best flexibility and perhaps we should consider a mechanism which allows user to at least select which kind of parameters (paging, sort order, filters) should be applied in the canonical link |
@a-laurowski |
hi @sja-dS For the time being, if you need this functionality, please add it to one of yours template. It could be placed anywhere in the DOM (after.body.start block in my opinion is good place), the most important thing is that it has to be wrapped inside the ffReady event listener if you want to be sure a given callback is successfully registered. |
Hi @sja-dS We have some new thoughts on this problem. We think that the only case to cover is to provide correct link only on initial rendering of the page, further asynchronous actions like changing page or filtering are irrelevant. As a proof of this way of intuition you can check the page source. It looks that dynamical changes on the canonical link are not contained there and page source is more or less this what web crawlers will see during their visit. |
Hey @a-laurowski |
When you are on a page, e.g.
https://www.myagrar.de/pflanzenschutzmittel/?page=2
the canonical Reference is<link rel="canonical" href="https://www.myagrar.de/pflanzenschutzmittel/">
but in this case it should reference tohttps://www.myagrar.de/pflanzenschutzmittel/?page=2
The text was updated successfully, but these errors were encountered: