FAQ
Honest answers about GEO, SEO, page generation, and realistic timelines. Still stuck? Email us.
SEO is about ranking in Google’s list of links. GEO (Generative Engine Optimization) is about being mentioned in AI search engine answers: ChatGPT, Perplexity, Claude, Google AI Overviews. When someone asks ChatGPT "which tool should I use" — AI names specific products. Getting into those answers is the job of GEO. SaaSForge optimizes for both channels simultaneously.
Yes, if the product has a website and solves a specific problem for a specific audience. The narrower the niche, the faster the results. For products without a website, there is the Pre-Launch Audit.
No. That’s exactly why SaaSForge exists. You describe your product in plain language — the system handles the technical analysis and generation. You only need to read the results and publish the pages.
No. SaaSForge is a visibility tool, not a sales growth tool. We help make your product visible to people who are searching for it. Whether they become customers depends on your product quality, pricing, and many other factors outside our control.
Possible reasons: very narrow or very new niche, non-standard product description, or competitors are protected from crawling. The system automatically broadens the search to a wider category. If competitors are still not found, they can be entered manually.
Out of 30 queries we sent to ChatGPT and Perplexity, your product was mentioned in 7% of cases (roughly 2 out of 30). The remaining 93% went to competitors or no one. This is not an absolute figure — it’s an indicator of relative visibility.
AI search engines are non-deterministic — the same query can produce a different answer in different sessions. That’s why on the Pro plan each query is run 3 times and the average is taken. This makes the metric more stable but not absolute. GEO Check is an indicator, not an exact science.
On Pro and Agency plans — automatically every 2 weeks. More often doesn’t make sense — AI search engines update their understanding of content with a delay. After publishing new pages, wait 2–4 weeks before the next check.
SaaSForge gives you the page — a file, a framework component, or a ready prompt for Claude Code — but it does not host it for you. You publish it on your own website, the same place your homepage lives, and your platform decides the address (URL). The exact steps depend on your platform: on Webflow or Framer you paste it into an Embed element on a new page; on WordPress you use a Custom HTML block; with Claude Code you copy the generated prompt and paste it in, and it wires up the page for you. There is a full step-by-step guide for every platform at the How to Publish page (/how-to-publish), and the same instructions appear right after you generate a page.
The page lives on your own website, not on SaaSForge. The address (for example yoursite.com/vs-competitor) is set by your site — the page slug, route, or path you choose when you add it. SaaSForge never assigns a URL. The “Published” field on the Pages screen is just a tracker: you paste in the address after you publish, so we can monitor whether Google has indexed it.
These are spots where your real data is needed — specific prices, actual features, real-world examples. SaaSForge doesn’t know the details of your product that you didn’t provide. Placeholders are not a bug — they’re a reminder that the page needs your input before publishing.
Technically yes, but we don’t recommend it. Google can identify templated content (thin content) and may penalize the page. Spend 15–20 minutes adding real data — this is critical for results.
SaaSForge generates semantic HTML without styles because it doesn’t know what your site looks like. After publishing, the page will automatically inherit your theme or CSS styles. For custom React/Next.js sites, a component with Tailwind classes is generated instead.
On the Free plan — 1 page. On Starter and above — all 6 page types with no quantity limits. Integration pages and use case pages scale: one integration or vertical = one page.
Publishing a large number of similar pages in a short time is a programmatic spam signal for Google. This can lead to demotion of the entire domain. Recommendation: no more than 3–5 new pages per week.
GEO visibility (mentions in ChatGPT) — 2–4 weeks after publishing pages, provided you’ve registered on G2 and Capterra. Google indexation — 3–14 days. Organic traffic — 2–4 months. These are realistic timelines, not promises.
SEO is inherently slow — Google indexes and evaluates content gradually. GEO works faster because AI search engines update more frequently. But even GEO takes time — AI needs to "see" your new pages through indexation.
Possible reasons: pages not yet indexed by Google (wait 1–2 weeks), no G2/Capterra registration (critical for GEO), placeholders not filled in (thin content), domain is too new (low authority). Check your action plan checklist — there are likely uncompleted items there.
Yes, especially if the competitor has been around for a long time and has many mentions. GEO is a marathon, not a sprint. Your goal is not to overtake the leader in a month — it’s to gradually increase your own visibility. Realistic growth: from 5–10% to 25–35% in 2–3 months of consistent work.
Perplexity and ChatGPT with search enabled use Bing’s index as one of their primary sources of current data. This means the quality of your Bing indexation directly affects your GEO visibility in these AI search engines. Registration is free and takes 10 minutes — one of the fastest actions with a disproportionately large impact on results.
It depends on your platform. In the dashboard after Schema generation, there is an "Instructions" button — it opens a step-by-step guide for your platform (WordPress, Webflow, Framer, Next.js, etc.).
llms.txt is a text file in the root of your site that tells AI crawlers which pages are important and what your product does. Similar to robots.txt but for AI. It takes 15 minutes to create and improves how AI systems understand your product. Instructions are in the Action Plan.
Some sites are protected against automated scanning (Cloudflare, CAPTCHAs). In this case the system shows a warning and offers to enter the relevant page URLs manually for a partial analysis.
Yes. Your product data is stored in an encrypted database and is not shared with third parties. Generated pages belong to you. See the Privacy Policy for details.
See the full process from start to finish.
How SaaSForge works →