# Yonaris — Public facts

Public content description. Illustrations are fictional; service scope is agreed separately.

All deployment examples on this site are fictional and are not Yonaris deployment capabilities.

## Yonaris / Yonaris
Status: public
中文来源: https://www.yonaris.com/?lang=zh
English source: https://www.yonaris.com/?lang=en

帮助企业看清 AI 如何介绍、比较和推荐自己的产品。
Helping teams understand how AI describes, compares and recommends their products.

### 我们解决的问题 / Purpose
Record: yonaris.purpose
对照产品事实、适用条件与公开证据，识别 AI 回答中的遗漏、偏差和证据缺口，明确团队下一步应完善什么。
Compare AI answers with product facts, conditions and public evidence to identify omissions, differences and evidence gaps, then clarify what teams should improve.

### 面向团队 / Audience
Record: yonaris.audience
营销、品牌、产品营销、增长和商业团队，尤其是需要解释复杂产品、比较条件或多个市场与语言的企业。
Marketing, brand, product marketing, growth and commercial teams, especially those working with complex products, buying conditions or multiple markets and languages.

### 当前产品入口 / Current product entry
Record: yonaris.current-entry
AI Visibility / AI 可见度诊断。
AI Visibility diagnosis.

### 长期方向 / Long-term direction
Record: yonaris.direction
为人和 Agent 共同参与的营销与购买决策建立基础设施。
Infrastructure for marketing and buying decisions involving both people and agents.

### Product Truth 产品事实 / Product Truth
Record: yonaris.product-truth
把产品能力、适用条件与公开依据整理在一起，作为产品介绍与 AI 回答核对的共同事实基础。这是信息组织方式，不表示独立 SaaS、API 或自动化后台已经上线。
Product Truth organizes capabilities, conditions and public evidence as a shared factual basis for product descriptions and AI-answer review. It describes how information is organized, not the availability of an independent SaaS, API or automated backend.

### 后续内容工作 / Follow-up content work
Record: yonaris.content-follow-up
网站完善、内容运营与后续观察可按需要另行约定，不默认包含在一次诊断中。
Website improvements, content work and follow-up monitoring can be scoped separately; they are not automatically included in a diagnosis.

## AI 可见度诊断 / AI Visibility
Status: public
中文来源: https://www.yonaris.com/product?lang=zh
English source: https://www.yonaris.com/product?lang=en

从实际回答出发，解释产品如何被呈现，以及团队应优先完善什么。
Start with actual answers to understand product presentation and decide what to improve first.

### 分析内容 / Analysis
Record: product.analysis
产品呈现、竞品比较、回答中的可见引用与链接、改进方向。
Product presentation, competitor comparisons, visible citations and links in answers, and improvement opportunities.

### 获得什么 / Deliverables
Record: product.deliverables
约定范围内的 AI 可见度评估、产品定位与理解差异分析、优先行动建议。
An AI visibility assessment within the agreed scope, an analysis of positioning and understanding differences, and prioritized recommendations.

### 开始方式 / Getting started
Record: product.start
确认产品、市场和客户问题；分析回答及依据；讨论发现并确定优先事项。
Agree on the product, market and buyer questions; review answers and their evidence; discuss findings and priorities.

### 观察范围 / Observation scope
Record: product.scope
每次诊断由客户问题、AI 平台、市场、语言和观察时间共同限定。
Each diagnosis is bounded by buyer questions, AI platforms, market, language and observation time.

### 证据边界 / Evidence boundary
Record: product.evidence
来源分析仅依据回答中可见的引用和链接，不代表掌握模型内部的推荐原因。
Source analysis is based on visible citations and links in answers. It does not reveal a model’s internal reasons for recommendations.

### 服务边界 / Service boundary
Record: product.follow-up
诊断包含对行动优先级的讨论；持续执行或后续复核是否包含在内，需要单独确认。
Diagnosis includes a discussion of action priorities. Ongoing execution or follow-up review requires a separate scope agreement.

### 本站演示问题 / Website illustration
Record: product.illustration
演示问题是“这款产品支持私有化部署吗？”示例资料明确支持，并要求项目开始前确认环境要求与实施范围；演示回答未明确说出部署能力。两种内容均为虚构示例。
The illustration asks: “Does this product support private deployment?” Its source explicitly supports it, with environment requirements and implementation scope to be confirmed before the project. The illustrative answer leaves the capability unclear. Both are fictional examples.

## AI 营销洞察 / AI Marketing Intelligence
Status: public
中文来源: https://www.yonaris.com/resources?lang=zh
English source: https://www.yonaris.com/resources?lang=en

围绕 AI 发现与推荐、产品理解、营销演进组织内容。
Topics about AI discovery and recommendations, product understanding and marketing evolution.

### AI 发现与推荐 / AI discovery and recommendations
Record: resources.discovery
客户向 AI 提出需求后，产品如何进入回答、比较与推荐。
How products enter answers, comparisons and recommendations after a buyer asks AI for help.

### 产品理解 / Product understanding
Record: resources.understanding
产品是什么、适合谁、有什么不同，如何被 AI 组织和表达。
How AI organizes and describes what a product is, who it suits and how it differs.

### 营销演进 / Marketing evolution
Record: resources.evolution
企业的内容、工作优先级和衡量方式如何适应新的决策路径。
How content, priorities and measurement adapt to changing decision paths.

### 内容状态 / Content status
Record: resources.status
三条选题预告。详情页为标明状态的研究草稿，尚未正式发布，不作为客户成果。
Three topic previews. Detail pages contain clearly labelled research drafts, not published articles or customer results.

## 关于 Yonaris / About Yonaris
Status: public
中文来源: https://www.yonaris.com/company?lang=zh
English source: https://www.yonaris.com/company?lang=en

第一轮介绍、比较与筛选，可能发生在客户访问企业官网之前。
The first introduction, comparison and shortlist may happen before a buyer visits a company’s website.

### 为什么存在 / Why Yonaris exists
Record: company.why
帮助企业把产品事实、适用条件和公开证据连接到 AI 参与的理解与购买判断。
Connect product facts, conditions and public evidence with understanding and buying decisions involving AI.

### 两种读者 / Two readers
Record: company.readers
人通过叙事、体验与信任理解价值；Agent 需要明确的事实、关系、条件与证据。两者共享一致的产品事实。
People understand value through stories, experience and trust. Agents need explicit facts, relationships, conditions and evidence. Both use the same product facts.

### 今天从哪里开始 / Where we start today
Record: company.today
从 AI 可见度诊断切入，分析现有回答和支持材料，帮助团队确定改进优先级。
Start with AI Visibility diagnosis: analyze existing answers and supporting information, then help teams set improvement priorities.

### 长期方向 / Long-term direction
Record: company.future
面向 Human 与 Agent 共同参与的市场，建立支持营销与购买决策的基础设施。
Build infrastructure for marketing and buying decisions in a market shared by people and agents.

## 开始沟通 / Start a conversation
Status: public
中文来源: https://www.yonaris.com/contact?lang=zh
English source: https://www.yonaris.com/contact?lang=en

同一入口承接 AI 可见度诊断与普通咨询。
One contact entry for AI Visibility diagnosis and general enquiries.

### 需要填写 / Requested details
Record: contact.fields
姓名、电话、公司，并选择咨询类型。
Name, work email and company, plus the type of enquiry.

### 沟通内容 / Conversation scope
Record: contact.next
围绕产品与目标市场确认需求和范围，不意味着即时生成诊断报告。
Clarify the product, target market, needs and scope. An enquiry does not instantly generate a diagnostic report.

### 当前页面状态 / Current page status
Record: contact.preview
正式网站表单直接提交至服务器，并由邮件服务发送至 Yonaris 团队的咨询收件邮箱；成功提示表示邮件服务已接受，不代表团队已阅读、预约已确认或报告已生成。
The live website form submits directly to the server and is sent to the Yonaris team’s enquiry inboxes through an email service. Confirmation means the email service accepted it, not that the team has read it, a booking is confirmed or a report has been generated.

### 公开联系邮箱 / Public contact email
Record: contact.email
contact@yonaris.com。表单直接发送咨询，也可通过此邮箱联系；备用邮件链接需由访客在邮件应用中发送。
contact@yonaris.com. The form sends enquiries directly. Visitors can also use this address; the alternative email link requires sending from their own mail application.

## 隐私说明 / Privacy information
Status: policy
中文来源: https://www.yonaris.com/privacy?lang=zh
English source: https://www.yonaris.com/privacy?lang=en

说明网站如何处理表单咨询和统计信息。
How this website handles enquiry and analytics information.

### 你填写什么 / What you enter
Record: privacy.1
中文表单填写姓名、联系电话和公司；英文表单填写姓名、工作邮箱和公司。你也可以选择 AI 可见度诊断或普通咨询，并自愿补充一个想讨论的问题。
The Chinese form asks for name, phone and company; the English form asks for name, work email and company. You choose AI Visibility diagnosis or a general enquiry and may optionally add a question.

### 表单如何工作 / How the form works
Record: privacy.2
点击“提交咨询”后，表单通过加密连接提交至 Yonaris 的服务器，再由邮件服务发送至 Yonaris 团队的咨询收件邮箱。只有服务器确认邮件服务已接受咨询后，页面才显示“咨询已提交”。这不代表团队已阅读、预约已确认或诊断报告已生成。
Selecting “Send enquiry” submits the form over an encrypted connection to the Yonaris server, which uses an email service to send it to the Yonaris team’s enquiry inboxes. The page shows “Enquiry submitted” only after the server confirms that the email service has accepted it. This does not confirm that our team has read it, a booking is confirmed or a diagnostic report has been generated.

### 信息保存在哪里 / Where details are stored
Record: privacy.3
提交前，表单内容保留在当前页面内存中，不写入站点 Cookie 或 localStorage。提交后，相关托管与邮件服务商会为处理咨询而处理信息，咨询邮件保存在收件邮箱中。浏览器自动填充与页面恢复由你的浏览器设置决定。
Before submission, entries remain in the current page’s memory and are not written to site cookies or localStorage. After submission, the relevant hosting and email providers process the information to handle your enquiry, and the enquiry email is stored in the receiving mailbox. Browser autofill and page restoration are governed by your browser settings.

### 失败重试与备用邮箱 / Retries and the email alternative
Record: privacy.4
提交失败时，页面会保留当前填写内容，供你修改或重试。你也可以通过 contact@yonaris.com 联系我们；备用邮件链接会打开你的邮件应用，需要你在那里确认发送。
If submission fails, the page keeps your current entries so you can edit or retry. You can also contact contact@yonaris.com. The alternative email link opens your mail application, where you need to send the email yourself.

### 网站统计与选择 / Analytics and your choice
Record: privacy.5
预览环境不加载 Google Analytics。正式网站只有在你选择“允许统计”后才加载 Google Analytics 4，记录页面访问、语言、Human/Agent 切换、咨询入口、成功提交及备用邮件链接等操作。不会向 Google Analytics 发送姓名、电话、邮箱、公司或问题。Google 会接收统计请求及其网络信息；成功提交事件不代表团队已阅读咨询。
Previews do not load Google Analytics. On the production website, Google Analytics 4 loads only after you allow analytics. It measures page visits, language, Human/Agent switching, contact entry, successful submission and alternative email link actions. Names, phone numbers, email addresses, companies and questions are not sent to Google Analytics. Google receives analytics requests and associated network information. A successful submission event does not mean our team has read the enquiry.

### 统计存储与更改 / Analytics storage and changes
Record: privacy.6
浏览器 localStorage 仅保存你的统计偏好；无法保存时，sessionStorage 会尝试记录仅用于当前标签页的拒绝标记；同意后 Google Analytics 会使用 _ga 系列 Cookie 识别浏览器。你可通过页脚“统计偏好”拒绝或撤回；撤回后停止采集并删除本站可访问的 _ga Cookie，不会删除此前已汇总的数据。拒绝统计不影响浏览或提交咨询。
Browser localStorage stores only your analytics preference. If saving fails, sessionStorage attempts to retain a denial-only fallback for the current tab. After consent, Google Analytics uses _ga cookies to recognize a browser. Use Analytics preferences in the footer to decline or withdraw. Withdrawal stops collection and removes accessible _ga cookies on this website; it does not delete previously aggregated data. Declining does not affect browsing or submitting an enquiry.

### 咨询用途与更正 / Enquiry use and corrections
Record: privacy.7
Yonaris 团队使用你提交的联系方式、公司与问题来回复咨询、讨论需求和确认工作范围。为了防止重复提交和滥用，服务还会处理必要的请求及提交标识。如需更正或删除已提交的咨询信息，可通过 contact@yonaris.com 联系。
The Yonaris team uses the contact details, company and question you submit to respond, discuss your needs and agree on the scope of work. The service also processes necessary request and submission identifiers to prevent duplicate submissions and abuse. To request correction or deletion of submitted enquiry information, contact contact@yonaris.com.

## 你的产品，AI 读懂了多少？ / Does AI understand what your product can do?
Status: draft
中文来源: https://www.yonaris.com/resources/ai-product-understanding?lang=zh
English source: https://www.yonaris.com/resources/ai-product-understanding?lang=en

产品有的能力，为什么没有出现在答案里？从一句具体回答开始。
A product capability can exist without appearing in an answer. Start with one specific question.

### 内容状态 / Content status
Record: resources.ai-product-understanding.status
选题预告中的研究草稿，尚未正式发布。示例为虚构说明，不是客户结果。
Research draft for an upcoming topic, not formally published. Examples are fictional illustrations, not customer results.

### 先问一个具体问题 / Ask a question you can assess
Record: resources.ai-product-understanding.1
“这款产品支持私有化部署吗？”这比“AI 是否理解我们的品牌”更容易判断。把产品、问题、平台、市场、语言和观察时间记在一起，保留完整回答。
“Does this product support private deployment?” is easier to evaluate than “Does AI understand our brand?” Keep the full answer together with the product, question, platform, market, language and observation time.

### 把能力与条件放在一起 / Keep the capability and its conditions together
Record: resources.ai-product-understanding.2
假设产品说明写着“支持私有化部署，部署环境要求与实施范围需事先确认”。准确表达应同时保留能力和前提。如果答案只说“需要进一步确认”，就值得核对它遗漏了什么。
Imagine a product document says, “Private deployment is supported. Environment requirements and implementation scope must be agreed in advance.” An accurate description needs both the capability and the conditions. If the answer only says “Further confirmation is needed,” check what was left out.

### 先核对，再下结论 / Verify before drawing a conclusion
Record: resources.ai-product-understanding.3
对照官网原句、版本与适用范围。如果答案提供了可见引用，再核查引用是否支持这句话。一次回答只能说明这一次观察，不能代表所有平台、所有问题或未来的回答。
Compare the answer with the original product statement, version and scope. Where an answer includes visible citations, check whether they support the claim. One answer is one observation, not a result for every platform, question or future response.

## 客户还没访问官网，第一轮筛选如何发生？ / The shortlist can start before your website
Status: draft
中文来源: https://www.yonaris.com/resources/before-the-website?lang=zh
English source: https://www.yonaris.com/resources/before-the-website?lang=en

当客户先问 AI，产品需要在哪些问题里，把自己说清楚？
When a buyer asks AI first, which questions does your product need to answer clearly?

### 内容状态 / Content status
Record: resources.before-the-website.status
选题预告中的研究草稿，尚未正式发布。示例为虚构说明，不是客户结果。
Research draft for an upcoming topic, not formally published. Examples are fictional illustrations, not customer results.

### 从客户的筛选条件出发 / Start with the buyer’s conditions
Record: resources.before-the-website.1
客户可能先问“支持私有化部署吗”“能否接入我们现有的系统”。这些问题都在确认产品是否适合自己的环境。先列出销售与产品团队经常被问到的问题，比凭空扩充一份问题清单更有帮助。
A buyer might ask whether a product supports private deployment or works with an existing system. These are practical questions about fit. Start with questions your sales and product teams actually receive.

### 读完整个答案 / Read beyond the mention
Record: resources.before-the-website.2
产品被提到，只是观察的起点。还需要看它被怎样介绍、与哪些方案比较、推荐理由里保留了哪些限制。名称正确，并不代表关键能力已经说清楚。
Being named is the beginning of an observation. Look at how the product is described, which alternatives appear and what limits the recommendation retains. A correct product name does not mean the important capabilities are clear.

### 把发现落回公开信息 / Bring the finding back to public information
Record: resources.before-the-website.3
如果某个重要条件没有被准确表达，先查官网与产品文档是否清楚、是否一致。来源分析可以核对可见引用，但不能据此确定模型内部为什么给出某项推荐。
If a relevant condition is missing, check whether the website and product documentation state it clearly and consistently. Visible citations can be checked. They cannot establish a model’s internal reason for a recommendation.

## 面对 AI 推荐，企业该先做什么？ / What should you improve first?
Status: draft
中文来源: https://www.yonaris.com/resources/where-to-start?lang=zh
English source: https://www.yonaris.com/resources/where-to-start?lang=en

从官网已有的产品信息开始，把一次发现变成一项具体行动。
Start with the product information you already have. Turn one observation into a concrete next step.

### 内容状态 / Content status
Record: resources.where-to-start.status
选题预告中的研究草稿，尚未正式发布。示例为虚构说明，不是客户结果。
Research draft for an upcoming topic, not formally published. Examples are fictional illustrations, not customer results.

### 只选一个有明确依据的问题 / Choose one question with clear evidence
Record: resources.where-to-start.1
先处理一个高频且有事实依据的问题。比如，官网已经明确支持私有化部署，但示例回答仍然模糊。优先级应结合客户关心程度、事实是否清楚以及团队能否完成修改来讨论。
Start with a recurring buyer question supported by a verified product statement. For example, the website confirms private deployment while an illustrative answer remains vague. Discuss priority based on buyer relevance, evidence and the effort needed to make a useful change.

### 让建议落到一个具体位置 / Make the recommendation specific
Record: resources.where-to-start.2
把“完善产品信息”改成可执行的任务：在产品页加入直接回答部署方式的问答，并链接到说明部署条件的文档。文案经过产品负责人核对后，再决定是否发布。
Replace “improve product information” with a concrete task: add a direct deployment FAQ to the product page and link to the document describing its conditions. Have the product owner review the wording before publication.

### 复核时保留条件 / Keep the conditions when reviewing again
Record: resources.where-to-start.3
后续观察应尽量保留相同的问题、平台、市场与语言，记录时间及样本范围。回答有变化，不等于变化一定由某次改稿造成。执行和复核是否包含在服务中，需要事先确认。
Keep the question, platform, market and language comparable where possible, and record timing and sample scope. A changed answer does not establish that a particular edit caused it. Execution and follow-up review need an agreed service scope.

## Boundaries

- 私有化部署的产品、AI 回答与官网原文均为编写的演示，不是客户结果，也不表示 Yonaris 自身的部署能力。
- 价格、分析数量、交付周期与监测频次需另行确认。
- 诊断不承诺排名、引用、推荐或商业结果。
- The private-deployment product, AI answers and source text are authored illustrations, not customer results or claims about Yonaris deployment capabilities.
- Pricing, analysis volume, delivery timing and monitoring frequency require a separate agreement.
- Diagnosis does not promise rankings, citations, recommendations or commercial outcomes.