Image and Case Study SEO: Make Portfolio Work Discoverable

The short version #

Case study pages and portfolio images are the most under-leveraged SEO assets on most Chinese exporters' websites. Overseas buyers don't search for "professional team." They search for "steel structure warehouse case study Vietnam," or "injection molding supplier ISO 9001 Germany." The entry points for those long-tail queries almost always sit on a case page. A case study with real numbers and a clear shape pulls organic traffic, gets quoted in AI Overviews, and doubles as a link your sales team can paste into a follow-up email.

Most case pages we audit do the opposite. The H1 says "Project Case for a Client." The body is one paragraph of "after thorough communication, we successfully delivered." Every actual fact, including the dimensions, the tolerances, the certifications, is baked into a 3MB collage with the filename IMG_8392.jpg and an empty alt attribute. Google can't read pixels. AI summaries can't quote them.

This piece walks through how to fix that: a reusable page skeleton, the image-level must-dos, how to wire case studies into your service pages and blog, and why the English case page is not a translation of the Chinese one.

A real example #

Last year a precision metal parts manufacturer came to us. Their European sales team hadn't booked a new inquiry in six months. We opened their site and found 12 case studies, all titled "Project XX Case Study," URLs like /case/202304_01.html. Each had a 200-word body and 5–8 huge images. The actual specs (dimensions, tolerance, material, certifications) were handwritten onto the photos. None of it appeared in HTML text.

We didn't redesign anything. One thing changed: we pulled the text out of the images and into the body, renamed every file (e.g. precision-cnc-aluminum-bracket-aerospace-tier1.jpg), wrote real alt text and captions, and rewrote each H1 in the format "industry + process + key parameter." Three months later those 12 pages had pulled in 47 overseas inquiries, about half landing directly on a case page from a long-tail search.

Not a miracle. That is how case pages were always supposed to work. We documented a similar before-and-after in our old website rebuild case study, same playbook, different industry.

Page skeleton #

A case page that ranks, converts, and gets cited by AI follows a fixed shape:

• Background: who the client is (real name with permission, otherwise a description like "a German Tier 1 automotive supplier"), when the project ran, and how big it was.
• Problem: the specific issue the client came to you with. Not "the client wanted higher efficiency." Write "the previous supplier ran a 92% yield rate and could not pass IATF 16949 audit."
• Solution: what you actually did, broken into phases or steps. Numbers wherever possible.
• Outcome: verifiable metrics. "Yield rate from 92% to 98.5%, lead time from 21 days to 14, zero customer complaints on the first 5,000 units" is exactly the kind of sentence AI Overviews like to quote.
• Industry and stack: a dedicated section listing industry, process, equipment, certifications, and materials. This is where long-tail searches actually hit.
• Next step: a link to the relevant service page, plus a contact path or "discuss a similar project" CTA.

Wrap each section in an H2 or H3. Don't dump everything into a wall of paragraphs. Google's SEO Starter Guide is direct on this point: clear heading hierarchy improves indexing.

Write one H1, in the format "industry + process or product + client characteristic or region." "Precision CNC Aluminum Brackets for a German Tier 1 Aerospace Supplier" outperforms "Aerospace Project Case" on long-tail coverage by an order of magnitude.

Image must-dos #

On a case page, every image plays three roles at once: visual evidence, SEO entry point, and AI summary fodder. Run each one through this list:

• Filename: lowercase, hyphenated, information-dense. precision-cnc-aluminum-bracket-aerospace.jpg works. IMG_8392.jpg does not. Even on a Chinese site, use English filenames so Google Images can index them.
• Alt text: describe what's happening, don't stuff keywords. "Five-axis CNC machining of an aluminum aerospace bracket, surface roughness Ra 0.8" is far more useful than "high-quality manufactured product image." Decorative images get an empty alt (alt=""), not "decorative image."
• Caption: the line below the image. Google routinely pulls captions into SERPs and AI Overviews. Use it for specific parameters, processes, or client industry context.
• Compression: convert everything to WebP or AVIF, target under 200KB per image. Hero images get loading="eager", anything below the fold gets loading="lazy".
• Never put critical text only in images: dimensions, tolerances, technical specs, client names, prices, CTAs. All of these have to live in HTML text. If they're in the image, they must also be in the body.

That last point is where Chinese manufacturers most often trip up. A single collage that summarizes the entire project looks polished, but Google reads HTML, not pixels. If the image is the only place a fact exists, that fact does not exist for search.

Don't over-stack images #

We've seen case pages open with 30 images, take 12 seconds to load, and post a 78% bounce rate. Four to eight images per case is the sweet spot:

• 1 hero image (above the fold, eager-loaded)
• 1–2 detail shots (process or product close-up)
• 1–2 process shots (production, assembly, or testing in action)
• 1 outcome shot (delivery, in-service use, or inspection report)
• Optional: 1 client logo or a screenshot of a written testimonial (with permission)

Every one gets a caption. Extra photos go in a separate project gallery page, not piled onto the main case study.

Cases, services, blog #

Case pages are not islands. A content network that actually drives traffic has cases, service pages, and blog posts citing each other:

• Case to service page: at least one natural anchor in the body, like "we ran this project through our website rebuild service standard process."
• Service page to 2–3 cases: a "Related Case Studies" block at the bottom of every service page, each entry with a one-line summary plus a key metric.
• Blog to case as evidence: when a blog post like "SEO for export factories" needs proof, link to the case page that backs the claim.

Vary anchor text. Use five or six different phrasings ("website rebuild case study," "overseas website launch case," "SEO audit example") instead of repeating "click here." For the broader internal linking pattern, see Internal Linking Strategy for Service Businesses.

If you have the engineering bandwidth, add Article or CaseStudy schema so Google understands these are factual content, not marketing landings. Implementation walkthrough in Schema Markup for Service Websites.

Don't translate #

The Chinese case study and the English case study are not translations of each other. They are two independent pieces of content:

• Client identity: in Chinese you might write "a precision injection molding factory in the Yangtze River Delta." In English, write "a Chinese precision injection molding manufacturer based in the Yangtze River Delta region." Most overseas readers don't know where that is and won't look it up.
• Certifications and standards: a Chinese reader recognizes "ISO 9001 + IATF 16949" instantly. An English reader needs context. IATF 16949 is the supply-chain qualification gate for European and North American automakers. Spell that out.
• Numeric units: tons vs metric tons, square meters vs square feet, RMB quotes vs USD or EUR. If a buyer has to do unit conversion in their head, most will close the tab.
• Keywords don't overlap: a Chinese buyer searches "精密注塑案例." An English buyer searches "precision injection molding case study" or "ISO 9001 injection molding supplier China." The long-tail queries have almost no overlap.

For a deeper take on the difference, see Localized SEO vs Direct Translation. Our default workflow: the Chinese project manager writes a fact sheet (background, specs, actions, results), then a native English writer rebuilds it around what an overseas buyer cares about. A final pass cross-checks numbers and client names against the Chinese version.

Must-do, worth-doing, can-wait #

Case study SEO needs ruthless prioritization. Here's the default order we give clients:

Must do (P0):

• Rewrite case page H1s in "industry + process or product + client characteristic" format.
• Rename, alt, and caption every image on every case page.
• Lift critical specs out of images and into HTML text.
• At least one link from each case page to the relevant service page.

Worth doing (P1):

• Add Article or CaseStudy schema to every case.
• Add a "Related Case Studies" block at the bottom of each service page.
• Standardize the case page template so new cases are quick to publish.
• Write Chinese and English versions independently, never as translations.

Can wait (P2):

• Video case studies (high production cost, limited organic traffic).
• Localizing into a third or fourth language (lock down Chinese and English first).
• Custom cover art per case (product photography is enough).
• Paid promotion of case pages (let organic data run first, then decide).

Trying to ship all 16 in one quarter is how teams burn six months and have nothing to show the boss. Do the P0 list, watch three months of data, then promote items from P1 based on what the data tells you.

What to watch after launch #

For the first 30 days after restructuring case pages, three numbers matter:

1. Search Console impressions and clicks: which cases start picking up long-tail impressions? Which queries are triggering AI Overviews?
2. GA4 engaged sessions on case pages: are visitors actually reading, or bouncing in five seconds? High bounce usually means images are too heavy or the body is too thin.
3. Inquiry attribution: do form and WhatsApp messages start mentioning specific cases? This is the hardest signal to track and the most valuable.

Method-level detail in How to Measure SEO with Search Console and Analytics. For a fuller post-launch playbook on a content-driven WordPress build, see our WordPress overseas website case study.

FAQ #

How long should a case page be? #

Long enough to cover the facts. 600 words plus images is fine for a focused case. 1,500–2,000 works for a multi-phase project. Don't pad with "this industry has bright prospects" or "we will continue to strive" to hit a word count. Both Google and AI summaries downrank that. The actual ranking signal is fact density: numbers, named clients, specific processes, concrete actions in every paragraph.

What if the client won't let us use their real name? #

Fall back to industry + region + scale. "A German Tier 1 automotive supplier" or "a Southeast Asian electronics OEM operating three plants" carries far more SEO weight than "a certain client." Then negotiate one or two specific numbers you can publish (capacity, lead time, yield rate). Numbers are themselves trust signals.

How often should we publish a new case? #

For a small team: one in-depth case per month, plus a quarterly industry roundup. That beats weekly low-effort posts every time. After each new case ships, go back to the relevant service page and recent blog posts and add internal links. After five or six cases you have a self-reinforcing content network.

Should we use an image carousel on case pages? #

No. Most users never reach the second slide, and carousels hurt loading performance. Lay images out vertically, in problem → solution → outcome order. Both conversion rate and SEO improve.

Get a diagnosis #

If your case pages are eating server bandwidth without producing inquiries, send us your case page URLs and target markets. We'll run a free initial review under our overseas website build and SEO/GEO support service, walk through this checklist line by line, and tell you which pages will lift just from H1 and image fixes, which need a full body rewrite, and which should come down entirely.