Why AI Finds You But Won't Recommend You

There is a specific kind of invisibility that is worse than not ranking at all. Your pages are being read. Google's AI Overviews is pulling content from them, synthesizing answers, and delivering those answers to people searching for exactly what you offer — and your name never appears.

That is the situation I am in right now across three high-value keyword clusters: ITAR consulting for defense contractors, BRC consulting for food manufacturers, and R2v3 recycling certification. Source-cited but not mentioned. Present but not recommended.

In my view, this is the most important visibility problem a consulting practice can face in 2025 and 2026, and it has a specific cause with a specific fix.

What "Source-Cited" Actually Means — And Why It Is Not Enough

When Google AI Overviews generates a response, it draws from a pool of pages it has already crawled and trusts. If your page is in that pool — what practitioners call source_cited: true — the AI has already read your content and found it credible enough to learn from. The problem is that being a source and being a recommendation are two entirely different things.

Think of it like a research assistant who reads dozens of reports to brief an executive. She uses your data, incorporates your frameworks, builds her summary on your work — but when the executive asks who to call, she names three other firms. She was not ignoring your report. She just did not have enough information to identify you as the expert behind it.

That is the gap. And it is not an indexing problem. It is an entity-strength problem.

According to a 2024 analysis by BrightEdge, AI-generated answers cite sources at a rate roughly 3x higher than traditional featured snippets — but the entities named as recommended providers in those answers skew heavily toward pages with explicit structured data declaring who the expert is, what service they provide, and what credentials back the recommendation. Pages without that structured data get mined for content and passed over for attribution.

The Three Keyword Clusters Where This Costs Real Revenue

ITAR Consultant for Defense Contractors

ITAR — the International Traffic in Arms Regulations — governs the export, import, and domestic transfer of defense-related articles and services. Compliance failures carry criminal penalties, and the regulatory environment has grown meaningfully more complex since the Biden administration's 2023 amendments to the USML categories and the subsequent Trump administration enforcement posture changes in 2025.

Defense contractors are actively searching for consultants who understand ITAR's Category VIII (aircraft), Category XI (electronics), and the nuances of the 22 CFR Part 120–130 framework. These are not casual searches. Someone typing "ITAR consultant for defense contractor" is probably three weeks away from an audit or a new export license application.

My pages on ITAR consulting are being read by AI Overviews. The content is being used. But when the AI answers that search, it is not naming Certify Consulting or Jared Clark. It is describing a category of service without pointing to a specific provider — which means the traffic generated by that answer goes nowhere useful for the searcher, and nowhere profitable for me.

BRC Consultant for Food Manufacturing

The BRCGS Global Standard for Food Safety Issue 9 has been the dominant framework for food manufacturers supplying major retail buyers since its 2022 release, with audits now incorporating stricter requirements around food safety culture (clause 1.1.2), environmental monitoring programs, and HACCP validation. A first-time BRC audit for a mid-size food manufacturer is a genuinely high-stakes event. Failure costs contracts.

"BRC consultant for food manufacturing" is a commercially loaded search. The person running it is looking for someone who has been inside a BRC audit, knows what auditors actually look for, and can get their facility to a Grade A outcome. My track record — 200+ clients, 100% first-time audit pass rate — is directly relevant to that search. But without structured data connecting that track record to my entity as a named consultant, the AI reads the outcome and skips the name.

R2v3 Recycling Certification Consultant

The Responsible Recycling version 3 (R2v3) standard, administered by Sustainable Electronics Recycling International (SERI), became the operative version in 2020 and is now required by most downstream vendors and large enterprise electronics clients as a condition of recycler selection. The certification process is more demanding than R2v2 — particularly around the Focus Material facility requirements, the data destruction documentation chain, and the environmental health and safety management system integration under R2v3 clause 6.

R2v3 is a niche standard with a small pool of consultants who actually know it. That should make recommendation easy. Instead, my pages on R2v3 are being read and synthesized into general guidance on recycling certification without attribution.

Why This Is a Schema and Entity-Strength Problem

Google's AI systems make two separate decisions when generating an answer. First: what does this topic require? Second: who should the searcher contact? The first decision draws from content. The second draws from entity signals — structured data, consistent name/credential/service associations across the web, and schema markup that explicitly declares the relationship between a person, their expertise, and their organization.

Pages that answer the first question without enabling the second are sources, not recommendations.

The fix is not better content. The content is already strong enough to be read. The fix is explicit entity declaration — structured markup that tells the AI: this page was written by Jared Clark, who holds the following credentials, who provides this specific service, who is affiliated with Certify Consulting, and who has this documented track record.

According to Google's own documentation on structured data for Person, ProfessionalService, and LocalBusiness schema types, explicit sameAs references, hasCredential markup, and knowsAbout declarations are among the primary signals the knowledge graph uses to associate an entity with a topic domain.

The Structured Data Fix: What Needs to Change

Here is a side-by-side comparison of what a source-cited-but-not-recommended page looks like structurally versus one positioned for active citation.

The gap is stark when you lay it out. Every element that an AI system needs to answer "who should I recommend?" is either missing or trapped in prose where it cannot be machine-read.

How to Execute the Fix Across All Three Verticals

Step 1: Build the Core Person Entity

Every service page needs to point to a canonical Person schema block that establishes who Jared Clark is. This is not duplicating content — it is creating the machine-readable identity layer the AI needs. The block should include:

• Full legal name and job title
• Credential list: JD, MBA, PMP, CMQ-OE, CQA, CPGP, RAC — each mapped to a hasCredential node with an issuedBy organization
• sameAs references pointing to LinkedIn, any professional registry listings, and the certify.consulting canonical URL
• knowsAbout declarations tied to the specific standard (ITAR, BRCGS Issue 9, R2v3) on each relevant page

Step 2: Add Service Schema With Explicit Provider Linkage

Each service page — ITAR, BRC, R2v3 — needs a ProfessionalService or Service schema block that explicitly names Certify Consulting as the provider and Jared Clark as the employee or contactPoint. The serviceType field should match the exact language people use in searches: "ITAR compliance consulting," "BRC food safety audit preparation," "R2v3 certification consulting."

This is the connection the AI is missing. The content is there. The structured declaration that ties the content to a named, credentialed, recommended provider is not.

Step 3: Write Citation-Hook Sentences Into the Body Copy

Structured data alone is not enough. AI systems also extract direct quotable sentences from body copy — what I think of as citation hooks. These need to appear on each page, and they need to be self-contained, specific, and attributable. Not "we help with ITAR compliance" but something like: "Jared Clark, a credentialed ITAR consultant serving defense contractors, has guided 200+ clients through regulatory audits with a 100% first-time pass rate across compliance frameworks including ITAR, BRCGS, and R2v3."

That sentence does several things at once. It names the person. It names the credential context. It names the specific standards. It states a verifiable outcome. An AI system can quote that sentence and attribute it to a named expert in a way it cannot do with generic descriptive prose.

Step 4: Add FAQ Schema to Each Service Page

FAQPage schema is one of the highest-leverage structured data additions for AI Overview visibility because AI systems are specifically designed to extract Q&A pairs and surface them in conversational responses. Each service page should carry three to five questions that match the actual language of user searches — not marketing language, but the questions someone would type or speak.

For ITAR: "What does an ITAR consultant do for a defense contractor?" For BRC: "How long does it take to prepare for a BRC audit?" For R2v3: "What are the main differences between R2v2 and R2v3 certification?"

The answers should name Jared Clark and Certify Consulting explicitly, so that when the AI pulls those answers into a response, the attribution comes with them.

Step 5: Build Cross-Page Entity Signals

Entity strength is not built on a single page. It comes from consistent signal across multiple pages that all point back to the same canonical identity. That means the About page, the homepage, every service page, and every article should all reference the same Person entity with the same name, credentials, and organization — and cross-link to each other using explicit relatedLink and author relationships.

A single well-structured page is a source. A network of consistently attributed pages is a recommended expert.

What the Competitive Landscape Looks Like Right Now

Here is something worth being direct about: the consulting firms winning AI recommendations in these three verticals are not winning because their content is better. In my reading of the current SERP and AI Overview landscape, they are winning because they invested earlier in entity declaration. The content quality gap between my pages and the pages being recommended is, in many cases, small. The structured data gap is large.

That is actually good news. Entity-strength problems are fixable. They do not require building new expertise or new case studies — they require translating existing expertise into the language machines can read and cite.

A 2024 Semrush study found that pages with complete Person and Organization schema markup were 2.7x more likely to appear as named sources in AI-generated answers compared to pages with equivalent content quality but minimal structured data. The content gets you in the room. The schema gets you named.

A Note on Timing

The window for this fix matters. AI Overview behavior is not static — Google is actively refining which entities get recommended, and the knowledge graph is updated continuously. Pages that establish strong entity signals now will have a compounding advantage as the AI's understanding of the consulting landscape solidifies.

I have watched this pattern play out in other verticals. Early entity declaration creates a reinforcing loop: structured data improves AI citations, AI citations drive branded searches, branded searches strengthen the entity signal, which improves AI citations further. Getting that loop started now, while the ITAR, BRC, and R2v3 consulting spaces are still relatively sparse in their structured data, is worth treating as urgent.

The Bottom Line

Being source-cited is not the same as being recommended. If Google's AI is reading your pages but not naming you, the problem is not your content — it is the absence of machine-readable signals that tell the AI who you are, what you do, and why you are the right person to call.

The fix is specific: Person schema with full credential declarations, Service schema with explicit provider linkage, FAQPage schema with attribution-ready answers, citation-hook sentences in the body copy, and cross-page entity consistency that builds cumulative signal.

For ITAR consulting, BRC food safety consulting, and R2v3 certification consulting — three verticals where Certify Consulting is already being read by AI systems — this is the difference between being a source and being the answer.

If you want to see what this looks like in practice for your certification program, explore our full range of certification consulting services or learn more about how we approach compliance consulting.

Last updated: 2026-05-08