Coder Legion - Recent posts tagged ai-search

SEO for 2027: A Developer Workflow for AI Search Visibility and Trust

Fri, 30 Oct 2026 19:21:01 +0000

A page can be technically accessible, appear in a search result and still fail to help someone choose a service. An AI answer can mention a business and still describe it incorrectly.

Those are different problems. They need different tests.

I am Jarno Saarimies, founder of AEOvara in Lappeenranta, Finland. I work on SEO and AI search visibility, and I also run a photography business. That combination gives me a useful question to bring to a technical discussion: can a customer actually understand and use what we have built?

For a 2027 planning discussion, I would start with a testable workflow rather than an algorithm prediction. The recommendations below are engineering choices, not promises of higher rankings.

Start with documented requirements

Google's documentation on AI features and websites says that a supporting page in AI Overviews or AI Mode must be indexed and eligible for a search snippet. It does not specify additional technical requirements for those features.

The same guidance recommends accessible textual content, internal links, crawler access and structured data consistent with the visible page. These are eligibility and implementation considerations, not guarantees of selection.

That distinction matters when someone proposes a new AI visibility feature. Ask which documented requirement it satisfies and what observable result would count as success.

Separate discovery from answer quality

I would organise the work around four questions.

Can the page be retrieved? Can its service information be understood? Does an answer represent the business correctly? Can a visitor complete the intended task?

For a service page, my suggested review would cover:

The response status and the canonical URL.
Applicable indexing and snippet directives.
Crawler restrictions at the application, CDN and robots.txt layers.
The important service information in the rendered page.
Internal links that lead to the page.
Agreement between visible content and structured data.
The contact or booking flow on a phone.

Record what was inspected and what was observed. A successful response from one HTTP client does not establish what Google indexed. For Google-specific diagnosis, inspect the page in Search Console as well.

I would avoid collapsing all of this into one pass or fail score. A form validation error and an incorrect service description require different fixes.

Make the service page a useful specification

Consider a hypothetical company booking portraits for ten employees.

The useful questions are specific. Can the photographer work at the office? What is included? How are travel costs handled? When are the files delivered? What information is needed to request a quote?

A developer can turn those questions into acceptance criteria. For example, someone unfamiliar with the business should be able to identify the service area and submit a valid enquiry without asking the owner to explain the page.

This is where I would bring the service provider into the review. Developers can make information accessible, but the owner has to supply accurate scope, prices and limitations.

My proposed content model would include a service name, audience, location, inclusions, exclusions, pricing explanation, process and next action. It is a review template, not a search engine requirement.

Measure four different AI answer outcomes

For AEOvara's visibility work, I use four categories to keep the questions separate: Mention, Recommendation, Citation and Narrative Accuracy.

Here is a proposed operational definition for a test log:

Category	What to record
Mention	Is the target business named?
Recommendation	Does the answer explicitly suggest choosing or considering it?
Citation	Does the answer link to a page on the target domain as supporting evidence?
Narrative Accuracy	Are the factual claims about the business correct?

These are my measurement definitions, not metrics supplied by Google. A different team can choose different definitions, but it should write them down before scoring answers.

Fun fact from that scoring model: an answer can pass the first three categories and fail the fourth. It could name and recommend a company, cite its website, and still invent a service the company does not offer. That is a hypothetical example, but it shows why a citation is not an accuracy check.

For each test, I would retain the exact question, platform, date, language, relevant location and response. Record whether browsing was enabled and any known account or conversation context. Repeat the questions and report the number of observations alongside the results.

Keeping the prompt unchanged improves comparability. It does not control every variable in a changing search or language model system. I would therefore treat a small test as a sample of behaviour, not a market share estimate or evidence that one site change caused the result.

Treat trust as evidence a reader can inspect

Google's people-first content guidance says E-E-A-T is not itself a specific ranking factor. It also encourages accurate authorship information and clarity about how content was produced.

My practical interpretation is to make claims auditable. Name the author, explain the relevant experience, link the primary source and describe the test method. If an example is hypothetical, label it. If a result comes from your own small sample, say so.

A byline cannot substitute for evidence. Neither can a large schema block. For this article, the Google-specific requirements are linked above; the review process and scoring definitions are my recommendations.

Ship one change you can evaluate

For the next iteration, I would choose one important service page, record its current state and fix a concrete problem. That might be missing service information, inaccessible content or a broken enquiry step.

Keep a dated change log. Compare relevant search observations with actual enquiries, and note other changes that could affect the result. A before and after comparison is useful for investigation, but it is not automatically a controlled experiment.

This is how I would approach planning for 2027: documented requirements, explicit definitions and changes small enough to inspect. No forecast about the next algorithm update is needed to start.

About the author

Jarno Saarimies is the founder of AEOvara, based in Lappeenranta, Finland. His work focuses on technical SEO, content clarity and visibility in AI-powered search. He also runs the photography business Kuvaajankulma.

A related article written in Finnish is available at https://aeovara.fi/hakukoneoptimointi-2027/. It covers the broader 2027 planning topic, including predictions. This developer-focused article stands on its own.

What is the hardest part to validate in your projects: crawler access, the accuracy of an AI answer, or whether search visibility leads to a useful enquiry? I would be especially interested in a concrete test that changed your implementation, including one that disproved your original assumption.

The Authority Paradox: A Practical GEO Strategy for Smaller Brands

Thu, 29 Oct 2026 17:27:21 +0000

By Jarno S., founder of AEOvara, Lappeenranta, Finland

A small company rarely wins by publishing more pages than an established competitor. It can, however, publish a better answer to a narrower question.

That is the useful opportunity behind Generative Engine Optimization (GEO): making expertise easier to discover, understand and substantiate when AI-powered search systems build an answer.

The authority paradox is not that reputation has stopped mattering. It is that broad recognition and usefulness for a specific question are different advantages. A specialist may have the stronger source for one particular problem—even when a larger brand dominates the wider market.

What you will learn

How GEO relates to SEO and Answer Engine Optimization (AEO).
What smaller brands can improve without a large publishing budget.
How to make claims easier for readers and search systems to verify.
How to measure mentions, recommendations, citations and factual accuracy separately.

GEO extends the visibility problem

Traditional search visibility often means appearing among the results a user can click. Generative search adds another possibility: a system may use information from a page while composing its own response, sometimes with a supporting link.

GEO is the practice of improving the likelihood that relevant content and brands are represented accurately in generative answers. AEO overlaps with this work, especially when content directly answers a user's question. The terminology varies across the industry; it does not describe neatly isolated ranking systems.

For a more detailed introduction, see AEOvara's guide to Answer Engine Optimization (in Finnish).

SEO remains part of the foundation. Crawlability, useful content, internal links and an understandable site structure still matter. Google's guidance on AI features and websites explicitly says that established SEO practices remain relevant to AI Overviews and AI Mode.

There is no universal shortcut that makes a page eligible for every AI answer engine.

What the research actually supports

The research paper GEO: Generative Engine Optimization reported visibility improvements of up to 40% in its experimental setting. Results varied across domains and optimization methods.

That is evidence worth exploring, but it is not a promise of 40% more citations, traffic or sales in today's commercial systems. An experimental visibility metric should not be presented as a guaranteed business outcome.

The practical lesson is to test improvements against a documented baseline. Clearer explanations and better-supported claims are useful editorial choices; their effect on a particular engine still needs measurement.

Domain scores are not the whole story

Domain Authority is a third-party SEO metric, not a Google ranking score. It should not be treated as a universal measure of how much an AI system trusts a website.

Equally, it would be misleading to say that links, established reputation or search rankings no longer matter. AI search products can rely on search indexes and retrieval systems, and the available sources influence what can appear in an answer.

A smaller brand's realistic opportunity is specific relevance.

Imagine a software consultancy documenting a difficult migration. A page that explains the source system, constraints, failed approaches and verified result can be more useful for that exact task than a generic overview from a famous publisher.

This is a hypothetical example, not a claim that specialist websites always beat larger domains.

Three layers a smaller brand can improve

1. Evidence: publish something that can be checked

Start with knowledge you actually have: a documented test, a worked example, a comparison with disclosed criteria or an anonymized case study shared with permission.

For research and benchmarks, include:

What you measured and why.
The sample, timeframe and method.
The result, including inconvenient findings.
The limitations and what readers should not infer.

A survey of 50 customers can offer useful local evidence, but it does not represent an entire industry. A small sample needs an honest description, not a dramatic headline.

Never invent a percentage or give an ordinary observation a research-sounding label. Link external claims to the original source, and distinguish your own findings from someone else's.

2. Clarity: make each section answer a real question

A useful section should identify the subject, answer the question and explain the conditions under which the answer holds.

For example, "our solution improves visibility" leaves almost everything undefined. "AEOvara provides AI-search visibility analysis and SEO implementation services" tells the reader what the company actually offers.

This is straightforward writing, not a secret embedding technique.

Use descriptive headings, explain abbreviations and keep terminology consistent enough to follow. Natural synonyms are fine when the relationship is clear. There is no established universal rule requiring an answer within exactly 40 words.

For developers, check whether the important information is present as accessible text and whether internal links lead to the supporting details. A visually impressive page is less useful when its central explanation is difficult to find.

3. Trust: connect claims to accountable people

Identify who wrote the content, what experience informs it and where readers can verify that background.

Show meaningful publication and update dates. Change an update date when you have reviewed or changed the information—not simply to make an old page look fresh.

Structured data can describe an article, organization or author where appropriate. It should match the visible content. Google's guidance states that there is no special schema.org markup required for its AI features.

Treat markup as an accurate description of your page, not a citation guarantee. Likewise, a byline or an E-E-A-T checklist cannot prove how every language model will evaluate a source.

Measure four different outcomes

A brand appearing in an answer is not the same as its website being cited. A citation is not necessarily a recommendation.

A practical tracking sheet should separate:

Mention: Is the brand named?
Recommendation: Is it presented as a suitable option for the user's need?
Citation: Is there a supporting link to the brand's content? Record third-party sources separately.
Narrative accuracy: Are the description, services, location and other checkable facts correct?

Record the prompt, date, product, available model or mode, language and whether web search was enabled. Keep the conditions as consistent as possible and repeat the tests over time.

Answers and source lists can vary because of retrieval changes, product updates, context and generation behavior. A single missing citation does not establish a trend, and one successful answer does not establish market-wide visibility.

Continue measuring relevant visits, enquiries and conversions alongside these indicators. Visibility has to connect to a business goal.

A practical starting plan

Choose a small group of questions your prospective customers genuinely ask. Include an explanation question, a comparison and a question with purchase intent.

Then:

Record how the selected AI products answer those questions today.
Identify one important page that lacks a clear explanation or supporting evidence.
Improve that page's answer, examples, source links and internal navigation.
Check technical accessibility and any structured data you use.
Repeat the same visibility tests and document what changed.

Avoid changing everything at once if you want to understand which improvements may have helped. Even then, before-and-after results show an association; they do not automatically prove causation.

AEOvara's AI-SEO and AEO services cover visibility analysis, audits and practical optimization work. The service is professional analysis and implementation—not a guarantee of inclusion in any AI system's answers.

The smaller-brand advantage is focus

Large brands bring recognition, resources and extensive information footprints. Smaller teams can bring detailed knowledge of a tightly defined problem and the ability to explain it carefully.

That opportunity is worth pursuing without claiming that authority has disappeared or that SEO is obsolete.

Build the page a reader would want to verify, bookmark and share. Make its evidence easy to inspect. Then measure whether it earns visibility for the questions that matter.

Want a clearer view of your starting point? Explore AEOvara's services to find an appropriate analysis or optimization project.

About the author

Jarno S. is the founder of AEOvara, based in Lappeenranta, Finland. His work focuses on SEO, Answer Engine Optimization and AI-search visibility, including practical analysis and content improvements for businesses. Read more about his background on AEOvara's expert page.

This article reworks and expands a topic previously discussed by the author on Medium, with revised claims, examples and practical guidance.

Best AI Keyword Research Tools to Find Low-Competition Search Terms

Mon, 19 Oct 2026 11:15:34 +0000

Finding keywords with low competition is one of the most practical ways to build organic search traffic without competing directly against established websites for every valuable query. For bloggers, affiliate marketers, small businesses, and SEO professionals, the goal is to identify search terms that match a website's expertise, attract the right audience, and offer a realistic opportunity to rank.

AI-powered keyword research tools make this process faster. They help marketers discover related queries, group keywords by topic, examine search intent, analyze competing pages, and identify content opportunities that might otherwise go unnoticed. However, artificial intelligence does not automatically make a keyword easy to rank for. Reliable decisions still depend on search data, the quality of competing pages, website authority, and the usefulness of the content being published.

The best approach is to combine AI-assisted discovery with measurable SEO data. Here are the tools worth considering and how to use them to find low-competition search terms.

What Are Low-Competition Keywords?
Low-competition keywords are search terms for which a website has a reasonable opportunity to rank compared with the pages already appearing in search results.

These terms often have more specific wording than broad keywords. For example, a broad query such as "email marketing" covers a large subject and attracts competition from established software companies, publishers, and marketing agencies. A more specific query such as "email marketing automation for independent online stores" targets a narrower audience and a clearer need.

The longer query is not automatically easier to rank for. Its actual competition depends on the websites appearing in search results, the quality of their pages, the searcher's intent, and the amount of useful information available on the subject.

Low competition also does not necessarily mean high traffic. A keyword may be relatively easy to target but attract very few searches. Successful keyword research balances ranking opportunities with relevance, demand, and business value.

Why Use AI for Keyword Research?
Traditional keyword research often involves collecting search terms, checking their metrics, examining search results, and organizing the findings manually. AI-assisted tools can reduce the time required for several of these tasks.

They can help marketers:

Generate keyword ideas from a seed topic, product, or customer problem.

Discover related questions and longer, more specific search queries.

Group keywords into topical clusters for blog posts and landing pages.

Identify search intent and distinguish informational queries from commercial searches.

Compare keyword opportunities against competing pages.

Develop content briefs, article outlines, and related subtopics.

Find gaps between the subjects a website covers and the subjects its audience searches for.

The distinction between generating ideas and validating them is important. An AI system can suggest hundreds of plausible keywords, but suggestions alone do not establish search volume, ranking difficulty, or commercial value. Those details require suitable keyword data and direct examination of search results.

Best AI Keyword Research Tools to Consider

Semrush
Semrush is an established SEO platform that offers keyword research, competitor analysis, position tracking, and content optimization features. Its keyword research tools can help marketers evaluate search demand, keyword difficulty, and related terms before deciding which topics deserve attention.

For low-competition research, begin with a broad seed keyword connected to the website's subject. Review related terms, question-based queries, and more specific variations. Filter the results by relevant difficulty metrics, then investigate the search results for the strongest candidates.

Semrush is particularly useful when keyword research needs to connect with competitor analysis and a wider SEO workflow. A marketer can use it to identify topics competitors target and investigate areas where their own website has limited coverage.

Best for: SEO professionals, agencies, affiliate marketers, and businesses managing several content campaigns.

Important consideration: Keyword difficulty is a comparative estimate, not a guarantee of ranking success. Check the actual search results and the strength of the competing pages before committing to a topic.

Ahrefs
Ahrefs provides keyword research and competitor analysis tools that help marketers examine search demand, related queries, ranking pages, and backlink profiles.

Its keyword research workflow can reveal long-tail variations that are more specific than a primary keyword. These variations may help publishers find topics that larger websites have not covered adequately.

One useful method is to examine pages ranking for a broad subject and identify the related queries they address. Next, investigate narrower terms that match the website's audience. Review the competing pages and determine whether an original, more useful resource could answer the query better.

Ahrefs is also useful for examining backlinks to competing pages. Links can influence ranking performance, so understanding the link profiles of ranking pages provides additional context when evaluating a keyword opportunity.

Best for: Content publishers, link-building teams, affiliate websites, and SEO professionals conducting detailed competitor research.

Important consideration: A low keyword difficulty score does not eliminate the need for useful content, appropriate technical SEO, or relevant links where competition makes them important.

Google Keyword Planner
Google Keyword Planner is a keyword research tool designed primarily for planning Google Ads campaigns. It can also help organic search marketers discover keyword ideas and examine search-demand estimates.

The tool is useful for generating ideas from products, services, and existing website content. Marketers can investigate related terms and compare estimated demand across different keyword groups.

One distinction matters here: Google Ads competition measures advertiser competition, not organic search difficulty. A keyword marked as having low advertising competition may still be difficult to rank for in unpaid search results.

Use Keyword Planner to investigate demand and discover ideas, then evaluate organic competition separately by reviewing search results and, where appropriate, using an SEO platform.

Best for: Beginners, small businesses, and marketers who need a source of keyword ideas and advertising demand estimates.

Important consideration: Do not use the advertising competition column as a substitute for organic keyword difficulty.

Google Trends
Google Trends helps users compare the relative popularity of search terms over time and across geographic areas. It is particularly useful for identifying seasonal topics, emerging interests, and changes in search behavior.

For example, a publisher planning content about tax software, holiday marketing, or educational products can use Trends to investigate when interest typically increases. This information helps with editorial planning and can reveal opportunities to publish before demand peaks.

Google Trends does not provide a direct organic keyword difficulty score. Instead, it complements other tools by helping marketers understand whether a topic has sustained interest, seasonal demand, or signs of growing popularity.

Best for: Publishers covering seasonal subjects, news-related topics, consumer trends, and changing market interests.

Important consideration: Relative search interest is not the same as absolute search volume. Validate demand and competition with additional data before selecting a target keyword.

LowFruits
LowFruits is a keyword research tool focused on identifying long-tail search opportunities and analyzing weaknesses among pages appearing in search results.

This approach is particularly relevant to smaller websites. Instead of targeting only broad keywords with established competition, marketers can investigate specific queries where the current results may include weaker or less relevant pages.

A practical workflow begins with a seed topic or keyword list. The tool helps identify opportunities worth investigating, after which the marketer should examine the pages ranking for each query. Look for unanswered questions, outdated information, limited topic coverage, and pages that do not directly satisfy the searcher's intent.

Best for: Niche websites, smaller publishers, affiliate marketers, and bloggers looking for specific topics to target.

Important consideration: A weak competitor does not guarantee a ranking opportunity. Search intent, content quality, and the overall strength of the remaining results still matter.

Keyword Insights
Keyword Insights focuses on keyword clustering and content planning. It helps marketers organize related search terms into groups that can inform individual articles, landing pages, and broader content strategies.

This is useful when AI-generated research produces a large list of similar keywords. Rather than creating a separate article for every variation, marketers can group terms that share the same intent and determine whether one comprehensive page can satisfy them.

For example, several queries about choosing an email autoresponder may belong to one commercial research topic. Publishing separate pages for nearly identical queries could create unnecessary duplication. Grouping related terms helps clarify the appropriate content structure.

Best for: SEO agencies, content strategists, publishers with large keyword lists, and teams planning content at scale.

Important consideration: Automated clustering should be reviewed against actual search results. Similar wording does not always indicate identical intent.

ChatGPT
ChatGPT can assist with the discovery and organization stages of keyword research. It can generate seed keywords, expand topics into long-tail variations, identify common customer questions, propose audience-specific queries, and organize research into useful categories.

For example, a marketer promoting email automation software could request keyword ideas for small online stores, independent consultants, or digital course creators. Each audience has different needs, which can produce more targeted research directions.

ChatGPT can also help classify a verified keyword list by search intent, draft content briefs, and suggest questions an article should answer.

However, generated suggestions should not be treated as verified search data. Unless supported by current keyword research data or another reliable source, a proposed keyword's search volume, ranking difficulty, and commercial value remain unconfirmed.

Best for: Brainstorming, audience research, keyword categorization, content briefs, and organizing findings from dedicated SEO tools.

Important consideration: Use ChatGPT alongside a keyword data provider and live search results. It is an assistant for research, not a replacement for validating keyword metrics.

How to Find Low-Competition Keywords With AI
Choosing a tool is only the beginning. A repeatable research process helps prevent marketers from wasting time on irrelevant queries or keywords they cannot realistically target.

Step 1: Start With a Specific Topic
Begin with a subject closely connected to the website's audience and commercial goals.

An email marketing company might start with "email automation." A finance publisher might investigate budgeting software. A blogger covering website growth might start with technical SEO or link building.

The seed topic should reflect what the website can explain accurately and what its audience needs.

Step 2: Generate Long-Tail Keyword Ideas
Use an AI assistant or keyword research platform to expand the seed topic into specific queries.

For email automation, possible research directions include:

Email automation for small online stores.

How to set up a welcome email sequence.

Email autoresponders for digital product sales.

How to automate abandoned-cart emails.

Email marketing software for independent creators.

These examples are research starting points, not verified claims about search volume or competition. Each candidate requires validation.

Step 3: Check Search Demand
Use a keyword research platform to examine available search-volume estimates and related terms. Consider the geographic market, language, and audience you intend to reach.

A keyword with very little demand may not justify a standalone article. However, a collection of related low-volume queries may support a useful page when they share the same search intent.

Do not select keywords solely because they have the largest reported search volume. Relevance and the value of the traffic matter just as much.

Step 4: Evaluate Organic Competition
Review the actual search results for each promising query.

Ask these questions:

Are the top results published by major websites with strong authority in the subject?

Do the ranking pages answer the question directly?

Is the information current and complete?

Are there important questions that the existing pages do not address?

Could your website produce a more useful resource for the intended audience?

SEO difficulty scores can narrow the list, but direct examination of the competing pages provides essential context.

Step 5: Confirm Search Intent
Determine what users expect to find when they enter the query.

Informational searches call for explanations, tutorials, and practical guides. Commercial investigation searches often require comparisons, reviews, and feature breakdowns. Transactional searches may require product pages, pricing information, or clear paths to purchase.

A page that targets the right keyword but fails to satisfy the expected intent may struggle to rank or convert visitors.

Step 6: Group Related Keywords
Use a clustering tool or AI assistant to group keywords by topic and intent. Decide which queries belong on the same page and which require separate resources.

This process helps establish a content plan without creating unnecessary duplicate articles.

A well-organized website can use a main guide to cover a broad subject and supporting articles to answer specific questions. Internal links can then connect those pages where they provide genuine value to readers.

Step 7: Prioritize Commercial Value
A low-competition keyword is more useful when the resulting traffic supports the website's objectives.

A software company may prioritize searches from people comparing tools or looking for a solution to a specific business problem. An educational publisher may focus on informational searches that attract its intended readership.

Evaluate each candidate by relevance, demand, likely ranking opportunity, search intent, and potential business value. Do not assume that every keyword with a low difficulty score deserves an article.

Step 8: Publish, Measure, and Improve
After publishing, monitor impressions, clicks, rankings, and relevant conversions using available analytics and search performance tools.

If a page receives impressions but few clicks, examine the title and description and compare them with the search intent. If it attracts visitors but produces little engagement or few conversions, review whether the content addresses the right audience and provides a useful next step.

Update pages when the subject, evidence, or user needs change. Use actual performance data to guide the next round of keyword research.

Common Mistakes to Avoid
Treating AI suggestions as verified data. Keyword ideas are not proof of search demand. Validate them with suitable tools.

Confusing paid and organic competition. Advertising competition and organic ranking difficulty measure different things.

Chasing low difficulty without checking relevance. A keyword is not valuable merely because it appears easy to target.

Creating a separate article for every variation. Closely related queries may belong on one comprehensive page.

Ignoring search intent. Content must answer the question or meet the need that prompted the search.

Overlooking the competition itself. Metrics cannot fully explain why particular pages rank. Examine the content, relevance, links, and overall quality of the results.

Which AI Keyword Research Tool Should You Choose?
The right choice depends on the research task and available budget.

Semrush and Ahrefs are useful options for broader SEO research and competitor analysis. Google Keyword Planner helps discover keywords and examine advertising demand, while Google Trends adds context about interest over time. LowFruits focuses on long-tail opportunities, and Keyword Insights supports clustering and content planning. ChatGPT can help generate ideas and organize findings, provided its suggestions are checked against reliable data.

For a beginner, a practical starting workflow is to generate ideas with ChatGPT, examine demand with Google's research tools, review the search results, and use a dedicated SEO platform when more detailed competition analysis is necessary.

For an established SEO team, combining keyword research, competitor analysis, clustering, and performance tracking can provide a more complete process.

Final Thoughts
Finding low-competition search terms requires more than asking an AI tool to produce a keyword list. The strongest opportunities come from combining relevant ideas with validated search data, careful analysis of existing results, and a clear understanding of the intended audience.

Start with specific customer problems. Expand them into long-tail queries. Check search demand, inspect competing pages, confirm search intent, and prioritize terms that support the website's goals.

AI can make the research process more efficient, but ranking decisions should remain grounded in evidence. The objective is not to publish the largest number of keyword-targeted articles. It is to publish useful pages for searches where the website has a credible opportunity to compete and deliver value to readers.

Content Signals and RSL: Stating How AI May Use Your Content

Sun, 18 Oct 2026 07:09:29 +0000

robots.txt only decides whether a crawler may fetch a path. It's silent on what happens next: whether the content appears in a search result, gets quoted in an AI answer or is used to train a model. Two newer mechanisms address that, and this guide explains both and is straight about their limits.

Content Signals, introduced by Cloudflare in September 2025, adds a Content-Signal line to robots.txt with three settings: search, ai-input (using content in a real-time AI answer) and ai-train. Each is yes or no, and a missing key means no stated preference. The split matters because search and AI answers send visitors and citations, while training only helps you indirectly, and robots.txt alone can't express "answer questions with my content but don't train on it" when one crawler serves several purposes. On this site I publish yes to all three.

RSL (Really Simple Licensing), also announced in September 2025, defines a machine-readable licence stating what AI systems may do with content and on what terms, from free with attribution to pay per crawl. We publish one here as an experiment.

The limits are important. Neither is enforcement, neither reaches content already collected, and real enforcement lives in CDN bot management and verified-bot programmes. I finish with a short list of what to publish and how to keep it consistent with your user-agent rules.

Key takeaways

robots.txt controls fetching, not later use
Content Signals covers search, ai-input and ai-train
RSL publishes machine-readable licence terms
Both state preferences; neither enforces them
Make sure your CDN isn't overwriting your signals

Related on BuiltToWinWeb: Cloudflare's AI crawl controls

Read the full guide on BuiltToWinWeb: Content Signals and RSL explained

A summary by Jacob Campbell of an article first published on built2winweb.com on October 5, 2026.

Six Steps to Make a WordPress Site Readable by AI Assistants

Fri, 16 Oct 2026 16:18:32 +0000

Most WordPress installs were configured with Google in mind rather than AI assistants. Fortunately WordPress already provides most of what's needed: structured content in a database, a REST API, permalinks and a big plugin ecosystem. Making it readable by AI is mostly about not blocking the right bots, exposing content in cleaner forms and telling agents where to look. This guide goes step by step, with plugin and manual options.

Step one is checking you aren't blocking AI search and user-triggered bots, not only in robots.txt but in security plugins and CDN toggles too. Step two is being indexed in Google and Bing, with sitemaps submitted and IndexNow on. Step three is checking your schema: organisation details filled in, a LocalBusiness subtype for local firms and no self-serving review markup expecting stars.

Step four is adding llms.txt, and actually reading what a plugin generates, because automatic files often list every post and say nothing about the business. Step five, the one most WordPress sites skip, is serving Markdown versions of posts with the right headers. Step six is an MCP server built on the REST API or WooCommerce, with read-only public tools.

I mention the one-plugin route through the AI Indexing Pack's WordPress edition, and end with two checks: a WebAgentScan score before and after, and asking a browsing assistant to read your llms.txt and describe your business.

Key takeaways

Check security plugins and CDNs as well as robots.txt
Be indexed in both Google and Bing, with IndexNow on
Review any auto-generated llms.txt by hand
Markdown versions of posts are the most-skipped step
Test by asking an assistant to describe your business from llms.txt

Related on BuiltToWinWeb: robots.txt rules for AI crawlers

Read the full guide on BuiltToWinWeb: How to make WordPress readable by AI

A summary by Jacob Campbell of an article first published on built2winweb.com on October 5, 2026.

What Is WebMCP and Why Should Website Developers Care

Tue, 29 Sep 2026 12:32:56 +0000

What is WebMCP—and why should website developers pay attention?

AI browser agents often navigate websites by interpreting pages and interacting with buttons and forms.

WebMCP offers another approach: developers can expose specific website functions that compatible agents can discover and call directly.

For example, a travel website could expose a flight-search function with defined inputs instead of requiring an agent to navigate several screens.

On September 28, 2026, Cloudflare announced WebMCP support in Kitesurf, its browser designed for AI agents. Kitesurf remains in beta.

What should development teams do with this information?

Start with one small, read-only workflow—such as searching a product catalog. Define its inputs, validate requests, and test what happens when information is missing or incorrect.

Our practical recommendation: keep authentication and authorization enforced on the server, and require confirmation before consequential actions.

The limitation: Support depends on the browser and agent being used. This announcement does not establish a Google ranking benefit or guarantee reliable automation on every website.

Source: Cloudflare, September 28, 2026
https://blog.cloudflare.com/kitesurf-update/

Explore AI integration and software development with Dotera:
https://www.dotera.co/

WebMCP #AIAgents #WebDevelopment #SoftwareEngineering #BrowserAutomation #AIIntegration #Cloudflare #Dotera

From SEO to AI Search: Jarno S’s Journey Into Making the Web More Understandable to AI

Fri, 18 Sep 2026 10:22:19 +0000

From SEO to AI Search: Jarno S’s Journey Into Making the Web More Understandable to AI

“Build for people. Structure for understanding. Measure what changes.”

Search is changing.

For years, businesses and website owners have focused on questions like: Where do we rank on Google? How much traffic are we getting? Which keywords are bringing visitors?

But as people increasingly turn to AI systems such as ChatGPT, Gemini, Perplexity and Copilot for answers, another question is becoming increasingly important:

What does AI say about your business — and is it accurate?

For Jarno S, founder of AEOvara in Finland, this question sits at the intersection of technical SEO, AI search, structured data, content architecture and measurement.

Jarno's path into this work has been practical rather than purely theoretical. He has built websites, worked with visual content and photography through Kuvaajankulma, and experienced how difficult it can be for a good business to become discoverable online.

SEO became a natural part of solving that problem.

Then AI search changed the question.

Instead of asking only whether a website can rank, Jarno became interested in whether AI systems could understand a business correctly, represent it accurately and recommend it for the right reasons.

That thinking led to AEOvara and his work around Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), and Large Language Model Optimization (LLMO).

From Traditional Search to AI Search

Jarno describes several related concepts that are increasingly appearing in conversations about search.

Traditional SEO is mainly concerned with earning visibility in search-result pages.

AEO — Answer Engine Optimization — focuses on structuring content so that it can answer a question directly.

GEO — Generative Engine Optimization — focuses on how a brand is represented and recommended in generative search experiences.

And LLMO — Large Language Model Optimization — is about making a website, its entities and its information understandable to large language models.

These approaches overlap, but for Jarno the broader shift is more important than the terminology.

The goal moves from simply trying to “rank for a keyword” toward becoming a reliable answer.

That distinction becomes particularly important when the interface between a person and the web is no longer simply a list of links.

The Question That Changed Everything

Jarno became interested in AI search when he noticed that people were increasingly asking ChatGPT, Gemini and Perplexity questions that they previously asked Google.

That introduced a new problem.

It was no longer enough to ask:

“Where do we rank?”

There was another question:

“What does the AI say about us, and is it accurate?”

That question became central to his work.

Jarno describes his work as having two audiences: the people reading a website and the AI systems trying to understand it.

That idea has influenced how he approaches website architecture and content.

A page should work for a person who is in a hurry, while also giving a system enough clarity to identify the business, its services, evidence and expertise.

That means clear page purpose, direct answers, logical headings, consistent facts and strong internal connections.

AI Visibility Should Be Measured

One of Jarno's strongest themes is measurement.

AI search can sometimes appear mysterious. Ask an AI system a question, receive an answer, take a screenshot and it can be tempting to conclude that a business is either visible or invisible.

Jarno argues that this isn't enough.

AI outputs can vary depending on the platform, wording, location and time.

A more useful approach is to create a repeatable measurement process.

His recommendation is straightforward:

Start with 8–15 real customer questions.

Keep the wording stable.

Test those questions across the relevant AI platforms.

Then record the results.

The goal isn't to create a perfect score.

The goal is to establish a trustworthy baseline that makes changes visible.

Think of AI Visibility Like Regression Testing

Jarno compares an AI visibility benchmark to a software regression test suite.

The analogy is particularly useful for developers.

If the test changes every time you run it, it becomes difficult to determine whether the software changed or the test changed.

The same applies to AI search.

If the prompt changes every time, you cannot reliably determine whether a change in the result came from an improvement in the brand's visibility or simply from asking a different question.

Jarno recommends keeping a stable core set of prompts while adding new questions over time when necessary.

It turns AI visibility from a collection of interesting screenshots into something that can be observed and compared.

A Mention Isn't the Same as a Citation

Another distinction Jarno considers important is the difference between mentions and citations.

An AI system might mention a business in an answer.

But that mention could be vague, incorrect or simply part of a long list.

A citation provides a stronger signal because it connects a specific claim to a source.

Both matter, but they answer different questions.

Visibility is useful.

But trusted and accurate attribution is more valuable.

For Jarno, metrics should therefore be separated rather than combined into one simplistic number.

He focuses on areas such as:

Visibility
Mentions
Citations
Accuracy
Meaningful or qualified actions

The distinction helps businesses understand not only whether AI systems are talking about them, but how they are representing them.

Structured Data Helps AI Understand the Pieces

Jarno's work also places significant emphasis on Schema.org structured data and entity clarity.

He doesn't describe Schema.org as a magic solution.

Instead, he sees it as a useful shared vocabulary that can help systems identify things such as:

Products
Services
People
Organisations
Locations
FAQs
Relationships between entities

But structured data becomes much more useful when it matches the visible content on a website and the information remains consistent across the site.

Adding schema isn't a substitute for having clear information.

The underlying content still matters.

What About `llms.txt`?

There has been considerable discussion around llms.txt as websites adapt to AI systems.

Jarno takes a measured approach.

He sees llms.txt as an experiment and a helpful orientation layer, rather than a visibility button.

It may make important pages and topics easier to discover, but it cannot replace useful content, technical quality, reputation or independent evidence.

Jarno's approach is simple:

Implement sensible experiments, then measure whether they actually change anything.

That philosophy is consistent throughout his work.

Don't adopt something simply because it is currently being discussed.

Test it.

Measure it.

Then decide what the evidence tells you.

Make Pages Easy to Quote

One of Jarno's ideas is that websites should be “easy to quote, not merely easy to crawl.”

That requires thinking about how information is presented.

His practical recommendations include:

Put the main answer where people can find it quickly.
Use descriptive headings.
Explain important terms clearly.
Support claims with evidence.
Show authorship.
Include update dates where appropriate.
Avoid hiding important facts inside marketing language.

The goal is to make information easier for an AI system to understand and represent accurately.

But these practices also make websites easier for humans to understand.

That overlap is important.

The AI Search Advice He Thinks Is Overhyped

The AI search industry is moving quickly, and with that comes a constant stream of new tactics.

Jarno is skeptical of the idea that one file, one prompt trick or one piece of schema can suddenly make a business “rank in ChatGPT.”

For him, AI visibility isn't a switch.

It is built from several things working together:

Helpful content + technical accessibility + entity clarity + credible references + ongoing measurement.

This is also why he prefers experimentation over blindly following trends.

If something has a plausible mechanism, can affect how people discover businesses and can be tested responsibly, he sees value in running a small experiment.

If it creates excitement but cannot be measured or explained, he treats it as noise until stronger evidence appears.

What AI Search Reveals About Businesses

One of Jarno's biggest surprises has been how uneven AI search results can be.

A business may be described accurately on one platform and poorly — or not at all — on another.

Even more interestingly, AI systems can sometimes produce confident-sounding answers when the underlying business information is incomplete or mixed up.

That creates a different kind of challenge for businesses.

It's not simply about gaining visibility.

It's about making sure the information that becomes visible is correct, consistent and supported by evidence.

Building AEOvara

Jarno founded AEOvara to help businesses navigate search in the AI era.

The challenge is partly technical and partly educational.

Many business owners already understand concepts such as Google rankings and website traffic.

But asking:

“How do AI systems describe my business?”

is still a relatively new question.

Jarno believes the answer is to keep the conversation practical.

Instead of selling mystery, show businesses:

What AI systems currently say
Where information is missing
Where information is inaccurate
What can be improved
What changed after the work

That makes a new category easier to understand.

It also keeps the focus on measurable outcomes rather than hype.

From AI Visibility to Repeatable Benchmarks

A major part of Jarno's current exploration is making AI visibility more reproducible.

He has developed an ongoing AI visibility benchmark and published practical guides around measuring how AI systems discover and cite content.

The idea is straightforward: if businesses want to improve their AI visibility, they need a way to observe what is happening before and after making changes.

That means stable prompts, repeated observations and clearly separated metrics.

Instead of asking whether a website is “good at AI search,” businesses can begin asking more specific questions:

What changed?

Where did it change?

Was the information accurate?

Was the business cited?

Did the change lead to a meaningful outcome?

Those questions turn an abstract concept into something that can be investigated.

Lessons From Photography

Jarno's work isn't limited to SEO and AI search.

He also has a background in professional photography and visual content through Kuvaajankulma.

That experience has influenced how he thinks about discoverability and trust.

Photography taught him that presentation matters.

A website needs a clear point of view, coherent presentation and real evidence.

It also taught him to respect the user's attention.

The best page isn't necessarily the one containing the most information.

It's the one that makes the right information easy to understand.

That principle carries naturally into his thinking about AI search.

Where Search Goes Next

Jarno doesn't see traditional search disappearing completely.

He expects it to remain important, particularly for research, navigation and comparison.

At the same time, he believes AI assistants will increasingly become the starting point for many questions, especially broad or conversational ones.

Rather than imagining a complete replacement, he sees a more blended search journey emerging.

People may move between traditional search engines, AI assistants, websites and other interfaces depending on what they are trying to accomplish.

For businesses, that means the underlying information needs to work across more than one type of discovery experience.

Advice for Developers and Small Businesses

For developers, technical founders and small businesses thinking about AI search, Jarno recommends starting with fundamentals rather than chasing every new trend.

His practical starting points are:

Keep business facts accurate and consistent.
Make important pages technically accessible.
Answer real customer questions clearly.
Use relevant structured data.
Make it clear who is responsible for the content.
Build a stable set of prompts and measure them over time.
Focus on changes that can actually be verified.

The common thread is simple:

Improve what you can measure.

A Lesson From Building a New Category

One lesson Jarno learned while building AEOvara is that too much jargon can make a new field harder to understand.

Technical terminology may be useful internally, but customers ultimately need answers to practical questions.

Are we being understood correctly?

Are we being recommended for the right reasons?

What changed after the work?

Those questions provide a much clearer way to explain the value of AI search visibility.

AI Search Is an Information-Quality Challenge

Jarno believes one of the biggest misunderstandings around AI search is treating it simply as a temporary traffic-generation trick.

He sees something broader.

AI search is also an information-quality challenge.

If a business cannot explain itself clearly, consistently and with evidence, AI systems will have a harder time understanding it correctly.

That makes AI visibility partly a technical problem, but also a content, information architecture and trust problem.

What's Next for AEOvara?

Jarno is most excited about making AI visibility more reproducible.

That includes practical benchmark methods, clearer reporting and tools that help smaller businesses understand how answer engines see them.

AEOvara has already explored this through practical guides, an llms.txt generator and ongoing AI visibility benchmarking.

The broader goal is to make AI search visibility less mysterious and more measurable.

Rather than asking businesses to trust a new acronym or a new optimization trick, the approach is to establish a baseline, run experiments, observe changes and learn from the evidence.

That mindset — measure what changes rather than simply following the latest trend — runs through Jarno's approach to AI search.

About Jarno S

Jarno S is the founder of AEOvara, based in Lappeenranta, Finland.

His work focuses on Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), AI Search Optimization, Technical SEO, Schema.org structured data and LLM Optimization (LLMO).

He works across search ecosystems including Google Search, ChatGPT, Gemini, Perplexity and Copilot, exploring how AI answer engines discover, interpret and cite web content.

His current work includes entity clarity, structured data, repeatable AI visibility benchmarks and practical ways to connect traditional SEO with AEO, GEO and LLMO.

His guiding principle is simple:

“Build for people. Structure for understanding. Measure what changes.”

CoderLegion Developer Stories

This story is part of CoderLegion Developer Stories, where developers, engineers, technical founders and technology professionals share their experiences, challenges, projects and lessons from their journeys.

The goal is to give the CoderLegion community a closer look at the people and ideas behind the technology.

Interviewed and edited by Mehadi Hasan, Community & Editorial Team at CoderLegion.

For developers, llms.txt offers undeniable efficiency. For marketers, it offers zero proof. The data

Thu, 17 Sep 2026 16:20:30 +0000

As developers, we know how messy raw HTML can be for parsers. The llms.txt standard addresses this directly, reducing token consumption by up to 10x for the same content.

But is shipping it an optimization priority or just industry noise? We went beyond the hype cycle to analyze the real data and technical reality in late 2026.

Key takeaways:

Strict Syntax:
This isn't a webpage; it’s an instruction manual. Deviation breaks the parse.

Dev-Heavy Adoption:
The standard clusters heavily around dev platforms like Mintlify, Fern, and Cursor, where users actively employ AI coding assistants.

Google’s Split:
Google Search ranking has zero use for the file, while Chrome teams use it as a signal for browser agents.

Google WebMCP:
Google's real infrastructure bet is functional tool contracts for agents, not just descriptions.

The data suggests that structural content work—clear headings and direct answers—remains the primary optimization task.

🔗 For the full technical breakdown, check the article on our site: [https://www.thefluxread.com/2026/09/llmstxt-and-rise-of-agentic-seo-why.html]

Traditional SEO vs AEO/GEO: Why Smaller Brands Can Win in AI Search

Tue, 15 Sep 2026 18:10:53 +0000

For years, I have heard the same assumption: “Large brands have more content, more backlinks, and greater recognition, so a smaller company cannot beat them in Google’s AI-powered search results.”

My practical experience tells a different story.

In 86% of our client campaigns, we have helped a small or midsize company earn a mention in an AI-generated answer ahead of a larger competitor. On average, that visibility has emerged 3.1 times faster than results from traditional SEO.

This is not luck or marketing rhetoric. Independent research is increasingly pointing in the same direction: AI search rewards relevance, structure, and specific expertise—not brand size alone.

The short answer

No, large brands do not automatically dominate Google AI Overviews. A substantial share of AI citations comes from pages that do not rank in Google’s top 10, and even major B2B companies are absent from most AI-generated answers for keywords where they already rank organically.

That creates a genuine opening for smaller companies. A focused expert who answers a question clearly can outperform a large general-purpose website that only addresses it halfway.

Ranking and citation are now separate layers

Walker Sands published its B2B AI Search Visibility Benchmark in June 2026. The study covered 828 enterprise B2B companies and more than 45 million searches.

The typical large B2B company ranked organically for roughly 9,700 keywords, and AI Overviews appeared for almost half of them. Yet the median brand was cited in only 3% of those AI answers. Some 4.6% of the companies received no citations at all for their own ranking keywords.

A major brand can therefore be highly visible in traditional search results while remaining almost invisible inside the generated answer itself.

WordStream’s statistics offer another perspective: Google’s 50 largest domains receive about 30% of all AI Overview mentions. The remaining 70% is distributed across the long tail—the part of the web where smaller specialists operate.

Traditional SEO logic says: rank high and you will be seen. In AI search, that relationship is no longer reliable.

Ahrefs analyzed 863,000 keywords and four million citations in March 2026. Only 38% of AI citations came from top-10 results, down from 76% a year earlier. Another 31% came from positions 11–100, while 31% came from pages outside the top 100.
Research from 5W Public Relations and Brandlight in May 2026 found that the overlap between Google’s leading results and sources cited by AI engines had fallen from roughly 70% to below 20% in two years.
seoClarity analyzed 362,000 keywords in October 2025. Although 94% of AI answers cited at least one top-20 result, 44% of all individual citations came from outside the top 20.

The studies use different methodologies. BrightEdge, for example, has reported a 54.5% overlap. But the direction is consistent: ranking and citation are distinct visibility layers, and companies need to measure both.

AI answers reduce clicks—but citations can reverse the effect

Pew Research Center studied 900 users in July 2025. When an AI summary appeared, only 8% clicked a traditional search result, compared with 15% when no summary was shown. In 26% of cases, the session ended on the summary page.

Ahrefs reported in December 2025 that the presence of an AI Overview correlated with a 58% decline in click-through rate for the number-one organic result.

That sounds alarming, but there is an important twist: being cited changes the outcome.

Seer Interactive analyzed 5.47 million queries and 2.43 billion organic impressions. Brands cited in an AI answer received about 35% more organic clicks than uncited brands on the same results page. In its 2026 data, cited brands generated as much as 120% more clicks per impression.

Citations also create an effect that analytics cannot fully capture. When a brand appears repeatedly in AI-generated answers, people begin to remember it. At AEOvara, we call this Share of Model—the brand’s share of how AI systems represent its market.

Why smaller companies can win

1. Specificity beats breadth

Yotpo’s comparison of Google AI Mode explains the basic mechanism: AI models prioritize relevance and consensus more heavily than domain authority alone.

A smaller brand whose content, expertise, and customer data precisely match the question can outrank a giant whose content is broad but generic.

2. AI search reacts quickly

According to 5W’s GEO report, new content can enter AI engines’ citation pools within three to five days. Traditional Google rankings often take three to six months. Content that is not refreshed may begin losing citation frequency after about 13 weeks.

Speed is an advantage for a smaller organization. A focused team can publish, test, and update answers while a large company is still moving content through multiple approval layers.

3. AI queries are long and narrow

A Semrush and Datos analysis of more than 10 million keywords found that queries containing eight or more words were seven times more likely to trigger an AI Overview. Nearly 90% of AI queries were informational.

These are specific “how,” “why,” and “which is better” questions. Deep specialist knowledge is often more valuable here than a large site’s general coverage.

Traditional SEO and AEO/GEO are complementary

Traditional SEO and Answer Engine Optimization or Generative Engine Optimization are not opposites. They are two layers of the same visibility strategy.

Traditional SEO

Starts with a keyword and aims for a ranking.
Often favors long, comprehensive pages.
Relies heavily on backlinks and domain authority.
Commonly takes three to six months to show results.
Is measured with Search Console and ranking tools.
Typically maps one article to one primary keyword.

AEO/GEO

Starts with a question and aims for a citation.
Uses modular content: the direct answer first, followed by supporting detail.
Relies on relevance, structure, clarity, and topical authority.
Can begin showing results within three to five days.
Is measured through citation frequency and Share of Model.
Maps one answer block to one specific question.

SEO builds discoverability. AEO/GEO makes your knowledge easy for an AI assistant to extract, trust, and cite. Strong brands need both.

A practical seven-step framework

Here is the framework I give every client:

Answer immediately. Put the direct answer in the first paragraph. Do not make the reader—or the model—work through a long introduction.
Use a predictable structure. Turn the question into a heading, answer it directly, and then add evidence and context.
Name entities clearly. Refer to people, places, companies, and products unambiguously.
Concentrate your expertise. Twenty deep articles on one subject can be more valuable than 100 superficial pieces spread across unrelated topics.
Refresh content regularly. Treat roughly 13 weeks as a useful review cycle for information that changes.
Build consensus. Expert commentary and independent third-party mentions strengthen the signals AI systems use to establish trust.
Measure citations separately from rankings. A position report alone no longer describes your real search visibility.

The core message is simple: SEO is not disappearing, but it is no longer sufficient on its own. AI search requires an optimization layer of its own.

Frequently asked questions

Can a small company really compete in AI search?

Yes. In Ahrefs’ analysis, 31% of citations came from pages that did not rank in the top 100 at all. seoClarity found that 44% of citations came from outside the top 20. A citation is not reserved for the biggest domain; relevance and answer quality matter.

How common are AI Overviews?

Google has stated that AI Overviews appear for about 50% of US queries. Nearly 90% of AI queries are informational, so the greatest impact falls on advice, education, and comparison content.

How quickly can results appear?

According to 5W’s report, new content can enter AI citation pools in three to five days, compared with the three to six months commonly required for traditional rankings. Across our own client campaigns, the difference has averaged 3.1 times faster.

Is a strong Google ranking enough?

Not by itself. Research from 5W and Brandlight found that fewer than 20% of sources cited by AI engines appeared in Google’s top 10 for the same query. Content must also be written and structured so that an AI assistant can extract a complete, well-supported answer.

Sources

Walker Sands (June 2026) · Ahrefs (February and March 2026) · Pew Research Center (July 2025) · Seer Interactive (April 2026) · seoClarity (October 2025) · 5W Public Relations / Brandlight (May 2026) · Semrush and Datos (May 2025) · Sistrix (February 2026) · AEOvara client campaign data

About the author

I am Jarno Saarimies, founder of AEOvara and a specialist in AI search optimization, including AEO, GEO, and LLMO. I help Finnish companies become visible where people now look for answers—from Google AI Overviews to ChatGPT. My work is based on measurable data, not assumptions.

👉 Learn more about Jarno Saarimies and AEOvara

How visible is your brand in AI search today? If you do not know the answer, that is the first thing worth measuring.

From Visibility to Trust: The Business Benefits of AI Search Optimization (AISO)

Sun, 13 Sep 2026 09:04:08 +0000

From Visibility to Trust: The Business Benefits of AI Search Optimization (AISO)

In my previous article, “AI Search Optimization (AISO): Helping AI Understand What You Actually Do,” I introduced a simple distinction:

SEO helps people find you.
AISO helps AI understand and explain you.

That distinction is becoming more important.

AI-powered search is no longer simply an experimental interface placed on top of traditional search. People increasingly ask complete questions, describe complex situations, compare alternatives and continue with follow-up questions rather than typing a few keywords and opening ten browser tabs.

Google's AI Mode, for example, can break a question into multiple related searches, gather information across different sources and construct a consolidated answer. Google calls this technique query fan-out.

This fundamentally changes the opportunity for businesses.

The objective is no longer only:

“Can somebody find my webpage?”

It is increasingly:

“When an AI system is asked about a problem we solve, does it understand enough about us to consider, describe and reference us correctly?”

That is where the real value of AI Search Optimization begins.

And the benefits extend far beyond getting mentioned by an AI.

1. AISO Creates Visibility Before the Website Visit

Traditional digital marketing often assumes that discovery happens when somebody visits your website.

AI search changes the sequence.

A potential customer might first encounter your company inside an AI-generated response:

“What software can migrate DICOM studies between PACS systems?”

“Which companies provide cybersecurity services for small manufacturers?”

“What platforms can automate invoice reconciliation?”

The user may never have heard of the companies appearing in the response.

The AI has effectively become part of the discovery layer.

This means a company can influence a buying journey before the prospect reaches its website.

That is an important shift.

Search visibility used to mean appearing somewhere on a results page.

AI visibility can mean becoming part of the explanation itself.

Google now explicitly describes its generative search experiences as opportunities for more types of websites to appear when users ask complex questions. Its AI systems may search across multiple subtopics to identify supporting sources rather than simply reproducing a conventional ten-link result.

AISO therefore expands the concept of visibility from page visibility to knowledge visibility.

2. AISO Improves the Accuracy of How Your Business Is Represented

Visibility is useful only if the representation is correct.

Consider a company whose website says:

“We deliver next-generation digital transformation solutions for tomorrow's connected enterprise.”

It sounds polished.

But what does the company actually do?

Does it build software?

Provide consulting?

Implement ERP systems?

Integrate medical devices?

Sell cloud infrastructure?

A human may browse several pages and eventually understand.

An AI system must reconstruct that meaning from whatever information it can retrieve.

AISO removes unnecessary ambiguity.

Instead of forcing machines to infer your business, you explicitly establish things such as what the product is, what problem it solves, who uses it, where it operates, how it works and what distinguishes it from alternatives.

That reduces the amount of interpretation required.

The benefit is not merely better AI visibility.

It is better AI accuracy.

And as AI becomes an intermediary between companies and customers, accurate representation becomes a form of digital reputation management.

3. AISO Builds Authority Around Problems, Not Just Keywords

Traditional SEO often begins with keywords.

AISO begins with questions, problems, entities, relationships and context.

That difference matters.

Imagine that your company develops a specialised radiology Picture Archival and Communication System (PACS) data-migration platform.

The useful knowledge around that product may include:

What causes migrations to fail?

How should migration completeness be verified?

What happens to metadata during migration?

How should duplicate studies be handled?

What is the difference between C-MOVE and C-STORE?

How should failed migrations be retried?

Those topics create something larger than a collection of keyword-targeted articles.

They create a knowledge territory around the problem your company understands.

When that knowledge is technically accurate, consistent and genuinely useful, your organisation becomes easier to associate with the subject.

That is a much stronger position than merely ranking a product page for a commercial keyword.

You are no longer saying:

“We sell this.”

You are demonstrating:

“We understand this.”

Authority follows understanding.

4. AISO Can Produce Better-Qualified Visitors

One fear surrounding AI search is that users will receive answers without visiting websites.

For simple factual queries, that will sometimes happen.

But commercial and complex decisions behave differently.

People still need deeper information, evidence, specifications, pricing, demonstrations, examples and reassurance before making decisions.

Google has reported that users asking AI-supported search questions are often making longer and more complex queries. Google has also reported that clicks originating from AI-search experiences can be higher-quality visits, with users more likely to remain on the destination website rather than immediately returning to the results.

This makes intuitive sense.

Compare two visitors.

The first searches:

“PACS migration.”

The second asks:

“What software can help a hospital migrate DICOM studies between PACS systems while tracking failures and validating completeness?”

The second person has revealed considerably more intent.

If an AI response introduces your product in that context, the visitor arriving at your website already understands why your product may be relevant.

AISO therefore has the potential to trade some low-context traffic for high-context discovery.

Ten well-qualified visitors may ultimately matter more than one hundred visitors who arrived with little understanding of what you offer.

5. AISO Allows Specialist Companies to Compete Through Specificity

Traditional search has historically rewarded many factors associated with established websites: authority, links, content history and competitive strength.

Those factors still matter.

But conversational AI search introduces another dimension:

specific relevance to a detailed question.

Google's own description of query fan-out shows why this is significant. AI search may investigate several aspects of a question and retrieve information from a wider range of relevant sources.

That creates an interesting opportunity for smaller specialist businesses.

A large corporation may have enormous domain authority but only a vague paragraph about a particular niche problem.

A specialist company may have detailed technical documentation explaining exactly how that problem occurs and how it is solved.

For a sufficiently specific question, the specialist information may be considerably more useful.

AISO therefore gives smaller organisations another competitive weapon:

clarity and depth.

You may not be the biggest company in the industry.

You can still become one of the clearest sources explaining a specific problem.

6. AISO Strengthens Brand Positioning

One of the less obvious benefits of AISO is that implementing it forces a company to clarify its own positioning.

Try completing this sentence:

“[Product] is a __ that helps __ solve __ by __.”

Many businesses discover that this is surprisingly difficult.

Their website may contain dozens of pages without providing one consistent answer.

AISO exposes that weakness.

To make a company understandable to AI, teams must agree on basic facts:

What category are we in?

What exactly do we sell?

Who is it for?

What problem do we solve?

How do we solve it?

What makes us different?

What should we not be confused with?

These may look like AI-search questions.

They are actually business strategy questions.

AISO therefore has an internal benefit as well as an external one.

It forces organisations to convert marketing language into structured knowledge.

The result is usually clearer positioning for humans too.

7. AISO Creates Consistency Across Your Digital Footprint

AI systems do not necessarily learn about a company from a single webpage.

Information may exist across websites, documentation, articles, product directories, repositories, interviews, industry publications, support pages and other publicly available sources.

Problems arise when those sources contradict each other.

One page describes the product as a migration platform.

Another calls it an integration platform.

An old profile describes functionality that no longer exists.

A third-party article uses obsolete terminology.

The company website introduces yet another category.

To a human, these differences may seem minor.

To a system trying to determine what the company actually does, they create uncertainty.

AISO encourages organisations to establish a canonical description—a stable source of truth for important facts—and then reinforce those facts consistently across their public knowledge footprint.

Consistency does not mean copying identical paragraphs everywhere.

It means maintaining consistent facts.

That improves machine understanding while also strengthening brand discipline.

8. AISO Makes Existing Content Work Harder

Another misconception is that AI visibility requires publishing enormous quantities of new content.

Often it does not.

A business may already possess excellent knowledge buried inside product pages, technical manuals, FAQs, presentations, support documents, case studies and internal expertise.

The problem is that this information was never organised for public discovery.

AISO can turn that material into reusable knowledge.

A twenty-page technical document might produce a clear product explanation, implementation guide, comparison page, troubleshooting article, FAQ, terminology page and several specialist articles.

The underlying expertise already existed.

AISO simply makes it easier to discover and interpret.

This changes the content question from:

“What else can we publish?”

to:

“What valuable knowledge do we already possess that the outside world cannot currently understand?”

That is often a much better investment.

9. AISO Supports the Entire Customer Journey

AI search is not limited to early-stage discovery.

People use AI throughout the decision process.

They may ask:

“What solutions exist?”

followed by:

“How do these approaches differ?”

then:

“What are the risks?”

then:

“Which option is appropriate for a hospital with 20 million DICOM images?”

and eventually:

“What should I ask the vendor before buying?”

This means organisations need more than a homepage optimised for one keyword.

They need knowledge that supports different stages of decision-making.

Educational material builds awareness.

Comparison content supports evaluation.

Technical documentation reduces uncertainty.

Implementation information increases confidence.

FAQs remove objections.

Case studies provide evidence.

AISO connects those pieces into a coherent knowledge environment.

The commercial benefit is significant: the organisation can participate in more stages of the customer's reasoning process.

10. AISO Can Reduce the Distance Between Question and Solution

Traditional search frequently requires several steps:

Question → search → results → webpage → navigation → explanation.

AI search can compress that journey:

Question → explanation → relevant source or solution.

That reduction in friction matters.

If somebody describes precisely the problem your product solves and an AI system can identify your product as relevant, discovery can happen much earlier.

The user does not necessarily need to know your company name.

They need to know their problem.

This is one of AISO's most powerful commercial characteristics.

It allows businesses to compete for problem awareness, not merely brand awareness.

11. AISO Protects Against Being Defined by Someone Else

There is another reason companies should publish clear information about themselves.

If you do not clearly explain your category, product and expertise, other sources may effectively do it for you.

Competitors may define the terminology.

Review sites may define the comparison criteria.

Old articles may describe obsolete functionality.

AI systems may combine incomplete fragments and reach the wrong conclusion.

You cannot control every AI-generated answer.

Nor should AISO be presented as a way of doing so.

But you can improve the quality of the evidence available.

Publishing precise, current and authoritative information gives AI systems stronger material from which to construct answers.

In an AI-mediated information environment, maintaining accurate public knowledge about your organisation becomes increasingly important.

12. AISO Creates a Foundation for AI Agents

AI search is also moving beyond answering questions.

AI systems are increasingly being designed to help users compare options, investigate products and perform tasks.

Google, for example, has already demonstrated agent-like capabilities within AI Mode for activities such as investigating products and completing parts of transaction workflows.

This introduces another future requirement.

Your information must not only be persuasive.

It needs to be interpretable.

Imagine an AI agent asked:

“Find three suitable systems for migrating a hospital's legacy PACS archive. Exclude solutions that cannot validate migration completeness.”

That agent needs factual information.

What does the system do?

What protocols does it support?

What limitations exist?

What deployment options are available?

What evidence supports the claims?

This is exactly the type of knowledge AISO encourages organisations to publish.

Today's AI-readable content may therefore become tomorrow's agent-readable commercial infrastructure.

13. AISO Makes AI Visibility Measurable

For some time, one challenge with AI search was measurement.

Traditional SEO has rankings, impressions, clicks and search-console data.

AI visibility was harder to observe.

That is starting to change.

In June 2026, Google introduced dedicated Search Generative AI performance reporting in Search Console, covering visibility in experiences such as AI Overviews and AI Mode. Google subsequently announced that these insights had rolled out worldwide by August 31, 2026.

That development is important.

It signals the emergence of AI visibility as a measurable acquisition channel.

Organisations can increasingly ask:

Are we appearing?

For which subjects?

Which pages are being surfaced?

Which competitors appear?

Are descriptions accurate?

Which topics are missing?

What questions lead to us?

AISO therefore evolves from a content philosophy into something that can be tested, measured and improved.

14. AISO Improves Human Communication Too

Perhaps the most overlooked benefit of AISO is that most things that make information easier for AI also make information easier for people.

Clear headings help both.

Direct explanations help both.

Consistent terminology helps both.

Useful FAQs help both.

Definitions help both.

Evidence helps both.

Logical structure helps both.

Accurate documentation helps both.

That is why good AISO should not produce robotic writing.

Quite the opposite.

The objective is clarity without sacrificing expertise.

Google's current guidance makes a similar point: organisations should continue producing useful, original, people-first content rather than rewriting pages purely for generative systems. There is no special AI schema or secret markup required to appear in Google's generative search experiences.

Good information architecture benefits humans and machines simultaneously.

AISO Is Not a Ranking Trick

As interest in AI search grows, an industry will inevitably emerge promising shortcuts:

“Rank #1 in ChatGPT.”

“Add this file and every AI will recommend you.”

“Use this schema and dominate AI results.”

That is the wrong way to think about AISO.

No legitimate optimisation strategy can guarantee what an independent AI system will say.

AI models change.

Retrieval systems change.

Indexes change.

Sources change.

User context changes.

Different systems may produce different answers to the same question.

AISO is therefore not about controlling AI.

It is about improving the quality, clarity, accessibility and authority of the knowledge AI has available to work with.

That distinction is fundamental.

The Bigger Benefit: Becoming Part of the Knowledge Layer

The greatest benefit of AISO may ultimately be larger than traffic.

For decades, businesses built websites because the web became a primary layer through which people discovered information.

We are now building another layer on top of that web.

AI systems increasingly interpret information before humans see it.

They summarise.

Compare.

Filter.

Explain.

Recommend sources.

Answer follow-up questions.

And increasingly, help users take action.

That means organisations have a new responsibility.

It is no longer sufficient merely to publish information.

The information must be structured well enough that intelligent systems can determine what it means.

Companies that achieve this gain more than AI visibility.

They gain clearer positioning.

More accurate representation.

Stronger subject authority.

Better-qualified discovery.

Reusable knowledge.

Greater consistency.

Improved customer education.

A foundation for AI agents.

And greater resilience as search behaviour continues to evolve.

Conclusion: From Being Found to Being Understood

The first era of digital visibility was about having a website.

The second was about getting that website found through search.

The next is about ensuring that machines can understand what the organisation represents well enough to include it in the answers they construct.

That is the opportunity behind AI Search Optimization.

AISO does not replace SEO.

It extends the job.

SEO asks:

Can the information be discovered?

AISO asks:

Can the information be understood, trusted, connected to the right problem and reused accurately?

The companies that recognise this shift early will not simply optimise for another search channel.

They will build something much more valuable:

a body of knowledge that remains understandable wherever the next generation of search happens.

And in an AI-first information environment, being understood may become one of the most valuable forms of visibility a business can have.

Your AI Visibility Score May Be Wrong: A Reproducible Testing Protocol

Fri, 11 Sep 2026 20:10:27 +0000

By Jarno Saarimies, Founder of AEOvara. This is Part 3 of the series How to Build a Repeatable AI Search Visibility Benchmark.

Ask ChatGPT the same commercial question twice and you may get two different shortlists. Change “best” to “most reliable,” and the shortlist may change again. Run the prompt in a continuing conversation, in another country, or after a model update, and you may no longer be measuring the same system.

That creates an awkward problem for AI visibility reporting: a dashboard can show a precise score even when the experiment behind it is not precise.

This does not make AI visibility measurement useless. It means the score must be treated as an estimate produced by a documented test—not as an objective ranking retrieved from a fixed index.

In Parts 1 and 2 of this series, I explained how to build a prompt corpus and track mentions, citations, competitors, and answer quality. This article addresses the harder question:

When is a change in AI visibility evidence, and when is it only measurement noise?

The answer requires more than repeating prompts. You need to control the test environment, preserve the raw evidence, quantify uncertainty, and separate effects that dashboards often collapse into one number.

First, identify what actually changed

Suppose your mention rate rises from 30% to 40%. At least three different things could have produced that result.

1. The brand changed

You published new evidence, earned independent coverage, corrected an entity description, improved a relevant page, or became more widely discussed. This is the effect an AEO or GEO programme is trying to measure.

2. The engine changed

The provider released a new model snapshot, changed retrieval behaviour, refreshed an index, altered citation rules, or modified the product. OpenAI explicitly states that model outputs are variable and that prompting behaviour can change between model snapshots. For API applications, it recommends pinned model versions and evals when consistency matters.

Consumer AI products rarely give researchers complete control over those variables. A visible product name such as “ChatGPT” is not a permanent experimental condition.

3. The sample changed

The wording, session history, location, language, login state, retrieval mode, time, or number of repetitions changed. Even if the website and model stayed untouched, the measured score could move.

If your log cannot distinguish these explanations, it cannot support a causal claim such as “our optimization increased AI visibility by 10%.” It can only say that the observed answers changed.

That distinction sounds cautious. It is also what makes the result credible.

A prompt is not a keyword

Traditional rank tracking usually observes a defined query, location, device, and search engine. AI prompts carry more semantic degrees of freedom.

Consider these questions:

What are the best technical SEO consultancies for a Finnish SME?
Which technical SEO consultancy is most reliable for a small Finnish company?
Who can help a Finnish business become visible in AI-generated answers?
Recommend an affordable Finnish specialist in SEO and AI search optimization.

They occupy the same commercial neighbourhood, but they are not interchangeable samples. “Best,” “reliable,” “affordable,” and “AI search optimization” introduce different selection criteria.

A 2026 controlled study by Jan Ehrlinspiel, Malte Landwehr, and Tomek Rudzki examined 37,804 responses across five AI answer engines. It found that prompt format and archetype can shift visibility baselines, with the clearest sensitivity appearing in unbranded, middle-funnel commercial prompts. The authors are affiliated with Peec AI, so that commercial relationship should be disclosed, but the methodological lesson is useful: one wording cannot represent an entire buyer intent.

Freezing a prompt list is therefore necessary, but not sufficient. A frozen list gives you repeatability for those exact prompts. It does not prove that the list represents the full market.

Use prompt families, not a bag of convenient questions

A stronger benchmark separates two layers:

Core prompts remain unchanged so trends can be compared over time.
Prompt variants test whether the result survives realistic changes in wording.

For each buyer intent, write one core prompt and two or three variants before checking which version favours your brand. This prevents an easy form of unconscious cherry-picking: keeping the wording that produces the most flattering result.

Buyer intent	Core prompt	Controlled variants
Category discovery	What are the best AEO agencies in Finland?	most reliable; established; suitable for SMEs
Problem solving	How can a Finnish SME improve visibility in AI answers?	get cited by ChatGPT; appear in AI search; improve generative search visibility
Supplier selection	Who should I hire for an AI visibility audit in Finland?	independent specialist; consultancy; local expert

Do not average branded questions such as “What is AEOvara?” into the same score as unbranded discovery questions. A branded prompt measures recognition and description accuracy. An unbranded prompt measures discovery. Combining them can make a weak discovery result look healthy.

Record the test environment like an experiment

Every observation should include enough metadata for another person to understand what was tested:

exact prompt text;
platform and visible product mode;
model identifier, when exposed;
web search or grounding status, when exposed;
date, time, language, and country;
signed-in or signed-out state;
clean session or continuing conversation;
personalization or memory state, when known;
repetition number;
full answer and cited URLs;
scorer name or scoring-rule version.

“ChatGPT, September” is not adequate provenance. Neither is a cropped screenshot that hides the prompt, date, citations, and product mode.

API-based monitoring improves control, but it creates a different test. An API model with a pinned snapshot and explicit search configuration is not necessarily equivalent to the consumer interface used by customers. Report API observations as API observations. Do not quietly label them “what users see in ChatGPT.”

Measure a rate—and show its uncertainty

If a brand appears in 3 of 5 runs, the observed mention rate is 60%. That does not mean the true probability of a mention is known to be 60%.

With only five binary observations, a 95% Wilson confidence interval is approximately 23% to 88%. The interval is wide because the sample is small.

If the brand appears in 30 of 50 comparable runs, the observed rate is still 60%, but the corresponding interval narrows to approximately 46% to 72%. More observations have not changed the headline percentage; they have changed how much confidence we should place in it.

For a binary mention metric:

mention rate = mentions / comparable runs

Report the numerator and denominator—not just the percentage:

ChatGPT web search: 12/20 mentions, 60%
95% Wilson interval: approximately 39%–78%

The interval is not decoration. It helps prevent claims that the evidence cannot support.

If period A is 6/20 and period B is 8/20, the dashboard has moved from 30% to 40%. But with samples that small, the difference may be ordinary variation. Call it an observed increase, not a confirmed improvement.

Do not use one noise budget for every metric

Mention, citation, prominence, sentiment, and factual accuracy behave differently.

Mention is binary and relatively easy to score.
Citation requires a link or source reference and should be stored at URL level.
Prominence depends on an explicit rule: first named, top three, recommended, or merely included.
Sentiment is a classification judgement and is usually noisier.
Accuracy must be checked against a dated source of truth.

A 2026 production-data paper on GEO measurement reported that sentiment was 6.7 times noisier than mention in its dataset. That is one vendor’s observational result, not a universal constant, but it illustrates why a single blended “AI visibility score” can hide more than it reveals.

Publish the components separately. A brand can have a rising mention rate while its citation rate falls or its description becomes inaccurate. Those are materially different outcomes.

Establish a noise floor before claiming a win

Before changing the site, run the unchanged benchmark over several measurement windows. This creates a baseline for natural movement.

Then document the intervention:

page or entity changed;
exact publication time;
URLs affected;
intended prompt family;
no other known campaign, migration, or major PR event;
first date the changed page was observed or cited.

Continue measuring with the same core prompts and conditions. Compare post-change movement with pre-change variation.

This is still not a perfect causal experiment. AI engines can update during the same period, and third-party sources can change independently. But it is much stronger than editing ten pages and attributing the next dashboard increase to whichever tactic sounds most impressive.

Evidence	Defensible wording
One answer changed	“The brand appeared in this observation.”
Repeated rate increased	“Observed mention frequency increased in this prompt set.”
Increase exceeds baseline variation	“The change is larger than the noise previously observed in this test.”
Controlled intervention with comparison group	“The intervention is a plausible cause of the measured difference.”
Repeated controlled result across engines and periods	“The evidence supports a robust effect under the tested conditions.”

Avoid jumping from the first row to the last.

Build a holdout set to catch overfitting

If you optimize pages against the exact prompts used for reporting, you may improve performance on the test without improving broader buyer discovery.

Reserve 20–30% of your prompt families as a holdout set. Do not use those prompts to decide what to write or edit. Run them only at defined validation points.

If the core tracking prompts improve but the holdout prompts do not, you may have optimized to the benchmark rather than the market. This is the AI-search equivalent of teaching to the test.

The holdout set should remain commercially relevant. Random prompts do not create scientific rigour; they only create irrelevant data.

Publish the method, including its limitations

E-E-A-T is not a numeric score that can be added with an author box or a block of schema. For readers—and for systems trying to evaluate a source—trust is easier to establish when claims have visible provenance.

A credible public benchmark should state:

who ran the test;
what was measured;
the exact period and platforms;
how prompts were selected;
how many observations were collected;
how answers were scored;
whether the evaluator had a commercial interest;
what changed since the previous version;
what the data cannot prove.

That is the approach used in the continuously updated AEOvara AI Visibility Benchmark Suomi 2026: the platform-level results, prompt scope, cadence, and limitations are part of the evidence, not hidden behind a proprietary score.

Publishing an unfavourable or inconclusive result can strengthen the work. A benchmark that only produces success stories looks like marketing. A benchmark that preserves negative findings begins to look like a useful dataset.

A minimum viable reproducibility checklist

Before publishing the next percentage, ask:

Are branded and unbranded prompts reported separately?
Were prompts written before seeing which ones favoured the brand?
Are the exact wording and realistic variants preserved?
Were runs made in clean, comparable sessions?
Are platform, model, retrieval mode, location, and date recorded?
Does every percentage show its numerator and denominator?
Is uncertainty visible when the sample is small?
Are mentions, citations, prominence, sentiment, and accuracy separate?
Was a pre-change noise floor established?
Is there a holdout prompt set?
Are raw answers and cited URLs archived?
Are limitations and commercial relationships disclosed?

If several answers are “no,” the result may still be useful as an observation. It should not be presented as a stable market measurement.

The bottom line

AI visibility is measurable, but not as a single universal rank.

What you can measure is a defined brand’s behaviour across a documented sample of prompts, engines, configurations, places, and times. Repeat that protocol and you can build evidence. Hide those conditions behind a polished score and you create false precision.

The strongest AI-search report is not the one with the most decimal places. It is the one another practitioner could challenge, reproduce, and learn from.

That is also the kind of source worth citing.

FAQ

How many times should I run each AI-search prompt?

There is no universal number. Three to five repetitions can expose obvious variability and provide a directional baseline, but a small sample does not produce a precise probability. Report the raw count and an uncertainty interval, then increase repetitions for important or volatile prompt families.

Should I freeze my prompts or update them?

Do both in separate layers. Keep a stable core set for trend comparison, and maintain a versioned discovery set that reflects new buyer language, products, and competitors. Never silently replace old prompts and continue the same trend line.

Can I compare an API result with the consumer AI product?

Only with an explicit caveat. The API may use a different model snapshot, system configuration, search policy, location input, or citation interface. Treat it as a separate measurement surface unless equivalence has been demonstrated.

Is a higher mention rate proof that my content change worked?

No. It is evidence that the observed rate changed. A causal claim requires stronger controls: stable test conditions, a pre-change noise floor, documented timing, enough observations, and preferably a comparison or holdout group.

Does a citation mean the AI answer used my page correctly?

Not necessarily. Store and inspect the cited URL, the claim it appears to support, and whether the answer accurately represents the source. Citation presence and citation correctness are separate metrics.

Sources and further reading

OpenAI, API backwards compatibility and model variability.
Ehrlinspiel, Landwehr & Rudzki, Prompt Tracking Works, But Not as a One-Prompt Measurement System, 2026.
Blago, Generative Engine Optimization at Scale: Measuring Brand Visibility Across AI Search Engines, 2026. Treat the vendor-operated production dataset and its generalizability accordingly.
Aggarwal et al., GEO: Generative Engine Optimization, KDD 2024.

About the author: Jarno Saarimies is the founder of AEOvara, a Finnish consultancy focused on technical SEO, Answer Engine Optimization, Generative Engine Optimization, and reproducible AI-search visibility measurement. His work emphasizes documented methods, source verification, and claims that remain useful after the hype cycle moves on.

AEO for Finnish SMEs: A Practical 2026 Guide to Getting Cited by AI

Thu, 10 Sep 2026 10:07:28 +0000

Search has changed. Quietly, rapidly, and permanently.

For years, businesses focused on climbing Google rankings. But in 2026, the game is different. Search engines, AI assistants, voice devices, and smart summaries increasingly deliver direct answers instead of lists of websites.

That means Finnish small and medium-sized enterprises must adapt—or risk becoming invisible.

This is where Answer Engine Optimization (AEO) comes in. AEO helps your business become the answer users see first. Not just another blue link. Not page seven. Not forgotten.

For Finnish SMEs, that shift is massive.

What is Answer Engine Optimization?

AEO stands for Answer Engine Optimization. It is the process of making your website, content, authority signals, and technical data easy for search engines and AI systems to understand, trust, and cite.

Traditional SEO asks:

How do we rank first?

AEO adds a sharper question:

How do we become the recommended answer?

The two disciplines work together. SEO helps people and crawlers discover your content. AEO helps answer engines confidently extract and reuse the right part of it.

Why Finnish SMEs need AEO in 2026

Classic SEO still matters, but rankings alone no longer guarantee attention. AI-powered search experiences increasingly summarize information before a user visits a website. They favour businesses that communicate with clarity, demonstrate expertise, and provide structured, verifiable information.

For an SME, this can translate into:

More appearances in AI summaries and answer boxes
Better-qualified leads with stronger buying intent
Improved visibility for local and city-based searches
Greater trust through transparent expertise, reviews, and business information
Less dependence on paid advertising

In plain English: when someone asks an assistant for a provider, price range, comparison, or next step, you want your business to be easy to recommend.

The shift from rankings to answers

Being number one is useful. Being cited may be even more valuable.

A page can rank well and still fail to answer the visitor's question quickly. Another page with clearer definitions, direct answers, useful examples, strong authorship, and structured data may be easier for an answer engine to use.

This is good news for smaller businesses. You do not need the biggest marketing budget to produce the clearest, most credible answer.

At AEOvara, I approach AEO as a practical visibility discipline: remove ambiguity, show real expertise, and make important facts machine-readable without making the content sound robotic.

Start with real customer questions

The best AEO content usually starts in conversations, not keyword tools.

Listen to the questions prospects ask before buying:

How much does an accountant cost for a limited company in Finland?
When should I outsource payroll?
Which web agency is suitable for a small business in Lappeenranta?
What is included in a technical SEO audit?
How does Finnish VAT work for a new company?
Is service A better than service B for my situation?

These questions reveal intent. They also give you natural headings and concise answers that search engines and AI systems can understand.

Useful question patterns include how much, best, how to, near me, what is, compare, why choose, and when should I.

Answer the question immediately, then add context, evidence, exceptions, and a clear next step.

Build topic authority, not a pile of random posts

One strong page is helpful. A connected group of genuinely useful pages is much stronger.

Imagine an accounting firm. Its main service page could link to focused resources about:

VAT in Finland
Payroll outsourcing
Limited-company taxation
Accounting prices
Changing accountants

Together, these pages form a topic hub. Internal links clarify how the subjects relate, while consistent authorship and business information reinforce the entity behind the advice.

The goal is not to manufacture dozens of thin articles. It is to cover the decisions your customer actually needs to make.

Use structured data with purpose

Schema markup gives machines explicit clues about your organisation and content. It can clarify who you are, what you offer, where you operate, who wrote the page, and how different pages relate.

Useful schema types for Finnish SMEs often include:

LocalBusiness
Organization
Service
FAQPage
Product
Review
Article
Person
BreadcrumbList

Structured data is not a magic ranking button, and it should never describe information the visitor cannot see. Think of it as a clean data layer that supports the page's visible claims.

For example, an article about a specialist topic becomes more trustworthy when the page clearly identifies the author, links that author to a credible profile, shows a publication date, and accurately marks those facts in Article and Person schema.

Win the local answer

Local AEO matters because many searches carry immediate commercial intent:

accountant near me
photographer in Tampere
construction company in Espoo
SEO consultant in Finland

Create dedicated location pages only when you can make them genuinely useful. A strong local page includes specific services, local examples, customer stories, practical contact information, testimonials, and clear reasons the service fits people in that area.

Avoid duplicating the same text and swapping only the city name. That creates pages for algorithms rather than people—and neither audience is likely to be impressed.

Your Google Business Profile matters too. Keep categories, services, opening hours, photos, reviews, and answers accurate. Consistent business information across your site and trusted profiles helps systems connect the dots.

Publish content formats that answer buying questions

Blog posts have their place, but many buying decisions happen on other page types.

FAQ blocks

Put a short answer first. Follow it with nuance, examples, or conditions. Do not hide every important answer behind an accordion if the content becomes difficult to access.

Comparison pages

A fair comparison earns trust. Explain who each option is for, where the trade-offs are, and when your own service is not the best fit.

Pricing pages

You do not always need a fixed price. A starting price, typical range, package structure, or list of cost drivers is far more useful than “contact us for a quote.”

Step-by-step guides

Use numbered steps, descriptive headings, checklists, and concrete examples. Make each step understandable even when an answer engine extracts it from the wider article.

Think multilingual from the start

Many Finnish businesses serve customers in Finnish and English, while Swedish may also be commercially important.

Do not rely on literal translation alone. Search behaviour, vocabulary, examples, and customer expectations vary by language. Each version should sound natural, answer the local audience's questions, and use the correct language signals and internal links.

A useful English page can also improve discoverability among international founders, visitors, and companies looking for Finnish expertise.

Get the technical foundations right

Excellent content cannot do its job if a site is slow, confusing, or difficult to crawl.

Check that your website:

Uses HTTPS
Works properly on mobile
Loads quickly and remains visually stable
Has clear navigation and internal links
Avoids broken pages and redirect chains
Provides descriptive page titles and headings
Includes crawlable text rather than placing essential information only inside images
Uses canonical URLs consistently

Technical quality supports trust. It also reduces the risk that search and AI systems miss or misunderstand your best material.

Demonstrate experience and trust

E-E-A-T is not a badge you add to the footer. It is the cumulative impression created by experience, expertise, authority, and trustworthiness.

Show who wrote the content and why they are qualified. Use real names, useful author profiles, transparent company details, and references where a claim needs support. Keep old advice updated.

Reviews are more helpful when they mention the service, result, location, or experience rather than offering a vague “great company.” Case studies become stronger when they explain the challenge, strategy, timeline, measurable outcome, and business context.

Specificity is evidence.

A practical 30-day AEO plan

Week 1: Find the gaps

Audit your most important service pages. List the questions customers ask, check whether the pages answer them directly, and improve unclear headings.

Week 2: Fix the technical layer

Review mobile usability, performance, crawlability, canonical URLs, internal links, and relevant schema markup.

Week 3: Strengthen commercial content

Add useful pricing information, comparisons, FAQs, author details, reviews, and evidence. Turn vague claims into concrete facts.

Week 4: Expand and measure

Improve important local or language-specific pages. Track impressions, qualified visits, conversions, branded searches, referrals, and appearances in AI answers for a repeatable set of prompts.

Do not treat one ChatGPT query as a scientific benchmark. Models, personalisation, wording, and live retrieval can change the result. Use a consistent prompt set and look for trends over time.

Common AEO mistakes

Several shortcuts cause more trouble than they solve:

Publishing thin pages for every keyword variation
Duplicating city pages
Hiding all pricing information
Ignoring mobile performance
Producing only top-of-funnel blog posts
Adding unsupported superlatives such as “the best”
Using schema that does not match visible content
Writing for machines until humans stop enjoying the page

The fix is refreshingly unglamorous: be clear, accurate, specific, and helpful.

The takeaway

AEO is not tomorrow's tactic. It is today's competitive edge.

The Finnish SMEs that win in 2026 will not simply rank. They will be selected, cited, trusted, and chosen. That requires better answers, stronger trust signals, smarter structure, and content built around real customer needs.

Customers rarely want ten links. They want one clear answer.

Make sure it can be yours.

If you want to see how I apply these ideas in practice, explore the AEOvara expert profile and methodology.

Frequently asked questions

Is AEO replacing SEO completely?

No. AEO builds on SEO. Technical discoverability and rankings remain important, while answer-focused structure helps AI systems understand and cite the content.

Can a small Finnish business compete with larger brands?

Yes. Smaller businesses can win specific questions through stronger local relevance, clearer expertise, first-hand evidence, and better answers.

How quickly can AEO produce results?

Some improvements can appear within weeks, especially for local or question-based searches, but durable visibility requires consistent measurement and refinement.

Does every Finnish SME need multilingual content?

No. Add languages when they match real customers. Finnish and English are a sensible combination for many firms; Swedish matters in relevant markets and regions.

What is the best first step?

Audit your main service pages. Add direct answers to genuine customer questions, clearer pricing or cost drivers, trustworthy authorship, and evidence that supports your claims.

About the author

I'm Jarno S, founder of AEOvara in Finland. I work hands-on with technical SEO, Answer Engine Optimization, Generative Engine Optimization, structured data, and AI-search visibility. My focus is simple: help businesses become easier for people to trust and easier for search and answer engines to understand.

AI Search Visibility Is Finally Measurable: A Developer’s Field Guide for 2026

Thu, 10 Sep 2026 09:43:10 +0000

If you have ever tried to measure whether ChatGPT, Gemini, Copilot, or an AI-powered search result “knows” a brand, you have probably discovered the technical term for the experience: a mess.

Traditional search gave us rankings, impressions, clicks, and a fairly tidy funnel. AI answers broke that tidy funnel into pieces. A brand can be mentioned without a link, cited without a click, or used as background evidence while another source gets the visible citation.

The good news is that this is no longer completely invisible.

In 2026, Google and Bing are giving site owners more control and more reporting around generative search. That does not make AI visibility easy, but it does make it measurable enough to stop arguing from screenshots and start building a repeatable benchmark.

I’m Jarno S., founder of AEOvara, a Finnish consultancy focused on Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), and LLM visibility. I have been testing how content is discovered, interpreted, and recommended by AI systems since 2022. Here is the practical framework I use when I want evidence instead of vibes.

The short answer

AI search visibility is the measurable presence of a brand, person, product, or URL inside AI-generated answers. Track it with a fixed set of prompts, citation data from search platforms, referral analytics, and page-level content checks. Measure mentions and citations separately, because they are not the same thing.

If you only remember one formula from this article, use this:

AI visibility = mention share + citation share + answer accuracy + qualified actions

No single tool gives you the whole picture. Your job is to combine several imperfect signals into one useful trend.

Why the old SEO dashboard is not enough

Imagine someone asks an answer engine:

What is the best deployment platform for a small TypeScript team?

The answer may mention five platforms, cite three pages, and send zero clicks. One company might be named first but not cited. Another might supply the benchmark data. A third might get the only click because its title promises a useful comparison.

A normal rank tracker sees almost none of that.

This is why “we rank number three” is becoming an incomplete sentence. Number three where? In a blue-link result, an AI Overview, an AI Mode follow-up, a Copilot answer, or a model response generated without live web retrieval?

Classic SEO still matters. Google’s own guidance says that the same foundations remain relevant for its AI features: crawlability, useful content, internal links, page experience, and accurate structured data. There is no magic AI-only meta tag that turns average content into a trusted source.

What has changed is the output you are optimizing for. You are no longer chasing only a position. You are trying to become a source an answer system can confidently retrieve, understand, and cite.

The four signals worth tracking

Mention share answers: How often is my brand included when the model discusses this topic?

Build a stable prompt set around real user intentions. For example, a developer-tool company might test:

Recommend CI tools for a five-person Node.js team.
Compare hosted error-monitoring platforms for a Next.js app.
What should I use to document a public REST API?
Which tools are good alternatives to [known competitor]?

Run the same prompts on a schedule. Record which brands appear, their order, the wording around them, and whether the answer expresses confidence or caution.

Do not change half the prompt set every week. A benchmark that moves with your mood is not a benchmark.

Citation share answers: How often does the system visibly reference my domain?

This is stricter than mention share. A model may know your company name from many sources while citing a review, a documentation page, or a community thread instead of your website.

Bing Webmaster Tools now has an AI Performance report for citations across Microsoft Copilot, Bing’s AI-generated summaries, and selected partner experiences. It includes cited pages and the grounding queries associated with them. That is useful because it connects the answer back to both a URL and an intent.

For Google, check the generative AI reporting and controls available in Search Console for your property, then compare the trend with ordinary Search performance. The important part is not whether the numbers from different platforms match. They will not. The important part is whether each platform’s own trend improves over time.

3. Answer accuracy

Visibility is not automatically good news.

If an assistant calls your open-source library abandoned, invents a pricing tier, or confuses your product with another company, you have an entity problem. Track factual accuracy as a first-class metric:

{
  "prompt_id": "alternatives-07",
  "brand_mentioned": true,
  "brand_cited": false,
  "facts_correct": 3,
  "facts_checked": 5,
  "accuracy": 0.6,
  "notes": "Old pricing and wrong framework support"
}

This small bit of structure turns “the answer looked weird” into something your team can investigate.

4. Qualified actions

Eventually, visibility has to do something useful.

Track referrals from AI and answer platforms in analytics, but do not stop there. Look at what those visitors do: documentation views, demo requests, sign-ups, package installs, newsletter subscriptions, or whatever matters for your product.

AI referrals are often low-volume and high-intent. Ten visitors who arrive with a specific implementation problem can be more valuable than a thousand accidental impressions.

Build a prompt benchmark like a test suite

Developers already have the right mental model for this. Treat your AI visibility benchmark like a regression suite.

Start with 30 to 50 prompts. Group them by intent:

Discovery: “What tools solve X?”
Comparison: “X vs Y for this use case”
Validation: “Is X reliable or secure?”
Implementation: “How do I do X?”
Troubleshooting: “Why does X fail when Y?”

Then add three levels of specificity:

broad category prompts;
use-case prompts;
prompts that include constraints such as team size, language, budget, or region.

Run the suite from a clean context. Store the date, platform, model or mode when visible, prompt, answer, citations, and result classification. Do not compare a logged-in personalized result with an anonymous result and pretend they are equivalent.

A simple schema is enough:

CREATE TABLE ai_visibility_runs (
  run_date DATE,
  engine TEXT,
  prompt_id TEXT,
  brand_mentioned BOOLEAN,
  cited_urls JSON,
  mention_position INTEGER,
  accuracy_score DECIMAL(3,2),
  answer_hash TEXT
);

The answer hash helps identify repeated answers without storing endless duplicate text. Keep the original answer where your policies allow it, because qualitative changes often explain the numbers.

Make pages easy to quote, not merely easy to crawl

Technical access is the entry ticket. Citation-worthy content is the performance.

An answer engine needs passages that survive being lifted out of context. Give important pages:

one clear topic and intent;
a concise definition near the top;
descriptive headings that resemble real questions;
factual claims supported by primary sources;
named authors with relevant experience;
visible publication and update dates;
examples, limitations, and edge cases;
consistent facts across your website and public profiles.

That last point is easy to underestimate. If your homepage says the product supports ten integrations, the docs list eight, and an old directory lists six, the model has to choose among conflicting facts. Consistency is an optimization tactic.

Use structured data where it accurately describes visible content, but do not turn schema into fan fiction. Marking every author as an award-winning global expert does not manufacture expertise. It manufactures a debugging session for whoever inherits the site.

E-E-A-T is mostly a publishing discipline

Experience, expertise, authoritativeness, and trust are often discussed as if they were four secret ranking switches. A more useful way to think about E-E-A-T is as a publishing checklist.

Can a reader tell who wrote the page? Does the author have relevant first-hand experience? Are claims supported? Can someone verify the organization behind the advice? Is the content maintained? Are commercial interests obvious?

At AEOvara, my practical rule is simple: make the evidence visible. Do not merely say that you know a topic. Show the test, the decision, the result, and what did not work.

That principle helped shape the methodology I now use professionally. I first applied it while building and growing my own website: better semantic structure, direct answers, entity consistency, and deliberate internal linking. The work produced real search growth and became a testing ground for AEOvara’s approach. You can read more about my background and the case study on my AEO and AI-search expert page.

First-hand detail is also pleasantly hard to commoditize. Anyone can publish “ten GEO tips.” Only you can explain why your caching strategy failed on Friday, which query exposed the problem, and what the graph looked like after the fix.

What about llms.txt?

Treat llms.txt as an experiment, not a visibility button.

It may become a useful convention for pointing AI systems toward important resources. It does not replace crawlable pages, strong information architecture, sitemaps, robots directives, or good documentation. If you add one, keep it accurate and small. Then measure whether supported crawlers actually request it.

The same rule applies to every fashionable AEO tactic: if it cannot be tied to a plausible retrieval mechanism and a measurable outcome, it belongs in the experiment column, not the strategy column.

A 30-day implementation plan

Week 1: Establish the baseline

Choose your engines, define 30 to 50 prompts, and record mentions, citations, accuracy, and referral traffic. Export current data from Google Search Console, Bing Webmaster Tools, and analytics.

Week 2: Fix identity and access

Check crawlability, canonical URLs, robots rules, sitemaps, JavaScript rendering, author pages, organization details, and conflicting brand facts. Make sure your best content is reachable through normal internal links.

Week 3: Upgrade five source pages

Pick pages that already have impressions, backlinks, citations, or qualified traffic. Improve the direct answer, evidence, headings, examples, authorship, update date, and internal links. Five serious upgrades usually teach you more than fifty synthetic articles.

Week 4: Re-run and annotate

Run the same benchmark again. Annotate changes by URL and date. Look for direction, not miracles. AI answers are probabilistic, so one missing mention is noise; a repeated decline across related prompts is a signal.

Common mistakes I would avoid

Counting every brand mention as a win. A recommendation, a neutral mention, and a warning are different outcomes.

Publishing generic FAQ spam. Good answer formatting helps. Empty answers written only to occupy query space do not.

Changing content without logging the change. If visibility rises, you need to know what might have caused it.

Trusting one model run. Sample repeatedly and compare trends.

Ignoring the pages that models already cite. Those URLs are telling you what the system considers useful. Study their format and strengthen adjacent coverage.

Measuring only clicks. Zero-click visibility can influence later branded searches, direct visits, and purchase decisions.

Frequently asked questions

Is AEO different from SEO?

Yes, but they overlap heavily. SEO improves discovery and performance in search systems. AEO focuses on making content suitable for direct answers, citations, and recommendations. Strong technical SEO and people-first content remain the foundation.

Can you guarantee that an AI engine will cite a page?

No. Anyone who promises a guaranteed citation is selling certainty that the systems do not provide. You can improve eligibility, clarity, authority signals, and evidence; the final answer remains query- and system-dependent.

How often should an AI visibility benchmark run?

Monthly is a sensible starting point for most teams. Weekly runs can help during a migration or focused experiment, but daily testing often creates more noise than insight.

The useful conclusion

AI search optimization is becoming less mystical because the measurement layer is finally catching up.

You do not need to predict every model. Build a stable prompt benchmark. Separate mentions from citations. Score factual accuracy. Watch qualified actions. Improve the pages that already show signs of trust. Then repeat.

That is not a hack. It is an engineering loop — and it is much more reliable than hoping an AI chatbot says something nice about your brand.

About me: I’m Jarno S., founder of AEOvara. I specialize in AEO, GEO, AI SEO, and LLM visibility, and I’ve been testing AI-search content optimization hands-on since 2022.

llms.txt Explained: What It Is, Who Uses It, and How to Add It to Next.js

Mon, 24 Aug 2026 04:06:47 +0000

You've probably seen a stray llms.txt link in someone's site footer, or noticed a new file sitting next to robots.txt and sitemap.xml on a docs site you visited. Maybe you've even been told "you need this or ChatGPT won't recommend your site." Before you spend an afternoon building one, it's worth asking the boring-but-important question nobody answers clearly: does anything actually read it?

The honest answer is more nuanced than the hype suggests — and also more nuanced than the dismissals. llms.txt is real, it has a real spec, and real companies use it. It's also not a magic AI-SEO switch, and it isn't officially supported by the major search engines or model providers the way robots.txt is.

By the end of this guide, you'll know exactly what llms.txt is, what it isn't, who actually fetches it today, and — if you decide it's worth it — how to add one to a Next.js 16 App Router site in a few minutes.

Why This Is Confusing

llms.txt gets compared to robots.txt constantly, which is exactly why people misunderstand it. robots.txt is a decades-old, genuinely standardized protocol that tells crawlers what they're allowed to request — if you haven't set yours up yet, our Google Search Console setup guide covers robots.ts and sitemap.ts from scratch. llms.txt looks similar — a plain text file at your site's root — but it does something completely different: it's a curated, human-and-LLM-readable summary of your site's most important content, meant to be read on demand when someone (or their AI assistant) is actively trying to understand your project.

It's also less than two years old, was proposed by one person, and isn't controlled by any standards body. That's not a knock on it — it just means "should I add this?" deserves a more grounded answer than "yes, everyone's doing it."

What Is llms.txt, Exactly?

llms.txt is a plain Markdown file you publish at https://yoursite.com/llms.txt. It was proposed on September 3, 2024 by Jeremy Howard of Answer.AI (the team behind fast.ai and FastHTML), as a way to solve a specific problem: large language models have limited context windows, and a full HTML page — full of navigation bars, ads, and JavaScript — is a wasteful, imprecise way to hand a model information about your site.

The idea is to give models a shortcut: one concise file, in a format they already parse well (Markdown), that says "here's what this site is, and here's where to find more detail if you need it."

Your Website

├── robots.txt
│      ↓
│   Search Crawlers

├── sitemap.xml
│      ↓
│   Index Discovery

└── llms.txt
       ↓
 AI Coding Agents

💡 Tip: llms.txt is a community-maintained specification, not a ratified web standard like HTTP or robots.txt's RFC. It's hosted and documented at llmstxt.org, with a public GitHub repo where people can propose changes.

The Required Format

The spec is intentionally strict about structure so both humans and simple parsers can read it reliably. A valid llms.txt file contains these sections, in this order:

An optional byte-order mark
An H1 with your project or site name — this is the only required section
A blockquote with a short summary containing the key facts someone needs to understand the rest of the file
Zero or more plain paragraphs or lists with more context (no headings allowed here)
Zero or more H2-delimited sections, each containing a Markdown list of links — these are your "file lists" pointing to more detailed pages

Here's the minimal shape:

# Project Name

> One or two sentences summarizing what this is and why it matters.

Optional extra context or notes go here — things like "this API isn't
compatible with X" or "written for developers who already know Y."

## Docs

- [Getting Started](https://example.com/docs/start.md): Setup and first steps
- [API Reference](https://example.com/docs/api.md): Full endpoint reference

## Optional

- [Changelog](https://example.com/changelog.md): Full version history

What's happening here: the H1 and blockquote are the only parts a model must be able to rely on — everything else is there to help it decide what to fetch next. That ## Optional section has special meaning in the spec: it's explicitly for secondary material that can be skipped if a model needs to save context space. Anything genuinely optional (a full changelog, an old migration guide) belongs there instead of in your main sections.

⚠️ Common Mistake: Treating llms.txt like robots.txt and trying to write "allow" or "disallow" rules into it. It has no access-control syntax at all — it's purely informational. If you want to control what AI crawlers can fetch, that's still robots.txt's job.

The Companion Idea: `.md` Versions of Your Pages

The original proposal also suggests something separate but related: serving a clean Markdown version of any page at the exact same URL, with .md appended. So example.com/docs/routing would also be reachable at example.com/docs/routing.md — the same content, minus the nav bar, ads, and JS chrome. This is optional, and most sites that adopt llms.txt skip it, but it's the other half of the same idea: give models plain text instead of forcing them to parse a full rendered page.

llms.txt vs robots.txt vs sitemap.xml

This is the comparison that actually matters, because each file solves a different problem:

File	Purpose	Who reads it	Format
`robots.txt`	Tells crawlers what they're allowed to request	Search engine and AI crawlers, generally respected	Simple directive syntax
`sitemap.xml`	Lists every indexable URL on your site, for discovery	Search engine crawlers	XML
`llms.txt`	A curated, concise summary of your most important content	Coding agents, some chatbots, on-demand — inconsistently	Markdown

The llms.txt spec itself is upfront about this distinction: it's designed to complement robots.txt and sitemap.xml, not replace either. A sitemap is exhaustive and built for indexing; llms.txt is deliberately small and curated, and it's meant to be pulled in at inference time — when someone's actually asking a question — rather than during a training run or a full crawl.

Does Anyone Actually Read It? (The Honest Answer)

This is the part most articles either oversell or dismiss entirely, so let's be precise.

What's confirmed:

Coding-focused AI tools — Cursor, GitHub Copilot, Windsurf, Claude Code, and similar IDE agents — do fetch llms.txt (and often llms-full.txt) when they're pointed at a documentation site or a library's docs, as part of pulling in relevant context before writing code.
Companies that ship developer tools — Anthropic, Stripe, Cloudflare, Vercel, Supabase, Mintlify, and others — publish one, largely for exactly that audience: developers and their AI coding assistants.

What's not confirmed:

Google has not stated that any of its crawlers use llms.txt to inform Search or AI Overviews. When asked directly why a site's llms.txt wasn't showing up in crawl logs, Google's John Mueller responded that no AI crawler has publicly confirmed that it extracts information via llms.txt.
A large-scale study covering roughly 300,000 domains (SE Ranking, late 2025) found adoption sitting around 10% of sites — modest growth after well over a year of industry conversation.
Search Engine Land reported that in a small sample of sites that added llms.txt, most saw no measurable change in AI referral traffic afterward.

So the realistic picture in 2026: llms.txt is a genuinely useful convention for developer-facing content consumed by coding agents and AI-assisted IDEs — but it is not a confirmed input to ChatGPT Search, Google AI Mode, or Perplexity's general web answers, and there's no solid evidence yet that adding one moves the needle on general AI citations or search rankings.

💡 Tip: Treat llms.txt the way you'd treat any unofficial-but-plausible SEO tactic: cheap to try, worth doing if it fits your site, but not something to obsess over or expect measurable ranking gains from.

Should Your Next.js Site Have One?

It depends entirely on what your site is:

You run a docs site, an SDK, an open-source library, or a developer tool (like DevStacked's tools and guides): yes, worth it. Your actual audience includes other developers whose coding assistants will genuinely benefit from a clean, curated summary — this is the use case the spec was built for.
You run a general blog, marketing site, or e-commerce store: lower priority. There's no confirmed benefit yet for general-purpose AI search visibility, and your time is probably better spent on the fundamentals — structured data, internal linking, and content depth — which are confirmed to matter for both traditional SEO and AI citations. See the complete technical SEO checklist for where to focus instead, and the JSON-LD Generator for structured data that's actually proven to affect rich results.
Either way: it costs almost nothing to add, doesn't conflict with anything else on your site, and gives you a clean, canonical "here's what this is" file you can point people (and their tools) to directly.

When You Probably Don't Need One

It's worth being just as direct about when to skip this. Adding llms.txt isn't harmful, but it isn't free either — it's one more file to keep accurate, and a stale or careless one is arguably worse than none at all. Skip it (for now) if:

You're pre-launch or pre-traffic. A curated summary file is only useful once there's something worth curating. Get your core pages, metadata, and content live first — see how to add metadata in Next.js 16 if that part isn't done yet.
Your site is small and already simple to crawl. A five-page marketing site doesn't need a curation layer — a model (or a human) can already understand it from the page content and your sitemap alone.
You don't have the bandwidth to keep it accurate. An llms.txt that still lists a deprecated API or a renamed pricing plan six months later actively misleads anything that reads it. If you can't commit to updating it alongside your content, it's better left out until you can.
You're chasing it purely for "AI SEO." As covered above, there's no confirmed ranking or citation benefit yet. If that's your only motivation, your time is better spent on things with a proven payoff — structured data, canonical URLs, and Core Web Vitals, all covered in the technical SEO checklist.

💡 Tip: If you're unsure, the safest default is: build it for genuinely developer-facing content (docs, tools, APIs) where coding agents are a real audience, and skip it everywhere else until the spec's adoption picture is clearer.

Step-by-Step: Adding llms.txt to a Next.js 16 App Router Site

This guide assumes Next.js 16 with the App Router, TypeScript in strict mode, and content that changes over time (like blog posts) — so we'll generate the file dynamically instead of hand-maintaining a static one.

Step 1: Decide Static or Dynamic

If your site's content is small and stable (a handful of pages that rarely change), a plain static file is simplest.

If you have a blog or a growing set of tools/docs pages — which is the more common case — generating the file from your existing data source keeps it accurate without manual upkeep every time you publish.

We'll build the dynamic version, since it's the one that actually needs explaining. If you want the static route, skip to the callout at the end of Step 3.

Step 2: Create a Route Handler for `/llms.txt`

Next.js Route Handlers can serve any content type at any path — including a plain text file — so this is the right tool for a file that needs to be generated per-request (or cached and revalidated). If Route Handlers are new to you, our full breakdown of Route Handlers in Next.js 16 covers the route.ts convention this step relies on.

// app/llms.txt/route.ts
import { getAllPosts } from "@/lib/posts";
import { TOOLS } from "@/lib/tools-data";
import { appURL } from "@/lib/utils";

export const dynamic = "force-static"; // safe to prerender — same content for every visitor

export function GET() {
  const posts = getAllPosts();

  const docsSection = posts
    .slice(0, 25) // keep the file focused — see the note on curation below
    .map((post) => `- [${post.title}](${appURL}/blog/${post.slug}): ${post.description}`)
    .join("\n");

  const toolsSection = TOOLS.map(
    (tool) => `- [${tool.name}](${appURL}${tool.href}): ${tool.tagline}`
  ).join("\n");

  const content = `# DevStacked

> DevStacked is a developer-focused site with practical Next.js, React, Supabase,
> and Stripe implementation guides, plus a set of free browser-based developer tools.

Guides are implementation-driven, covering real architecture decisions and
production code rather than surface-level tutorials.

## Tools

${toolsSection}

## Guides

${docsSection}

## Optional

- [Full sitemap](${appURL}/sitemap.xml): Every indexable page on the site
`;

  return new Response(content, {
    headers: {
      "Content-Type": "text/plain; charset=utf-8",
    },
  });
}

What's happening here:

The route lives at app/llms.txt/route.ts — Next.js folder names can include a dot, so this maps directly to the URL /llms.txt, no rewrites needed.
export const dynamic = "force-static" tells Next.js this route's output doesn't depend on the incoming request, so it can be generated once at build time instead of on every visit — the same optimization your sitemap.ts and robots.ts files already get.
The response sets Content-Type: text/plain; charset=utf-8 instead of the default JSON or HTML content type, since llms.txt is meant to be read as plain Markdown text, not rendered.
Only the 25 most recent posts are included in the main section — see the note below on why bigger isn't better here.

⚠️ Common Mistake: Dumping your entire sitemap into llms.txt. The spec exists specifically because full-page dumps are what sitemap.xml is already for — llms.txt is supposed to be a curated shortlist. If every single page is listed, you've just built a worse, non-standard sitemap that a model has no more reason to trust than the real one.

Step 3: Verify the Output

Run your dev server and visit the route directly:

npm run dev

Then open http://localhost:3000/llms.txt in your browser. You should see plain Markdown text (not rendered HTML) — if your browser tries to download it or shows raw HTML instead, double-check the Content-Type header in Step 2.

💡 Static-site alternative: If your content doesn't change often, skip the Route Handler entirely and just drop a hand-written llms.txt file into /public/llms.txt. Anything in public/ is served as-is at the site root, so public/llms.txt becomes yoursite.com/llms.txt automatically — no route code needed. This is the simpler option for a personal site or a small marketing site with a handful of pages.

Step 4: Link to It From robots.txt (Optional, but Tidy)

Since the spec says llms.txt is meant to coexist with robots.txt, it's a reasonable place to reference it — the same way you already point to your sitemap:

// app/robots.ts
import { appURL } from "@/lib/utils";
import { MetadataRoute } from "next";

export default function robots(): MetadataRoute.Robots {
  return {
    rules: {
      userAgent: "*",
      allow: "/",
    },
    sitemap: `${appURL}/sitemap.xml`,
  };
}

There's no official field for referencing llms.txt inside robots.txt — this step is just a discoverability nicety, not part of the spec. A simple comment-style mention or a link from your footer/README works just as well.

Step 5: Keep It Curated, Not Comprehensive

The single biggest quality mistake is treating llms.txt like a dumping ground. A few concrete guidelines from the spec authors, worth following:

Use plain, unambiguous language — avoid jargon you haven't already defined
Give every linked resource a short, informative description, not just a bare link
Put genuinely secondary material (old changelogs, deprecated docs) under the ## Optional heading so it's easy for a model to skip
If your file starts feeling long, that's a sign to trim it, not add a summary section on top of it

Frequently Asked Questions

Does llms.txt help my Google rankings?

No confirmed evidence of that yet. Google's own John Mueller has said no AI crawler has confirmed using llms.txt for content extraction, and it isn't part of Google's documented Search ranking systems. Treat it as separate from your regular SEO work — Google Search Console and a solid technical SEO checklist are still where the confirmed ranking signals live.

Is llms.txt an official web standard?

No — it's a community-maintained convention proposed by Jeremy Howard of Answer.AI in September 2024, documented at llmstxt.org. There's ongoing community discussion about formalizing it further, but as of now there's no ratified standards-body specification the way there is for robots.txt.

Will ChatGPT or Perplexity actually read my llms.txt?

Not reliably, based on current evidence. The clearest, best-documented use case today is coding tools and IDE agents (Cursor, GitHub Copilot, Claude Code, and similar) fetching a project's llms.txt when a developer is working with that library. General-purpose chat search products haven't confirmed using it the same way.

Should I generate llms.txt dynamically or just write it by hand?

If your content is small and stable, hand-writing a static file in public/llms.txt is simpler and easier to review. If you have a blog or a growing tools page, generating it from the same data source your site already uses (like getAllPosts()) keeps it accurate without extra manual work every time you publish.

Can llms.txt block AI crawlers from my content?

No — it has no access-control syntax at all. It's purely descriptive. If you want to allow or block specific AI crawlers, that's still handled through robots.txt, using each crawler's documented user-agent string.

Wrapping Up

llms.txt is a real, well-specified convention — not an official standard, but not vaporware either. It has a clear, honest use case today: helping AI coding tools and IDE agents quickly understand a developer-facing site without wading through rendered HTML. For a project like a Next.js tools-and-guides site, it's a cheap, low-risk addition. What it isn't, at least as of now, is a proven lever for general AI search visibility or Google rankings — so add it because it genuinely helps your developer audience, not because someone promised it'll get you cited by ChatGPT.

If you're already generating sitemap.ts and robots.ts from your post data, adding app/llms.txt/route.ts following the same pattern takes about ten minutes — and now you know exactly what it will, and won't, actually do.

Continue Learning

Free SEO Tools

Meta Tag Generator for Next.js & HTML — generate SEO meta tags, Open Graph tags, canonical URLs, and JSON-LD in one pass.
JSON-LD Generator for Next.js & HTML — generate structured data checked live against Google's actual Rich Results requirements, not just schema.org validity.

How to Get Your SaaS Recommended by ChatGPT and AI Search [Dev Guide]

Wed, 10 Jun 2026 09:07:47 +0000

Traditional SEO is no longer the only way users discover products online.

Today, developers, founders, and buyers increasingly ask ChatGPT, Gemini, Claude, and Perplexity for recommendations instead of searching through dozens of Google results.

The challenge? Many SaaS companies have strong Google rankings but are practically invisible inside AI-generated answers.

This is where AI Search Visibility, Generative Engine Optimization (GEO), and Answer Engine Optimization (AEO) come into play.

In this guide, you'll learn how AI systems discover, evaluate, and recommend SaaS products—and what developers can do to improve their visibility.

What Is AI Search Visibility?

AI Search Visibility refers to how often your brand, product, or website appears in AI-generated responses.

For example, when someone asks:

What is the best project management software for startups?

What are the best customer support platforms with AI capabilities?

AI systems generate answers using a combination of:

Public web content
Documentation
Reviews
Third-party mentions
Knowledge bases
Structured data
Search engine results

Unlike traditional SEO, there is no "position #1" inside ChatGPT.

Instead, your goal is to become a trusted source that AI models choose to reference.

Why Traditional SEO Alone Is No Longer Enough

Many SaaS companies focus entirely on:

Keyword rankings
Backlinks
Domain authority
Organic traffic

These still matter.

However, AI systems evaluate additional signals such as:

Brand mentions
Topic authority
Entity recognition
Structured content
Documentation quality
Third-party validation

A page ranking first on Google may still never appear inside AI-generated responses.

Note

AI engines prioritize confidence and trustworthiness over simple keyword matching.

How AI Systems Discover Your Product

Most AI search platforms use a combination of retrieval systems and language models.

The simplified process looks like this:

User Question

↓

Search/Retrieval Layer

↓

Content Evaluation

↓

Source Selection

↓

Generated Answer

The better your content performs during retrieval and evaluation, the more likely it is to be included.

Step 1: Create Structured Content AI Can Understand

Large language models prefer well-organized content.

Bad example:

Everything about our software. Lots of features. Lots of benefits. Contact us.

Better example:

Features

AI-Powered Automation

Description...

Integrations

Description...

Pricing

Frequently Asked Questions

Why It Matters

Structured content helps:

Search engines
AI crawlers
Retrieval systems
Knowledge extraction pipelines

understand your website more effectively.

Step 2: Implement Schema Markup

Structured data helps machines understand entities.

Example:

{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "Example SaaS",
"applicationCategory": "BusinessApplication",
"operatingSystem": "Web"
}

Schema can improve:

Entity recognition
Knowledge graph inclusion
AI understanding

Official documentation:

https://schema.org/SoftwareApplication

Step 3: Build Strong Documentation

One surprising trend is how frequently AI systems rely on documentation.

Many SaaS companies invest heavily in blogs but neglect:

Product documentation
API references
Knowledge bases
Tutorials

Great examples include:

Stripe
Twilio
Vercel

These companies become highly visible because their content is precise, authoritative, and easy for AI systems to interpret.

Step 4: Create Content That Answers Questions

AI systems thrive on questions and answers.

Instead of publishing:

Our Platform Features

Create content like:

How does customer support automation work?
What is the best CRM for startups?
How do AI chatbots reduce ticket volume?

This format naturally aligns with how users interact with AI assistants.

Step 5: Build Entity Authority

AI models recognize entities rather than just keywords.

For example:

OpenAI
Stripe
GitHub
Atlassian

are understood as entities.

To strengthen your entity:

Maintain consistent branding
Publish expert content
Earn mentions from trusted websites
Participate in industry discussions
Build a strong knowledge base
Common Questions About AI Search Visibility
Does AI Search Replace SEO?

No.

AI visibility builds on top of SEO.

Strong SEO foundations remain essential.

Can ChatGPT Crawl My Website?

Not directly in the same way Google does.

However, AI systems may access information through:

Search engine indexes
Public datasets
Retrieval systems
Partner integrations
Do Backlinks Still Matter?

Yes.

Backlinks remain a strong trust signal.

However, contextual mentions and entity recognition are becoming increasingly important.

How Long Does It Take to Improve AI Visibility?

Most companies begin seeing measurable improvements within several months after:

Improving content structure
Expanding documentation
Increasing brand mentions
Strengthening entity authority
Best Practices Checklist

✔ Use proper heading hierarchy

✔ Implement schema markup

✔ Publish comprehensive documentation

✔ Answer real user questions

✔ Build authoritative backlinks

✔ Create topic clusters

✔ Maintain consistent branding

✔ Monitor brand mentions

✔ Optimize for both humans and machines

References

Schema.org SoftwareApplication:
https://schema.org/SoftwareApplication

Google Structured Data Documentation:
https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data

Google Search Central:
https://developers.google.com/search

Conclusion

The future of search is becoming increasingly AI-driven. While SEO remains critical, companies that ignore AI Search Visibility, GEO, and AEO risk becoming invisible in the places where users are increasingly discovering products. By creating structured content, implementing schema markup, publishing high-quality documentation, answering real user questions, and building strong entity authority, developers can significantly improve how AI systems understand and recommend their products. The organizations that adapt early will have a major advantage as AI-powered search continues to grow. Focus on creating trustworthy, structured, and authoritative content, and both search engines and AI assistants will be more likely to surface your brand.

Is Your Website Invisible to AI Search? A Developer's Checklist

Thu, 09 Apr 2026 08:52:02 +0000

I run an AI-powered test prep platform (LearnQ.ai) and a SaaS product for educational institutions (VEGA AI). When AI search engines like ChatGPT, Perplexity, and Google AI Overviews started becoming real traffic sources, I went back to basics and audited both sites for AI crawlability.
What I found surprised me. Several things that were perfectly fine for Google were actively blocking AI crawlers. This checklist is what I now run on every site before doing any AI search optimization work.

1. Check Your robots.txt for AI Crawler Blocks

Most developers set up robots.txt for Google and Bing and forget about it. AI crawlers use different user-agent strings.

Open your robots.txt file and check for blocks on these agents:

GPTBot (OpenAI)
ClaudeBot (Anthropic)
PerplexityBot
GoogleOther (used for AI training and features)
CCBot (Common Crawl, used by many LLM training pipelines)

A blanket Disallow: / on User-agent: * blocks all of them. If you added aggressive bot protection after a traffic spike or a security scare, there is a good chance you blocked AI crawlers along with the bad bots.

Fix: Add explicit Allow rules for AI crawlers you want to permit, or remove overly broad Disallow rules.

2. Create and Publish an llms.txt File

llms.txt is an emerging standard (think robots.txt but designed for LLMs). It sits at yourdomain.com/llms.txt and tells AI systems what your site is about, which pages are most important, and how the content should be used.

It is not yet universally supported, but ChatGPT, Perplexity, and several AI agents are beginning to respect it. Early adoption gives you an edge.

A basic llms.txt looks like this:

 llms.txt for proaisearch.com

> Pro AI Search is India's first AI search optimization resource.

 Key Pages
- [Home](https://proaisearch.com/)
- [GEO Guide](https://proaisearch.com/generative-engine-optimization/)
- [AEO Guide](https://proaisearch.com/answer-engine-optimization/)

Keep it simple. List your most important pages with clean descriptions.

3. Audit Your Bot Protection Settings

Cloudflare, Wordfence, Sucuri, and similar tools are aggressive by default. Check these specific settings:

Cloudflare: Under Security > Bots, check if "Block AI Scrapers and Crawlers" is enabled. This is a relatively new toggle that blocks GPTBot, ClaudeBot, and others by default when switched on.

Wordfence: Check the rate limiting rules. If you set aggressive thresholds after a brute force attack, legitimate AI crawlers hitting multiple pages during a crawl session can get auto-blocked.

Sucuri: Check the "Block All Bots" option under Security > Hardening. It does exactly what it says.

Review your server access logs if you have them. Look for 403 or 429 responses against GPTBot or ClaudeBot. Those are your AI crawlers getting turned away at the door.

4. Validate Your Schema Markup

AI engines do not just crawl text. They parse structured data to understand entities, relationships, and content type. Missing or broken schema is a silent visibility killer.

Check for these schema types depending on your site:

Organization schema on your homepage (name, URL, logo, social
profiles)
Article or BlogPosting schema on content pages
FAQPage schema on pages with Q&A content
BreadcrumbList schema for site structure signals
Person schema for author pages (critical for E-E-A-T in AI citations)

Use Google's Rich Results Test and Schema.org's validator. Fix any errors before doing anything else. AI engines rely heavily on structured data to decide whether to cite your content.

5. Check Page Rendering: Is Your Content Actually in the HTML?

If your site is JavaScript-heavy and content renders client-side, AI crawlers may be seeing blank pages. Most AI crawlers do not execute JavaScript the way Googlebot does.

Quick test: Disable JavaScript in your browser and load your key pages. If the main content disappears, AI crawlers likely see the same empty page.

Fix options:

Implement server-side rendering (SSR) or static site generation (SSG)
Use pre-rendering services for specific pages
At minimum, ensure critical content (headings, body text, key facts)
is in the initial HTML response

6. Check Canonical Tags and Indexability

This one catches people off guard. If you have:

<meta name="robots" content="noindex"> on important pages
Canonical tags pointing to a different URL
Pages blocked in robots.txt that you actually want crawled

...AI search engines will either ignore those pages or attribute the content to the wrong URL.

Run a crawl with Screaming Frog or Sitebulb. Filter for noindex pages and mismatched canonicals. Fix anything that should be crawlable and citable.

Running This Checklist

I go through these six checks in this order on any new site before touching content or link building. Technical access comes first. There is no point optimizing content that AI crawlers cannot reach in the first place.

For WordPress sites specifically, WPCode is useful for adding llms.txt content via a snippet rather than manually creating a file on the server. That is how I manage it on proaisearch.com.

If you find issues, fix robots.txt and bot protection first since those are the most common blockers. Then llms.txt, then schema, then rendering.

If you want to go deeper on any of these, I cover the full AI search optimization framework at proaisearch.com.

Amit Kumar is the founder of Pro AI Search and Growth Manager at LearnQ.ai.

Coder Legion - Recent posts tagged ai-search

SEO for 2027: A Developer Workflow for AI Search Visibility and Trust

Start with documented requirements

Separate discovery from answer quality

Make the service page a useful specification

Measure four different AI answer outcomes

Treat trust as evidence a reader can inspect

Ship one change you can evaluate

About the author

The Authority Paradox: A Practical GEO Strategy for Smaller Brands

What you will learn

GEO extends the visibility problem

What the research actually supports

Domain scores are not the whole story

Three layers a smaller brand can improve

1. Evidence: publish something that can be checked

2. Clarity: make each section answer a real question

3. Trust: connect claims to accountable people

Measure four different outcomes

A practical starting plan

The smaller-brand advantage is focus

About the author

Best AI Keyword Research Tools to Find Low-Competition Search Terms

Content Signals and RSL: Stating How AI May Use Your Content

Key takeaways

Six Steps to Make a WordPress Site Readable by AI Assistants

Key takeaways

What Is WebMCP and Why Should Website Developers Care

WebMCP #AIAgents #WebDevelopment #SoftwareEngineering #BrowserAutomation #AIIntegration #Cloudflare #Dotera

From SEO to AI Search: Jarno S’s Journey Into Making the Web More Understandable to AI

From SEO to AI Search: Jarno S’s Journey Into Making the Web More Understandable to AI

From Traditional Search to AI Search

The Question That Changed Everything

AI Visibility Should Be Measured

Think of AI Visibility Like Regression Testing

A Mention Isn't the Same as a Citation

Structured Data Helps AI Understand the Pieces

What About llms.txt?

Make Pages Easy to Quote

The AI Search Advice He Thinks Is Overhyped

What AI Search Reveals About Businesses

Building AEOvara

From AI Visibility to Repeatable Benchmarks

Lessons From Photography

Where Search Goes Next

Advice for Developers and Small Businesses

A Lesson From Building a New Category

AI Search Is an Information-Quality Challenge

What's Next for AEOvara?

About Jarno S

CoderLegion Developer Stories

For developers, llms.txt offers undeniable efficiency. For marketers, it offers zero proof. The data

Traditional SEO vs AEO/GEO: Why Smaller Brands Can Win in AI Search

The short answer

Ranking and citation are now separate layers

AI answers reduce clicks—but citations can reverse the effect

Why smaller companies can win

1. Specificity beats breadth

2. AI search reacts quickly

3. AI queries are long and narrow

Traditional SEO and AEO/GEO are complementary

Traditional SEO

AEO/GEO

A practical seven-step framework

Frequently asked questions

Can a small company really compete in AI search?

How common are AI Overviews?

How quickly can results appear?

Is a strong Google ranking enough?

Sources

About the author

From Visibility to Trust: The Business Benefits of AI Search Optimization (AISO)

From Visibility to Trust: The Business Benefits of AI Search Optimization (AISO)

1. AISO Creates Visibility Before the Website Visit

2. AISO Improves the Accuracy of How Your Business Is Represented

3. AISO Builds Authority Around Problems, Not Just Keywords

4. AISO Can Produce Better-Qualified Visitors

5. AISO Allows Specialist Companies to Compete Through Specificity

6. AISO Strengthens Brand Positioning

7. AISO Creates Consistency Across Your Digital Footprint

What About `llms.txt`?