fix: add dynamic canonical tags to auth endpoints to fix duplicate SEO errors#267
Open
balpreetgrowthnatives wants to merge 1 commit into
Open
Conversation
Contributor
|
Someone is attempting to deploy a commit to the ComfyUI Team on Vercel. A member of the Team first needs to authorize it. |
balpreetgrowthnatives
changed the title
balpreetgrowthnatives
force-pushed
the
fix-auth-canonical-tags
branch
from
1a96597 to
028ec6c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do?
This PR injects a dynamic
<link rel="canonical">tag into the authentication layouts (login.tsx,signup.tsx, andlogout.tsx) to resolve duplicate content SEO errors.Why is this needed?
Currently, when login pages are accessed with state trackers like
?fromUrl=, Googlebot flags them as "Duplicate without user-selected canonical".Implementation details:
To fix this without breaking Next.js internationalization (i18n), the canonical tag is generated dynamically using
router.pathnameandrouter.locale. This ensures that all query parameters are cleanly stripped out, while localized paths (like/zh-CN/auth/login) are safely preserved.