Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Marketing site search (Algolia) returns stale, unversioned docs links

Aperta
  • Qualcosa non va?
#617 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
next.js, typescript
Ambito
search

Direzione di ricerca

The issue points to the marketing search integration in src/components/navbar.tsx and the https://kagent.dev/docs/sitemap.xml sitemap. Start by checking the Algolia DocSearch crawler status and its start URLs or sitemaps; then unblock it, run a crawl, and accept the expected safety check. Done means searching “BYO OpenAI” returns a link to /docs/kagent/0.x/supported-providers/byo-openai/.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug DocOps

Problem

The search box on the kagent.dev marketing pages (Algolia DocSearch, in src/components/navbar.tsx) returns stale results:

  • Every result uses a pre-versioning URL, such as /docs/kagent/supported-providers/byo-openai. None include 0.x/ or 1.x/.
  • No 1.x pages appear at all.
  • Result text reflects the docs as of late July 2026.

The search inside /docs/ uses the Hugo FlexSearch index and is not affected.

Old URLs redirect to 0.x through next.config.mjs. Today, any old URL with two or more path segments returns a 500 instead of redirecting, which affects 52 of the 60 kagent pages in the index. That redirect bug is fixed separately. This issue covers only the stale index.

What the index shows

The public search key can list indexes, so the dates below come from Algolia's GET /1/indexes endpoint (app 0Q0AZY5UR3):

Index Last written Records
kagent (live, read by the site) 2026-07-31 1,934
kagent.tmp (crawler scratch index) 2026-08-21 1,479

The DocSearch crawler writes each crawl to kagent.tmp and swaps it into kagent only if it passes the crawler's checks.

Likely cause

This is a best guess, since the crawler dashboard isn't visible with the public key:

  1. On 2026-08-19, the old Next.js docs pages were removed (ad3a69d).
  2. The 2026-08-21 crawl found about 24% fewer records. The crawler's safety check blocks publishing when too many records disappear, so the live index was kept.
  3. A blocked crawler stays stopped until someone unblocks it. kagent.tmp hasn't been written since 2026-08-21, which fits.

The 2026-08-21 crawl ran against the Hugo pages and still got 1,479 records, so the existing selectors probably mostly work on the Hextra markup.

Fix

Someone with access to the Algolia crawler (DocSearch was added in e9e4b03):

  • Check the crawler status. Confirm it's blocked, or find the actual error.
  • Make sure the crawler's start URLs or sitemaps include https://kagent.dev/docs/sitemap.xml, which lists the 0.x and 1.x pages.
  • Unblock the crawler and run a crawl. Accept the safety check for this run, because a large record change is expected.
  • Spot-check results: search "BYO OpenAI" and confirm the result links to /docs/kagent/0.x/supported-providers/byo-openai/.

Note: the crawler probably skips pages marked noindex by default. While 0.x is the current release, 1.x pages that also exist under 0.x are marked noindex, so a healthy crawl may show few 1.x results. That's likely fine while 1.x is in alpha.

Longer term (optional)

The site has two search indexes for the same docs: Algolia on the marketing pages and FlexSearch under /docs/. Only the FlexSearch one rebuilds on every deploy. Consider either scheduling a crawler health check, or pointing the marketing search at the Hugo index and retiring Algolia.

Lingua principale
TypeScript
Stelle
21
Fork
69
Merge medio
14h 16m
PR unite (30g)
105

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di kagent-dev/website

Tutte le issue di kagent-dev/website

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.