functoryThe problem
Although Functory had an SSR setup, the actual keywords and meta descriptions generated in the SPA were still missing from the server-rendered HTML.
This meant that Google could crawl the page but not fully understand its content — a major blocker for SEO visibility.
What shipped
After several days of debugging across vite-plugin-ssr, Express middleware, and React SEO context propagation, we finally achieved full parity between SPA and SSR rendering.
Now, every page — from function listings to user profiles — renders its title, description, and keywords directly on the server before hydration.
This guarantees that crawlers see the same semantic structure as users, unlocking true indexation of Functory’s long-tail content.
Why it matters
This fix massively improves search visibility and credibility.
Functory’s unique keywords (e.g., “run Python in the cloud,” “monetize TypeScript functions”) can now be crawled and ranked effectively — a key step toward organic discovery and developer trust.
How we built it
We reworked the SSR server to intercept rendered HTML, strip existing SPA SEO tags, and inject the correct metadata using a normalized and escaped pipeline.
Edge cases like nested components, conditional meta updates, and async data were handled to ensure deterministic SSR output.
A new health check verifies that SSR output matches expected meta values before deployment.
What’s next
Next, we’ll automate SEO regression checks per page (snapshot testing of titles and meta tags) and link the pipeline to the dynamic sitemap generator for full SEO coverage.
With this foundation, Functory’s content is finally both dynamic and discoverable — exactly as intended.