[Frontend] SEO site origin is read from two different env vars (NEXT_PUBLIC_SITE_URL vs NEXT_PUBLIC_APP_URL) with mismatched defaults, so canonical/OG can diverge from sitemap/robots

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

metadata.ts:15 and layout.tsx:17 read NEXT_PUBLIC_SITE_URL (default http://localhost:3000) for metadataBase/canonical/OG, while robots.ts:25 and sitemap.ts:3 read NEXT_PUBLIC_APP_URL (default https://remitlend.com). Neither var is in frontend/.env.example. If only one is configured in prod, canonical/OG URLs and the sitemap/robots host point at different origins (e.g. canonical=localhost).

Acceptance criteria

• All four files resolve the site origin from a single shared constant/env var
• The chosen var is documented in frontend/.env.example
• Defaults are consistent across metadata, robots, and sitemap

Files to touch

• frontend/src/app/lib/metadata.ts
• frontend/src/app/layout.tsx
• frontend/src/app/robots.ts
• frontend/src/app/sitemap.ts
• frontend/.env.example

Out of scope

• Backend env var naming

[stpatrickghost]

@stpatrickghost has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please maintainer... Assign me this issue... I'll resolve it without errors 🙏

ℹ️ Repo Maintainers: To accept this application, review their application or assign @stpatrickghost to this issue.

[Jerry-Tekh]

@Jerry-Tekh has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Repo Manager, I’ll take this.

I’ll unify SEO origins in LabsCrypt/remitlend: single shared constant/env var for metadata, robots, and sitemap with consistent defaults, and add it to frontend/.env.example so canonical/OG won’t diverge from sitemap/robots.

Please assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jerry-Tekh to this issue.

[Akanimoh12]

@Akanimoh12 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd love to work on this issue. I'm a full-stack blockchain developer specializing in web apps and Smart Contracts, with experience in Next.js, TypeScript, Tailwind, and blockchain integration's and writing tests. I can handle this confidently, here's my portfolio and key projects:

• https://frontend-nine-mocha.vercel.app/
• https://i-predict.vercel.app/
• https://somnia-screams.vercel.app/
• https://chessflip-celo.vercel.app/

Active OSS contributor.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Akanimoh12 to this issue.

[drips-wave]

Congratulations, @Akanimoh12! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Akanimoh12: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @Akanimoh12 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1238)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.