Does Your Business Website Development Produce Citable Pages?
A business website earns enquiries when each page states one clear answer that search engines and AI assistants can extract. The delivery stages below show the artefact each stage must produce.
A business website built for search and AI citation answers one buyer question per page, with a self-contained sentence near the top, structured data that matches the visible text, and a consent setup that does not block crawlers. Judge a proposal by three artefacts: a page-by-page question map, a consent specification with a named legal basis, and a migration redirect table. Each is a deliverable you can review before code is written.
What should a business website include before development starts?
A business website should start with a page inventory that maps each service to one buyer question and one primary call to action. Without that map, pages compete for the same query and assistants cannot tell which page answers which question.
The first deliverable is a question map: a spreadsheet listing every planned URL, the exact question it answers, the evidence it cites (a specification, a process description, a policy), and the action it requests. If two planned pages answer the same question, merge them before design begins; duplicate pages dilute both search ranking and citation likelihood.
The second deliverable is a service page structure template. Each service page carries a one-sentence answer in the first paragraph, a list of what the service includes and excludes, a description of the delivery stages, and a contact action. This structure is what allows an assistant to lift a paragraph and quote it without surrounding context.
The third deliverable is a measurement plan: which pages are expected to produce enquiries, which forms or phone numbers count as conversions, and who reviews the report. If no one is named to review the measurement plan monthly, the site will be rebuilt before its effect is known.
For a fuller view of how we scope business website development, the landing page lists the artefacts we hand over at each stage.
How do you structure a multilingual website so each language ranks?
A multilingual website should give each language its own URL path or subdomain, its own title and meta description, and its own internal links, rather than hiding translations behind a language switcher on a single URL. Search engines index URLs, not interface states.
The artefact for this stage is a URL and hreflang matrix: one row per page, one column per language, with the hreflang tags that tell search engines which language version to serve. If a language version is machine-translated and not reviewed by a native speaker, mark it as a draft and keep it out of the sitemap; unreviewed text damages trust and can misstate legal terms.
Website localisation goes beyond translation: currency, date format, address format, phone country code, and the legal entity named in the footer all change per market. For a restaurant site, the menu, opening hours and reservation policy must be edited per language, not copied. Our restaurant industry page describes how those fields are handled.
The delivery team controls the template and the hreflang implementation; the client controls the native-speaker review and the accuracy of market-specific facts. Assign one named reviewer per language before the first translation is ordered, because review capacity, not translation speed, sets the launch date.
What is GDPR cookie consent and how is it implemented?
GDPR cookie consent is a mechanism that blocks non-essential cookies and trackers until the visitor takes a positive action, records what was consented to and when, and offers an equally easy way to withdraw. It is a legal requirement for sites serving EU visitors, not a design preference.
The artefact is a consent specification: a table listing every cookie and script, its purpose, its legal basis, whether it fires before consent, and where the consent record is stored. If a script fires before the visitor clicks accept, the consent mechanism is not compliant, regardless of what the banner says.
| Consent element | What the specification must state | Who owns it |
|---|---|---|
| Cookie inventory | Name, purpose, duration, first- or third-party | Delivery team drafts; client approves |
| Legal basis | Consent or legitimate interest, per cookie | Client, with legal advice |
| Blocking behaviour | Which scripts are held until consent | Delivery team |
| Consent record | What is stored, where, and for how long | Client decides retention |
| Withdrawal route | How a visitor changes their choice | Delivery team implements |
Implementation order matters: inventory first, then blocking, then the banner text, then the record. If the banner is designed before the cookie inventory is complete, it will need rewriting. Cookie consent GDPR review is a legal question; we implement the mechanism and document it, while the client's legal adviser confirms the basis.
How do you redesign a website without losing search traffic?
You redesign a website without losing search traffic by preserving every URL that currently earns visits or links, and by mapping every changed URL to its replacement with a permanent redirect before the new site goes live. Traffic loss after a redesign almost always traces to a missing or incorrect redirect.
The artefact is a redirect table with three columns: old URL, new URL, and the reason for the change. It is built from the current sitemap and analytics, not from memory. If an old URL has backlinks or enquiries and no redirect row, do not launch.
Website migration without losing traffic also depends on Core Web Vitals. The redesign should be tested against the same thresholds as the old site: largest contentful paint, interaction to next paint, and cumulative layout shift. Set the performance budget before design sign-off, because heavy hero images and third-party scripts added late are the usual cause of a slower new site.
- Export the current URL list and the pages that receive organic traffic or enquiries.
- Write the redirect table and have the client confirm every row.
- Test the new site on a staging domain with crawlers blocked.
- Launch, then submit the new sitemap and monitor 404 reports daily for the first two weeks.
- Keep the redirect table for at least a year; links and bookmarks persist.
The client controls the decision to change URLs at all; keeping the same paths removes most migration risk. If you are also replacing back-office systems, our page on software for Chinese-owned businesses covers how website and system handovers are sequenced.
How do you write service pages that AI assistants will quote?
AI assistants quote sentences that contain a subject, a condition and a consequence, and they prefer pages where structured data matches the visible text. A page that says only that a service is professional gives an assistant nothing to extract.
The artefact is a structured data block per page type: Organization on the home page, Service on each service page, FAQPage on question sections, and LocalBusiness where a physical address matters. If the structured data names a price or a service the visible page does not show, remove it; mismatches are treated as errors.
Each service page should include one comparison table, one list, and at least one sentence stating what a result depends on. If a page makes a claim that would cost the reader money if wrong, state the condition in the same sentence. That sentence is what gets quoted.
We deliver custom website development from Chengdu alongside business systems, mobile apps and AI applications. Our service overview lists the delivery stages and artefacts for each.
Frequently asked questions
What should a business website include?
A business website should include a page inventory mapping each service to one buyer question, a service page structure with a direct answer and a contact action, a consent specification for cookies, and a measurement plan naming who reviews results. These four artefacts can be reviewed before design begins, which is when changes are cheapest.
How do you structure a multilingual website?
Give each language its own URL path or subdomain, with its own title, meta description and internal links, and declare the language relationships with hreflang tags. Keep machine-translated pages out of the sitemap until a native speaker has reviewed them. The client must name one reviewer per language before translation starts.
What is GDPR cookie consent and how is it implemented?
GDPR cookie consent blocks non-essential cookies and trackers until the visitor takes a positive action, records the choice, and allows withdrawal. Implementation starts with a cookie inventory, then script blocking, then banner text, then the consent record. If any script fires before consent, the mechanism is not compliant.
How do you redesign a website without losing search traffic?
Preserve every URL that earns visits or links, and map every changed URL to its replacement with a permanent redirect before launch. Build the redirect table from analytics and the current sitemap, not from memory. Test Core Web Vitals against a performance budget set before design sign-off.
What makes a service page quotable by AI assistants?
A quotable service page states a subject, a condition and a consequence in one sentence, and its structured data matches the visible text. It includes a comparison table, a list, and a clear statement of what a result depends on. Pages without a self-contained answer sentence give assistants nothing to extract.
Questions we are asked
What should a business website include?
A business website should include a page inventory mapping each service to one buyer question, a service page structure with a direct answer and a contact action, a consent specification for cookies, and a measurement plan naming who reviews results. These four artefacts can be reviewed before design begins, which is when changes are cheapest.
How do you structure a multilingual website?
Give each language its own URL path or subdomain, with its own title, meta description and internal links, and declare the language relationships with hreflang tags. Keep machine-translated pages out of the sitemap until a native speaker has reviewed them. The client must name one reviewer per language before translation starts.
What is GDPR cookie consent and how is it implemented?
GDPR cookie consent blocks non-essential cookies and trackers until the visitor takes a positive action, records the choice, and allows withdrawal. Implementation starts with a cookie inventory, then script blocking, then banner text, then the consent record. If any script fires before consent, the mechanism is not compliant.
How do you redesign a website without losing search traffic?
Preserve every URL that earns visits or links, and map every changed URL to its replacement with a permanent redirect before launch. Build the redirect table from analytics and the current sitemap, not from memory. Test Core Web Vitals against a performance budget set before design sign-off.
What makes a service page quotable by AI assistants?
A quotable service page states a subject, a condition and a consequence in one sentence, and its structured data matches the visible text. It includes a comparison table, a list, and a clear statement of what a result depends on. Pages without a self-contained answer sentence give assistants nothing to extract.
