Addon profile pages are missing from the sitemap

Open Beginner friendly
  • Is something wrong?
#834 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
nextjs, typescript
Domain
search, web-dev

Research direction

Read web/src/app/sitemap.ts and the referenced platform spec at docs/design/specs/2026-10-18-platform-expansion-design.md:610. Check how the sitemap lists addon routes and where loadPopularAddons() and the curated list are defined, then add coverage for the requested profile URLs. Done means popular and curated addon profiles appear in the sitemap with encoded names.

Written by the indexing model from the issue text.

Description

night-shift web

From the 2026-11-06 web audit (W12). The platform spec (docs/design/specs/2026-10-18-platform-expansion-design.md:610) says each /addons/<name> page is server-rendered, canonical and in the sitemap, but web/src/app/sitemap.ts:40 lists only the four static addon routes. Profiles for any addon with 3 installs or on the curated list are indexable but never submitted.

Fix. In sitemap.ts, add loadPopularAddons() names (when reachable) plus the curated list, mapped to /addons/${encodeURIComponent(name)}. Test. Size S.

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CDVolvik/everloot

All issues in CDVolvik/everloot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.