Skip to content

[P2] Audit: Sitemap needs validation for legacy URLs, parameter URLs, and stale lastmod values #144

Description

@baixiangcpp

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: sitemap.xml exists, but it needs a full validation pass. The audit identified legacy taxonomy URLs and possible parameterized All Tools states that should not be present. lastmod values also need verification so crawlers receive useful freshness signals.

Affected URL:

Reproduction steps:

  1. Fetch sitemap.xml.
  2. Parse every URL.
  3. Check for legacy category URLs such as /en/web-api, /en/design-media, and /en/convert-encode.
  4. Check for query-parameter URLs.
  5. Check for 404, redirect, noindex, or canonical-to-other-page entries.
  6. Validate lastmod against actual content update history.

Expected behavior: sitemap should include only canonical, indexable, 200-status URLs with meaningful lastmod values.

Actual behavior: sitemap existence is confirmed, but its content needs systematic validation.

Impact: crawl budget waste, stale signals, and indexation of unintended pages.

Proposed fix:

  • Add a sitemap audit script to CI.
  • Fail builds if sitemap contains redirected, noindex, 404, parameterized, or legacy URLs.
  • Generate lastmod from content/tool manifest modification dates where possible.
  • Split sitemap by locale or page type if size grows.

Acceptance criteria:

  • Sitemap contains only canonical indexable 200 URLs.
  • Legacy and parameter URLs are excluded.
  • lastmod values are generated from reliable source data.
  • CI validates sitemap before deploy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions