Tutorial

Reading citation sources in VStok

Which domains shape AI answers about your brand — and how to influence them.

Citations are the hidden layer of AI answers

When Perplexity answers a buyer question, it often shows linked sources. ChatGPT with browsing, Gemini, and Claude may ground responses in retrieved pages even when links are not visible to the user. Those domains shape facts, rankings, and tone — sometimes more than whether your brand name appears in the final paragraph.

VStok captures citation sources during audits: which URLs and domains models rely on when responding to your tracked prompts. Aggregated over time, this view shows whether AI trusts your site, leans on review platforms, or parrots competitor content hubs.

Reading citations turns visibility from a score into an action plan. A strong mention with weak owned-domain citations means you are winning narratively but not controlling the evidence trail.

How to read the citation report

Start at the domain level. High-frequency domains across commercial and comparison prompts are the pillars of your category's AI knowledge graph. If g2.com, reddit.com, and a competitor's docs site dominate, your blog traffic is not the full picture — those third parties are teaching the models.

Drill into prompt clusters. Educational prompts may cite Wikipedia and industry media; pricing prompts may cite your pricing page or a outdated aggregator. Misalignment — stale pricing on a review site cited instead of your page — is a fixable AEO issue.

Compare citations across models. Perplexity often surfaces more explicit sources than ChatGPT; Gemini may weight Google-indexed properties differently. VStok's per-model breakdown helps you prioritize: fix what matters for the engines your ICP actually uses.

Influencing which sources get cited

Owned media: ensure key pages are crawlable, structured with schema, listed in llms.txt, and written for extraction — clear headings, factual bullets, dated updates. Site audit in VStok flags gaps that reduce the chance models retrieve your URLs.

Earned media: reviews, analyst mentions, podcast transcripts, and guest posts create durable citations. Agencies often win AI answers through client case studies on third-party sites before their own domain ranks. Budget for review velocity on platforms that appear repeatedly in your citation report.

Community presence: Reddit, Stack Overflow, and niche Slack exports feed training and retrieval corpora. Authentic participation beats astroturfing; models and platforms penalize spam. Answer real questions with specifics — implementation detail gets cited, marketing fluff does not.

Turning citation insights into a quarterly plan

Export citation trends from VStok after each audit cycle. Tag domains as owned, earned, competitor, or neutral. Set quarterly goals: increase owned citation share on top ten commercial prompts by five points, or displace a competitor's docs domain on integration-related questions.

Pair citation work with prompt-level visibility. If mentions rise but citations stay on third-party summaries, deepen on-site technical content so models prefer your primary source. If citations land on your domain but mentions drop, competitors may be winning on narrative adjectives — address with comparison and proof points.

Share citation findings in stakeholder reports alongside visibility score and share of voice. Leadership understands "we are not the source AI quotes for enterprise security questions" faster than abstract metric deltas. Citations make AEO concrete.

Ready to understand why AI recommends competing apps?

Run a free mobile baseline, inspect the evidence, and save the highest-impact fixes to Action Center.