-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Improper Handling of Pagination SEO #14971
Comments
I also need to correct this issue |
@winterk80, thank you for your report. |
Hello, |
#mmuk2019 Assign to me |
@benathomeofchampions thank you for joining. Please accept team invitation here and self-assign the issue. |
Hi @benathomeofchampions. Thank you for working on this issue.
|
This removes the p= query string parameter in pagination for the first page, when navigating back to page 1, to avoid duplicate content SEO issues.
#mm19pl |
Hi @Nekoozu. Thank you for working on this issue.
|
Hi @winterk80. Thank you for your report.
The fix will be available with the upcoming 2.4.0 release. |
Preconditions
Magento 2.1.x or 2.2.x
Steps to reproduce
Go to a category with 3 or more pages
Goto page 2
When you click back to page 1 OR click previous button it appends ?p=1 to the url
Expected result
?p=1 should not be appended to the url. This creates a duplicate page. Even though the url is canonical this degrades SEO page authority because you have created a duplicate page in Google and Bing's eyes by appending the ?p=1 to the url Should be the original page url without ?p=1 appended
https://webmasters.googleblog.com/2011/09/pagination-with-relnext-and-relprev.html
https://support.google.com/webmasters/answer/1663744?hl=en
https://moz.com/blog/seo-guide-to-google-webmaster-recommendations-for-pagination
Actual result
Magento appends a ?p=1 to the page one url and the previous button, creating a duplicate content problem.
This also creates a problem with rel="next" rel="prev" when you try to implement because magento is creating the duplicate page with ?p=1 for page one.
The text was updated successfully, but these errors were encountered: