Entity Consistency Review Before Submitting a Site as a Source
Key takeawayWhen site content is used to generate a brand summary, two versions of the same entity fact make it hard to confirm which is accurate. This sheet aligns company name, address, contact details and business description to a single dataset across the site.
Industries and use cases
- Before submitting site details to content platforms or directories
- After a company rename, relocation or phone change
- When entity details differ across language versions
- When a published summary contradicts the official site
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| Legal company name | Chinese and English names are fixed, match the business licence and abbreviations are defined separately | High | Keep one entity data sheet and reference it site-wide instead of retyping per page. |
| Registered and office address | Both are labelled separately in a consistent format with country, region, city and street number | High | When several addresses exist, state clearly which is registered and which is office or factory. |
| Phone number | Includes country and area codes and matches exactly across footer, contact page and structured data | High | Keep one or two working numbers and remove discontinued ones promptly. |
| Email domain | Outbound email uses the company domain rather than a free mailbox as the main contact | High | Sales and support can be split by function, but the domain should be consistent. |
| Business description | One sentence definition stays the same on the home page, about page and markup description | High | Define it in under 40 words first, then adapt length elsewhere without rewriting. |
| Founding year and scale | Founding year, headcount and plant area are consistent at the same point in time | Medium | Refresh the figures annually so pages do not sit on different years. |
| Credentials | Licence and certificate names and numbers match what is displayed | High | Replace images and text when certificates renew and never keep expired ones on display. |
| Multilingual consistency | Company name, address and contact details are not paraphrased across languages | High | Keep brand names in original form and follow local address conventions without changing facts. |
| Public accounts | The official account list matches what is shown on the site and maps to the brand | Medium | List only accounts that are actively maintained, not retired entry points. |
| Map coordinates | The embedded map pin matches the stated address | Medium | Check the pin manually so it does not default to the city centre. |
| Structured data | Organization markup name, address and contact details match the page | High | Generate markup from the entity sheet and never maintain it separately. |
| Last verified date | The entity page shows the date it was last checked | Low | Update the date after each check so freshness is visible. |
Common misjudgements
- Assuming the English and Chinese names need not correspond: when both are used publicly, the site should explain the mapping.
- Updating the footer but not the contact page, when scattered entity details mean every edit creates a new mismatch.
- Mixing factory and registered addresses: they are legitimately different, and merging them reads as less credible.
How to use this checklist
- Pair with the brand entity sheet: this one covers data consistency, that one covers brand expression.
- Update everything at once when entity details change and verify every six months.
- Link with the contact page sheet, which is the entry point outsiders use most to verify the entity.
FAQ
Can an office address be shown without a factory?
Yes. State the office address and business model honestly rather than inventing a production site.
Do trading companies describe details differently from factories?
Yes. A trading company should explain its supply chain role and avoid wording that could mislead.
How many entity datasets does a multilingual site need?
One dataset, with each language adapting only the expression, not the content.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
Structured Data Self-Check for an Own-Brand SitePrivacy Policy and Cookie Notice ReviewContact Page Entity Verification for Factory SitesOEM and Sample Page Compliance ReviewShipping and After-Sales Page ReviewNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.