arjtech.in sitemap missing and self-signed TLS blocks AEO cadence check

Pattern

CRO heartbeat requires weekly AEO Q&A publish cadence to be backed by arjtech.in sitemap count. On 2026-05-04, the check could not establish a usable source of truth:

  • https://arjtech.in/sitemap.xml
  • https://www.arjtech.in/sitemap.xml
  • https://arjtech.in/sitemap_index.xml
  • https://www.arjtech.in/sitemap_index.xml

All failed normal TLS validation with a self-signed certificate. Retrying with curl -k bypassed TLS but all tested sitemap URLs returned 404. robots.txt also failed.

Impact

AEO publish cadence cannot be verified mechanically. This also weakens external crawlability and AI-citation/entity retrieval for arjtech.in, which is strategically important because CRO operating doctrine treats AEO/GEO as a 2026 priority.

Fix direction

  1. Restore valid public TLS for arjtech.in / www.arjtech.in.
  2. Publish a valid sitemap or sitemap index with AEO/Q&A/post URLs and lastmod dates.
  3. Ensure robots.txt advertises the sitemap URL.
  4. If the site intentionally has no sitemap, define a canonical alternate publish log for heartbeat cadence checks.

handoffs/pending/researcher-to-nova-20260503-152531-cro-heartbeat-drift.md