Do they name you without being asked?
4/44
unprompted answers
Acme Analytics is named in 4 of 44 unprompted answers.
Acme Analytics is almost never recommended unless the buyer already asks for it.
Do they name you without being asked?
4/44
unprompted answers
Acme Analytics is named in 4 of 44 unprompted answers.
When they answer, do they cite your site?
18/63
answers cited your domain
acme-analytics.example was a cited source in 18 of 63 answers.
Who owns the links in the top 10?
18/142
of top-10 citation mass
posthog.com leads the pack. acme-analytics.example is #2 (18 of 142 top-10 citations).
Citation counts across all models in this run. Subdomains are rolled up to the parent domain. You are #2 on this list. These surfaces are shaping answers.
Same prompts. Different source graphs. Read the pack above as an average — then check who actually disagrees.
16 answers
15 answers
16 answers
16 answers
| Domain | Claude | Grok | OpenAI | Perplexity |
|---|---|---|---|---|
| posthog.com | 7 | 5 | 6 | 2 |
| acme-analytics.example | 5 | 1 | 7 | 6 |
| plausible.io | 4 | 5 | 6 | 3 |
| support.google.com | 5 | 8 | 11 | 1 |
| baremetrics.com | 5 | 3 | 2 | 4 |
| usefathom.com | 3 | 5 | 3 | 2 |
| chartmogul.com | 5 | 3 | 5 | · |
| dreamdata.io | 5 | 1 | 5 | · |
| triplewhale.com | 4 | 3 | 4 | · |
| developers.google.com | 5 | 8 | 11 | 1 |
Share of all extracted citations, grouped by what kind of surface it is.
Demand clusters from this run. Themes only — raw prompts stay out of the report.
Acme Analytics is almost never recommended unless the buyer already asks for it.
Acme Analytics is almost never recommended unless the buyer already asks for it.
Brand appears in answers when not named in the prompt
Organic visibility is 9% — 4 of 44 unprompted answers named Acme Analytics. Guide-style questions currently have no official page models can quote.
| Path | /guides/what-to-look-for-in-revenue-analytics |
| Effort | Low |
| Goal | Become the default cited explainer for how to choose Revenue analytics. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a marketing page in Markdown (or semantic HTML) for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Official site: https://acme-analytics.example Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product in one paragraph: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Typical jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI A common alternative models already cite: posthog.com Page URL to assume: https://acme-analytics.example/guides/what-to-look-for-in-revenue-analytics Goal: a quotable “what to look for in Revenue analytics” guide that AI answers can cite when a buyer has not named Acme Analytics. Tone: plain, confident, founder-to-founder. No hype, no superlatives, no “game-changing”. Short sentences. Required structure: 1. 3 headline options (H1). Pick a recommended one. 2. Opening: the buying problem in ≤60 words. Include this sentence verbatim unless you can make it tighter: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 3. “What to look for” — 5–7 evaluation criteria with 2–3 lines each. 4. “Where Acme Analytics fits” — one screen: who it’s for, who should use posthog.com instead. 5. Comparison table dimensions (fill honestly; invent no fake numbers): job-to-be-done, time-to-value, attribution depth, privacy/cookies, who it’s for. 6. FAQ — 3 questions a buyer actually asks, including one about posthog.com. 7. CTA: one line, link to https://acme-analytics.example/, no urgency language. Output: a complete page draft ready to paste into a CMS or a Next.js/React page. Mark the recommended H1.
g2.com was cited 7 times. Models treat review indexes as a shopping list. An empty or stale profile is a missed unprompted mention.
| Path | listing on g2.com |
| Effort | Low |
| Goal | Make the g2.com profile a complete, quotable Acme Analytics card. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write the copy for Acme Analytics's official listing on g2.com. Brand: Acme Analytics (https://acme-analytics.example) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Deliver: 1. 40-word listing description. Include this idea: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 2. Category / tag suggestions (8 max) using buyer language. 3. 3 short “best for” bullets. 4. 3 “not for” bullets. 5. One-line pricing shape (use [price] if unknown — do not invent). 6. Homepage URL: https://acme-analytics.example/ Tone: same as a review-site card, not a landing page. No hype. Output: labeled fields ready to paste into g2.com.
Best-of and alternatives prompts name whoever already has a public list. Acme Analytics is volunteered in 9% of unprompted answers — a roundup with Acme Analytics in the set is how you get named without being asked.
| Path | /alternatives/revenue-analytics |
| Effort | Medium |
| Goal | Own 'best Revenue analytics tools / alternatives' with a fair list that includes Acme Analytics. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a public “best Revenue analytics tools / alternatives” roundup for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Official site: https://acme-analytics.example Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Known alternatives: Plausible, Fathom Analytics, Simple Analytics, PostHog, Mixpanel, Amplitude Page URL: https://acme-analytics.example/alternatives/revenue-analytics Goal: a citable shopping-list page. Acme Analytics is in the set, not the only item. Tone: plain, fair, founder-to-founder. No hype. Required: 1. 3 H1 options; recommend one that does not start with Acme Analytics. 2. Opening ≤70 words. Include: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 3. Table of 8–12 tools (use the known alternatives; invent no fake products). Columns: best for, time-to-value, when not to use. 4. A “pick Acme Analytics when…” paragraph that is specific. 5. Last-updated line. 6. CTA to https://acme-analytics.example/ — one line. Output: complete Markdown or semantic HTML, ready to ship.
Models already pull product names from reddit.com (9 citations in this run). A specific, non-sales comparison in a thread they cite beats a new blog post.
| Path | comment on reddit.com |
| Effort | Medium |
| Goal | Get a lived-use Acme Analytics mention into a thread models already cite. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a comment I can post on reddit.com about Revenue analytics. I founded / work on Acme Analytics (https://acme-analytics.example). Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Rules: - Non-sales. Lead with the job I was trying to do, not the brand. - 180–280 words. - One concrete lived-use comparison (workflow or metric). No fake numbers — use placeholders like [X%] if unknown. - State when I would still pick an alternative instead of Acme Analytics. - Mention posthog.com fairly if relevant. - Include this idea, not necessarily verbatim: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” - Link https://acme-analytics.example at most once, only if it answers the question. - Tone: plain, specific, slightly dry. No emojis, no “happy to help”. Output: the comment only, ready to paste.
Buyers describe the job, not the category. A page that names this problem gives models a Acme Analytics-owned URL when the prompt never says Acme Analytics.
| Path | /guides/analytics-tools-that-report-pageviews-visitors-a |
| Effort | Medium |
| Goal | Get cited when someone asks how to solve: Analytics tools that report pageviews, visitors, and bounce rate instead of revenue. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a guide page about this problem: Analytics tools that report pageviews, visitors, and bounce rate instead of revenue Brand: Acme Analytics (https://acme-analytics.example) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Page URL: https://acme-analytics.example/guides/analytics-tools-that-report-pageviews-visitors-a Goal: get cited when someone asks how to solve this problem without naming Acme Analytics. Tone: plain, specific. H1 is the problem, not the brand. Required: 1. 3 H1 options that name the problem. 2. What good looks like (3–5 tests). 3. How to approach it (5 steps). 4. Where Acme Analytics fits — one paragraph including: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 5. When this is the wrong tool. 6. CTA to https://acme-analytics.example/. Output: complete Markdown or semantic HTML.
Buyers describe the job, not the category. A page that names this problem gives models a Acme Analytics-owned URL when the prompt never says Acme Analytics.
| Path | /guides/not-knowing-which-marketing-channels-produce-pay |
| Effort | Medium |
| Goal | Get cited when someone asks how to solve: Not knowing which marketing channels produce paying customers versus empty traffic. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a guide page about this problem: Not knowing which marketing channels produce paying customers versus empty traffic Brand: Acme Analytics (https://acme-analytics.example) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Page URL: https://acme-analytics.example/guides/not-knowing-which-marketing-channels-produce-pay Goal: get cited when someone asks how to solve this problem without naming Acme Analytics. Tone: plain, specific. H1 is the problem, not the brand. Required: 1. 3 H1 options that name the problem. 2. What good looks like (3–5 tests). 3. How to approach it (5 steps). 4. Where Acme Analytics fits — one paragraph including: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 5. When this is the wrong tool. 6. CTA to https://acme-analytics.example/. Output: complete Markdown or semantic HTML.
Yearly best-of answers recycle last year's URLs. A dated roundup on acme-analytics.example is how Acme Analytics gets into the next cycle's citations.
| Path | /blog/best-revenue-analytics-2026 |
| Effort | Medium |
| Goal | Have a 2026 URL ready when models look for this year's list. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a public “best Revenue analytics tools / alternatives” roundup for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Official site: https://acme-analytics.example Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Known alternatives: Plausible, Fathom Analytics, Simple Analytics, PostHog, Mixpanel, Amplitude Page URL: https://acme-analytics.example/blog/best-revenue-analytics-2026 Goal: a citable shopping-list page. Acme Analytics is in the set, not the only item. Tone: plain, fair, founder-to-founder. No hype. Required: 1. 3 H1 options; recommend one that does not start with Acme Analytics. 2. Opening ≤70 words. Include: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 3. Table of 8–12 tools (use the known alternatives; invent no fake products). Columns: best for, time-to-value, when not to use. 4. A “pick Acme Analytics when…” paragraph that is specific. 5. Last-updated line. 6. CTA to https://acme-analytics.example/ — one line. Output: complete Markdown or semantic HTML, ready to ship.
acme-analytics.example is a working citation — keep feeding it pages models can quote.
Official domain is cited, scaled so 25% of answers = 100
High when mentioned — still rare unprompted.
acme-analytics.example was cited 18 times across 63 answers (brand-as-source 100). Citations land here — the opening lines are what models reuse.
| Path | / |
| Effort | Low |
| Goal | Make the first screen of acme-analytics.example a sentence models can cite as what Acme Analytics is. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Rewrite the homepage above-the-fold copy for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Canonical definition URL to link: https://acme-analytics.example/what-is-acme-analytics Goal: when an AI model cites acme-analytics.example, the first paragraph is a usable product definition. Tone: plain, confident, no hype. Deliver: 1. 5 H1 options. Recommend one. H1 = problem + who it’s for, not a slogan. 2. Opening paragraph ≤60 words that includes this definition (tighten if needed, do not dilute): “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 3. 3 supporting bullets (jobs, not features). 4. One-line secondary CTA linking to https://acme-analytics.example/what-is-acme-analytics (“What Acme Analytics is”). 5. What to delete from a typical SaaS hero (one short list). Output: Markdown suitable for a marketing homepage. No fake social-proof numbers.
Comparison and best-of answers need a stable official URL. Homepage copy changes; a definition page stays citable.
| Path | /what-is-acme-analytics |
| Effort | Low |
| Goal | Give models one official URL that states what Acme Analytics is and is not. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a canonical “what is Acme Analytics” page in Markdown or semantic HTML. Brand: Acme Analytics URL: https://acme-analytics.example/what-is-acme-analytics Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Homepage: https://acme-analytics.example/ Goal: one official URL models can cite as the definition of Acme Analytics. Tone: plain, confident, encyclopedia-brief, no hype. Required sections: 1. 3 H1 options; recommend one. 2. 40-word product definition. Start from: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 3. Who it’s for / who it’s not for (two short lists). 4. How it works (5 steps max). 5. Pricing shape in one honest line (use [price] if unknown — do not invent). 6. FAQ — 3 questions, including “How is this different from posthog.com?” 7. CTA linking to https://acme-analytics.example/. Output: a complete page draft. No comparison table vs a named competitor (that lives on /vs pages).
FAQ pages are easy to cite: one question, one paragraph. Brand-as-source is 100 — extra official URLs raise the chance acme-analytics.example is the link.
| Path | /faq |
| Effort | Low |
| Goal | Cover the 6 questions buyers (and models) ask about Acme Analytics. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write an FAQ page for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. A common alternative: posthog.com Page URL: https://acme-analytics.example/faq Required questions (add 2 more if useful): - What is Acme Analytics? - Who is it for / not for? - How is it different from posthog.com? - How long to first value? - Pricing shape? - Where do I start? Each answer ≤120 words. The first answer should include: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” Tone: plain, encyclopedia-brief. Output: complete Markdown FAQ.
When models cite acme-analytics.example, they need a how-it-works URL, not only a homepage. A 5-step start page is what 'how do I use Acme Analytics' answers copy.
| Path | /get-started |
| Effort | Medium |
| Goal | Give models a copy-pasteable getting-started URL on acme-analytics.example. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a get-started page for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Typical jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Page URL: https://acme-analytics.example/get-started Goal: a page models can quote as “how Acme Analytics works”. Required: 1. Prerequisites (3 bullets). 2. 5 steps max, each with a command or UI click. Use placeholders like [project] if unknown. 3. What you should see when it worked. 4. One troubleshooting note. 5. Link to https://acme-analytics.example/ and to a docs root. Include this definition somewhere near the top: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” Tone: tutorial, short sentences. No hype. Output: complete Markdown.
Models cite pages that match the job in the prompt. A dedicated URL for this use case is a landing site for citations that today miss acme-analytics.example.
| Path | /use-cases/identify-marketing-channels-that-drive-paying-cu |
| Effort | Medium |
| Goal | Own the 'Identify marketing channels that drive paying customers, not just clicks' query with an official Acme Analytics page. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a use-case page: Identify marketing channels that drive paying customers, not just clicks Brand: Acme Analytics (https://acme-analytics.example) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Page URL: https://acme-analytics.example/use-cases/identify-marketing-channels-that-drive-paying-cu H1 = the job, not a slogan. Include: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” Required: 1. Who this is for. 2. How it works (5 steps). 3. What good looks like. 4. When Acme Analytics is the wrong tool for this job. 5. CTA to https://acme-analytics.example/. Tone: specific, no hype. Invent no fake metrics. Output: complete Markdown or semantic HTML.
Models cite pages that match the job in the prompt. A dedicated URL for this use case is a landing site for citations that today miss acme-analytics.example.
| Path | /use-cases/attribute-stripe-shopify-polar-and-lemon-squeezy |
| Effort | Medium |
| Goal | Own the 'Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns' query with an official Acme Analytics page. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a use-case page: Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns Brand: Acme Analytics (https://acme-analytics.example) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Page URL: https://acme-analytics.example/use-cases/attribute-stripe-shopify-polar-and-lemon-squeezy H1 = the job, not a slogan. Include: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” Required: 1. Who this is for. 2. How it works (5 steps). 3. What good looks like. 4. When Acme Analytics is the wrong tool for this job. 5. CTA to https://acme-analytics.example/. Tone: specific, no hype. Invent no fake metrics. Output: complete Markdown or semantic HTML.
The lead pack belongs to others. posthog.com is shaping answers more than Acme Analytics.
Share of citation mass among the top 10 domains
Graph presence is 13% — one URL that lists Acme Analytics against Google Analytics, PostHog, Plausible, Stripe is what roundup answers scrape.
| Path | /compare |
| Effort | Low |
| Goal | Give models a single Acme Analytics comparison index, then deep-link to each /vs page. |
Must include
Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.
Done means
Write a comparison hub page for Acme Analytics (https://acme-analytics.example). Brand: Acme Analytics Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Rivals to include: Google Analytics, PostHog, Plausible, Stripe Page URL: https://acme-analytics.example/compare This page indexes vs pages. Deep links: - Acme Analytics vs Google Analytics → https://acme-analytics.example/vs/google-analytics - Acme Analytics vs PostHog → https://acme-analytics.example/vs/posthog - Acme Analytics vs Plausible → https://acme-analytics.example/vs/plausible - Acme Analytics vs Stripe → https://acme-analytics.example/vs/stripe Required: 1. Short definition including: “Acme Analytics is Revenue analytics for Indie founders — Identify marketing channels that drive paying customers, not just clicks.” 2. Table: rival | pick Acme Analytics when | pick them when | link to /vs/… 3. Last-updated line. 4. CTA to https://acme-analytics.example/. Tone: index page, not a full comparison. Fair. Output: complete Markdown.
google.com shows up in comparison answers (25 citations in this run). Acme Analytics's graph presence is 13% of the top 10. A public vs page is the URL models can cite instead.
| Path | /vs/google |
| Effort | Medium |
| Goal | Own the Acme Analytics vs Google Analytics query with an honest table on acme-analytics.example. |
Must include
Pick Acme Analytics over Google Analytics when the job is Identify marketing channels that drive paying customers, not just clicks; pick Google Analytics when you need a broader Revenue analytics suite.
Done means
Write a public comparison page: Acme Analytics vs Google Analytics. Brand: Acme Analytics (https://acme-analytics.example) Competitor: Google Analytics (google.com) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Page URL: https://acme-analytics.example/vs/google Context: google.com was cited 25 times in an AI citation audit of Revenue analytics answers. This page must be citable instead of sending buyers only to google.com. Tone: plain, confident, honest. No hype. Say when Google Analytics wins. Required structure: 1. 3 H1 options (include “Acme Analytics vs Google Analytics”). Recommend one. 2. Opening ≤80 words. Include this sentence (tighten if needed): “Pick Acme Analytics over Google Analytics when the job is Identify marketing channels that drive paying customers, not just clicks; pick Google Analytics when you need a broader Revenue analytics suite.” 3. Comparison table with rows: - Best for - Job-to-be-done - Attribution / revenue tracking - Privacy / cookies - Time-to-value - Pricing shape (use [price] if unknown — do not invent) - When not to use Canonical product link in the Acme Analytics column: https://acme-analytics.example/ — never google.com as the Acme Analytics URL. 4. “When to pick Acme Analytics” and “When to pick Google Analytics” — two short sections, equally fair. 5. FAQ — 4 questions a buyer typing “Acme Analytics vs Google Analytics” actually has. 6. CTA: try Acme Analytics at https://acme-analytics.example/. No fake urgency. Output: complete Markdown or semantic HTML for a marketing page, ready to ship.
posthog.com shows up in comparison answers (20 citations in this run). Acme Analytics's graph presence is 13% of the top 10. A public vs page is the URL models can cite instead.
| Path | /vs/posthog |
| Effort | Medium |
| Goal | Own the Acme Analytics vs PostHog query with an honest table on acme-analytics.example. |
Must include
Pick Acme Analytics over PostHog when the job is Identify marketing channels that drive paying customers, not just clicks; pick PostHog when you need a broader Revenue analytics suite.
Done means
Write a public comparison page: Acme Analytics vs PostHog. Brand: Acme Analytics (https://acme-analytics.example) Competitor: PostHog (posthog.com) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Page URL: https://acme-analytics.example/vs/posthog Context: posthog.com was cited 20 times in an AI citation audit of Revenue analytics answers. This page must be citable instead of sending buyers only to posthog.com. Tone: plain, confident, honest. No hype. Say when PostHog wins. Required structure: 1. 3 H1 options (include “Acme Analytics vs PostHog”). Recommend one. 2. Opening ≤80 words. Include this sentence (tighten if needed): “Pick Acme Analytics over PostHog when the job is Identify marketing channels that drive paying customers, not just clicks; pick PostHog when you need a broader Revenue analytics suite.” 3. Comparison table with rows: - Best for - Job-to-be-done - Attribution / revenue tracking - Privacy / cookies - Time-to-value - Pricing shape (use [price] if unknown — do not invent) - When not to use Canonical product link in the Acme Analytics column: https://acme-analytics.example/ — never posthog.com as the Acme Analytics URL. 4. “When to pick Acme Analytics” and “When to pick PostHog” — two short sections, equally fair. 5. FAQ — 4 questions a buyer typing “Acme Analytics vs PostHog” actually has. 6. CTA: try Acme Analytics at https://acme-analytics.example/. No fake urgency. Output: complete Markdown or semantic HTML for a marketing page, ready to ship.
plausible.io shows up in comparison answers (18 citations in this run). Acme Analytics's graph presence is 13% of the top 10. A public vs page is the URL models can cite instead.
| Path | /vs/plausible |
| Effort | Medium |
| Goal | Own the Acme Analytics vs Plausible query with an honest table on acme-analytics.example. |
Must include
Pick Acme Analytics over Plausible when the job is Identify marketing channels that drive paying customers, not just clicks; pick Plausible when you need a broader Revenue analytics suite.
Done means
Write a public comparison page: Acme Analytics vs Plausible. Brand: Acme Analytics (https://acme-analytics.example) Competitor: Plausible (plausible.io) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Page URL: https://acme-analytics.example/vs/plausible Context: plausible.io was cited 18 times in an AI citation audit of Revenue analytics answers. This page must be citable instead of sending buyers only to plausible.io. Tone: plain, confident, honest. No hype. Say when Plausible wins. Required structure: 1. 3 H1 options (include “Acme Analytics vs Plausible”). Recommend one. 2. Opening ≤80 words. Include this sentence (tighten if needed): “Pick Acme Analytics over Plausible when the job is Identify marketing channels that drive paying customers, not just clicks; pick Plausible when you need a broader Revenue analytics suite.” 3. Comparison table with rows: - Best for - Job-to-be-done - Attribution / revenue tracking - Privacy / cookies - Time-to-value - Pricing shape (use [price] if unknown — do not invent) - When not to use Canonical product link in the Acme Analytics column: https://acme-analytics.example/ — never plausible.io as the Acme Analytics URL. 4. “When to pick Acme Analytics” and “When to pick Plausible” — two short sections, equally fair. 5. FAQ — 4 questions a buyer typing “Acme Analytics vs Plausible” actually has. 6. CTA: try Acme Analytics at https://acme-analytics.example/. No fake urgency. Output: complete Markdown or semantic HTML for a marketing page, ready to ship.
stripe.com shows up in comparison answers (15 citations in this run). Acme Analytics's graph presence is 13% of the top 10. A public vs page is the URL models can cite instead.
| Path | /vs/stripe |
| Effort | Medium |
| Goal | Own the Acme Analytics vs Stripe query with an honest table on acme-analytics.example. |
Must include
Pick Acme Analytics over Stripe when the job is Identify marketing channels that drive paying customers, not just clicks; pick Stripe when you need a broader Revenue analytics suite.
Done means
Write a public comparison page: Acme Analytics vs Stripe. Brand: Acme Analytics (https://acme-analytics.example) Competitor: Stripe (stripe.com) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Page URL: https://acme-analytics.example/vs/stripe Context: stripe.com was cited 15 times in an AI citation audit of Revenue analytics answers. This page must be citable instead of sending buyers only to stripe.com. Tone: plain, confident, honest. No hype. Say when Stripe wins. Required structure: 1. 3 H1 options (include “Acme Analytics vs Stripe”). Recommend one. 2. Opening ≤80 words. Include this sentence (tighten if needed): “Pick Acme Analytics over Stripe when the job is Identify marketing channels that drive paying customers, not just clicks; pick Stripe when you need a broader Revenue analytics suite.” 3. Comparison table with rows: - Best for - Job-to-be-done - Attribution / revenue tracking - Privacy / cookies - Time-to-value - Pricing shape (use [price] if unknown — do not invent) - When not to use Canonical product link in the Acme Analytics column: https://acme-analytics.example/ — never stripe.com as the Acme Analytics URL. 4. “When to pick Acme Analytics” and “When to pick Stripe” — two short sections, equally fair. 5. FAQ — 4 questions a buyer typing “Acme Analytics vs Stripe” actually has. 6. CTA: try Acme Analytics at https://acme-analytics.example/. No fake urgency. Output: complete Markdown or semantic HTML for a marketing page, ready to ship.
baremetrics.com shows up in comparison answers (14 citations in this run). Acme Analytics's graph presence is 13% of the top 10. A public vs page is the URL models can cite instead.
| Path | /vs/baremetrics |
| Effort | Medium |
| Goal | Own the Acme Analytics vs Baremetrics query with an honest table on acme-analytics.example. |
Must include
Pick Acme Analytics over Baremetrics when the job is Identify marketing channels that drive paying customers, not just clicks; pick Baremetrics when you need a broader Revenue analytics suite.
Done means
Write a public comparison page: Acme Analytics vs Baremetrics. Brand: Acme Analytics (https://acme-analytics.example) Competitor: Baremetrics (baremetrics.com) Category: Revenue analytics Audience: Indie founders, SaaS operators, and marketers who need to attribute paying-customer revenue to channels, pages, and campaigns Product: Acme Analytics is a revenue-focused web analytics product created by its founder for founders who need to see which channels, pages, and campaigns produce paying customers rather than vanity traffic metrics. It attributes revenue to sources such as SEO, ads, social posts, email, affiliates, and offline QR codes, and includes funnels, visitor journeys, cookieless tracking, payment-provider integrations, an API, a CLI, and an MCP server for AI agents. Jobs: Identify marketing channels that drive paying customers, not just clicks; Attribute Stripe, Shopify, Polar, and Lemon Squeezy revenue to pages, posts, and campaigns; Measure SEO, YouTube, newsletter, Reddit, affiliate, and sponsorship ROI Page URL: https://acme-analytics.example/vs/baremetrics Context: baremetrics.com was cited 14 times in an AI citation audit of Revenue analytics answers. This page must be citable instead of sending buyers only to baremetrics.com. Tone: plain, confident, honest. No hype. Say when Baremetrics wins. Required structure: 1. 3 H1 options (include “Acme Analytics vs Baremetrics”). Recommend one. 2. Opening ≤80 words. Include this sentence (tighten if needed): “Pick Acme Analytics over Baremetrics when the job is Identify marketing channels that drive paying customers, not just clicks; pick Baremetrics when you need a broader Revenue analytics suite.” 3. Comparison table with rows: - Best for - Job-to-be-done - Attribution / revenue tracking - Privacy / cookies - Time-to-value - Pricing shape (use [price] if unknown — do not invent) - When not to use Canonical product link in the Acme Analytics column: https://acme-analytics.example/ — never baremetrics.com as the Acme Analytics URL. 4. “When to pick Acme Analytics” and “When to pick Baremetrics” — two short sections, equally fair. 5. FAQ — 4 questions a buyer typing “Acme Analytics vs Baremetrics” actually has. 6. CTA: try Acme Analytics at https://acme-analytics.example/. No fake urgency. Output: complete Markdown or semantic HTML for a marketing page, ready to ship.
What to do now
Publish the pages from Opportunities. Drafts do not change these scores. Wait 30–45 days, then re-run CitePeek.
This report (August 12, 2026) is your starting score. The next run will show what moved.