Technical SEO Infrastructure: The Foundation of Machine Readability
Technical SEO is the substrate that lets crawlers and agents parse, render, and trust your entity graph. HEG assumes SSR HTML with JSON-LD @graph, stable canonicals, disciplined crawl paths, and measurable Core Web Vitals — not a client-only shell that hides meaning behind JavaScript.
- Prefer SSR/HTML-first content for Phase-1 indexing of entity pages.
- One canonical URL + matching @id per entity; fix logo URLs that return SPA HTML.
- Crawl budget is spent on discovery — silence soft-404 SPA fallbacks for keys, sitemaps, and assets.
- Ship practical L3 tools (e.g. llms.txt generator) that implement the infrastructure you teach.
1. The modern crawl and render pipeline
Crawlers discover URLs, fetch bytes, and may defer full rendering. If your primary entity definitions only exist after client hydration, you risk incomplete Phase-1 understanding. HEG pages should expose headlines, relationships, and JSON-LD in the initial HTML response.
Every soft-404 SPA fallback on a static path (logo.png, IndexNow key, .txt) wastes crawl attention and breaks machine consumers that expect plain text or image bytes.
2. Core components of technical excellence
Canonicalization, hreflang pairs, robots/sitemap coherence, Core Web Vitals, and a consistent @graph (Organization, Person, WebPage/TechArticle, BreadcrumbList) form the minimum viable HEG infrastructure. Tools such as the llms.txt generator operationalize agent-facing discovery on top of that stack.
Child entities in this silo
Parent: EN L0 Hub. Children below stay inside this pillar only.