Paper pallet exporter — full SEO optimization
Rebuilt the SEO structure so an export-focused B2B site is read accurately by both search engines and potential buyers.
A B2B manufacturer that makes paper pallets and exports them internationally. Product info and certifications were well-documented, but search engines couldn't read the site structure, so potential buyers struggled to find the site.
SEO for a B2B export site has a different texture than a typical B2C site. Search volume is small, but almost everyone running those searches is a near-decision-maker — a potential buyer — and a single organic visit can turn into a substantial contract. So what matters isn't keyword volume; it's whether the people specifically looking for your product can find your site cleanly.
This paper pallet manufacturer had product information, technical sheets, and certifications nicely laid out on the site. But once we looked at how search engines were actually seeing the site, signals were leaking in several places.
The first thing we found was missing hreflang in the multilingual setup. The site ran in two languages — Korean and English — but there was no signal anywhere telling search engines that the two language versions corresponded to each other. From a search engine's point of view, the same company's same product looked like two unrelated pages, and in the worst case those pages could end up flagged as duplicate content. Someone searching from Korea should land on the Korean page; someone searching from the US or Europe should land on the English page. That mapping simply wasn't there.
Structured data on product pages was also absent. Without Product schema, search engines weren't explicitly recognising these pages as "pages for a product called paper pallet". Even with rich certification, spec, and material info on the page, none of it qualified to show up as rich content in search results.
Per-page metadata was inconsistent too. The Korean homepage leaned into a "company introduction" tone, the English homepage used a different tone, the product category pages used yet another format — tone and keyword mapping were scattered across the site. The sitemap was an older version, and robots.txt had no policy for the multilingual paths.
We started the work with the multilingual SEO layer. We added hreflang on every page in both directions. For example, /ko/products/eco-pallet declared itself as ko-KR and its English counterpart as en; /en/products/eco-pallet did the symmetric declaration back. We set x-default to the English page so that regions without an explicit language match would default to English. Getting search engines to recognise the two language pages as "the same content in two languages" was the starting point of everything that followed.
Next was the metadata and schema cleanup for product categories and individual product pages. We unified titles into a "{product name} | {category} | {company name}" format, and built the meta description so it auto-assembles the product's core specs, dimensions, and certifications. Product JSON-LD included product name, material, dimensions, manufacturer, and certification info; the company information area carried Organization JSON-LD with business info, contact details, social links via sameAs, and the business registration number.
We rebuilt the sitemap to match the multilingual structure. It now includes every public page under /ko and /en, with the corresponding hreflang information reflected in the sitemap itself. The robots.txt got a clear multilingual path policy, and we blocked private areas (/ko/admin, /en/admin and similar) on both sides.
Finally we sorted out OG and Twitter metadata and finished Search Console registration and verification. On a multilingual site, OG tags also need to vary by language so that social shares show the correct-language preview — we handled that as well.
The directly measurable changes after the work were clear. Bidirectional hreflang mapping is applied across all multilingual pages, Product and Organization JSON-LD pass the validation tools, and the sitemap correctly reflects the multilingual structure. B2B export sites are an area where the structure you put in place once tends to compound over a long horizon, so this cleanup laid the foundation for potential buyers to find the site cleanly whether they're searching in Korean or English.
Outcome points
- 01Product and category page meta cleaned up
- 02Sitemap and robots brought up to date
- 03Search engine structural recognition stabilized
- 04Foundation in place for global search visibility
Problems found
- Titles and meta descriptions varied page by page
- No search intent separation across product category pages
- Sitemap and robots stuck on old versions
- No structured data — product information wasn't reaching search clearly
- Multilingual SEO essentials like hreflang were missing
Work performed
- Redesigned site-wide title and meta description templates
- Separated search intent across product, category, and company pages
- Applied Organization, Product, and BreadcrumbList structured data
- Regenerated the sitemap and cleaned up robots.txt
- Cleaned up hreflang across the multilingual pages
- Registered and verified Search Console, requested indexing
- Tidied OG tags and social sharing meta
Specific edits
- Site-wide headBidirectional hreflang ko-KR / en + x-default=enSo multilingual pages aren't treated as duplicate content, and the right page surfaces for the searcher's region and language.
- Product page headAdded Product JSON-LD (name, material, dimensions, manufacturer, identifier=cert number)Search engines now explicitly recognize the page as a product page. Certifications and specs can show up richly in results.
- Footer (both languages)Inserted Organization JSON-LD (business registration, contact, sameAs)The most important signal for a B2B export site — a verifiable business — is now explicit to search engines and AI.
- Meta descriptionsTemplate auto-composes product specs, dimensions, and certificationsBuyers can grasp the key facts (specs, certifications) right from the first line of a search result.
- sitemap.xmlReflects the multilingual structure with xhtml:link rel=alternate hreflang per URLSearch engines see the multilingual mapping explicitly through the sitemap.
- robots.txtDisallow private paths in both languages (/ko/admin, /en/admin, etc.)On multilingual sites, blocking only one language leaves the other exposed. Both need cleanup at once.
- OG / Twitter metaPer-language branches (og:locale=ko_KR / en_US)When shared, the preview matches the viewer's language.
Before / After
| Item | Before | After |
|---|---|---|
| hreflang (language mapping) | Missing site-wide | Bidirectional ko-KR / en + x-default applied |
| Product JSON-LD | Not applied | Includes product name, material, dimensions, manufacturer, certifications |
| Organization JSON-LD | Not applied | Includes business info, contact, sameAs, business registration number |
| Multilingual meta consistency | Korean and English had different tones and formats | One template per language; keyword mapping aligned across both |
| Sitemap multilingual structure | Old version, single language only | Both languages included with hreflang information |
| Per-language OG | Identical meta on both languages | OG meta separated per language |
Timeline
- 01Week 0 - Diagnosis
- Audited multilingual setup: hreflang, canonical, sitemap
- Audited product and company info meta and schema
- Prioritized from a global SEO perspective
Locked multilingual cleanup as the top priority
- 02Week 1 - hreflang and language mapping
- Added bidirectional hreflang declarations site-wide
- Set x-default to English
- Audited the multilingual page mapping table
Search engines started treating the two language pages as the same content in different languages
- 03Week 2 - Meta and schema
- Applied a single title and meta description template
- Product JSON-LD (specs, certifications, manufacturer)
- Organization JSON-LD (business info, sameAs)
- Per-language OG and Twitter meta
- 04Week 3 - Sitemap and indexing
- Regenerated sitemap.xml with the multilingual structure
- Cleaned up robots.txt for multilingual paths
- Registered Search Console for both languages, verified, requested indexing
Potential buyers searching in either language can now find the site reliably
Summary
- Search foundation rebuilt for a B2B export site
- Stronger product information delivery to search engines
- Global SEO environment stabilized
If you need similar work, start with the free audit or get in touch directly.