You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Every page inherits canonical "/" from the root layout #115
in the root metadata. Next.js merges metadata downward, so every page that doesn't set its own canonical (most of them) tells search engines "I am a duplicate of the home page". That can keep pages like /gsoc and /blog/<post> out of search results.
Done when
The root layout no longer sets alternates.canonical. Keep it on the home page only: move it to app/page.tsx's metadata, or drop it.
Spot-check with view-source on /, /gsoc and one blog post: none of them may claim <link rel="canonical" href="https://www.devforge.club/"> except /.
npm run build passes.
Size: ~3–6 lines. Small diff, real impact: explain in the PR why it matters.
Taking this? Comment /assign and the bot assigns you if it's free. One issue per person at a time; comment /unassign to hand it back. That's milestone 2 of the 10 PR Journey. Setup, the checks CI runs, and how to open the PR from your fork are in CONTRIBUTING.md. Put Fixes #<this issue> in your PR description.
Activity
drathava847-beep commentedon Sep 22, 2026
@geetxnshgoyal assign this issue to me.
github-actions commentedon Sep 23, 2026
@hridhinvarkeyjoseph this one is already taken by @drathava847-beep. Pick another from the unassigned good first issues.
fix: NST-DEVFORGE#115 add homepage canonical URL
fix: NST-DEVFORGE#115 remove global canonical URL (NST-DEVFORGE#144)