When customers ask AI “Do you do export?”, your official site only covers domestic business and your export site does not name the company—which half of the answer gets missed?

Bottom line first: AI answer engines decide whether sites belong to the same company by looking at cross-verifiable entity signals; the number of domains alone is not evidence. If one site clearly states the entity name, business description, contact details, and ICP filing information, while another site only shows an English brand name and product images, the latter is hard to count into your company profile no matter how much content it has. A common 2026 scenario: a customer asks AI “Do you do export?”, and the answer cites only the official site’s line “focused on domestic custom development,” or simply introduces the export site as a separate supplier.

Whether a branch site counts as yours depends on whether its snippets can prove attribution

When AI answers company-related questions, it usually first performs entity mapping: matching the name in the question to a specific entity, then assembling facts from multiple sources. More source URLs do not mean more entities; but if a source lacks a complete sentence saying “who is doing this,” that snippet is hard to attribute to you.

In other words, a branch site is not automatically counted just because its pages go live. It needs a self-proving sentence that can be extracted on its own—for example, stating in the first paragraph that “the export business of the company is run by the same team, and this site is the English version.” Without that sentence, the engine is more likely to use only the fact it has already confirmed and skip the rest as noise.

• Name signals: full registered company name, public short name, English name and its Chinese counterpart
• Description signals: one-sentence business description, core service terms, industry positioning
• Contact signals: phone number, email domain, office address
• Entity signals: ICP filing entity and business registration information
• Association signals: cross-site links, brand relationship statements on pages, same-entity declarations in structured data

Their impact is not equal. Name wording and ICP filing entity are hard signals, followed by business description and contact details. Cross-links and relationship statements are low-cost and fast to show effect; usually you add these two first, then see whether contradictions still cluster.

When an export site does not name the company, what exactly gets lost?

In delivery work, three common patterns show up: first, only an English brand name appears, and the body text is all product terms and specifications; second, the first paragraph goes straight into product categories, capacity, and shipping capability without any entity appearing at all; third, the introduction is stuck on a previous-generation business—for example, it still describes the line the company focused on in earlier years.

The consequence is not that the content is wasted; it is that attribution is lost. When customers ask “Do you do export?” or “Which regions have you exported to?”, the answer may cover only the official site side, or describe the export site as a separate trading company. The reverse is worse: if the export site’s pricing approach and delivery terms get merged into the custom development business, customers will come to negotiate with the wrong expectations, and the cleanup cost is higher than a missed mention.

The self-check is simple. Copy the first paragraph of the export site’s first screen on its own, give it to someone who has never seen your company, and ask, “Who is saying this?” If they cannot identify the entity, AI most likely cannot either.

One entity card so every site can prove attribution

Rather than correcting each site one by one, first compress “who we are” into a copyable card, and let each site draw from it. The reason is that engines extract snippets, not whole pages, and snippets must corroborate one another; if each site improvises, the snippets cancel each other out, and writing more can make things messier.

1. Make the entity card: one line for the full registered company name, one line for the unified public short name, with the English name and Chinese counterpart written together; then add a business description of no more than 40 Chinese characters that includes the core service terms.
2. Unify contact and entity: keep one primary set of phone, email, and address; when a branch site must differ, state clearly on the page which team it belongs to.
3. Build cross-links: link sites to each other in the footer, use the unified short name as anchor text, and avoid low-information wording such as “click here.”
4. Keep markup aligned: use the same entity name and the same description on About pages; when structured data is present, declarations for the same entity should point to the same set of official accounts and the same address.
5. Lock down a sync mechanism: once the business description changes, update all sites together with the WeChat official account and map business listings in the same iteration, and assign one owner.

Step 5 determines how long the alignment lasts. Based on 2026 delivery practice, many projects drift apart again three months after alignment; the problem is usually not the method, but that no one owns synchronization.

In one project, the client’s three sites were managed by three different vendors, and the export site was in the hands of an overseas company, so changing one sentence meant waiting for their schedule. The budget only covered changes to the official site and the online store, so we first implemented the entity card on the two sites we could change: the About page stated the Chinese-English name mapping, the footer added a business relationship statement and cross-links, and the export site got only one statement without a link. As a result, the official site side converged first; the export site’s entity name was added only about two months later. During that period, when customers asked “Do you do export?”, the answer still often cited only the official site’s sentence. The typical range for full messaging convergence is two weeks to three months, depending on when the site with the later change schedule acts. The cost was an extra round of checking and one rework. The lesson is direct: for cross-vendor projects, first confirm who can make changes and when, then set the launch order.

Merge into one site, or keep multiple sites and align them?

This is a business-structure question, not a matter of better or worse. Online stores and export sites often have independent payment, logistics, and language requirements, and forcing a merge can hurt conversion; for purely presentational branch sites, merging usually saves maintenance.

• Merge into one main site: suitable when the business is simple and branch sites are just historical leftovers. The experience range for redesign plus content migration is 3–8 weeks. The benefit is a single source of messaging; the cost is short-term traffic fluctuation at the original branch site’s standalone entry points.
• Keep multiple sites and align them: suitable when online store, export, and multiple brands run in parallel. The typical range for the first round of copy changes and cross-link additions is 1–3 weeks, with lower cost; the cost is long-term maintenance, and sync responsibility must be assigned to a person.
• Hybrid approach: keep the domains, fold purely presentational branch sites into main-site sections or redirect them, and let only branch sites that carry independent transactions and independent languages remain separate.

A rough rule of thumb: if a branch site has had no content updates and no independent transactions for six months, merging is usually more cost-effective; if it carries independent payment, an independent language, or an independent brand, keeping it and aligning it is more realistic.

Where this applies and where it does not

Entity alignment reduces the probability of being split apart or missed in calculations. It solves messaging contradictions, not the problem of unprofessional content itself. First check whether you are in the situations below, then decide how much to invest.

• Worth doing: the official site coexists with an online store and an export site, and customers ask AI what you actually do; the company has changed its name or brand and old domains are still resolving; multiple sub-brands under a group need their relationships clarified; after a merger or team integration, page messaging is still stuck before the integration.
• Not necessary: a single site on a single domain with a simple business has limited alignment benefit, and putting effort back into page content and delivery evidence is more practical; temporary campaign pages and ad landing pages have short lifecycles and do not need to be included in sync; old domains that will definitely no longer serve external business are cleaner to redirect or take offline than to fill with relationship statements.

Common questions

Do three domains have to be merged into one?

No. Branch sites that carry independent payment, an independent language, or an independent brand are more realistically kept and aligned; usually only purely presentational historical branch sites with no long-term updates are worth merging.

Is changing only the export site’s page titles enough?

No. A brand name in the title rarely makes it into body-text snippets. Usually you need a standalone entity statement in the first paragraph, then sync the name to the About page and footer.

If the ICP filing entities differ, will AI always treat them as two companies?

Not necessarily, but the risk is clearly higher. A common approach is to state the relationship and business division between the two entities on the page, while keeping name wording and contact details consistent.

How can you tell which part of the business is being missed?

Ask the same question in three or four AI tools—for example, “Do you do export?”—and see whether the answer covers the business of only one site. Where the gap clusters, first fix that site’s first-paragraph entity sentence.

If the English brand name and Chinese company name do not match, which side should you change first?

First build a Chinese-English mapping, and make sure the Chinese site includes at least one explanation of the English name counterpart. Changing only the export site leaves the Chinese side without a reference, and the two sides still will not match.

A next step: capture each site’s About page, footer, and contact details into a one-page comparison table, circle the contradictory sentences that repeat, fill in the entity name and business description first, then add cross-links and relationship statements. If budget and schedule allow changes to only one site, prioritize the one customers search for most often. This approach suits small and medium-sized companies with multiple sites and split messaging; if you have only one site and a simple business, spending the same effort on page content and delivery evidence gives a more direct return.