Leeroo's blog lists four posts, including "Organizational Superintelligence", the essay behind Uniforge, which was shared on Hacker News. When the post URLs are fetched without running scripts (the way most link-preview bots, AI assistants and many crawlers read pages), each one returns the homepage's title and text instead of the article. Made-up paths such as /privacy return the same homepage, and the sitemap lists only five URLs and no posts. So the company's thought leadership is effectively invisible outside a browser: a LinkedIn or Slack share of a post previews as the homepage, AI assistants asked about Leeroo can't quote it, and search engines see many URLs with one identical title.
First action
Pre-render "Organizational Superintelligence" and check its URL with a link-preview debugger and a plain fetch.
How to measure it
Posts returning their own title and text without scripts
- Now
- –
- Target
- 4 of 4, plus a 404 for unknown paths
- By
- 2 weeks
Steps
Confirm the gap
Fetch each post URL with scripts off and with a link-preview debugger; note title and text.
CTO 1 hour
Pre-render posts
Generate static HTML per post at build time, with title, description, canonical, Open Graph and date.
CTO 2 days
Return real 404s
Stop the catch-all fallback from serving the homepage for unknown paths; add a helpful 404 page.
CTO half a day
Update the sitemap
Add all posts with lastmod dates and resubmit in Search Console.
CTO 1 hour
Add the bridge
A closing audit call to action, plus a note on how older posts led to Uniforge.
CEO half a day
Re-share
Share the essay again on LinkedIn and X now that the preview shows the article.
CEO 1 hour
Measure
Indexed pages, impressions per post and audit requests from blog sessions.
CTO monthly
Why it works
Pre-render each blog post to static HTML at build time and serve it from the existing S3 and CloudFront setup, with its own title, meta description, Open Graph image, canonical tag, publish date and author role. Add all four posts to the sitemap with lastmod dates. Make unknown paths return a real 404 page with links to the product, the blog and the audit, instead of the homepage. Then give each post a closing call to action for the free audit, and a short note on how the older posts (Orchestrator, multi-model systems) led to Uniforge, so readers arriving from old links reach today's product.
For an enterprise sale, essays are what champions forward to colleagues. A share that previews as a generic homepage, or a link an assistant can't read, loses that forward. Pre-rendering is a small change on a static site, and it lets every post rank and be quoted on its own topic.
Ready to use
ChecklistBlog page launch checks
[ ] Plain fetch of each post returns the article title and first paragraph [ ] Unique <title> and meta description per post [ ] Open Graph title, description and image per post [ ] Self-canonical tag [ ] Publish date and author role visible [ ] Post URLs in sitemap.xml with lastmod [ ] Unknown paths return 404, not the homepage [ ] Audit call to action at the end of each post
Risks and how to handle them
Breaking existing client-side routes
Pre-render only /blogs/* first and keep the app shell for everything else.
Old posts describe an earlier product
Add a dated editor's note at the top rather than deleting them.
Evidence
- Your websiteBlog: /blogs lists four posts: "Organizational Superintelligence" (2025.11.10), "End2end Multi-Agent finetuning: Open Source Meets SOTA" (2024.12.19), "The First-Principle Multi-Model System" (2024.04.02) and "Leeroo Orchestrator V1: Towards an AI Operating System" (2024.01.24). Fetched twice on November 9, 2026 without running scripts, each post URL returned the homepage title "Leeroo | A Living Model of Your Business, Built by AI" and homepage text instead of the article; made-up paths such as /privacy return the same homepage.Source
- Your websiteSitemap: five URLs (/, /product, /company, /contact-us, /blogs), none with a lastmod date and no blog post URLs.Source
- Hacker News"Organizational Superintelligence" was submitted with the leeroo.com blog post URL and has 1 point.Source