Zolvo has built a large library for lenders: 20 use cases, 10 comparison pages, 71 glossary terms, 16 calculators and 74 blog posts. But every page we fetched without running JavaScript came back as a page title and nothing else: no text, no links, no meta description. That covered the homepage, the freight factoring use case, the 2026 lending operations report, the FactorSoft comparison, the borrowing base glossary entry, the factoring calculator and the Abaco customer story. Zolvo plainly wants machine readers: it publishes an llms.txt and its robots.txt lets every crawler in. Yet readers that fetch the raw HTML get an empty shell. That includes link previews on LinkedIn, where a seed-stage B2B company does most of its sharing, and many AI-assistant crawlers. Google can render JavaScript, but rendering is slower and less reliable than plain HTML for a new domain.
First action
Fetch five URLs with JavaScript disabled, confirm they show only a title, and switch the build to pre-render the /glossary/ section first.
How to measure it
Organic and assistant-referred demo requests
- Now
- –
- Target
- 228 of 228 pages pre-rendered; 10 demo requests a month from organic and AI referrals
- By
- 90 days
Steps
Confirm the gap
Fetch homepage, a use case, a glossary term, a calculator and a comparison with JavaScript off; record what arrives.
Co-founder, CTO 1 hour
Pick the method
Static generation at build time for all marketing routes; keep the app (/app, /dashboard) client-rendered.
Co-founder, CTO 1 day
Pre-render the glossary first
71 short, stable pages: the safest place to prove the build.
Co-founder, CTO 2 days
Roll out to all sections
Use cases, solutions, compare, tools (explanations and examples), blog and customers.
Co-founder, CTO 3 days
Add meta and schema
Unique descriptions, Open Graph images, FAQ, Article and SoftwareApplication markup.
Founding Growth and Sales 2 days
Fix the sitemap and 404s
Add /customers/abaco/; unknown routes return a 404, not the homepage title.
Co-founder, CTO 2 hours
Check previews and indexing
LinkedIn Post Inspector, Search Console URL inspection, Bing Webmaster Tools.
Founding Growth and Sales 1 day
Measure
Indexed pages, impressions, AI-assistant referrals and demo requests by landing page.
Founding Growth and Sales monthly
Why it works
Serve every marketing route as complete HTML. Pre-render the static sections (use cases, solutions, compare, glossary, tools, blog, customers) at build time, so each URL ships its headings, body text, internal links, a unique meta description, Open Graph tags and schema markup (FAQ on glossary terms, SoftwareApplication on solutions, Article on the blog). The calculators can still run their interactive part in the browser, but the explanation, formula and an example result should sit in the HTML. Add the customer story and any new pages to the sitemap, and give unknown routes a real 404 instead of the homepage title. Then check that a LinkedIn share of /glossary/borrowing-base-certificate/ shows a description and image, and track how often Zolvo's pages are cited when buyers ask assistants about factoring software.
Zolvo's buyers research in search and AI assistants ("how do I automate cash posting for factoring", "FactorSoft alternatives") and share links with colleagues on LinkedIn. The content already answers those questions. Making it readable turns months of writing into pages that can rank, be quoted and preview properly, at almost no extra cost.
Ready to use
ChecklistReadable-page checklist for each Zolvo URL
[ ] View source shows the H1 and body text [ ] Unique <meta name="description"> [ ] Open Graph title, description and image [ ] Internal links to the matching solution, use case and calculator [ ] Schema: FAQ (glossary), Article (blog), SoftwareApplication (solutions) [ ] URL is in sitemap.xml [ ] Unknown URLs return 404 [ ] LinkedIn Post Inspector shows a full preview [ ] Search Console URL inspection: page indexed
Risks and how to handle them
Pre-rendered HTML drifts from what the app shows
Generate both from the same content files on every deploy.
Interactive calculators break
Pre-render the explanation and an example; load the calculator in the browser on top.
Evidence
- Your websiteFetched November 9, 2026 with a reader that does not run JavaScript: the homepage, /use-cases/freight-factoring/, /blog/state-of-commercial-lending-operations-2026/, /compare/factorsoft/, /glossary/borrowing-base-certificate/, /tools/factoring-calculator/ and /customers/abaco/ each returned only a page title (for example "Invoice Factoring Cost Calculator | Zolvo"), with no body text, links or meta description.Source
- Your websiteSitemap (228 URLs, checked November 9, 2026): 10 solutions, 3 integrations, 10 comparison pages (FactorSoft, ABLSoft, Solifi, WinFactor, FactorCloud, Bectran, Lendscape, HighRadius, Turnkey Lender, legacy software), 20 use cases, 71 glossary terms, 16 calculators including an automation ROI calculator and a back-office automation scorecard, and 74 blog posts, most dated June 26 to July 2, 2026, the newest July 25, 2026. It has no /customers/ page and no /pricing page, although the homepage links to /customers/abaco/.Source
- Your websitellms.txt and robots.txt: Zolvo describes itself as "AI back-office automation for commercial lenders" for factoring companies, asset-based lenders and private credit funds; it runs on top of FactorSoft, LoanPro and QuickBooks rather than replacing them, and says a typical pilot goes live in 2 to 4 weeks. robots.txt admits all crawlers outside /login, /app, /dashboard and /embed/.Source