circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#467 Event pages of log timelines crowd the sitemap

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#467
  • issue
  • state:closed

The synthetic incident timeline `athan/incident-2026-03-14` gives each log line a page of its own in the sitemap: 2,299 of timescale.info's 9,647 URLs (24%). The pages are thin, about 285 words mostly of boilerplate. Their titles repeat, such as "GET /api/orders 200 21ms · Incident 2026-03-14: orders API outage", which appears several times. Many thin, near-duplicate pages can lower how search engines rate a site's other pages. Wanted: a timeline can keep its own page indexed while its events' pages are left out of the sitemap and marked `noindex`. For example, a per-timeline setting "List events for search engines", off by default for timelines filled by the log importers (syslog, journald, log files). For timescale.info, it would be turned off for the incident timeline. Found in an SEO audit of timescale.info on 2026-11-06. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/issues/467

Related

Open #467 Event pages of log timelines crowd the sitemap in the timeline

#467 Event pages of log timelines crowd the sitemap