# Hotfix10 / Build Fix 41 SEO Second Audit

## Scope

Hotfix10 follows the Hotfix9 server-rendered SEO foundation with a second pass focused on migration safety, index-control correctness, academic-template information architecture, useful research content and crawlable product differentiation.

## High-impact findings addressed

1. **Template URL equity:** `/latex-templates` and legacy detail URLs now have permanent migration handling instead of silently becoming SPA 404s. Individual template canonicals stay stable at `/templates/{slug}` while institution/country/category pages remain collection surfaces.
2. **Faceted noindex after hydration:** server and React metadata now retain `noindex,follow` for filtered `/templates?...` and `/blog?...` URLs instead of the client resetting them to indexable.
3. **robots/noindex alignment:** safe application shells can be crawled long enough to observe `noindex`; internal API/WebSocket/render plumbing stays excluded.
4. **Template search surface:** template metadata now supports institution, country, degree, provenance, compiler, bibliography engine, document class, packages, features and verification information.
5. **Interactive learning:** Learn examples can create isolated browser-local projects through `Try in Editor` without placing manuscript/example source in URLs.
6. **Research intent:** dedicated researcher, thesis, research-team, local-first, Visual editor, reproducibility/Terminal, Paper Memory, local AI and Overleaf-alternative pages make product capabilities explicit without generating thin keyword permutations.
7. **Entity/schema refinement:** template CreativeWork schema can expose truthful license, author, provenance/source, version, category/tags and institution context where supplied.
8. **Social metadata:** the supplied 1200x630 TeXise image remains the generic fallback; article covers and template preview imagery take precedence where available. `twitter:site` and Organization social identity are explicit.

## Content-quality policy

TeXise should prefer a small number of substantial first-hand guides, technical workflows, verified template pages and research tools over mass-generated query-variation pages. Institution pages must not imply endorsement, and `official` template status must come from explicit provenance rather than inference.

## Deferred by design

- **Body SSR/prerender:** the initial SEO head is server rendered. Moving the whole public React body to SSR would be a much larger rendering/build change and is deferred until it can be production-built and browser-certified with dependencies available.
- **Automatic image derivatives:** Hotfix10 enforces useful blog-cover dimensions and supports page-specific images, but does not add an unverified production image-transform dependency to a source-only release.
- **Server-side compilation of uploaded templates:** structural template validation is implemented. Uploaded LaTeX is not executed in the privileged web process simply to create previews; automatic compilation should use an existing isolated compiler worker/container when that integration is explicitly certified.

## Production migration requirement

Treat deployment as an SEO migration: capture known legacy template URLs, populate `texise-templates/redirects.json` for slug changes, deploy redirects and destination pages together, regenerate the sitemap/template manifest, inspect representative old/new URLs, then monitor indexing after deployment.