Date: March 10, 2026

Session span: Single Cowork session (ran out of context before completing all action items)

Session Overview

Sam noticed that his XML sitemap at aguiarinjurylawyers.com/sitemap/ looked incomplete after adding many new location pages in early March 2026. He asked for a full audit: identify every missing page, explain why they are missing, submit them all for indexing, identify orphan pages, and flag internal linking issues. The session uncovered significant sitemap and structural problems that need follow-up work.

What Was Accomplished

Full Sitemap Cross-Reference Audit

The session pulled and analyzed three XML sitemaps (page-sitemap.xml, post-sitemap.xml, video-sitemap.xml) and cross-referenced them against the /locations/ hub page, which contains 36 city pill links.

Finding 1: 17 location pages missing from the XML sitemap. All are under the /locations/{city}/ path and were published in early March 2026. The pages exist, are set to index/follow in RankMath (confirmed via the REST API endpoint /wp-json/rankmath/v1/getHead), and are linked from the locations hub. The root cause is a stale RankMath sitemap cache. The batch REST API deployments that created these pages likely did not trigger RankMath's sitemap rebuild hooks, and WP Rocket caching may also be interfering.

The 17 missing pages:

  1. /locations/fairdale/
  2. /locations/fern-creek/
  3. /locations/glasgow/
  4. /locations/hillview/
  5. /locations/hurstbourne/
  6. /locations/j-town/
  7. /locations/lagrange/
  8. /locations/lyndon/
  9. /locations/middletown/
  10. /locations/mount-washington/
  11. /locations/new-albany/