The case does not identify the brand, show confidential prototypes, or use unauthorized traffic, ranking, enquiry, or AI citation data.
Context and constraints
The company has several product families, cross-industry applications, technical resources, and Chinese and English content. The old site had products, applications, news, downloads, and enquiry paths, but the links between them were unclear.
The new site needed to help buyers find products and make technical choices. It also needed to help search and AI understand what the company provides, where products fit, what limits apply, and where facts come from.
Core problems
- Product facts, applications, technical articles, and downloads were not linked consistently.
- Chinese and English page pairs could not be guessed safely from titles or paths.
- FAQs needed to appear on relevant pages without creating many thin pages.
- Old URLs, canonicals, hreflang, sitemaps, and release refresh had to agree before launch.
- Enquiry source tracking needed the actual page context, not only “website.”
Step 1: decide what each page type should explain
Products, categories, use cases, solution areas, technical documents, downloads, FAQs, cases, and enquiry context were listed before page types were defined. Each page answers its own main question without copying everything from related pages.
A product page explains what the product is, who it fits, and how to choose it. A use-case page explains the task, solution, and integration. Guides hold longer explanations.
Step 2: show FAQs on the pages where they help
Each FAQ records its category, related product or use case, source, and language. Pages only show relevant questions, and FAQPage data only includes answers visible to users.
Simple questions stay on the page and in the FAQ center. Questions that need tables, parameters, or a process become full guides.
Step 3: keep SEO/GEO information in sync with the page
Titles, descriptions, canonicals, hreflang, schema, old URLs, sitemaps, and enquiry sources follow the real state of the product, use case, article, or FAQ. Unconfirmed translations do not receive hreflang. Unpublished facts do not enter schema.
Completed deliverables
- Complete page structure and hierarchy.
- Required content and purpose for each core page type.
- FAQ grouping, linking, and structured data rules.
- Language mapping and SEO field requirements.
- Old URL, launch, CDN refresh, and rollback rules.
- Frontend and backend responsibilities, tests, and launch checklist.
The most important lesson from this project
A GEO-first site is not a normal website with a few extra modules. Company knowledge must be clear, important claims need sources, and someone must own future updates.