feat: implement edge-side rendering for SEO-optimized landing page - #2
Merged
Conversation
palmithor
force-pushed
the
feat/seo-edge-side-rendering
branch
from
February 16, 2026 10:47
ba5bca7 to
503675c
Compare
🚀 Preview Environment DeployedPreview URL: https://cloudflare-worker-app-pr-2.coding-cowboys.workers.dev This preview environment will be automatically cleaned up when the PR is closed. |
palmithor
force-pushed
the
feat/seo-edge-side-rendering
branch
5 times, most recently
from
February 16, 2026 13:10
16f2ae1 to
fc456c4
Compare
Add comprehensive SEO implementation with server-side rendering at the edge: - Create shared components package (@coding-cowboys/cloudflare-worker-app-components) with server-safe LandingPage component using React createElement - Implement SEO route in worker (apps/worker/src/features/seo/seo-route.ts): * Server-render landing page using renderToString * Full SEO meta tags: title, description, keywords, canonical * Open Graph tags for social sharing * Twitter Card meta tags * JSON-LD structured data (WebApplication schema) * Inline critical CSS to prevent FOUC - Add static SEO assets: * robots.txt - controls search engine crawling * sitemap.xml - helps search engines discover pages - Configure wrangler.jsonc to run worker first for root path (/) enabling edge-side rendering before static asset serving - Update Tailwind config to include SSR classes: * Add @source directive for components package * Create ssr-classes.ts to force-include grid utilities - Landing page SSR optimized while /todos remains SPA: * / - Server-rendered with full SEO (indexable) * /todos - Client-side only (noindex via robots.txt) This hybrid approach gives us: - SEO: Fully crawlable landing page with rich meta information - Performance: Edge rendering from closest data center - UX: SPA navigation after initial load for fast app experience No need for full SSR framework like Next.js - best of both worlds.
palmithor
force-pushed
the
feat/seo-edge-side-rendering
branch
from
February 16, 2026 13:31
fc456c4 to
6ea3622
Compare
🧹 Preview Environment Cleaned UpThe preview environment and database have been deleted. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements comprehensive SEO using edge-side rendering with Hono while maintaining SPA architecture for authenticated routes.
Changes
New Features
/) with full HTML and meta tags@coding-cowboys/cloudflare-worker-app-components) for server/client compatibilityrobots.txtandsitemap.xmlArchitecture
/- Server-rendered by Hono at the edge (SEO-optimized, indexable)/todos- Client-side SPA (noindex via robots.txt)/api/*- Hono REST endpointsTechnical Implementation
react-dom/serverrenderToStringfor SSRcreateElement(no JSX for tsgo compatibility)Benefits
Testing
tsgooxlintFiles Changed
apps/worker/src/features/seo/seo-route.ts- New SSR routepackages/cloudflare-worker-app-components/- New shared components packageapps/web/src/index.css- Tailwind source configurationapps/web/src/ssr-classes.ts- Force-include Tailwind classesapps/web/public/robots.txt- Search engine directivesapps/web/public/sitemap.xml- Site structureapps/worker/wrangler.jsonc- Worker-first routing configREADME.md- SEO documentation added