TanStack Start gives you SSR and route-level head metadata, but launch readiness still depends on how your routes, Worker headers, static assets, and generated files line up in production.
Route metadata
Every public route should emit title, description, canonical, Open Graph, Twitter Card, and robots metadata from server-rendered route data. Do not wait for client hydration to correct canonical tags.
Worker headers
Cloudflare _headers rules do not cover every Worker-generated response.
Set security headers, cache directives, discovery Link headers, and
X-Robots-Tag in the Worker response path for SSR pages and APIs.
Static and dynamic cache policy
Cache hashed assets aggressively. Keep HTML revalidating, and keep report
or user-specific routes out of long browser caches. If you serve markdown
variants with Accept: text/markdown, set Vary: Accept so caches do not
mix representations.
Verify the deployed origin
Run the website readiness checker against the deployed production URL, not a local preview. The scan will catch staging canonicals, missing CSP, blocked sitemap URLs, and agent-discovery gaps that framework defaults cannot infer.