* docs(seo): add static file options for robots.txt and sitemap.xml
Document that users can place static robots.txt and sitemap.xml files
in the public directory as a simpler alternative to server routes.
* docs(seo): add Nozzle.io recommendation for rank tracking
Add a "Track Your Rankings" section recommending Nozzle.io as a partner
tool for monitoring SEO performance and keyword rankings.
---------
Co-authored-by: Claude <noreply@anthropic.com>
* docs(start): add SEO guide for React and Solid frameworks
Add a comprehensive SEO guide that clarifies what SEO actually means
for developers and explains TanStack Start's technical SEO capabilities:
- Document head management (meta tags, titles, Open Graph)
- Server-side rendering for crawlability
- Static prerendering for performance
- Structured data (JSON-LD) for rich results
- Sitemap and robots.txt generation via server routes
- Best practices for technical SEO
This addresses the common misconception that SEO is just a checkbox,
explaining that it's about using available tools effectively.
* docs(start): add LLMO guide and cross-references with SEO guide
Add a comprehensive LLM Optimization (LLMO) guide for both React and
Solid frameworks, covering:
- What LLMO/AIO/GEO is and how it differs from traditional SEO
- Structured data (JSON-LD) for AI consumption
- Schema.org examples: Article, Product, Organization, FAQ
- Machine-readable API endpoints
- Content best practices for AI extraction
- llms.txt implementation
- Monitoring AI citations
Also adds cross-reference callouts between SEO and LLMO guides to help
users discover related content.
* ci: apply automated fixes
* docs(start): move SEO and LLMO guides to end of guides list
* docs(start): fix server route examples to use createFileRoute
Update SEO and LLMO guides to use createFileRoute with server.handlers
instead of createServerFileRoute for consistency across React and Solid.
* docs(start): document built-in sitemap and fix route file naming
- Add built-in sitemap generation with prerender + crawlLinks
- Show dynamic sitemap as alternative for dynamic content
- Fix escaped period syntax in file names: sitemap[.]xml.ts, robots[.]txt.ts, llms[.]txt.ts
- Add CDN caching recommendation for dynamic sitemaps
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
docs: improve Netlify hosting docs golden path
Revamp the Netlify hosting docs again, to provide a single golden default path that is precise and
works for most use cases, and call out alternatives separately in subsections.
Also add links out to further Netlify docs where appropriate to increase discoverability and
troubleshootability.
The docs make references to react in a lot of places. I updated the ones
I could find in the build-from-scratch guide to use proper solid-js
package names and other references.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Expanded "build from scratch" guide for migrating from React to
SolidJS.
- Added comprehensive mapping of React libraries, tooling, and plugins
to Solid equivalents.
- Documents alternative React tooling options and Solid-compatible
plugin recommendations.
- Clarifies updating JSX runtime and project configuration for SolidJS.
- Describes import/usage changes and fragment/JSX differences needed for
Solid.
- Notes removal of React-specific type artifacts during migration.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Nico Lynzaad <44094871+nlynzaad@users.noreply.github.com>
Co-authored-by: Nico Lynzaad <nlynzaad@zylangroup.com>
Fixes#5085
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Updated the Solid framework “Learn the Basics” guide to correct the
client hydration example, targeting the appropriate DOM root.
* Clarifies which element to hydrate, aligning the snippet with current
best practices and reducing confusion for readers.
* Improves copy‑paste reliability of the example for newcomers following
the setup steps.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->