Client
KingConn
Sector
Manufacturing · Taoyuan
Lines
Grow-Search, SEO GEO AEO, Site Rebuild
A 1,500-page catalogue. First scan: 3 of 12 AI answers cited it.
Where it stood
A connector manufacturer in Taoyuan with a bilingual catalogue of about 1,500 pages. The site was run by the previous web vendor as a managed template and nobody had ever worked on search: buyers who already knew the company name found it, buyers who described the part did not. The first citation scan, on 2026-08-25, found the domain in 3 of 12 question-and-engine pairs.
What we were asked to move
01
Be findable by the people who describe the part
Non-brand Google clicks over 28 days: 128 on 2026-09-14 → 256
02
Be the source an AI assistant quotes
Citation rate across three engines: ≥ 60%
03
Turn that into enquiries we can trace
Enquiries carrying a source chain: ≥ 3 a month
The plan
Make the catalogue itself the asset that gets found and quoted, rather than buying traffic to sit on top of it.
Keep the search work separate from the hosting handover. The previous vendor managed the site but never did search, so this is the layer nobody had done — not a replacement for them.
What we did for KingConn
What we do for them: search (SEO, AI citations) and the website itself.
Catalogue rebuilt in four languages; every legacy URL given a 301 map.
Indexation verified one URL at a time — one URL Inspection API call per submitted URL, the whole set, not a sample (1,412 of 1,508 on 2026-09-07).
28 facet, glossary and cross-reference pages added across four languages (2026-09-11).
A cross-reference table mapping 39 discontinued sockets to 22 of the client's own part numbers, in four languages (2026-09-02).
The 27 Chinese guides rewritten to depth — median 329 → 852 words, in-page figures 27 → 244, every figure a real product photograph the site already owned (2026-09-15).
A three-field quick enquiry added to the part-number pages, posting to the same endpoint as the full form (2026-09-14).
Search Console pulled every morning by a scheduled job and appended to a ledger; citations scanned weekly.
What we changed after measuring
The citation scan went from one engine to three on 2026-09-07, 18 questions each. That is a change of ruler, so it is printed on the chart rather than smoothed over.
High-ranking queries with no clicks turned out to be answers quoted inside Google's AI overview — 37 of 52 tracked queries had one — so the tracker grew a column for it.
Three signals were dropped once checked: a 504 that was early hints, a foreign query that matched a phone rather than a part, and one noisy number that was taking half the clicks.
What it did
Four series, each read from a dated file. The first is Cloudflare's own edge log: 311,667 requests over fifteen days, daily uniques averaging 2,967 then 3,980. The ruler change on 2026-09-07 is on the chart.
Catalogue rebuilt in four languages; every legacy URL 301-mapped. Indexation verified per URL. The client agreed to be named on 2026-09-15.
Search Console logged daily; citations scanned weekly.