How We Got a SaaS Website Cited in Perplexity Within 30 Days

How did GrowthOS get cited in Perplexity within 30 days?

When GrowthOS came to us, their website had a problem most B2B SaaS companies do not know they have: it was invisible to AI search engines. Their buyers, revenue operations leaders, were already asking ChatGPT and Perplexity questions like "best RevOps reporting tools." The engines were answering. GrowthOS just was not in the answers.

This is exactly what we changed, what happened each week, and the framework you can apply to your own site.

The starting point: a site built for 2019, not 2026

GrowthOS is a B2B SaaS platform for revenue operations teams. The product was strong; the website was not. Our audit found the same issues we see on most aging marketing sites.

• A six-year-old WordPress build that blocked marketing updates, so campaigns shipped weeks late.
• A mobile PageSpeed score of 54, with Core Web Vitals failing across the board.
• Generic positioning that could have belonged to any SaaS company.
• No structured data: no Organization, FAQ, or Article schema for engines to read.
• No answer-first content: every page was marketing prose, and AI engines cite answers, not prose.

What we changed

We ran a two-week discovery sprint, then rebuilt the site in Webflow over three weeks. Five changes mattered most for AI visibility.

1. We rewrote key pages as answers, not brochures

Every high-intent page was restructured around a real buyer question: the question as a heading, a two-to-three sentence direct answer immediately after, then supporting detail. We added genuine FAQ sections using language from real sales calls. This is the core of AEO: engines cite content that answers questions in clear, extractable language.

2. We added JSON-LD structured data across the site

We implemented Organization, FAQPage, WebSite, BreadcrumbList, and Article schema so engines had machine-readable facts to extract. Schema does not guarantee citations, but it removes ambiguity, and an easy-to-extract page wins over one with neither schema nor direct answers.

3. We rebuilt performance from 54 to 94 on mobile

The old WordPress site scored 54 on mobile; the new Webflow build scored 94. AI engines factor site quality into which sources they cite, and a fast, clean site is more likely to be crawled, parsed, and quoted. The gains came from Webflow's hosting, removing render-blocking plugins, and clean semantic code.

4. We built topical depth with answer clusters

Instead of isolated posts, we structured content into clusters: a pillar page answering the big question, surrounded by supporting articles for the sub-questions, all linked together. Engines evaluate topical authority, so comprehensive coverage gets cited repeatedly.

5. We made every claim verifiable

We replaced vague marketing claims with specific, verifiable ones: real numbers, real outcomes, real client language. Experience, expertise, authoritativeness, and trust are not just Google ranking factors anymore; they are citation factors.

What happened, week by week

Within 60 days of launch, the site also produced a 3x increase in demo bookings, because the same answer-first structure that engines reward is the structure that converts human visitors.

• Week 1: Site launched. We submitted the sitemap, verified indexing in Search Console, and monitored AI crawler activity.
• Week 2: Google indexed the new pages. No AI citations yet, which is normal; engines need time to re-crawl.
• Week 3: First signal. Perplexity cited GrowthOS for a high-intent category keyword, pulling directly from a restructured FAQ answer.
• Week 4: A second citation appeared for a different keyword, this time from the product page's problem-solution section.

The repeatable framework

Five steps you can apply to any website:

• Audit your answer-ability. Can you extract a clear two-sentence answer to "what does this company do and why should I care?" If not, engines cannot either.
• Restructure content as answers. Question as heading, direct answer immediately after, detail below, plus genuine FAQ sections.
• Add structured data. At minimum Organization, WebSite, and FAQPage schema, and Article schema for content. Test in Google's Rich Results Test.
• Fix performance. Under 70 on mobile is a credibility problem with both Google and AI engines; get it above 90.
• Build answer clusters, not isolated posts. A pillar page per core topic, supporting articles for the sub-questions, all linked.

The honest caveat

Thirty days is fast, and not every site will see citations that quickly. GrowthOS had advantages: a real product, existing domain history, and buyers already asking category questions in AI engines. A brand-new domain will take longer. But the direction is not optional. The businesses that structure for AI answers now become the default cited sources in their categories; everyone else catches up.

What this means for your website