Who this note is for
Read this if you buy, brief, or do search work. It is an operating note, not a vendor comparison, and it does not promise rankings.
Company size here means coordination cost: how many people must agree before a page can change. A twenty-person firm with three agencies can be “large” on this page. A focused enterprise team that can edit its own cornerstone pages can act like a small one.
這份備忘錄給誰
如果你負責購買、簡報或執行搜尋工作，這份備忘錄是寫給你的。它是操作說明，不是供應商比較，也不保證排名。
這裡的公司規模指協調成本：改一頁之前要有多少人同意。二十人的公司若同時用三家代理，在本頁就算「大型」。能自行修改基石頁的企業團隊，則可以按小公司的方式行事。
Five issues that do not care how large you are
1. The first screen explains the brand, not the offer
Searchers and answer engines both need a sentence they can reuse: who you help, the job you do, and where you do it. A slogan cannot be cited. When the homepage, the About page, and the service page each describe a different company, rankings and answers drift apart.
2. Names do not match
Legal name, trading name, product names, and city spellings disagree across the site, profiles, and press. Small companies do this by accident. Large companies do it by department. Retrieval systems then attach your proof to the wrong entity, or to none.
3. Pages have no owner and no date
A page that cannot say who is responsible, or when it was last checked, is a weak source. GEO systems prefer passages that look maintained. SEO wastes crawl attention on pages nobody will defend.
4. Measurement stops at a rank report
A rising rank on the wrong query is not demand. A flat traffic chart can hide an answer engine that describes you incorrectly. Track three things: footprint on priority queries, whether public descriptions of you are accurate, and qualified conversations that mention search or an AI answer.
5. A second language is treated as a duplicate
English and Traditional Chinese — or any pair — are related markets. The facts must match. The questions people ask do not. One page plus an unedited machine translation ranks for the wrong intent and gets cited for an offer you do not sell. The bilingual operating model is the longer version of this point.
五個與規模無關的問題
1. 首屏在解釋品牌，沒有解釋服務
搜尋者和答案引擎都需要一句可以重用的話：你幫誰、做什麼、在哪裡做。口號無法被引用。如果首頁、關於我們和服務頁各自描述一家不同的公司，排名和答案就會各走各路。
2. 名稱對不上
法定名稱、商號、產品名和城市寫法，在網站、公開檔案和報導之間不一致。小公司是不小心。大公司是部門各寫各的。檢索系統於是把證據掛到錯誤的實體，或掛不到任何實體。
3. 頁面沒有負責人，也沒有日期
說不出誰負責、上次何時核對的頁面，是弱來源。GEO 系統傾向引用看起來仍在維護的段落。SEO 則把爬取注意力花在沒有人會維護的頁上。
4. 量度停在排名報告
錯誤查詢的排名上升不是需求。流量持平，也可能掩蓋答案引擎對你的錯誤描述。追三件事：優先查詢的能見度、公開描述是否準確，以及提到搜尋或 AI 答案的合格對話。
5. 第二語言被當成複製品
英文與繁體中文，或任何一對語言，是相關市場。事實必須一致。人們問的問題並不一致。一頁加上未經編輯的機器翻譯，會讓你為錯誤意圖排名，並被引用成你並不出售的服務。較完整的做法見 香港雙語 SEO 與 GEO。
What actually changes with size
| Size | The expensive mistake | The useful first move |
|---|---|---|
| Small. One site owner, roughly under 20 people. | Buying a content calendar or an “AI visibility” retainer before the offer is written in public. | One cornerstone page per offer. Name the person who knows the work. Add three proof points you can defend on a sales call. |
| Mid-market. An in-house marketer, an agency, or both. | An SEO report and a brand site that describe different companies, plus a separate AI-content stream that contradicts both. | One naming sheet, and 15 to 25 questions customers actually ask. Once a month, check whether Google and two answer engines still match the live offer. |
| Large. Many brands, regions, or CMS instances. | Local teams and a global template fighting. Answer engines repeat the description that appears most often, which is often the old one. | One entity record — name, offers, markets, spokespeople — that local pages must match. Give each market its own quotable page. |
A note for small teams: do not ask a chatbot “who are we?” and then try to correct the model. You cannot edit the model. You can publish a clearer source and get one other site to agree with it.
A note for large teams: schema that claims expertise the page does not show makes the mismatch easier to detect. Markup is not a substitute for the sentence on the page.
規模真正改變的是什麼
| 規模 | 昂貴的錯誤 | 有用的第一步 |
|---|---|---|
| 小型。一個網站負責人，大約二十人以內。 | 服務還沒有公開寫清楚，就先買內容日曆或「AI 能見度」月費。 | 每個服務一頁基石頁。寫上真正懂這項工作的人。放三個你在銷售對話裡守得住的證據。 |
| 中型。有內部市場人員、代理商，或兩者都有。 | SEO 報告和品牌網站描述的是不同的公司，再加上一條互相矛盾的 AI 內容產線。 | 一份名稱表，以及 15 至 25 條客戶真正會問的問題。每月檢查 Google 和兩個答案引擎是否仍符合現行服務。 |
| 大型。多品牌、多地區或多套 CMS。 | 地區團隊和全球模板互相打架。答案引擎重複出現最多的描述，而那往往是舊的。 | 一份實體紀錄——名稱、服務、市場、發言人——地區頁面必須對齊。每個市場有自己可被引用的頁面。 |
給小團隊：不要問聊天機械人「我們是誰」，然後試圖改正模型。你改不了模型。你能做的是發表更清楚的來源，並讓另一個網站同意這段描述。
給大團隊：結構標記如果聲稱頁面並沒有展示的專業，只會讓不一致更容易被發現。標記不能取代頁面上的那一句。
Thirty days, any headcount
- Week 1. Write the one-sentence offer and the canonical name list. Put both in the first paragraph of the homepage and the About page.
- Week 2. Collect 15 real customer questions from sales, support, and Search Console. Record how Google and two answer engines currently describe you. Mark factual errors.
- Week 3. Revise the one page that would correct the worst error. Put a named owner and a review date on it.
- Week 4. Ask one customer, partner, or association to describe you in their own words on a page you do not control. Check whether the week-2 error is still there.
If you only have an afternoon, do week 1. The rest of the month is wasted while the sentence is still a slogan.
After the month, use the GEO readiness checklist for the gaps this sequence did not touch, and how to earn citations when you are ready to be quoted rather than merely indexed.
三十天，任何人手
- 第 1 週。 寫下一句服務說明和規範名稱表。放進首頁和關於我們的第一段。
- 第 2 週。 從銷售、客服和 Search Console 收集 15 條真實客戶問題。記錄 Google 和兩個答案引擎目前如何描述你。標出事實錯誤。
- 第 3 週。 修改最能糾正最嚴重錯誤的那一頁。寫上負責人姓名和覆核日期。
- 第 4 週。 請一位客戶、夥伴或協會，在你控制不了的頁面上用他們的話描述你。檢查第 2 週的錯誤是否還在。
如果只有一個下午，做第 1 週。句子仍是口號的話，這個月剩下的工作都會浪費。
What this note will not do
- It will not rank a page, replace a technical crawl, or settle a legal name.
- Size is a proxy for how many people must agree. It is not a maturity score.
- A small company with a clear offer outperforms a large one with three conflicting brochures.
本備忘錄做不到的事
- 它不會讓某一頁排名，不能取代技術爬取，也不能解決法定名稱。
- 規模是「要多少人同意」的代理指標，不是成熟度分數。
- 服務寫得清楚的小公司，會勝過三份互相矛盾簡介的大公司。
Questions operators ask
Does a small company need GEO if it barely ranks?
Yes, in a small scope. Publish one page that states who you help, what you do, and where. Answer engines repeat the description that appears most often. If the public web only has a slogan, the citation will be the slogan.
Should a large company centralize SEO and GEO?
Centralize names, offer scope, and spokespeople. Leave pages close to the market that asks the question. A global template should lock the facts, not every sentence.
Is a blog the right first move?
Usually not. Fix the pages sales already uses and other sites already link to. A new article with no owner is another source that will go stale.
How do we know an answer engine is wrong about us?
Ask in the customer’s words, not in your brand slogan. If the answer’s service, market, pricing model, or audience does not match the live offer, it is an error. Log it against the public page, not against the version you wish the model remembered.
營運者常問的問題
小公司幾乎沒有排名，還需要做 GEO 嗎？
需要，但範圍很小。先讓一頁說清楚你幫誰、做什麼、在哪裡。答案引擎會重複網上出現最多的描述。如果公開網頁只有口號，被引用的就是口號。
大公司應不應該把 SEO 和 GEO 集中管理？
名稱、服務範圍和發言人要集中。頁面應該留在最接近客戶問題的市場。全球模板可以鎖定事實，不應鎖定每一句話。
網誌是不是第一步？
通常不是。先修正銷售已經在用、其他網站已經在連結的頁面。沒有負責人的新文章，只是多一個會過期的來源。
怎樣知道答案引擎說錯了？
用客戶的原話問，而不是用品牌口號問。如果答案裡的服務、市場、收費模式或對象與現況不符，就是錯誤。把錯誤記在公開頁面上，而不是記在你希望模型記得的版本上。