Algorithmic Authority Stack · Layer 4: Training-Ready Content

Fix Citation Invisibility: Why AI Ignores Your Content

You ranked. You published. AI cited your competitor anyway. Sometimes the reason is structural: a relevant passage AI could lift cleanly wasn't there to find. This guide shows you how to structure content so a relevant answer is easy to locate, understand, and attribute, and how to tell a structure problem apart from a retrieval or authority one.

By Maria Dykstra · AI Visibility Architect · Last updated: July 2026

Open Perplexity AI. Type the question your best blog post answers. The one you spent three days writing. Read the response. Read the citations. Is your post in the list?

If it isn't, that's a symptom, not a diagnosis. A single absence can come from many causes: the system retrieved a different source, judged another page more relevant, preferred a more authoritative one, hadn't refreshed its index, or answered a slightly different sub-query. Passage structure is one possible cause among those. If your post is repeatedly absent despite being accessible and directly relevant, structure is worth checking.

Ranking and citation selection overlap, but they aren't the same thing. One study of Google AI Overviews (Surfer, 10,000 keywords) found 67.82% of its citations came from pages outside the top ten organic results. That shows citation and ordinary rankings don't perfectly align. It doesn't show ranking is irrelevant. Google's AI features run on Google Search infrastructure, so search fundamentals still matter. A page has to become a viable source first. Then its passages have to support the answer clearly.

When your competitor's post makes the answer easier to lift, the citation can go to them even when you rank higher. You keep the ranking. They get the buyer.

Quick Answer

Content becomes easier to cite when a relevant passage answers the question clearly, includes enough context to stand alone, supports its claims, and can be understood without reading the whole page. Clear structure improves the opportunity for extraction. It does not guarantee retrieval or citation. Source authority, relevance, freshness, and platform-specific selection also decide whether a passage gets used.

Most companies with this problem have useful answers buried inside pages built for a linear reading experience that AI retrieval doesn't use. The information is present. The self-contained, attributable passage a system would lift is not.

In Wave 1 of the Algorithmic Authority Index study (20 B2B companies, 5 industries, Q4 2025), content structure was among the most consistent differences between companies that appeared in AI citations and those that didn't. One anonymized audit: a B2B sales intelligence company published 24 blog posts in a year and appeared in no Perplexity or ChatGPT citations for its target category queries. A competitor published 8 posts, several consistently cited. The cited posts opened with a one-sentence answer to the title question, then specific evidence, then explanation. The absent posts opened with a problem narrative and reached the answer in the fourth paragraph. Multiple factors differed, so this is an observed pattern, not a controlled test.

Wave 2, published July 2026, showed how widespread the gap is at category scale. Each industry deep-dive tested 120 vendors across 12 sub-categories and 3 platforms.

In fintech, 74.17% of the 120 were absent from every platform tested. Among the 90 emerging vendors measured separately, 88 were absent (97.78%). Healthcare ran 86% and industrial 84%, both across 120 vendors. The study documents the methodology and the per-industry findings.

This is what the Algorithmic Authority Stack calls Citation Invisibility: a page is accessible and relevant, but its most useful evidence is hard to locate, isolate, understand, or attribute. The content is present. The extractable answer is not.

Run the free 5-minute AI Visibility Test to see where you stand across the 7 layers →

Do you have a citation invisibility problem? Run this test.

Twenty minutes. It shows whether your highest-value content is structured so a relevant answer is easy to lift, or whether the answer is there but hard to isolate.

Run it clean. Three fresh sessions per platform, search enabled, identical prompts, same day. Capture the sources each answer cites. Compare the passages that were selected against your own. One run is too noisy to draw a conclusion from.
01
Run the Perplexity extraction test on your top 5 posts
For each of your top 5 posts by organic traffic, type the question the post is designed to answer into Perplexity AI. Note whether your post is cited. Open the posts cited instead and read their opening. If they lead with a direct answer and yours leads with context, that's a structural difference worth acting on.
02
Check whether your opening answers the question
Read the opening of each post. Does it contain a direct, verifiable answer to the title question, or background and setup? Answer the main question early. Deeper sections should still make sense on their own, since a system may retrieve a section from the middle of the page, not only the opener.
03
Check whether each section stands alone
For each H2 section in your three highest-traffic posts, ask: can this section be understood without the five paragraphs before it? Self-contained sections are easier to lift. SE Ranking observed higher ChatGPT citation rates for pages with sections in the 120 to 180 word range than for pages dominated by very short fragments. Treat that as a formatting clue, not a required length: a section should be long enough to answer one question completely and short enough to scan.
04
Check the strength of your evidence
In each top post, look for claims that are specific, sourced, and verifiable versus generic statements a model could generate from training data. Original evidence gives a system and a reader a stronger reason to choose your page over interchangeable summaries. It isn't required for citation, but it helps.
05
Check freshness against the subject
Note the visible date on your top 10 posts. AI-cited content tends to run fresher than typical organic results (Ahrefs found citations averaged 25.7% fresher). Recency matters most for fast-moving subjects like prices, features, law, and research, and little for evergreen ones. Accurate and current enough for the query beats simply newer.

How to read your results

These are possible causes to investigate against the cited sources, not verdicts. Absence can also come from retrieval, authority, relevance, or index refresh.

ResultScoreWhat it suggests
Top posts appear in citations, openings answer directly, sections stand alone, evidence is specific and sourced Extractable Your content gives systems a clean passage to lift. Any remaining absence is more likely retrieval, authority, or relevance than structure.
Posts appear occasionally, openings set context, sections uneven, evidence thin in places Partially Extractable You get cited when the topic matches exactly and missed on adjacent queries. Restructuring your highest-traffic posts can widen coverage without new content.
Absent across tests, narrative-first structure, sections that depend on prior paragraphs, little specific evidence Citation Invisible The answer is present but hard to isolate. Restructuring what you already have is usually higher-value than publishing more in the same format.
What this test cannot tell you
  • Whether the platform retrieved your page at all
  • Whether structure, not authority or relevance, caused the omission
  • Whether the competing citation came from a more authoritative source
  • Whether your page answers the exact sub-query being resolved
  • Whether your brand is eligible for the recommendation set
  • Whether the same failure appears across platforms
  • Which passage, page, or source to fix first

The Snapshot separates retrieval failure from extraction failure before you rewrite twenty posts.

Why citation invisibility happens. And why more posts can deepen it.

Many AI systems that use retrieval-augmented generation (RAG) work with passages or chunks rather than whole pages. That's why self-contained sections help: a section that only makes sense after five prior paragraphs is harder to lift than one that answers a question on its own. The exact chunking, retrieval, reranking, and summarization differ by platform, and some systems combine multiple sections or use page-level and domain-level signals. Don't assume a fixed number of citation slots per page. Do assume that a clear, standalone passage is easier to use than a buried one.

The difference is visible at the passage level. Here is a weak passage and a strong one on the same topic:

Weak: generic and unsupported
"AI visibility is becoming increasingly important as buying behavior changes. Organizations that adapt tend to see better results, while those that don't risk falling behind. This article explores the key considerations."
AnswerNo direct answer to a specific question
EvidenceNo numbers, sources, dates, or named entities
Stands aloneNothing here a model couldn't generate itself
Strong: specific and attributable
"In the Algorithmic Authority Index Wave 2 fintech test (July 2026), 88 of 90 emerging vendors were absent across ChatGPT, Perplexity, and Google AI Overviews for the defined buyer-query set."
Claim88 of 90 emerging vendors absent
Scope90 emerging fintech vendors, three named platforms, defined query set
Source + dateAlgorithmic Authority Index, July 2026
Stands aloneVerifiable and unreplicable from training data

Why generic content is easy to pass over

Systems do cite clear, authoritative generic explainers when those pages are relevant and well indexed. But when your page repeats what hundreds of sources already say, a model has weaker reason to choose your version specifically. Original, attributable evidence changes that. It gives a system something it can't reproduce without you.

This is what I use Citation Density to measure. It is my editorial gauge of how much attributable, specific, and verifiable evidence a passage carries. It is not an information-theory metric and not a signal any platform publishes. Score a passage on five things: specificity, source attribution, originality, verifiability, and relevance to the question. Then raise the weak passages.

Low Citation Density
"Companies with better content strategies tend to see improved lead generation. Organizations that publish consistently often outperform competitors and build authority over time."
Generic, unsourced, and reproducible from training data. A model can write an equivalent passage without citing you.
High Citation Density
"In the Algorithmic Authority Index Wave 2 fintech test (July 2026), 88 of 90 emerging vendors were absent across ChatGPT, Perplexity, and Google AI Overviews for the defined buyer-query set."
Specific, sourced, scoped, and dated. A system has a concrete reason to cite this passage rather than paraphrase it.

A named entity or a number is not automatically strong evidence. It can be wrong, cherry-picked, or unsupported. Score the quality of the evidence, not the count of nouns.

Why platforms behave differently

Perplexity is web-oriented and usually shows sources, so answer-first structure and current evidence tend to show up in its citations. OpenAI's ChatGPT can search based on the query or when a user invokes it, and otherwise draws on prior model knowledge. Coherent site architecture and internal linking help users navigate, help crawlers discover pages, and help systems understand how your pages relate. A "pillar and spoke" structure is a reasonable way to organize a topic, but it isn't a documented requirement for ChatGPT citation. Build clear topic relationships because they help people and crawlers. No fixed cluster shape guarantees anything.

Does schema markup get you cited by AI?

There's no reliable evidence that it does on its own. Ahrefs tracked 1,885 pages that added JSON-LD and compared them against controls. Across Google AI Overviews, Google AI Mode, and ChatGPT, citations did not meaningfully rise. A separate searchVIU experiment found that during live retrieval, several major systems extracted only visible HTML and did not read the JSON-LD.

So treat citation as two gates. The Two-Gate Model: Gate 1 is inclusion, whether a system retrieves and trusts your page. Gate 2 is citation, whether it can lift a clean answer once it has the page. Structure earns Gate 2. Schema can express meaning to systems that process it, and it helps Google understand your content, but your visible content has to carry the answer on its own, because platform use of JSON-LD varies. Write the visible answer first. Add schema second, and don't expect it to substitute for the answer.

Citation Invisibility is my term for when a page is accessible and relevant but its most useful evidence is hard to locate, isolate, understand, or attribute. Passage structure can contribute. It is one possible cause of citation absence, not proof of the cause whenever a page isn't cited.

How to fix citation invisibility: the sequence

Total time: 4 to 6 hours for your top 10 posts, plus a production habit that builds extractability into the first draft.

When complete: your highest-value posts lead with clear, self-contained, attributable answers a system can lift, and you can tell a structure problem apart from a retrieval or authority one.

Diagnose the gate before restructuring the library. Moving the answer to paragraph one can help. It will not fix a retrieval, authority, or evidence problem. If your pages are already structurally clean and still absent, the block is upstream, not on the page. Confirm which gate is failing before you rewrite everything.
Phase 1: Diagnose
Step 1
Run an extractability audit on your top 20 posts
Time45 minutes
WhatMapping which existing posts give a system a clean passage to lift, which are partly extractable, and which bury the answer despite strong traffic or rankings.
HowPull your top 20 posts by organic impressions from Google Search Console. Score five dimensions per post: (1) does the opening answer the title question directly (Yes / Partial / No); (2) do sections stand alone; (3) is the evidence specific and sourced; (4) how recently was it meaningfully updated; (5) is it linked from a hub page. The posts that score poorly with high traffic are your highest-value restructuring candidates.
OutputA prioritized list of your top 20 posts ranked by the gap between traffic and extractability.
Common mistake: Ranking candidates by traffic rather than by relevance to buyer queries. A post with heavy traffic on a topic buyers don't ask AI about generates little citation value. A lower-traffic post on a question buyers ask constantly is the higher-value target.
Phase 2: Fix
Step 2
Restructure your top posts to answer first
Time20 to 30 minutes per post
WhatLeading each section with a direct answer, then supporting it. Answer-first is the most consistently identified structural factor in AI citation research.
HowFor each H2 section, lead with the shortest complete answer that stays accurate. State the direct answer and its essential qualification together, then give the evidence, then the mechanism. Answer the primary question early in the opener, and make deeper sections understandable on their own so a system can lift one from the middle. Descriptive, question-style headings that reflect how a buyer asks help a system match the section to the query. You don't need an exact keyword match, but "How to calculate customer churn rate" is clearer than "The math behind retention."
OutputYour top posts restructured so each section opens with a direct, self-contained answer.
Common mistake: Cutting a necessary qualification to look "extractable." For medical, legal, financial, or compliance content, the qualification is part of the correct answer. A direct answer that dropped its nuance is a liability. Remove throat-clearing. Keep necessary nuance.
Step 3
Strengthen your evidence where you have it
Time30 to 60 minutes per post
WhatReplacing generic claims with specific, attributable evidence where you have credible data, and citing the best primary source where you don't. This raises Citation Density: how much specific, sourced, verifiable evidence a passage carries.
HowFor each post, find the generic claims ("studies show...") and either replace them with your own data or cite a named primary source. When you use original data, give the finding, the sample or scope, the date, and any material limitation, and lead with it rather than burying it in paragraph seven. Not every page needs original statistics: glossaries, documentation, and definition pages can be strong on clarity and primary sourcing alone.
OutputPosts where the key claims are specific, sourced, and easy to attribute.
Common mistake: Manufacturing weak internal statistics to hit a quota. A vague or unsupported number is worse than an honest primary citation. Add original evidence where it's real; otherwise point to the best source.
Step 4
Add a visible FAQ where readers actually have follow-up questions
Time15 to 20 minutes per post
WhatAdding a visible FAQ section that answers the real follow-up questions a buyer asks, in self-contained form. The visible answer does the work. FAQPage markup can describe that structure for systems that read it.
HowIdentify 3 to 5 genuine follow-up questions your post answers. Write each answer to stand on its own in a few sentences. Add them as a visible FAQ with H3 question headings. You can add FAQPage schema in a Custom HTML block, but add it to describe the visible section, not instead of it. Don't add a FAQ to every post, and don't duplicate the body to manufacture more answer units.
OutputA visible FAQ on the posts where it genuinely helps readers.
Set expectations honestly: Adding schema to already-cited pages produced no citation lift in the Ahrefs test, and several systems ignore JSON-LD during live retrieval. For most commercial B2B sites, don't expect a visible Google FAQ rich result either; Google restricted those to well-known authoritative government and health sites in 2023, and valid markup never guarantees a rich result. Build the visible answer. Treat the markup as supporting, not decisive. Full data in the schema section above.
Common mistake: Writing FAQ questions as promotional prompts. "Why is [company] the best choice?" is not a buyer question. Use the real questions buyers ask; Perplexity's related questions for your topic are a good source.
Phase 3: Deploy
Step 5
Organize content into clear topic clusters
Time2 to 3 hours to plan, then per post
WhatGrouping related content so readers, crawlers, and search systems can see how your pages relate, and so a complex question can be answered from a coherent set rather than one isolated post.
HowMap your content into a few topic areas. For each, keep one thorough overview page that covers the topic and links to the deeper posts, and deeper posts that link back to it. Link in both directions. Length is whatever the material needs. The point is genuine topical coverage and clear internal links that help users and crawlers understand the relationships, not a fixed word count or a required cluster shape.
OutputContent organized into clear topic areas with bidirectional internal links.
Common mistake: Building the structure without the links. An overview page that doesn't link to its deeper posts, and posts that don't link back, don't form a cluster. Both directions matter.
Step 6
Keep your highest-value posts current against the subject
Time30 to 45 minutes per post, as needed
WhatReviewing content on a schedule set by how fast the subject changes, so recency-sensitive pages stay accurate. AI-cited content tends to run fresher than typical organic results (Ahrefs, 25.7% fresher on average), with the strongest recency bias on fast-moving topics.
HowSort your top posts by how quickly the subject moves. Review fast-moving ones more often: update statistics to the latest available, replace stale data, add current findings. Update the visible date only when you've genuinely revised the page. Resubmit changed URLs to Google Search Console. Don't run a date-only refresh machine on evergreen pages that haven't changed; accurate beats artificially new.
OutputA review cadence matched to each subject, with visible dates that reflect real updates.
Common mistake: Refreshing high-traffic posts on topics buyers don't ask AI about, instead of the posts that answer real buyer queries. Freshness on the wrong pages doesn't build citation potential.
Step 6b (optional)
Add a short executive summary to high-value posts
Time10 to 15 minutes per post
WhatA concise summary near the top that helps a busy reader grasp what the page offers and who it's for. It may also make the page easier for automated systems to parse, though there's no evidence that agents look for a specific summary format.
HowAdd a short block near the opening covering: what the post helps you do, the main outcome, the key prerequisite, and the next step. Keep it factual and specific, written for a person. Don't claim it enables an AI agent to recommend you; treat any parsing benefit as a bonus, not the reason.
OutputA clear executive summary on your highest-value posts.

Example summary block:

In Summary
Helps youRestructure existing blog content so a relevant answer is easy to lift, without publishing new posts.
OutcomeClearer, self-contained answers that improve the chance of being cited when the page is retrieved.
PrerequisiteYour content is indexed and your identity signals are consistent. If not, start with Fix Identity Fragmentation.
Next stepThe $497 Snapshot tells you whether structure is your actual gap before you rewrite the library.
Common mistake: Writing the summary as marketing copy. "We help companies get more AI visibility" tells a reader nothing. State what the page does, who it's for, and what it requires.
Phase 4: Verify
Step 7
Re-test and track the trend, not a single answer
Time20 minutes monthly
WhatConfirming whether restructured posts appear in citations for target buyer queries, while being honest about what you can attribute.
HowRe-run the diagnostic with the same clean method. For each restructured post, run its buyer query in Perplexity and ChatGPT across a few sessions and note whether it's cited and where. Track four things separately: whether the answer is correct, which source was cited, the likely cause, and whether that cause is confirmed. A correct answer doesn't prove a platform used your page. Watch the trend across runs. If restructured posts still don't appear, check re-indexing in Search Console, verify the answer addresses the exact sub-query, and confirm the page is reachable at all; if crawlers can't reach it, fix AI crawlability first.
OutputA monthly baseline by query showing the trend since restructuring.
Common mistake: Testing branded queries. "What does [company] do?" isn't a buyer query. Your citation frequency on non-branded category questions is the number that shows whether the restructuring is working.

When a post still isn't cited, label the failure before you act on it:

  • Not retrievedThe system never pulled your page. Retrieval, authority, or crawlability sits upstream of structure here.
  • Retrieved, not selectedPulled but a stronger source was preferred. Look at evidence quality and authority.
  • Selected, not citedUsed to inform the answer without attribution. Sharper, self-contained passages help here.
  • Cited, misattributedCited but tied to the wrong entity. That's an identity problem upstream.
  • Cited inconsistentlyAppears some runs, not others. Often relevance, freshness, or session variance.

The training-ready content checklist

Twelve principles to check before publishing. These are judgments, not pass-fail thresholds. A page that satisfies most of them is easier to retrieve, understand, and cite.

  • 01The title describes the real question or subject a buyer would recognize, not a branded or clever frame.
  • 02The main answer is easy to find, stated early and directly rather than after paragraphs of setup.
  • 03Headings are descriptive and reflect how buyers phrase the question, so a system can match a section to a query.
  • 04Key sections stand alone, understandable without the paragraphs before them. Long enough to answer one question, short enough to scan.
  • 05Factual claims are sourced, with the study owner, date, and scope near the claim.
  • 06Original evidence is clearly distinguished from general knowledge, where you have credible data of your own.
  • 07Material limitations are included, especially for medical, legal, financial, or compliance content.
  • 08Authorship or organizational responsibility is clear, particularly for expert or high-stakes material.
  • 09The page is current enough for the subject, with a visible date that reflects a genuine review or revision.
  • 10Related pages are linked naturally, in both directions, so the topic reads as a coherent set.
  • 11Visible content is complete without schema. Any markup supports interpretation; it never carries the answer.
  • 12The page genuinely helps the intended buyer, which is the signal every platform is ultimately trying to reward.

What this looks like: before and after

Anonymized observational case. Multiple changes were implemented, so individual causal impact cannot be isolated, and platform behavior can shift during the same window.

Example: the post that ranked but wasn't cited

Before

B2B sales intelligence company. Post title: "How to improve pipeline visibility for enterprise sales teams." Ranked well in Google. Absent from Perplexity and ChatGPT citations across the pipeline-visibility queries tested.

Structure: a long introduction on why pipeline visibility matters, the direct answer arriving near the end, sections of wildly uneven length, no self-contained answers, no specific evidence, and no visible recent update.

After

The opening was rewritten to answer the title question directly and concretely, with the essential qualification kept in place. Sections were made self-contained. Generic claims were replaced with sourced, specific evidence. A visible FAQ was added for real follow-up questions. The page was genuinely updated and resubmitted to Search Console.

Over the following weeks, the post began appearing in some of the pipeline-visibility queries on Perplexity, and its FAQ answer surfaced occasionally in ChatGPT. Google ranking held. Because several things changed at once, the trend is attributable to the restructuring as a whole, not any single edit.

How to know it's working

Perplexity shows visible citations, which makes it the most directly measurable surface. Run a fixed set of buyer queries monthly and record whether your restructured posts appear, at what position, and which pages are cited when yours isn't. Track the trend across runs rather than reacting to one answer.

Separate four things every time you test: whether the answer is correct, which source was cited, the likely cause, and whether that cause is confirmed. A correct answer with an unconfirmed cause is still progress worth recording. Claiming your restructuring caused a citation when the platform cited a different page is not.

First, on your own surfaces
Your posts now lead with clear, self-contained answers. This you control and can confirm directly the day you finish.
Then, after re-indexing
Search Console reflects the updated pages. This shows Google indexing, not whether any AI platform has used the page.
Eventually, in AI answers
Citations shift as indexes and retrieval refresh. Timing is platform-dependent and can't be predicted. Watch the trend across your retests.

If restructured posts still aren't cited after a reasonable window, check three things in order. First, whether the answer addresses the exact sub-query being resolved or a close variant; run the query in Perplexity and read the response. Second, whether the page has re-indexed; use Search Console URL Inspection. Third, whether the page is reachable at all; if crawlers can't fetch it, crawlability is the blocker and it sits upstream of structure.

The re-test: Ask Perplexity the question your best restructured post answers, across a few sessions. If your post appears and the citation references a specific point from it rather than only your site name, the passage is doing its job. If it doesn't, label the failure mode above before rewriting anything else.

What this reveals about your other AI visibility failures

This guide covered Citation Invisibility: the on-page structure that determines whether a relevant answer is easy to lift. Fixing it makes your owned content easier to cite once it's retrieved. It doesn't decide whether it gets retrieved, or whether AI trusts you enough to cite you over a competitor.

Clean structure without off-page corroboration means AI can lift your answer but still defaults to competitors whose external evidence is stronger. See Fix Citation Authority. Clean structure with fragmented identity means your answer can be cited but attributed to the wrong entity; fix identity fragmentation first. Clean structure without measurement means you restructure and never see whether it registered; Fix Measurement Blindness builds the baseline Step 7 depends on.

The AI Visibility Snapshot screens all 7 layers across ChatGPT, Perplexity, and Gemini in 48 hours and names the first one failing. Its wedge here is separating retrieval failure from extraction failure: it tells you whether structure is your actual gap or whether entity and authority problems are keeping you out regardless of how clean your passages are, before you rewrite twenty posts.

Frequently Asked Questions

If my posts rank well in Google, why aren't they being cited by AI?

Ranking and citation selection overlap but aren't identical. One study of Google AI Overviews (Surfer, 10,000 keywords) found 67.82% of its citations came from pages outside the top ten organic results, which shows the two don't perfectly align. A well-ranked page can still be hard to cite if the answer AI needs is buried in narrative rather than stated directly in a self-contained section. Ranking helps you become a candidate source; passage structure helps you get selected once you are.

How long should a post be to maximize AI citation potential?

Length matters less than structure. A focused post whose sections each answer one question clearly, with specific sourced evidence, tends to serve retrieval better than a long narrative piece. Write each section long enough to answer its question completely and short enough to scan. For topic depth, a thorough overview page that links to deeper posts helps readers and crawlers understand the subject, without a required word count.

Does FAQ schema actually make a difference to AI citations?

There's no reliable evidence it increases AI citation on its own. Ahrefs tracked 1,885 pages adding JSON-LD and saw no meaningful citation increase, and searchVIU found major systems read only visible HTML during live retrieval. The value is the visible FAQ: a real buyer question and a self-contained answer. FAQPage markup can describe that structure, but for most commercial sites it won't produce a visible Google FAQ result either, since Google restricted those in 2023. Write the visible answers first; treat the markup as supporting.

Should I update old posts or publish new ones for better AI citations?

Update your highest-value existing posts first, especially ones that already rank, since restructuring an established page is faster than building a new one from zero. The exception is when a post covers a topic buyers don't actually ask about; there, publish a new post targeting a real buyer query instead. Propagation timing varies by platform, so track the trend rather than expecting a fixed date.

How is citation invisibility different from citation authority?

Citation authority is the off-page trust question: whether AI trusts your company enough to cite it at all, based on third-party presence like reviews, trade press, and community. Citation invisibility (this guide) is the on-page structure question: whether a relevant answer is easy to lift once your page is retrieved. You can have strong authority and still be hard to cite if the answer is buried. See Fix Citation Authority for the off-page layer.

What changed in AI retrieval this month.

One brief. The patterns your competitors aren't tracking yet. Covers ChatGPT, Perplexity, and Google AI Overviews. Published monthly.

Monthly. No spam. Unsubscribe anytime.