Why most sites don't get cited
The sites Google includes in AI Overviews share a consistent profile: they're already ranking in the top 10 for the query, they have well-structured and specific content, and they demonstrate clear topical authority through related indexed content. Sites that don't get cited typically fail on one or more of these:
Not indexed or ranking poorly. AI Overviews pull from Google's live index. If your page isn't indexed, or ranking outside the top 20 for the relevant query, it won't be considered as a source regardless of content quality.
Content too general. AI Overview sourcing heavily favours pages that answer specific questions directly. A page titled "Our SEO Services" that describes your offerings in general terms will not be cited for queries like "how to fix keyword cannibalization." A page that specifically and completely answers that question might be.
Missing structured data. Schema markup helps Google understand exactly what your content is about. Pages without any structured data require more inference from Google's systems — and inference is slower and less reliable than explicit signals.
No E-E-A-T signals. Google's Quality Rater Guidelines evaluate Experience, Expertise, Authoritativeness, and Trustworthiness. For AI Overview sourcing, this manifests as: does the author demonstrate real-world experience, are there citations or references to specific data, and does the site have an established presence in the topic area?
How to improve your chances of being cited
Fix indexing first
Before any content optimisation, confirm your target pages are indexed. Open Google Search Console, go to the Pages report, and check the "Not indexed" section. Any pages showing "Crawled — currently not indexed" need content or technical fixes before they can appear in AI Overviews.
Run site:yourdomain.com in Google to see roughly how many pages are indexed. If you have 50 pages on your site and only 15 appear in this search, 35 pages are invisible.
Write to answer questions, not to describe services
Compare these two content approaches for the same topic:
Service-page style (won't get cited):
"At Nordax Digital, we offer comprehensive visibility infrastructure services designed to help your business rank higher and reach more customers."
Answer-first style (gets cited):
"Visibility infrastructure refers to the complete technical and content foundation that determines whether search engines and AI systems can find, understand, and rank your site — including structured data, indexing health, internal linking, and content specificity."
The second version can be pulled directly into an AI Overview as a definition. The first can't.
For each page you want to appear in AI Overviews, identify the specific question it should answer and make sure the answer appears clearly in the first two paragraphs.
Add structured data for your content type
The most impactful schema types for AI Overview visibility:
Article schema — tells Google the content is a defined piece of writing with an author, publish date, and topic. Apply this to any blog or article content.
{
"@type": "Article",
"headline": "Your article title",
"author": { "@type": "Person", "name": "Author name" },
"datePublished": "2026-01-15",
"publisher": { "@type": "Organization", "name": "Nordax Digital" }
}
FAQPage schema — marks up FAQ sections so Google can parse individual questions and answers. Pages with FAQPage schema have a measurably higher rate of appearing in AI Overviews for conversational queries.
HowTo schema — for instructional content with numbered steps. Signals to Google that the page contains actionable procedural content.
Build topical clusters, not isolated pages
AI Overviews favour sites that demonstrate authority across a topic area, not just a single strong page. If you publish one article about SEO, that's a single data point. If you publish 10 well-structured articles covering different aspects of SEO, each linking to the others, Google begins to treat your site as an authoritative source on that topic.
This is why help centres and documentation sites get cited disproportionately — they have dense, interlinked, specific content across an entire topic area.
Start with 3–5 tightly related articles on your most important topic, make sure they link to each other with relevant anchor text, and point them all at a central hub page (your service page or a dedicated guide).
