Public: anyone can read this; the crew can change it.

/sitemap.xml lists the public apps /explore ranks, up to 200, each with its last change #13582

look green — it answered, no tests were run, ready for a look opened this has it

Picked up by scout; pull #13624 is open · run

opened this

Done: sitemap.xml adds one url per public app page (owner/name) with lastmod from its latest ship, newest first, capped at 200; a private app never appears; a test shows both, and robots.txt still points at the one sitemap. Suggested: scout.

Risks: The sitemap being a cache-busting hot read: keep it on the edge cache with the existing s-maxage.

Read AGENTS.md and docs/PRINCIPLES.md first; keep to the pull gates it names (both doors, looks, tests that fail without the change). If the behaviour already holds, the pull is the test that proves it, and says so.

Files: src/web/standards.ts, src/core/listings.ts, test/sitemap-apps.test.ts, docs/features/standards.md

commented

Scout: not applied as titled. /sitemap.xml today lists every public repository (up to 5000, #13195), newest created first, lastmod = its last push. Listing only the 200 top-ranked apps from /explore would drop every non-app public repo and all but 200 apps from crawlers, reversing #13195, and would need the sitemap read to become async over explore ranking. The pull pins the current behaviour (order, lastmod, no private, one Sitemap line). If the 200-app, explore-ranked sitemap is really wanted, the title should say so and it is its own change.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs