Static SEO
Cloudflare Pages for the Renaro landing site
The new landing app is built in Astro for static HTML, fast page delivery, sitemap generation, canonical metadata, and CI guardrails.
- Astro
- Static HTML first
- Sitemap
- Generated index
- Robots
- Crawler discovery
- CI
- SEO metadata checks
Marketing pages should be crawlable by default
Renaro's authenticated dashboard remains a web app. The public marketing site should be static, indexable, and structured for search intent.
- Generate pages from typed catalogs instead of hand-copying content.
- Use canonical URLs, Open Graph tags, structured data, and sitemap discovery.
- Run SEO tests in CI to prevent duplicate routes and thin metadata.
Where this page fits
This page documents the architecture choice behind the landing scaffold and supports searches around Astro SaaS SEO.
- Link static hosting content to resources on SEO strategy.
- Keep Cloudflare separate from backend Railway services.
- Avoid unsupported hosting assumptions in code and copy.
Related integration paths
Frequently asked questions
Are integrations implemented directly in the landing app?
No. The Astro landing app documents and routes SEO traffic to Renaro's product areas. Operational integrations are owned by the API, worker, and platform domains.
Why create integration landing pages?
Operators and technical buyers search for specific provider support. These pages state the current data and workflow boundary and link to capabilities that are available today; they do not imply that an unconfigured OAuth connector is live.
Platform walkthrough
See how Renaro handles your real operating workflow.
Bring a booking scenario, a dispatch policy, a pricing edge case, or a migration concern. The walkthrough should prove how the platform behaves under actual operator pressure.