fix(pagination): ensure canonical URLs exclude ?page=1
#70
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mization fix(pagination): ensure canonical URLs exclude `?page=1` for SEO optimization This commit updates the `setPaginationLinks` method to ensure that the canonical URL for the first page does not include `?page=1`. Including this parameter can create SEO issues by generating duplicate canonical tags for the same content, leading to potential penalties or confusion for search engines. ### Changes: - Modified `setPaginationLinks` to check if the current page is greater than 1. If not, it sets the canonical URL to the base URL without `?page=1`. - Updated test cases to reflect Laravel’s paginator behavior, ensuring canonical, next, and previous links are correctly formatted. - Ensured test coverage includes: - First page scenarios, where `?page=1` is excluded from canonical URLs. - Middle and subsequent pages, where all pagination links (`next`, `prev`, and canonical) are properly formatted with query parameters like `?page=n`. ### Example: For the first page: - Canonical URL: `http://site.com` (without `?page=1`). - Next link: `http://site.com?page=2`. For page 10: - Canonical URL: `http://site.com?page=10`. - Next link: `http://site.com?page=11`. - Previous link: `http://site.com?page=9`. ### Reason: By excluding `?page=1` from canonical URLs on the first page, we avoid duplicate content issues in search engines, ensuring that the main content URL is consistent and SEO-friendly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit updates the
setPaginationLinksmethod to ensure that the canonical URL for the first page does not include?page=1. Including this parameter can create SEO issues by generating duplicate canonical tags for the same content, leading to potential penalties or confusion for search engines.Changes:
setPaginationLinksto check if the current page is greater than 1. If not, it sets the canonical URL to the base URL without?page=1.?page=1is excluded from canonical URLs.next,prev, and canonical) are properly formatted with query parameters like?page=n.Example:
For the first page:
http://site.com(without?page=1).http://site.com?page=2.For page 10:
http://site.com?page=10.http://site.com?page=11.http://site.com?page=9.Reason:
By excluding
?page=1from canonical URLs on the first page, we avoid duplicate content issues in search engines, ensuring that the main content URL is consistent and SEO-friendly.