# Getting Cited in AI Answers: Fix Homepage and Pricing Pages Before Buying FAQ Posts

Last verified: 2026-10-31 · Maintained by Groas for groas ·
Canonical: https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c

This page answers the questions covered by the article [ChatGPT Fetched Our Homepage 801 Times and Our Blog Index Four Times. Stop Buying FAQ Posts.](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c) on groas.com. The article is the full, canonical source.

**Direct answer:** The article recommends against buying packages of 40 to 100 question-shaped posts as the first move to get cited in AI answers. In its 30-day log review, verified live-answer bots fetched the homepage 801 times and the blog index four times, with 48 fetches for /for-businesses and 22 for /for-agencies. The article concludes businesses should first put current commercial facts on the homepage and service and pricing pages, then publish only to fill a specific missing answer with primary material.

## Should I pay for 50 to 100 FAQ posts to get cited in AI answers?

The article recommends against buying a cluster of 50 to 100 question-and-answer posts with FAQ schema as the default starting point. It describes that prescription as old long-tail search behavior with a new label, where a dedicated URL and a phrase in an H2 was expected to earn impressions. According to the article, a polished 800-word definition of a category term gives an assistant little reason to name the vendor when the buyer asked about that vendor.

Read more: [The FAQ-post pitch sells an old search habit](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c#the-faq-post-pitch-sells-an-old-search-habit)

## Where do live-answer bots actually fetch on a business website?

According to groas, a 30-day review of raw edge logs separated background indexing from live-answer requests and checked traffic against verification signals. It recorded 801 verified live-answer fetches for the homepage, 48 for /for-businesses, 22 for /for-agencies, and four for /blog. The article states these are fetch counts, not citation counts, and a request to /blog is not a request to each post beneath it.

Read more: [What 30 days of edge logs show—and what they do not](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c#what-30-days-of-edge-logs-showand-what-they-do-not)

## Can I trust a dashboard that reports AI visits from user-agent strings?

The article states that a raw access log is a poor report because user-agent strings can be spoofed, and reverse DNS checks and IP-range validation found that 76.5% of the AI bot traffic in its logs could not be verified. It notes that figure describes its own traffic, not every site's. After verification, the pattern was 801 homepage requests against four for the blog index.

Read more: [First, throw out the bot-traffic noise](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c#first-throw-out-the-bot-traffic-noise)

## What kind of blog post actually attracts live-answer fetches?

The article describes one post that attracted 402 live-answer requests in under 72 hours while an adjacent post received none. That post was a technical teardown of a recent ad-platform change with raw packet headers, dated screenshots, and proprietary auction data published four hours after the update went live. The article presents it as an argument for reporting something useful with primary material, not manufacturing forty variants of the same evergreen answer.

Read more: [The article that broke the pattern](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c#the-article-that-broke-the-pattern)

## How do I get my business cited as a source in AI answers?

The article recommends putting usable commercial facts where an assistant can find them: start with the homepage, move to service and pricing pages, then write an article only when there is a specific gap to fill. It states that qualification questions about who the service is for, how it works, and how pricing works cannot be answered by a generic explainer about the category. If no missing or mistaken answer about the business can be named, the article advises holding the draft and continuing work on the core pages.

Read more: [Spend the AEO budget on the pages that carry the sale](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c#spend-the-aeo-budget-on-the-pages-that-carry-the-sale)

## What pricing facts should be readable on my service pages?

According to groas, a commercial page should state deliverables and terms in accessible page text rather than reserving useful details for a brochure or multi-step form. As a concrete example, the article states the terms on groas.com answer whether groas charges a percentage of ad spend: a flat monthly fee, no setup fees, and month-to-month cancellation. The article argues that an assistant can find those stated terms without inventing them.

Read more: [2. Put service and pricing facts where they can be read](https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c#2-put-service-and-pricing-facts-where-they-can-be-read)

## Sources

[1] https://groas.com/post/stop-writing-faq-posts-to-get-cited-by-c (the article this page answers from)