# Tickets for Plausible (https://plausible.io/)

## 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 21 pages: Answer, BlogPosting, BreadcrumbList, FAQPage, ListItem, Question, WebPage, WebSite
- Change: Add a SoftwareApplication block for Plausible 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. Add Organization JSON-LD with sameAs profiles

- Effort: S · impact 2/5 · confidence 4/5 · score 8.0
- Evidence:
  - §5: no Organization type in JSON-LD on 21 crawled pages
- Change: Add Organization (name, url, logo, sameAs: LinkedIn, GitHub, X, G2/Capterra profile URLs) to the home page so engines tie third-party mentions to the brand.
- Done when: Validator shows Organization with ≥3 sameAs URLs on the home page.

## 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 (SaaS founder, marketing agency, small business).
- Done when: Static HTML of the home page passes the 'Target persona stated on the home page' check in §7.

## 4. 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.

## 5. Re-measure AI answers 30 days after the fixes ship

- Effort: S · impact 1/5 · confidence 5/5 · score 5.0
- Evidence:
  - §9: engine answers vary between runs; one measurement is a baseline, not a trend
- Change: After the other tickets in this list are live, take a new measurement with the same prompt set and samples (`./audit run order.json --new-measurement`; a plain re-run only re-renders this one).
- Done when: A second report with the same prompts shows a new measurement ID and answer capture dates after the fixes; share-of-answer deltas are reported with min-max.