Search and AI visibility for companies: how to be the clear, consistent answer

Search and AI visibility for companies used to mean one thing: ranking in Google. Today a growing share of people ask an AI assistant first — "what is a good tool for Shopify store operations?", "is there a service that checks visa eligibility for Türkiye?", "who runs CastLyra?" — and the assistant answers from what it has read, retrieved or been told. The company that appears in that answer, described correctly, is the company that gets considered.

We run a group of independent companies, each with its own brand and domain. That makes discoverability both easier and harder. Easier, because shared standards mean every company starts with a sound technical base. Harder, because a group of related brands can easily confuse machines: which name belongs to which product, which site is authoritative, who is the parent and who is the child.

This note explains how we think about being discoverable in search engines and AI assistants, what we actually do across Oryvelon's companies, and what we deliberately refuse to do.

Why search and AI visibility now overlap

It is tempting to treat "AI visibility" as a new discipline with new tricks. In practice, the foundations are shared.

Search engines build an understanding of entities — organisations, people, products, places — and the relationships between them. They reward pages that clearly answer a question and come from a source that appears trustworthy on that topic. AI assistants do something similar through a different route. Some answer from what was in their training data. Many now search the web at answer time, retrieve a handful of pages, and summarise them. Either way, the assistant is looking for text that states clearly what something is.

So both systems reward the same things:

• An unambiguous entity. One name, one domain, one description, used consistently.
• Crawlable, readable pages. Content that loads without heavy scripts, with sensible headings and plain HTML.
• Clear answers. Pages that say directly what a product does, who it is for and what it does not do.
• Corroboration. The same facts appearing in several places the machine already trusts.

The differences are at the edges. AI assistants seem especially sensitive to quotable, self-contained statements — a sentence that can be lifted into an answer without losing its meaning. And because they compress everything into a few lines, ambiguity costs more. If your homepage says one thing and your social profiles say another, an assistant may confidently repeat the wrong one.

Entity consistency: the foundation most companies skip

An entity is a thing a machine can recognise and keep separate from other things. For a company, entity consistency means that everywhere the company appears — its own site, its structured data, its social profiles, directories, press mentions, the parent group's site — the core facts agree.

We keep a short, fixed set of facts for each company in its source-of-truth document:

That table becomes the input for everything else: page titles, meta descriptions, the Organization markup on the company's own site, the entry on the group site, the bio on social profiles, and what we say to journalists. When the facts change, they change in the source of truth first and flow outward from there.

This sounds bureaucratic. It saves a surprising amount of trouble. A common failure in multi-brand groups is description drift: the product page says "AI assistant for merchants", the social bio says "Shopify analytics", a directory listing says "e-commerce agency", and a press article says something else again. A human might reconcile these. A machine often cannot, and it may merge, split or mislabel the entity as a result.

Names with special characters

Some of our names carry non-ASCII letters. KeşifAtlası is the obvious case. The domain is kesifatlasi.com because domains are simpler that way, but the brand name keeps its Turkish characters. We are consistent about which form appears where: the brand name with diacritics in text and markup, the ASCII form only in URLs and handles where the platform requires it. We also make sure the plain-ASCII spelling appears somewhere natural on the site, so a person or a model searching for "Kesif Atlasi" still lands in the right place.

Parent and child, stated once and clearly

The relationship between the group and its companies is a frequent source of confusion. Is WeAreMedia part of Oryvelon? Is Oryvelon an agency? Is MerchNivo a feature of something bigger?

We answer those questions explicitly, in plain text, in the places machines read. The Oryvelon site says that Oryvelon is a digital company builder, that it does not sell agency services, and that WeAreMedia is the group's services company. Each company page on oryvelon.com links to the company's own domain. The companies use a light "An Oryvelon company" endorsement rather than folding the group name into their product name. The reasoning behind that structure is in Naming, domains and brand architecture.

The goal is for an assistant asked "is Oryvelon an agency?" to find a direct, quotable sentence that answers "no", and to find it in more than one place.

Helpful content: answer the questions customers actually ask

Search engines have spent years trying to demote pages written for ranking rather than for people. AI assistants inherit a version of the same preference: when they retrieve pages to answer a question, a page that answers it directly is far more useful than one that circles around a keyword.

For us, helpful content starts from real questions. Each company keeps a running list of what prospective customers ask before buying, what they ask during onboarding and what support hears repeatedly. Those questions become pages, FAQ entries and guides.

A few examples of what this looks like in practice:

• MerchNivo gets questions like "where do the numbers in my briefing come from?" The honest answer — from the store itself, never from the model — is also the answer that builds trust. It belongs on the site in plain words. See AI explains, verified data decides.
• KeşifAtlası gets questions about specific visa routes. Its content explains how rules work and what the free test checks, and is careful to say what the product cannot do: it does not give legal advice and routes hard cases to people. See Rules engines for eligibility.
• ZodiVela answers "is this a prediction?" directly: readings are framed for reflection and entertainment. Saying so clearly is both honest and good for discoverability, because it gives assistants an accurate one-line description.

Depth beats volume

One detailed page that fully answers a question tends to outperform ten thin pages that each answer a fragment. It also ages better. We would rather publish a small number of pages we are proud of and keep them current than build a large library that nobody maintains.

This is also why these Insights articles are long. They are written to be the complete answer to a question a founder or operator might ask, not a teaser for a sales call.

Honest limits are content too

Pages that describe what a product does not do are unusually valuable. They prevent the wrong customers from signing up, reduce support load, and give AI assistants the context they need to describe a product accurately. When an assistant says "KeşifAtlası checks eligibility against a rules database but does not provide legal advice", that is a better outcome for everyone than a vaguer, more flattering summary.

No programmatic spam

Programmatic SEO — generating hundreds or thousands of pages from a template and a keyword list — is attractive because it is cheap and sometimes produces a burst of traffic. "Visa requirements for [nationality] moving to [country]" multiplied across every combination. "Best Shopify app for [niche]" across every niche. Now add a language model to write the filler and the cost per page falls close to zero.

We do not do this for any company. The reasons are practical as much as principled.

It creates risk that outlasts the traffic. Search engines explicitly target scaled, low-value content. A site that gets classified that way can lose visibility across all its pages, including the good ones.

It is usually wrong in the details. For a product like KeşifAtlası, a templated page about a specific visa route that has not been checked against the verified rules database is worse than no page. It can mislead someone making a real decision. Our principle that the AI explains and verified data decides applies to marketing pages as much as to the product.

It pollutes what AI assistants learn about you. If an assistant retrieves a thin, generic page from your site, that page becomes part of how it describes you. Mediocre pages dilute the clear description you worked to establish.

It cannot be maintained. Rules change, products change, prices change. A thousand templated pages means a thousand pages that quietly go out of date.

There is a legitimate version of structured, data-driven pages: when each page is backed by verified, specific data that genuinely differs between pages and is kept current. A store's product pages are an example. Noveniq's catalogue pages exist because each product is real, in stock or not, with its own specifications. The test we apply is simple. Would this page be useful to a person who landed on it with no other context? If the answer depends on luck, we do not publish it.

Technical foundations every company inherits

Because the group shares infrastructure, each company starts with the same technical baseline. None of it is exotic. All of it matters.

• Server-rendered or static HTML for public pages, so crawlers and AI retrieval tools see the content without executing heavy scripts.
• One canonical URL per page, with redirects from variants (with and without www, trailing slashes) handled once, at the edge.
• XML sitemaps listing only indexable pages, with honest last-modified dates.
• A robots.txt that allows reputable search and AI crawlers to read public pages, while blocking admin panels, form handlers and thank-you pages.
• Structured data for the organisation, articles, breadcrumbs and FAQs, matching what is visible on the page.
• An llms.txt file that gives AI systems a concise, curated map of the site and the most important facts.
• Fast pages with sensible images and minimal third-party scripts.

The details of the machine-readable layer — llms.txt, schema.org markup, sitemaps and what oryvelon.com publishes — are in llms.txt and structured data.

Phase-zero sites follow the same rules from day one. Even a company that is still being validated gets a clean, honest, crawlable page describing what it is, as described in Phase-zero sites. It is much easier to start consistent than to repair an inconsistent entity later.

Each company earns its own visibility

A group site could, in theory, try to rank for every query its companies care about. Oryvelon could publish pages about Shopify operations, visa eligibility, creative talent and astrology, and funnel traffic onward.

We deliberately do not. Each company earns visibility on its own domain, for its own topics. The group site ranks for what the group is: a company builder, how it works, which companies it operates. It links to each company, and it writes about the operating principles behind them, but it does not try to become a second home for each company's customers.

This follows from our view that every company should be able to stand alone. If MerchNivo's visibility depended on oryvelon.com, separating MerchNivo from the group would damage it. Search equity, like data, belongs to the company that earned it.

It also produces clearer signals. When a person searches for a Shopify operations assistant, the best result is MerchNivo's own page, written for merchants. Not a group page written for investors and partners.

Founders, authority and trust

AI assistants and search engines both pay attention to who is behind a company. Our founders, Uğur Keser and Sinem Keser, each have their own authority site: ugurkeser.art and sinemkeser.com.tr. These sites describe their work and link to the group and to relevant companies in context.

What they do not do is act as link farms. A founder's site that links to every company from every page, with keyword-rich anchor text, looks manipulative to machines and to people. We keep those links contextual: a founder writing about e-commerce operations can naturally mention MerchNivo; a page about brand and creator work can mention CastLyra. The full approach is in Founder authority sites.

Measuring visibility without fooling ourselves

AI visibility is hard to measure precisely. There is no universal report that tells you how often an assistant mentions your company. We use a mix of signals, and we are careful not to over-read any of them.

Search console data for each company's domain shows queries, impressions and clicks. It is the most reliable signal we have for traditional search.

Referral traffic from AI assistants appears in analytics when assistants link to a source and people click. It is a partial signal — many answers are read without a click — but a useful trend.

Periodic manual checks. Once a quarter, for each company, someone asks a small set of fixed questions in several AI assistants and records whether the company appears and whether the description is accurate. "What does MerchNivo do?" "Is Oryvelon an agency?" "Which service checks relocation eligibility from Türkiye?" The point is not a score. It is to catch inaccurate descriptions early, trace them back to their source, and fix the source.

Consistent campaign tagging so that traffic from our own links, newsletters and founder sites is not confused with organic discovery. See UTM standards across brands.

All of this happens per company, in each company's own analytics property, without joining users across brands. See Analytics without surveillance.

Common mistakes we see

Across many years of working on e-commerce and digital businesses, the same visibility mistakes come up again and again.

1. Different descriptions everywhere. The homepage, the social bio and the directory listing each describe a slightly different company.
2. Heavy client-side rendering for key pages. The product description only exists after JavaScript runs, so some crawlers see an empty shell.
3. Blocking AI crawlers by accident. A security plugin or a copied robots.txt blocks every non-mainstream bot, and the company then wonders why assistants describe it from outdated sources.
4. Markup that disagrees with the page. Structured data claims ratings, prices or FAQs that are not visible to visitors.
5. Thin location or variant pages. "Service in [city]" pages with nothing specific to each city.
6. No statement of what the product is not. Assistants fill the gap with guesses, often flattering and often wrong.
7. Treating the parent brand as a shortcut. Pointing every sub-brand's authority at the group site instead of building each company's own reputation.

Each of these is cheap to avoid at the start and expensive to fix later.

A practical checklist for a new company

When a new company joins the group, its visibility setup follows a short checklist.

• The source-of-truth document contains the fixed entity facts: exact name, domain, one-sentence description, category, what it is not, and the parent relationship.
• The homepage states those facts in plain text near the top of the page.
• Organization structured data on the company's own domain matches the source of truth.
• The company's page on oryvelon.com uses the same description and links to the company's domain.
• Sitemap, robots.txt and llms.txt are published and checked.
• A first set of helpful pages answers the five to ten questions prospective customers ask most.
• A search console property and a dedicated analytics property exist for the domain, owned by the company.
• Social profiles use the same name and description.
• A small set of fixed questions is recorded for the quarterly AI-assistant check.

None of it requires a large budget. It requires consistency and a willingness to write things down.

Summary

Search and AI visibility for companies rests on the same foundations: a consistent entity, helpful pages, clean technical basics and honest descriptions that machines can quote. We give every Oryvelon company a fixed set of facts in its source of truth and repeat them everywhere the company appears; we publish pages that answer real questions in depth, including what each product does not do; and we refuse programmatic spam because it trades short-lived traffic for long-lived risk and inaccurate descriptions. Each company earns visibility on its own domain, the group site explains the relationships clearly, and we measure per company without joining users across brands.

Questions and answers

What is AI visibility for a company?

AI visibility is how accurately and how often AI assistants mention and describe a company when people ask relevant questions. It depends on consistent public facts, crawlable pages and content that clearly explains what the company does.

Is optimising for AI assistants different from SEO?

Mostly not. Both reward consistent entity information, clear helpful pages, structured data and crawlable sites; AI assistants add a stronger need for unambiguous, quotable descriptions of what a company is and is not.

Does Oryvelon use programmatic SEO?

No. Oryvelon and its companies do not mass-generate thin pages targeting keyword variations. Every published page is meant to answer a real question well.

Published by Oryvelon, a digital company builder · About the group · Our companies · More in Growth, Search & Measurement

Nextllms.txt and structured data: the machine-readable layer of a company website →