小型代理機構的 Organization Schema：可直接複製的 JSON-LD 範本及應省略的內容
Organization Schema for a Small Agency: A Copy-Paste JSON-LD Template and What to Leave Out
小型代理機構和顧問公司可在首頁加入精簡的 Organization JSON-LD，提供品牌名稱、網址、標誌、服務範圍及受控的社交資料連結，協助機器辨認機構。結構化資料須與網站及公開檔案上的資訊一致；無法在頁面上核實的評分、獎項或電話號碼應予省略。部署後應每月重新檢查。
Structured data will not magically rank a thin site, but it does help machines agree on who you are. For small agencies and consultancies, an accurate Organization block is the cheapest entity-clarity upgrade available. This post shows a minimal template and the mistakes to avoid.
A minimal template
Place one script block of type application/ld+json on the home page. Include these properties:
-
@type: Organization (or ProfessionalService if it fits) -
name: the exact brand name you use everywhere -
url: the canonical home page -
logo: an absolute URL to a square image -
description: one sentence about what you do and for whom -
address: postal address with city and country -
areaServed: the markets you actually serve -
sameAs: an array of profile URLs you control
What to leave out
Do not paste review ratings you cannot show on the page, since that violates guidelines and invites manual action. Skip fake awards. Skip phone numbers you do not answer. If a field would require invention, omit it.
Make it match the visible page
The structured data must agree with the footer, the contact page, and your directory profiles. If the schema says Hong Kong and your footer says Shenzhen, a model has two answers and will choose either. Pick one canonical set of facts and copy it everywhere.
sameAs is where entities connect
List your LinkedIn page, your directory profiles, and other official accounts. Only include URLs you control or that clearly describe you. A tidy sameAs array is one of the few places you can explicitly tell machines which profiles belong together.
Validate and monitor
Run the page through a schema validator and the rich results test, then fix warnings that relate to the properties you provided. After deployment, re-check monthly; template changes often strip the script by accident.
Beyond the home page
Consider Service pages with a short Service block, and article pages with Article and author information. Do not mark up everything; mark up what a person could verify on the page.
A note on expectations
Schema supports clarity; it does not replace content. Pair it with pages that answer real questions and with consistent profiles elsewhere.
Next steps
If you do only one thing this week, audit every public profile for the same name, address, and service list, then publish the schema that reflects that single source of truth. Consistency compounds: each matching profile makes the next machine reading of your brand more confident.
For the wider process we follow when making a company legible to AI search, see: the GEO optimization steps we use.
Published by PandaWM, an overseas marketing team based in Hong Kong.
來源：DEV Community · dev.to