Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improper Handling of Pagination SEO #14971

Closed
winterk80 opened this issue May 3, 2018 · 10 comments
Closed

Improper Handling of Pagination SEO #14971

winterk80 opened this issue May 3, 2018 · 10 comments
Assignees
@chickenland
Labels
Component: Catalog Event: mm19pl Event: mmuk2019 Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@winterk80
Copy link

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.
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label May 3, 2018
@yumicom
Copy link

yumicom commented May 8, 2018

I also need to correct this issue

@ghost ghost self-assigned this Jul 18, 2018
@ghost ghost added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Component: Catalog SEO Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Jul 19, 2018
@ghost
Copy link

ghost commented Jul 19, 2018

@winterk80, thank you for your report.
We've acknowledged the issue and added to our backlog.

@ghost ghost removed their assignment Jul 19, 2018
@sidolov sidolov removed the SEO label Jul 31, 2018
@winterk80
Copy link
Author

Hello,
It's been 4 months, when will there be a solution?

@benathomeofchampions
Copy link

#mmuk2019 Assign to me

@magento-engcom-team
Copy link
Contributor

@benathomeofchampions thank you for joining. Please accept team invitation here and self-assign the issue.

@benathomeofchampions benathomeofchampions self-assigned this Jun 18, 2019
@m2-assistant
Copy link

m2-assistant bot commented Jun 18, 2019

Hi @benathomeofchampions. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 3. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

benathomeofchampions added a commit to benathomeofchampions/magento2 that referenced this issue Jun 18, 2019
@benathomeofchampions
magento#14971: Improper Handling of Pagination SEO
ab9d188 
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.
Closed
4 tasks
@Nekoozu
Copy link

Nekoozu commented Sep 15, 2019

#mm19pl

@magento-engcom-team
Copy link
Contributor

@Nekoozu thank you for joining. Please accept team invitation here and self-assign the issue.

@Nekoozu Nekoozu self-assigned this Sep 15, 2019
@m2-assistant
Copy link

m2-assistant bot commented Sep 15, 2019

Hi @Nekoozu. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

@ghost ghost unassigned Nekoozu Oct 10, 2019
@chickenland chickenland mentioned this issue Oct 28, 2019
Merged
@ghost ghost assigned chickenland Oct 28, 2019
@VladimirZaets VladimirZaets added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Jan 9, 2020
@VladimirZaets
Copy link
Contributor

Hi @winterk80. Thank you for your report.
The issue has been fixed in #25337 by @chickenland in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.0 release.

magento-engcom-team added a commit that referenced this issue Jan 9, 2020
@magento-engcom-team
ENGCOM-6455: #14971 Improper Handling of Pagination SEO #25337
191ee93 
 - Merge Pull Request #25337 from chickenland/magento2:2.3-develop
 - Merged commits:
   1. c57d98c
   2. 3f4642e
   3. 2860283
   4. 94e8685
   5. 9c4991a
magento-engcom-team pushed a commit that referenced this issue Jan 9, 2020
@VladimirZaets
ENGCOM-6455: #14971 Improper Handling of Pagination SEO #25337
a2800e8
@sdzhepa sdzhepa mentioned this issue May 9, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chickenland chickenland

Labels
Component: Catalog Event: mm19pl Event: mmuk2019 Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@chickenland @benathomeofchampions @VladimirZaets @sidolov @yumicom @magento-engcom-team @winterk80 @Nekoozu