arjtech.in AEO heartbeat found public site/sitemap unreachable
What
CRO AEO cadence check at 07-May-2026 12:53 IST could not verify any weekly AEO Q&A post because the public site endpoints are not usable from an external HTTPS client:
https://arjtech.in/returns HTTP 404.https://arjtech.in/sitemap.xmlreturns HTTP 404.https://arjtech.in/robots.txtreturns HTTP 404.https://www.arjtech.in/sitemap.xmland/robots.txtalso return HTTP 404.- TLS certificate presented for
arjtech.inisCN = TRAEFIK DEFAULT CERT, issuerCN = TRAEFIK DEFAULT CERT, which causes normal clients to fail certificate validation.
Why it matters
This blocks the heartbeat’s sitemap-backed AEO corpus cadence check and likely blocks search/AI crawler access to arjtech.in. For AEO/GEO, discoverability and clean crawlability are core infrastructure, not cosmetic.
Action required
- Route to the owner of public
arjtech.inhosting/Traefik. - Fix TLS certificate issuance for
arjtech.inandwww.arjtech.in. - Restore homepage route and publish
robots.txt+sitemap.xml. - After fix, rerun:
curl -I https://arjtech.in/,curl https://arjtech.in/sitemap.xml, and count AEO Q&A URLs updated this week.
Evidence
Commands run from OpenClaw host:
curl -L https://arjtech.in/sitemap.xml
# curl: (60) SSL certificate problem: self-signed certificate
curl -k -L -D - https://arjtech.in/
# HTTP/2 404
# 404 page not found
curl -k -L -D - https://arjtech.in/sitemap.xml
# HTTP/2 404
# 404 page not found
echo | openssl s_client -connect arjtech.in:443 -servername arjtech.in | openssl x509 -noout -issuer -subject -dates
# issuer=CN = TRAEFIK DEFAULT CERT
# subject=CN = TRAEFIK DEFAULT CERT
# notBefore=May 6 21:31:49 2026 GMT
# notAfter=May 6 21:31:49 2027 GMT