Render routing and edge headers lag repository contract
Opened Jun 28, 2026, 6:20 PM UTC
Impact: SEO, crawl discovery, embed framing policy, and public security-header verification.
Current public deployment status and synthetic-check history.
All sampled prerendered routes and crawler discovery files now serve correctly. Remaining failures: legacy canonical redirects (/api-docs, /developers, /sitemap-index.xml) and edge security/noindex headers are not yet applied at the hosting layer.
Source: npm run check:deployed-routing -- https://ecofreight.co
All sampled routes (/calculator, /docs, /methodology, /pricing, /data-assets, /quality, lane and author pages) returned page-specific prerendered HTML on 2026-08-20.
Legacy docs and sitemap paths (/api-docs, /api/reference, /developers, /docs/index.html, /sitemap-index.xml) returned 404 or 200 instead of HTTP 301 on 2026-08-20.
robots.txt, sitemap.xml, sitemap-pages.xml, quality-snapshot.json, and status-history.json all served with expected content on 2026-08-20.
On 2026-08-20 the live root response is still missing HSTS, CSP, Referrer-Policy, and Permissions-Policy; /embed/calculator is missing frameable CSP; auth routes are missing X-Robots-Tag. The fix requires applying the repository render.yaml/_headers contract at the hosting layer.
Opened Jun 28, 2026, 6:20 PM UTC
Impact: SEO, crawl discovery, embed framing policy, and public security-header verification.
For real-time alerts, email hello@ecofreight.co to subscribe to status updates.