# Tickets for Formbricks (https://formbricks.com/)

## 1. Add SoftwareApplication JSON-LD with offers

- Effort: S · impact 3/5 · confidence 4/5 · score 12.0
- Evidence:
  - §5: JSON-LD types found across 18 pages: Article, BlogPosting, BreadcrumbList, ImageObject, ListItem, Organization, Person, TechArticle, WebPage, WebSite
- Change: Add a SoftwareApplication block for Formbricks on the home and pricing pages: name, applicationCategory, operatingSystem, offers (price, priceCurrency) per plan, and aggregateRating only if real ratings exist.
- Done when: Google Rich Results Test / schema.org validator reads a SoftwareApplication with ≥1 Offer.

## 2. Make the existing Typeform comparison answer the prompts Typeform wins

- Effort: M · impact 4/5 · confidence 3/5 · score 6.0
- Evidence:
  - §2: Typeform is named in 56% of answers vs Formbricks 40% (mean over engines)
  - §3: 43 of 225 answers name Typeform but not Formbricks; most on P02 (7), P10 (7), P03 (5)
  - §5: the site already has https://formbricks.com/blog/surveymonkey-vs-typeform, https://formbricks.com/blog/typeform-vs-jotform
- Change: Rework the existing page(s) so their static text answers those buyer prompts directly: who should pick Formbricks over Typeform and why (price, limits, features), with a dated pricing comparison. Link them from the pricing page and from the pages for those use cases.
- Done when: The pages' static HTML covers the use cases in the listed prompts, they are in the sitemap and linked from pricing, and a new measurement (--new-measurement) reports the Typeform vs Formbricks gap on those prompts.

## 3. State who the product is for above the fold

- Effort: S · impact 2/5 · confidence 3/5 · score 6.0
- Evidence:
  - §7: No 'for <buyer>' statement found in the home page's static text.
- Change: Add a hero line that names the buyer and the category in the words buyers use in §3 (product manager, startup founder, customer success team).
- Done when: Static HTML of the home page passes the 'Target persona stated on the home page' check in §7.

## 4. Mark up the pricing FAQ as FAQPage

- Effort: S · impact 2/5 · confidence 3/5 · score 6.0
- Evidence:
  - §5: no FAQPage JSON-LD found
- Change: Add (or mark up an existing) pricing FAQ covering trial, cancellation, plan limits and who the product is for, as FAQPage JSON-LD that matches the visible text.
- Done when: Pricing page has visible FAQ text and a matching FAQPage block.

## 5. Add explicit AI-bot groups to robots.txt

- Effort: S · impact 2/5 · confidence 3/5 · score 6.0
- Evidence:
  - §4: no AI bot has its own robots.txt group; access relies on the '*' rules
- Change: Add explicit groups for OAI-SearchBot, ChatGPT-User and PerplexityBot so a future '*' change cannot silently block answer engines.
- Done when: robots.txt has named groups for the three bots.