This case study documents a ten-month engagement with a Singapore B2B SaaS company that sells inventory and purchasing software to F&B groups across Singapore, Malaysia and the Philippines. Its buyers are operations managers, finance heads and owners of restaurant and cafe groups. They rarely search for a software brand they have not heard of. They search for the problem ("F&B inventory management", "reduce food wastage", "purchase order software for restaurants"), compare options, check that the software works with their POS and accounting systems, and only then book a demo.
The company's marketing site was built as a single-page JavaScript app. It looked polished to visitors, but most content loaded only after the page ran its scripts, internal links were click handlers rather than real links, and every page shared the same title tag. Google had indexed only 34% of the key marketing pages. Almost all organic traffic came from people who already knew the brand, and only 11 demo requests a month came from organic search. Sales could not say how many deals had started with a search, because the demo form passed no source data to the CRM.
We crawled the site with and without JavaScript and compared the results with Search Console's URL Inspection, which showed Google seeing near-empty pages for most routes. We wrote a specification for the client's developers: server-side rendering for all marketing pages, real links in the navigation and footer, a unique title, meta description and canonical for every route, an XML sitemap of marketing pages only, and app login and account URLs kept out of the crawl. The developers built it and we checked every template before and after release.
Content Google cannot render cannot rank, however good it is. Fixing rendering first meant every page written afterwards could be indexed within days rather than weeks. It also removed 300 thin app URLs that had been taking up Google's crawl.
The old site described the product in one long page. We split it into pages for each job buyers need done: stock counts, purchase orders, central kitchen transfers, wastage tracking, supplier price tracking and multi-outlet reporting. Each page explains how the feature works with real screenshots, who it is for, and the plan it comes with, priced in S$. We added SoftwareApplication schema and linked each feature page to the use cases and integrations that relate to it.
Buyers search for the job they want done, not for a product name. Separate feature pages gave Google one clear page to rank for each of those searches and gave buyers a short path from the problem to a demo.
We published eight comparison and alternative pages covering the main competing tools and the spreadsheet set-ups most F&B groups start with. Each one has a fair feature table and says plainly when another option may suit a buyer better. We then wrote 14 integration pages for the POS, accounting and supplier platforms the product connects with, explaining what data syncs, how often, and how long set-up takes.
Comparison and integration searches come late in the buying process, so the people making them are close to a decision. Honest comparisons convert better than one-sided ones, because buyers have usually read the competitor's page too. Integration pages answered the question that most often stalled deals: will this work with what we already use?
We wrote use-case pages for the business types the company serves: cafe groups, restaurant chains, central kitchens, cloud kitchens and bakeries. With the customer success team, we built research content around the questions buyers ask before they shortlist software: how to calculate food cost percentage, how to set par levels, how to run a stock take across outlets, and how to cut wastage. Each guide linked to the matching feature and use-case pages.
Most buyers are not ready to book a demo on their first visit. Research content brought them in earlier and kept the company in the running while they built a business case. Using real customer cases from the customer success team made the guides more specific than competing articles.
We set up GA4 conversions for demo requests and free trial sign-ups, and the client's developers added hidden fields that pass the landing page and source into the CRM with each form. A deal was marked as organic-influenced if organic search was the first touch or appeared anywhere before the demo. Each month we reported demo requests, trials and new pipeline by landing page.
A demo request is not revenue. Tying organic visits to CRM deals let the company see that comparison and integration pages produced fewer leads than the guides, but far more pipeline per lead. That shaped where effort went in the second half of the engagement.
Software buyers research for weeks and compare carefully before they talk to sales. These four points shaped the work.
A JavaScript app can look complete in a browser while Google sees an empty shell. Fixing rendering came before any content work, because nothing else would have ranked without it.
Comparison and alternative searches come from buyers close to a decision. Fair comparison pages caught those searches instead of leaving them to competitors and review sites.
F&B groups already run POS and accounting systems. Searches about integrations signalled real intent, and pages answering them removed the most common reason deals stalled.
Traffic and demo counts alone hid which pages brought in deals. Passing source data into the CRM showed the pipeline value of each page type.
If your marketing site is built with a JavaScript framework, check what Google actually sees before you invest in content. Search Console's URL Inspection shows the rendered page. If the content is missing there, fix rendering first.
Write the pages buyers look for late in the process: comparisons, alternatives, integrations and pricing. They bring less traffic than broad guides, but the people who land on them are much closer to booking a demo.
Connect organic search to your CRM from the start. Counting demo requests is useful, but knowing which pages led to pipeline in S$ is what tells you where the next quarter's effort should go.
It can. Google can render JavaScript, but it often does so later and less reliably than plain HTML, and content that needs scripts or clicks to appear may never be indexed. Server-side rendering or pre-rendering for marketing pages, with real links and unique titles, removes most of the risk.
Yes, if they are fair. Buyers searching for comparisons and alternatives are close to a decision, and they will read your competitors' pages too. A balanced feature table that admits when another tool fits better builds more trust than a one-sided page, and it converts better.
We track demo requests and trial sign-ups as GA4 conversions, pass the source and landing page into the CRM, and report pipeline and closed revenue influenced by organic search. On this project that showed S$684,000 in organic-influenced pipeline over ten months.
Technical fixes and late-stage pages such as comparisons and integrations can lift demo requests within three to six months. Broader research content takes longer to build up. On this project, demo requests went from 11 to 29 a month by month 6 and reached 46 by month 10.
Start with a free SEO audit. We check what Google can render and index on your marketing site, review your product, comparison and integration pages, and look at how organic leads reach your CRM, then show you a realistic path to more demos before you commit to anything.
Singapore’s specialist SEO agency for SMEs. We rank your business on Google — and only Google. No distractions, just results.
© 2026 Singapore SEO Agency. All rights reserved.