Mustafa ERBAY

Posted on Jul 28 • Originally published at mustafaerbay.com.tr

Visibility in Google AI Mode: A GEO Guide for Technical Blogs

#ai #sistemmimarisi #software

Google's use of artificial intelligence (AI) in Search is changing how technical content can be discovered and cited. This shift has also popularized the industry term Generative Engine Optimization (GEO), which describes practices intended to improve how AI-powered search systems understand and reference content. Google itself, however, continues to describe these practices as part of SEO rather than as a separate discipline. This guide focuses on the practical work that remains useful under that definition.

Reliable technical blogs remain valuable because readers can reproduce their steps and inspect their sources. Clear structure also makes the page easier for search systems to retrieve and summarize.

How Are AI-Powered Search Engines Changing?

Google's AI-powered search experience now includes features such as AI Overviews and AI Mode, which use large language models to synthesize information from multiple sources. These systems still depend on Google's Search index and ranking systems, but they can issue related searches, retrieve supporting pages, and assemble an answer with links. This means users may receive a useful summary before visiting a source page.

This transformation presents new challenges and opportunities for website traffic. A supporting link inside an AI-generated answer can provide visibility, while a complete answer on the results page may also change click-through behavior. The practical response is to make every technical claim useful, attributable, and verifiable.

ℹ️ AI Overviews and References

AI Overviews and AI Mode can show links to supporting web pages. Appearing there provides visible attribution, but inclusion is never guaranteed. The page must first be crawlable, indexed, eligible to appear with a snippet, and useful for the query.

What Changes When SEO Serves AI-Powered Search?

SEO for AI-powered Search is not a replacement for traditional SEO. Crawlability, indexability, relevance, links, and technical site health still matter. The additional editorial emphasis is on original, helpful, verifiable content with clear authorship and a structure that both people and retrieval systems can follow.

Feature	Traditional SEO	SEO for AI-powered Search
Focus	Crawlability, indexability, relevance, ranking	Retrieval, synthesis, grounding, and useful citations
Primary signals	Technical accessibility, relevance, links, page quality	Originality, helpfulness, verifiability, clear authorship, technical accessibility
Content style	Search-friendly pages that answer a query	Direct answers, reproducible detail, transparent sourcing
Goal	Earn qualified visibility in Search	Remain useful and citable within AI-assisted results
Optimization	Technical SEO, information architecture, internal and external links	The same SEO foundation plus explicit context, source quality, and maintainable structure

Accurate source material and explicit context make a page more useful and easier to verify. Keyword stuffing cannot replace a clear answer, technical accessibility, or evidence.

How Should E-E-A-T Be Interpreted in Technical Content?

Google added "Experience" to E-A-T in its Search Quality Rater Guidelines in December 2022, producing the E-E-A-T framework. E-E-A-T is not a single ranking metric, and quality raters do not directly control rankings. It is a useful framework for assessing whether content demonstrates experience, expertise, authoritativeness, and—most importantly—trust. In technical subjects, that assessment matters because incorrect information can cause real operational problems.

Experience

Real-world experience elevates knowledge from purely theoretical to practical value. For example, solving a network issue involving VLAN tagging firsthand, rather than just reading about it in books, offers a deeper and more applicable perspective. Content that includes first-hand observations, reproducible steps, and transparent methodology is generally more useful for both readers and AI-assisted search systems.

Expertise

The author's deep knowledge and competence in a technical subject determine the content's level of expertise. When writing about complex system architectures, specific protocols, or a particular database optimization technique, demonstrate mastery with detailed explanations, correct terminology, and cause-and-effect relationships. When discussing PostgreSQL WAL growth and checkpoint behavior, for example, explain the relevant version and the interaction among current settings such as max_wal_size, min_wal_size, and checkpoint_timeout.

Authoritativeness

Authoritativeness refers to the degree to which an author or website is considered a reference in a particular field. This is reinforced by being cited by other experts in the industry, referring to reliable sources (RFCs, official documentation), or actively participating in relevant communities. In technical blogs, the accuracy of the solutions and analyses you publish builds this authority over time.

Trustworthiness

Trustworthiness refers to the content being impartial, accurate, and transparent. When addressing a technical problem, honestly presenting the pros and cons of different approaches, stating potential risks, and being consistent in source code examples increases trustworthiness. For instance, when providing a kubectl command example, either provide real output or clearly explain the expected behavior instead of fabricating it. Fake metrics or inconsistent code outputs damage reader trust and make the article harder to verify.

⚠️ Avoid Fabricated Data

Do not use precise metrics such as "30% faster" or "took 48 hours" unless they come from a real measurement with a stated method. Prefer measured results with context; when measurement is unavailable, describe the observation without inventing precision. Never fabricate terminal output or log excerpts.

How to Use Structured Data (Schema.org) and Increase Semantic Richness?

Structured data helps search engines understand entities and page structure. It is recommended for supported search features, but Google does not require Schema.org markup for inclusion in AI Overviews or AI Mode. The markup must also describe content that is visible on the page; it cannot compensate for thin, inaccurate, or inaccessible content.

Enriching Your Content with Schema.org

Here are some basic Schema.org types you can use for a technical blog post:

Article or TechArticle: For general blog posts. Includes basic information like author, publication date, title, description. TechArticle can be used for more specific technical articles.
HowTo: Ideal for step-by-step guides or tutorials. You can define each step (HowToStep), tools used (HowToTool), and materials (HowToSupply).
FAQPage: For Q&A sections. Marking each question (Question) and answer (Answer) separately makes it easier for AI to extract this information directly.

Although Schema.org defines these types, their availability does not guarantee special treatment in Google Search. Always verify current support through Google's structured data documentation before implementing markup for a search feature.

You can add these markups in JSON-LD format, either in your page's <head> section or within the <body>. You can validate your implementation using Google's Rich Results Test tool.

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "Visibility in Google AI Mode: A GEO Guide for Technical Blogs",
  "author": {
    "@type": "Person",
    "name": "Mustafa Erbay"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Mustafa Erbay Blog",
    "logo": {
      "@type": "ImageObject",
      "url": "https://mustafaerbay.com.tr/icon-512.png"
    }
  },
  "datePublished": "2026-07-28",
  "description": "How technical blogs can publish accurate, structured, and verifiable content for Google's AI-powered search features."
}

Structured data can make page entities and relationships explicit, but it is only one layer. When writing about a system integration, clearly defining each step, prerequisite, API, and version makes the content easier for readers to use and for search systems to interpret.

💡 Create Context for Semantic Richness

Instead of scattering keywords randomly, use technical terms in a natural context and relate them to other relevant concepts. For example, when writing about "Docker containers," touching on related Linux system administration concepts like cgroup limits or journald logging strengthens your content's semantic network. This helps AI grasp the topic more deeply.

LLM-Friendly Content Structure

Clear headings, explicit definitions, focused paragraphs, and visible source links make technical content easier to retrieve and summarize. A better name for this editorial practice is LLM-friendly content structure: the page remains written for people, while its claims and relationships are easy for search systems to parse.

Strategies for Creating AI-Readable Content

Direct and Clear Headings: Your headings ("H2", "H3") should clearly state what the reader (and AI) can expect. Question-formatted headings like "What is X?", "How to do Y?" make it easier for AI to extract direct answers.
Summarize in the First Sentence: The first sentence of each paragraph or section should contain the main idea or answer of that section. This helps AI quickly identify key points.
Short and Focused Paragraphs: Long, complex sentences or paragraphs can make it difficult for AI to extract information. Prefer paragraphs of 2-4 sentences, focused on a single idea.
Definitions and Explanations: Define technical terms where they first appear and explain them with examples if necessary. This helps AI understand the terms in the correct context.
Clear Cause-and-Effect Relationships: When explaining a solution or situation, clarify the cause-and-effect chain with phrases like "this happens because...", "therefore, this result occurs." This enables AI to grasp the logical flow.

For example, when explaining a fail2ban pattern, instead of just providing the rule, explaining which log lines it targets, which regex it matches, and what kind of action (e.g., IP banning) is taken as a result, step-by-step, increases value for both humans and AI.

Visual tools such as Mermaid can help readers understand a complex flow. A simplified AI-assisted search path looks like this:

User Query → Retrieval → Ranking → AI Synthesis → Grounding → Citation → Answer

This is a conceptual model, not a disclosure of Google's internal implementation. It is useful for remembering that a page must first be accessible and retrievable before it can support a grounded answer or citation.

Source Attribution and Trustworthiness Mechanisms in Content Production

Transparent source attribution allows readers to verify technical claims and gives search systems clear supporting context. In a technical blog, link directly to the documentation, standard, release note, or advisory that supports the statement instead of adding a long, unrelated bibliography.

Implementation Steps for Trustworthy Content

Refer to Official Documentation: When providing information about a technology, protocol, or standard, link directly to official documentation, RFCs, or standards committee publications. For example, when explaining OAuth2 flows, referring to relevant RFC numbers (RFC 6749, RFC 7636 for PKCE) makes your content much more authoritative.
Specify Version Numbers: Clearly state the version numbers of the software or libraries you are using. When describing a PostgreSQL optimization, indicating which version these settings were tested on or from which version they are valid increases the applicability and accuracy of the information.
Present Case Studies Transparently: When discussing your own experiences, concretely convey the symptoms of the problem, error messages, and solution steps. For example, when presenting a case about Redis OOM eviction policy selection, explaining why a particular maxmemory-policy setting was chosen and why other policies were not suitable helps AI understand the context. However, in these cases, avoid unmeasurable or fabricated figures.
Cross-Reference and Internal Linking: Link related articles with descriptive anchor text. This helps readers and crawlers navigate the relationship between topics. For instance, a VLAN segmentation article can link to relevant firewall policy or VPN topology guides.
Author Biography and Social Proof: In your author biography, state your relevant experience, certifications, or areas of expertise. This strengthens the Expertise and Authoritativeness components of E-E-A-T. Adding social proof like your LinkedIn profile or GitHub account can also increase trustworthiness.

These strategies not only help AI better understand your content but also reinforce your readers' trust in you. Clearly stating the source of data and methodology increases user trust in the platform. The same principle applies to technical blogs.

Conclusion

Google's AI-powered Search features do not replace the foundations of SEO. Technical creators should keep pages crawlable and useful, make authorship and methodology clear, add structured data only where it accurately describes visible content, and support consequential claims with current first-party sources.

The objective is not to write for AI instead of people. The objective is to publish technically accurate, well-structured, and verifiable content that serves people first while remaining easy for AI-powered search systems to understand.

DEV Community