Zhihe GrowthWhen displaying partner brands, separate three facts: who the company worked with, what it delivered in a particular GEO project, and which third-party certifications it holds. Each requires different evidence; a logo wall establishes none automatically.
Three claims, three evidentiary thresholds.
| External claims | Minimum checks | What must not be inferred |
|---|---|---|
| Partner Brands | Partner identity, collaboration record, and permission to disclose the name and logo | Contract value, project scope, results, or endorsement |
| Named delivery case | Project entity, deliverables, customer-approved disclosure scope, and result definitions | Presenting stage-specific data as long-term performance across all platforms |
| Official accreditation/authorization | Authorizing body, certificate number, covered entity or object, validity, and verification route | Claiming official platform-partner status based only on collaboration history |
Do not count brands in the same group as separate companies simply by counting logos. The YAGEO and KEMET relationship illustrates the distinction: a display may list brands separately, but company counts, customer counts, and contractual relationships must follow the original records. A brand name is not necessarily a legal entity; verify the roles of the trademark, group, branch, and distributor when describing relationships.
A logo identifies a brand; it is not an endorsement certificate
Logo display also depends on file version, dimensions, colors, and permission scope. Zhihe Growth may display authorized partner names and logos, but must verify sources and permitted versions before publication. Do not copy low-resolution screenshots or import unrelated credits from third-party presentations. Some brands have specific trademark rules, such as Infineon's trademark guidance; without documented permission, use a factual text reference pending a rights check rather than assuming logo use is allowed.
Label the display 'Selected Partner Brands' and include only verified identities. Do not attach unconfirmed labels such as 'GEO services' or 'AI citation improvement' to every logo. Withhold the two unidentified icons and any brands whose names cannot be tied reliably to the correct entities. This restraint makes the limits of each public claim clear.
How Zhihe Growth separates collaboration from outcomes
Partner Brands page shows selected brands Zhihe Growth has worked with, without implying specific collaboration scope. Separately, the Case Studies section discloses the named, customer-authorized SuperPDR and ELEREIN GEO projects. Their respective case reviews and case reviews describe scale, explanatory links, and stage-specific citation rates. Public industry information about other partner brands cannot be used to invent additional results.
Media articles are another evidence category: they establish what was published, not automatic certification of the company's services by the media, a platform, or an industry body. Give brand identity, partnerships, cases, media, and formal credentials separate sections and appropriate structured data rather than labeling every link an authoritative endorsement.
Pre-publication checks
- Does the name identify the correct brand or legal entity, not a namesake or another group company?
- Do original collaboration records permit disclosure of names and logos? Does permission cover the website, logo version, and ongoing display?
- Does the page state only evidenced relationships and avoid unconfirmed deliverables?
- For customer results, are the project, period, question scope, platform, and metric denominator explicit?
- If claiming certification, is there a current certificate applicable to this legal entity and a verification route?
Finally, check Schema:Organization can describe the company and its official website, but a logo on a page does not justify adding award,credential or implying endorsement. Google's Structured data guidelines require markup to match visible content. Separating partner brands from actual case studies reduces misinterpretation; it is not a technical shortcut to platform recognition of those relationships.