Table of Contents
ToggleUK · USA · Germany · Japan
Format: Hands-On Live Project A–Z | aiseojournal.net | May 2026
SECTION 0 — PROJECT BRIEF & INTERNATIONAL FRAMEWORK
The Single Mistake That Kills Every International SEO Project Before It Starts
Most clothing manufacturers attempting international expansion translate their UK landing page into three other languages, point all versions at the same URL, and wait for rankings to appear.
They wait a long time.
Google does not rank a translated page as an international page. It ranks a page that signals, through technical structure, content specificity, and entity corroboration, that it belongs to a specific market. A German fashion brand founder searching on Google.de for “Bekleidungshersteller” will not find a UK-hosted page that happens to have been run through DeepL — not because Google cannot find it, but because Google has no confidence that the page is genuinely relevant to the German market.
This project builds that confidence. Systematically. For four markets.
Pro Tip: The most common international SEO failure is treating translation as equivalent to localisation. Translation changes the words. Localisation changes the currency, the date format, the trust signals, the legal compliance layer, the search engine targeting, and the buyer psychology. Every section of this project addresses localisation, not translation.
0.1 — The Four Markets and Why They Were Chosen
United Kingdom — the home market. London as HQ with established brand equity, UKFT membership, and a 17-year trading history. The baseline against which all other market expansions are measured.
United States — the largest English-language fashion manufacturing market outside the UK. High search volume, high competition, and a distinct buyer vocabulary (“apparel” not “clothing”, “cut and sew” not “garment manufacturing”). FTC Green Guides add a compliance layer absent from UK content.
Germany — the highest-value European market for B2B fashion. German buyers have the strictest ethical certification expectations in Europe, the highest average order values, and the most thorough decision-making processes. GOTS and OEKO-TEX are not differentiators in Germany — they are baseline expectations.
Japan — the most relationship-oriented B2B market on this list. Japanese fashion brands (from Harajuku independents to established Tokyo labels) expect the highest quality standards, non-negotiable sampling processes, and a manufacturing partner who understands the monozukuri (ものづくり) philosophy of production perfection.
0.2 — What the Single-Location and Multi-Location Projects Built
The single-location UK project built the London foundation: 35-keyword cluster, on-page specification, 3,200-word landing page, 3 schema blocks, full GBP, 15 citations, GA4 + GTM setup, and a 12-month action plan.
The multi-location UK project expanded to Manchester, Birmingham, Bristol, and Glasgow: location hub page, 5 city landing pages, per-location schema, per-location GBP, 75 citation submissions, cannibalisation management, and internal linking silo.
This international project adds the four-country layer on top of that UK foundation. It does not replace the UK work — it extends it. The UK market continues running the multi-location strategy. This project adds three new country strategies: USA, Germany, and Japan.
0.3 — Project Architecture Overview
| Layer | UK | USA | Germany | Japan |
|---|---|---|---|---|
| URL structure | /clothing-manufacturer-[city]/ | /us/apparel-manufacturer-[city]/ | /de/bekleidungshersteller-[stadt]/ | /ja/apparel-manufacturer-[city]/ |
| Language | en-GB | en-US | de-DE | ja-JP |
| Hreflang | en-GB | en-US | de-DE | ja-JP |
| Currency | GBP (£) | USD ($) | EUR (€) | JPY (¥) |
| Primary search engine | Google.co.uk | Google.com | Google.de | Google.co.jp |
| Secondary search engine | — | Bing (15%) | — | Yahoo! Japan (19%) |
| Schema addressCountry | GB | US | DE | JP |
| GBP listing | ✅ Per UK location | ✅ Per US location | ✅ Per DE location | ✅ Per JP location |
| Primary certification trust signal | UKFT, Made in Britain | WRAP, FTC-compliant | GOTS, OEKO-TEX | GOTS, ISO 9001 |
| Content language | English (UK) | English (US) | German | Japanese |
0.4 — Canonical NAP Per Market
International businesses commonly make NAP errors across markets. Define each market’s NAP before any submission, any schema block, or any GBP listing is created.
UK (established — from multi-location project): Meridian Cloth Co. | [Street], London, [EC Postcode], England, UK | +44 20 XXXX XXXX
USA: Meridian Cloth Co. | [Street], [City], [State] [ZIP], United States | +1 [Area Code] XXX XXXX
Germany: Meridian Cloth Co. | [Straße], [PLZ] [Stadt], Deutschland | +49 [Vorwahl] XXXX XXXX
Japan: Meridian Cloth Co. | [住所], [市区町村], [都道府県], 日本 | +81 [市外局番] XXXX XXXX
Pro Tip: Every country has a different phone number format convention. In Germany, local numbers are written without the country code in directory listings (0XX XXXX XXXX) but schema requires the international format (+49 XX XXXX XXXX). In Japan, Tokyo numbers are written as 03-XXXX-XXXX locally but +81-3-XXXX-XXXX in schema. Build a NAP format guide per market before any submissions begin.
0.5 — Project Delivery Timeline
| Section | Task | Est. Hours |
|---|---|---|
| S0 | Framework + architecture + NAP register | 2 |
| S1 | Keyword research — 4 markets | 10–14 |
| S2 | URL structure + site architecture decisions | 2 |
| S3 | Hreflang strategy + implementation | 3 |
| S4 | Landing page specs + Quick Answer blocks | 14–18 |
| S5 | Schema library — all 4 markets | 5–6 |
| S6 | GBP + local signals per market | 8–10 |
| S7 | Citation strategy per market | 8–10 |
| S8 | Content architecture — clusters per market | 4–6 |
| S9 | Technical SEO — international layer | 4–5 |
| S10 | Backlink strategy per market | 6–8 |
| S11 | Competitor analysis — 4 markets | 8–10 |
| S12 | GA4 + conversion tracking — international | 3 |
| S13 | 12-month action plan | 2 |
| S14 | Reporting template — per market + global | 2 |
| Total | Full international execution | ~85–110 hours |
✅ CHECKPOINT — SECTION 0
- [ ] Location register complete: all 4 markets, all NAP fields confirmed
- [ ] URL structure agreed and confirmed with dev team before any pages built
- [ ] Canonical NAP string defined per market — locked before any submission
- [ ] Market-specific phone numbers assigned per country
- [ ] Project tracking sheet: 4 country tabs created
SECTION 1 — KEYWORD INTELLIGENCE — ALL 4 MARKETS
Why International Keyword Research Cannot Be Done From One Country
Running keyword research for Germany from a UK IP on Google.com produces incorrect volume data, incorrect competition scores, and SERP results that bear no resemblance to what a German buyer actually sees.
Every market in this project requires its own research session: correct search engine, correct language, correct location setting, and a native-language keyword list built from how buyers in that market actually describe the service.
Pro Tip: The single most valuable local keyword research tool for international SEO costs nothing. Go to the target search engine, set location to the target city, and begin typing the service in the target language. Google Autocomplete shows you exactly how local buyers phrase their searches — not how a UK-trained content strategist guesses they phrase them. Japanese buyers search for 「小ロット縫製」(small lot sewing), not a direct translation of “low MOQ clothing manufacturer.” German buyers search “Bekleidungsproduzent” and “Modefertigung” — both of which a direct German translation of “clothing manufacturer” would miss.
1.1 — UK Keyword Cluster (Established — Maintained from Previous Project)
The full 35-keyword cluster across 5 tiers was built in the single-location project. The international project adds one cross-market layer: queries where UK buyers are explicitly comparing international vs domestic production options.
Additional UK international-intent keywords:
| Keyword | Monthly Vol (est.) | Intent | Target Page |
|---|---|---|---|
| clothing manufacturer UK vs overseas | 50–150 | Commercial investigation | /blog/uk-vs-overseas-clothing-manufacturer/ |
| ethical clothing manufacturer UK | 200–600 | Commercial | /ethical-clothing-manufacturer/ |
| GOTS certified clothing manufacturer UK | 50–150 | Transactional | /ethical-clothing-manufacturer/ |
| clothing manufacturer with UK office | 50–100 | Transactional | /clothing-manufacturer-london/ |
| international clothing manufacturer UK based | 30–100 | Transactional | /international/ |
1.2 — USA Keyword Cluster
Research method: Google.com · Location set to New York, NY · en-US · Keyword Planner + Autocomplete + People Also Ask
| Tier | Keyword | Monthly Vol (est.) | Competition | Intent |
|---|---|---|---|---|
| T1 | apparel manufacturer USA | 1,000–3,000 | High | Transactional |
| T1 | clothing manufacturer USA | 800–2,500 | High | Transactional |
| T1 | clothing manufacturer New York | 300–900 | Medium | Transactional |
| T1 | apparel manufacturer Los Angeles | 400–1,200 | Medium | Transactional |
| T1 | clothing manufacturer for startups | 200–600 | Medium | Transactional |
| T1 | cut and sew manufacturer USA | 300–900 | Medium | Transactional |
| T2 | clothing manufacturer near me | 500–1,500 | High | Proximity |
| T2 | apparel manufacturer near me | 400–1,200 | High | Proximity |
| T2 | cut and sew near me | 200–600 | Medium | Proximity |
| T3 | clothing manufacturer California | 200–600 | Medium | Area |
| T3 | apparel manufacturer Chicago | 100–300 | Low | Area |
| T3 | clothing manufacturer Texas | 100–300 | Low | Area |
| T3 | apparel manufacturer Miami | 100–300 | Low | Area |
| T4 | low moq apparel manufacturer | 200–600 | Medium | Long-tail |
| T4 | ethical apparel manufacturer USA | 100–300 | Low | Long-tail |
| T4 | clothing manufacturer for small brands | 100–300 | Low | Long-tail |
| T4 | apparel manufacturer with no minimum order | 50–150 | Low | Long-tail |
| T4 | sustainable apparel manufacturer USA | 100–300 | Low | Long-tail |
| T4 | overseas clothing manufacturer for US brands | 50–150 | Low | Long-tail |
| T4 | UK clothing manufacturer for US brands | 30–100 | Low | Long-tail |
| T5 | how do I find a clothing manufacturer in the US? | 50–150 | Low | AI/Voice |
| T5 | what is the average cost of apparel manufacturing? | 100–300 | Low | AI/Voice |
| T5 | which country makes the highest quality clothing? | 50–150 | Low | AI/Voice |
| T5 | is it cheaper to manufacture clothing in the UK or USA? | 30–100 | Low | AI/Voice |
| T5 | how do I start a clothing brand with a manufacturer? | 200–600 | Low | AI/Voice |
Key US insight: “Cut and sew” is the dominant US manufacturing term that has no direct UK equivalent. UK manufacturers calling themselves “clothing manufacturers” in US content are immediately identifiable as non-US businesses to American buyers. Landing pages targeting US buyers must use “apparel manufacturer” and “cut and sew” in the H1 and primary H2.
1.3 — Germany Keyword Cluster (German language)
Research method: Google.de · Location set to Berlin · de-DE · Google Ads Keyword Planner (German account) + Google Autocomplete (German) + Google PAA (German)
| Tier | Keyword (German) | Translation | Monthly Vol (est.) | Competition |
|---|---|---|---|---|
| T1 | Bekleidungshersteller | Clothing manufacturer | 500–1,500 | Medium |
| T1 | Kleidungshersteller Deutschland | Clothing manufacturer Germany | 200–600 | Low-Medium |
| T1 | Bekleidungsproduzent | Apparel producer | 100–300 | Low |
| T1 | Textilhersteller für Modeunternehmen | Textile manufacturer for fashion companies | 50–200 | Low |
| T1 | Modefertigung | Fashion manufacturing | 100–400 | Low |
| T1 | OEM Bekleidungsproduktion | OEM clothing production | 100–300 | Low |
| T2 | Bekleidungshersteller in meiner Nähe | Clothing manufacturer near me | 100–300 | Medium |
| T2 | Textilfertigung in der Nähe | Textile manufacturing nearby | 50–150 | Low |
| T3 | Bekleidungshersteller Berlin | Clothing manufacturer Berlin | 50–200 | Low |
| T3 | Bekleidungshersteller München | Clothing manufacturer Munich | 50–150 | Low |
| T3 | Kleidungsproduktion Europa | Clothing production Europe | 100–300 | Low |
| T4 | Kleine Auflagen Bekleidungsproduktion | Small run clothing production | 50–200 | Low |
| T4 | Mindestbestellmenge Bekleidung | MOQ clothing | 50–150 | Low |
| T4 | Nachhaltiger Bekleidungshersteller | Sustainable clothing manufacturer | 100–300 | Low |
| T4 | GOTS-zertifizierter Hersteller | GOTS-certified manufacturer | 50–200 | Low |
| T4 | Bekleidungsproduktion für Startups | Clothing production for startups | 30–100 | Low |
| T4 | Britischer Bekleidungshersteller für deutsche Marken | UK clothing manufacturer for German brands | 10–50 | Very Low |
| T5 | Was kostet Bekleidungsherstellung? | How much does clothing manufacturing cost? | 50–150 | Low |
| T5 | Wie finde ich einen Bekleidungshersteller? | How do I find a clothing manufacturer? | 30–100 | Low |
| T5 | Welche Zertifizierungen braucht ein Bekleidungshersteller? | What certifications does a clothing manufacturer need? | 20–80 | Low |
| T5 | GOTS oder OEKO-TEX — was ist besser? | GOTS or OEKO-TEX — which is better? | 30–100 | Low |
Key German insight: German fashion brands do not search for “low MOQ” in the English sense. They search for “kleine Auflagen” (small runs) or “Mindestbestellmenge” (minimum order quantity). Volume searches are lower than UK or US — but conversion rates from German B2B buyers are typically higher because they have completed more research before making contact. A German buyer who fills in a quote form has already decided to buy.
1.4 — Japan Keyword Cluster (Japanese language)
Research method: Google.co.jp · Location set to Tokyo · ja-JP · Google Keyword Planner (Japanese account) + Google Autocomplete (Japanese) + Yahoo! Japan Keyword Tool
| Tier | Keyword (Japanese) | Romanisation | Translation | Monthly Vol (est.) |
|---|---|---|---|---|
| T1 | アパレルメーカー | Apareru mēkā | Apparel manufacturer | 300–1,000 |
| T1 | 縫製工場 | Hōsei kōjō | Sewing factory | 500–1,500 |
| T1 | OEM縫製 | OEM hōsei | OEM sewing | 200–600 |
| T1 | アパレルOEM | Apareru OEM | Apparel OEM | 200–600 |
| T1 | 服の製造メーカー | Fuku no seizō mēkā | Clothing manufacturing maker | 100–400 |
| T2 | 近くの縫製工場 | Chikaku no hōsei kōjō | Nearby sewing factory | 100–300 |
| T3 | 東京 縫製工場 | Tōkyō hōsei kōjō | Tokyo sewing factory | 100–400 |
| T3 | 大阪 アパレルメーカー | Ōsaka apareru mēkā | Osaka apparel manufacturer | 50–200 |
| T3 | 海外縫製工場 | Kaigai hōsei kōjō | Overseas sewing factory | 100–300 |
| T4 | 小ロット縫製 | Shō rotto hōsei | Small lot sewing | 200–600 |
| T4 | 少量生産 アパレル | Shōryō seisan apareru | Small volume production apparel | 100–300 |
| T4 | サステナブル縫製 | Sasutanaburu hōsei | Sustainable sewing | 50–200 |
| T4 | GOTS認証工場 | GOTS ninshō kōjō | GOTS certified factory | 30–100 |
| T4 | ファッションブランド立ち上げ 製造 | Fasshon burando tachiiage seizō | Fashion brand launch production | 100–300 |
| T4 | 英国 縫製工場 | Eikoku hōsei kōjō | UK sewing factory | 20–80 |
| T5 | 縫製工場 どう探す | Hōsei kōjō dō sagasu | How to find a sewing factory | 50–200 |
| T5 | アパレルOEMの費用は? | Apareru OEM no hiyō wa? | What is the cost of apparel OEM? | 50–150 |
| T5 | 小ロットで服を作るには | Shō rotto de fuku o tsukuru ni wa | How to make clothes in small lots | 100–300 |
| T5 | GOTS認証の取り方 | GOTS ninshō no torikata | How to obtain GOTS certification | 30–100 |
Key Japan insight: Japanese buyers use 縫製工場 (sewing factory) and OEM縫製 far more than any direct translation of “clothing manufacturer.” The concept of “manufacturer” in Japanese B2B fashion maps more closely to 工場 (kōjō — factory) than メーカー (mēkā — maker/manufacturer). Content targeting Japanese buyers that uses only アパレルメーカー will miss a significant portion of actual search behaviour.
✅ CHECKPOINT — SECTION 1
- [ ] UK keyword list: expanded with 5 international-intent additions
- [ ] USA cluster: 25 keywords across 5 tiers, “apparel” and “cut and sew” variants confirmed
- [ ] Germany cluster: 21 keywords in German, volume researched on Google.de
- [ ] Japan cluster: 19 keywords in Japanese, verified on Google.co.jp and Yahoo! Japan
- [ ] All keywords logged in Tab 1: separate column per country
SECTION 2 — URL STRUCTURE & SITE ARCHITECTURE
The URL Structure Decision That Affects Everything Else
Three options exist for international site architecture. Every other technical decision in this project flows from the choice made here.
Option A — Subdirectories (recommended for this project) meridianclothco.co.uk/us/ meridianclothco.co.uk/de/ meridianclothco.co.uk/ja/
Option B — Subdomains us.meridianclothco.co.uk de.meridianclothco.co.uk ja.meridianclothco.co.uk
Option C — ccTLDs meridianclothco.com (USA) meridianclothco.de (Germany) meridianclothco.co.jp (Japan)
This project uses Option A — subdirectories. Here is why:
Subdirectories consolidate all domain authority under one domain. Every link built to the US pages strengthens meridianclothco.co.uk. Every link built to the German pages strengthens the same domain. With separate domains or subdomains, link equity is split and each country starts from near-zero authority.
The counter-argument is that ccTLDs send stronger geotargeting signals to Google. That is true — but for a business without an established international link profile, the authority consolidation benefit of subdirectories significantly outweighs the geotargeting benefit of ccTLDs at this stage of the project.
Pro Tip: The ccTLD strategy makes sense when two conditions are met: the business has a large existing link profile per market (so splitting authority is not a concern) and the business has a physical registered entity in each country (which strengthens the ccTLD geotargeting signal considerably). Neither condition applies to Meridian Cloth Co. at this stage. Subdirectories are the correct choice.
2.1 — Full URL Map
International hub: /international/ — hub page listing all four markets
USA pages: /us/ — USA country hub /us/apparel-manufacturer-new-york/ /us/apparel-manufacturer-los-angeles/ /us/apparel-manufacturer-chicago/
Germany pages: /de/ — Germany country hub /de/bekleidungshersteller/ — primary German landing page /de/bekleidungshersteller-berlin/ /de/bekleidungshersteller-muenchen/
Japan pages: /ja/ — Japan country hub /ja/apparel-manufacturer-tokyo/ — primary Japan landing page /ja/apparel-manufacturer-osaka/
Blog (country-tagged): /blog/us/[slug]/ — US-targeted blog content /de/blog/[slug]/ — German-language blog content /ja/blog/[slug]/ — Japanese-language blog content
2.2 — Architecture Decisions
GSC geotargeting: Set geotargeting for each subdirectory in GSC:
- /us/ → United States
- /de/ → Germany
- /ja/ → Japan
- (root domain remains UK by default — correct given .co.uk TLD)
Sitemap structure: One XML sitemap per language version. Submit all four to GSC. /sitemap-en-gb.xml — UK pages /sitemap-en-us.xml — US pages /sitemap-de.xml — German pages /sitemap-ja.xml — Japanese pages
robots.txt: Confirm all four subdirectory structures are crawlable. Common error: a robots.txt Disallow rule that blocks /de/ or /ja/ as unintended side effects of blocking internal search pages.
Canonical rules per market: Every US page self-canonicalises to its US URL. Every German page self-canonicalises to its German URL. Every Japanese page self-canonicalises to its Japanese URL. No cross-language canonicals (e.g. German page canonicalising to English version — this is the single most common international SEO technical error).
✅ CHECKPOINT — SECTION 2
- [ ] URL structure: subdirectory approach confirmed with dev team
- [ ] GSC: geotargeting set per subdirectory — /us/, /de/, /ja/
- [ ] Four XML sitemaps prepared and submitted to GSC
- [ ] robots.txt checked: no unintended blocks on international subdirectories
- [ ] Canonical rules confirmed: self-referencing per country, no cross-language canonicals
SECTION 3 — HREFLANG STRATEGY & IMPLEMENTATION
Why Hreflang Errors Are the Most Damaging International Technical Mistake
Hreflang tells Google which version of a page to serve to which user based on language and country. When implemented correctly, it eliminates cannibalisation between language versions and improves ranking confidence in each market.
When implemented incorrectly, it causes Google to serve the wrong language version to the wrong market, can suppress all international versions simultaneously, and creates cannibalisation between the UK and international pages.
The most common errors: missing reciprocal tags (page A points to page B but page B does not point back to page A), missing x-default, using language-only codes without country codes (lang=”de” instead of lang=”de-DE”), and canonical tags conflicting with hreflang tags.
Pro Tip: Hreflang and canonical tags must always agree. If a page’s canonical points to its English version, the hreflang tags on the German and Japanese versions are effectively ignored — Google will treat the canonical as the master and discount the language variants. Every international page must self-canonicalise (canonical = its own URL) before hreflang will work correctly.
3.1 — Hreflang Tag Set — International Hub Page
<!-- On every page that has international equivalents — place in <head> -->
<link rel="alternate" hreflang="en-GB" href="https://www.meridianclothco.co.uk/international/" />
<link rel="alternate" hreflang="en-US" href="https://www.meridianclothco.co.uk/us/" />
<link rel="alternate" hreflang="de-DE" href="https://www.meridianclothco.co.uk/de/" />
<link rel="alternate" hreflang="ja-JP" href="https://www.meridianclothco.co.uk/ja/" />
<link rel="alternate" hreflang="x-default" href="https://www.meridianclothco.co.uk/international/" />
3.2 — Hreflang Tag Set — Location Landing Pages
Each location page pair must have complete hreflang sets pointing to every equivalent page across all four markets. Below is the complete set for the primary landing page per market.
UK primary page (/clothing-manufacturer-london/):
<link rel="alternate" hreflang="en-GB" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
<link rel="alternate" hreflang="en-US" href="https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/" />
<link rel="alternate" hreflang="de-DE" href="https://www.meridianclothco.co.uk/de/bekleidungshersteller/" />
<link rel="alternate" hreflang="ja-JP" href="https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/" />
<link rel="alternate" hreflang="x-default" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
USA primary page (/us/apparel-manufacturer-new-york/):
<link rel="alternate" hreflang="en-US" href="https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/" />
<link rel="alternate" hreflang="en-GB" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
<link rel="alternate" hreflang="de-DE" href="https://www.meridianclothco.co.uk/de/bekleidungshersteller/" />
<link rel="alternate" hreflang="ja-JP" href="https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/" />
<link rel="alternate" hreflang="x-default" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
Germany primary page (/de/bekleidungshersteller/):
<link rel="alternate" hreflang="de-DE" href="https://www.meridianclothco.co.uk/de/bekleidungshersteller/" />
<link rel="alternate" hreflang="en-GB" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
<link rel="alternate" hreflang="en-US" href="https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/" />
<link rel="alternate" hreflang="ja-JP" href="https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/" />
<link rel="alternate" hreflang="x-default" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
Japan primary page (/ja/apparel-manufacturer-tokyo/):
<link rel="alternate" hreflang="ja-JP" href="https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/" />
<link rel="alternate" hreflang="en-GB" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
<link rel="alternate" hreflang="en-US" href="https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/" />
<link rel="alternate" hreflang="de-DE" href="https://www.meridianclothco.co.uk/de/bekleidungshersteller/" />
<link rel="alternate" hreflang="x-default" href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/" />
3.3 — XML Sitemap Hreflang Entries
For sites with many pages, XML sitemap implementation is more maintainable than per-page HTML tags. Below is the sitemap entry format for the primary landing pages.
<url>
<loc>https://www.meridianclothco.co.uk/clothing-manufacturer-london/</loc>
<xhtml:link rel="alternate" hreflang="en-GB"
href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/"/>
<xhtml:link rel="alternate" hreflang="en-US"
href="https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/"/>
<xhtml:link rel="alternate" hreflang="de-DE"
href="https://www.meridianclothco.co.uk/de/bekleidungshersteller/"/>
<xhtml:link rel="alternate" hreflang="ja-JP"
href="https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/"/>
<xhtml:link rel="alternate" hreflang="x-default"
href="https://www.meridianclothco.co.uk/clothing-manufacturer-london/"/>
</url>
Namespace declaration required in sitemap root element:
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
3.4 — Hreflang Validation Checklist
| Check | Tool | Pass Condition |
|---|---|---|
| Every page has return tags | technicalseo.com/tools/hreflang/ | All reciprocal pairs confirmed |
| x-default set on all pages | Manual check | x-default on every hreflang set |
| All URLs https:// | Screaming Frog | 0 http:// in hreflang URLs |
| All URLs return 200 | Screaming Frog + GSC | No 404 or 301 in hreflang targets |
| No canonical conflict | Screaming Frog | Self-canonical on all international pages |
| Language codes correct | Manual check | en-GB not en-gb (case matters in XML) |
| No duplicate hreflang pairs | Manual check | Each language/country pair appears once |
✅ CHECKPOINT — SECTION 3
- [ ] Hreflang tags implemented: HTML head or XML sitemap (not both — pick one)
- [ ] Reciprocal tags confirmed: every page has return tags from all language equivalents
- [ ] x-default set on all pages pointing to en-GB primary
- [ ] Validated at technicalseo.com/tools/hreflang/ — 0 errors
- [ ] GSC: International Targeting report checked — no detected errors
SECTION 4 — LANDING PAGE SPECIFICATIONS — ALL 4 MARKETS
4.1 — USA Primary Landing Page
Primary keyword: apparel manufacturer USA URL: https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/ Title (56 chars): Apparel Manufacturer USA | Meridian Cloth Co. Meta (148 chars): US apparel manufacturer for fashion startups and independent brands. Low MOQ from 200 pieces. WRAP certified factories. Request a quote in 48 hours. H1: Apparel Manufacturer for US Fashion Brands — Low MOQ from 200 Pieces
Quick Answer Block:
Meridian Cloth Co. is an apparel manufacturer serving US fashion brands and startups from our international network of 8 sourcing countries. We work from a minimum order quantity of 200 pieces per style — below the threshold most US manufacturers require. Our factory network holds WRAP (40%), GOTS (25%), Fair Trade (15%), and SA8000 (20%) certifications, all verifiable by certificate number. US brands receive itemised quotes within 48 hours. Production lead times run 8–14 weeks from approved sample to delivered goods.
(Word count: 83. Numbers: 8 countries, 200 pieces, 40%, 25%, 15%, 20%, 48 hours, 8–14 weeks.)
H2 Structure:
- H2-1: Why Do US Apparel Brands Choose an Overseas Manufacturer?
- H2-2: What Does Apparel Manufacturing Cost for US Brands?
- H2-3: What Is the Minimum Order Quantity for US Startups?
- H2-4: Which Ethical Certifications Apply to US Apparel Manufacturing?
- H2-5: How Does the Production Process Work for US Clients?
- H2-6: What Are Apparel Manufacturing Lead Times for US Delivery?
- H2-7: FAQ — Apparel Manufacturing for US Fashion Brands
Pricing Table (USD):
| Garment Type | Per Unit (est.) | MOQ | Typical Source Country | Lead Time (wks) |
|---|---|---|---|---|
| Basic jersey T-shirt | $16–22 (£13–18) | 300 pcs | Bangladesh | 8–10 |
| Casual woven dress | $28–42 (£22–33) | 250 pcs | India / Bangladesh | 10–12 |
| Knitwear / sweater | $20–32 (£16–25) | 300 pcs | China / Portugal | 10–14 |
| Technical activewear | $32–45 (£25–35) | 300 pcs | Vietnam | 10–14 |
| Outerwear (jacket) | $55–90 (£43–71) | 150 pcs | Turkey / UK | 12–16 |
| Uniform / workwear | $22–55 (£17–43) | 200 pcs | Romania / UK | 10–14 |
| Sample development | $150–450/style (£118–354) | 1 style | Any | 3–5 |
Market rate estimates only — prices vary by fabric weight (GSM), construction complexity, trim specification, and sourcing country. All prices subject to exchange rate movement. Request an itemised quote for your specific project.
FTC Compliance Note (mandatory on all US pages): Ethical certification claims apply to specific factories in Meridian Cloth Co.’s network — not 100% of production. The percentage of factories holding each certification is stated above. Full certificate documentation available on request.
US-Specific FAQ Block (5 questions):
Q: Does Meridian Cloth Co. manufacture clothing in the United States? A: Meridian Cloth Co. is a UK-based apparel manufacturer with an international factory network spanning 8 countries — Bangladesh, India, China, Turkey, Portugal, Romania, Vietnam, and the United Kingdom. We do not operate manufacturing facilities inside the United States. US brands work with our London headquarters, with dedicated account managers handling all communication, sampling, and production management on their behalf. Quotes are returned within 48 hours of brief submission.
Q: What is the minimum order for US apparel brands? A: Our standard minimum order quantity is 200 pieces per style. This applies to all garment categories. Some garment types — particularly knitwear and outerwear — carry a 300-piece minimum due to factory setup costs. For repeat orders from established clients, reduced minimums are available on selected categories. We do not accept orders below 100 pieces per style under any circumstances.
Q: Are Meridian Cloth Co.’s factories WRAP certified? A: 40% of the factories in our active production network hold WRAP (Worldwide Responsible Accredited Production) certification. WRAP is one of the most widely recognised ethical manufacturing certifications in the US market. We can provide WRAP certificate documentation for specific factories assigned to your production order. Certificate numbers can be verified directly through the WRAP website at wrapcompliance.org.
Q: How do US brands handle customs, duties, and import logistics? A: All production is shipped on DDP (Delivered Duty Paid) terms for US clients where requested — meaning Meridian Cloth Co. handles customs clearance and import duties to the US delivery address. For US-destined production, we work with a freight forwarding partner experienced in US CBP requirements. Standard US import duty on clothing is 12–32% depending on garment category and HS code — we provide HS code classification as part of our standard service.
Q: What does “cut and sew” mean, and is it the same as what Meridian Cloth Co. does? A: Cut and sew is the US term for what the UK calls garment manufacturing — the process of cutting fabric panels and sewing them into finished garments. Meridian Cloth Co. operates a full cut and sew service including pattern making, grading, fabric procurement, cutting, assembly, finishing, and AQL quality inspection. We can also supply fabric-only (CMT — cut, make, trim) pricing for brands who source their own fabric.
Pro Tip: US fashion brands are 3–5 times more likely to request DDP (Delivered Duty Paid) terms than UK or European brands of equivalent size. Build DDP pricing into the standard US quote template from the outset rather than treating it as a special arrangement. The duty calculation alone — 12–32% depending on HS code — can significantly change the landed cost per unit and must be factored into the buyer’s margin calculations before they commit.
4.2 — Germany Primary Landing Page (German Language)
Primary keyword: Bekleidungshersteller (Deutschland) URL: https://www.meridianclothco.co.uk/de/bekleidungshersteller/ Title (58 chars): Bekleidungshersteller Europa | Meridian Cloth Co. Meta (153 chars): Britischer Bekleidungshersteller für deutsche Modemarken. Mindestbestellmenge ab 200 Stück. GOTS-zertifiziertes Fabriknetzwerk. Angebot in 48 Stunden. H1: Bekleidungshersteller für Deutsche Modemarken — Mindestbestellmenge ab 200 Stück
Quick Answer Block (German):
Meridian Cloth Co. ist ein britischer Bekleidungshersteller mit einem internationalen Fabriknetzwerk in 8 Ländern. Wir produzieren ab einer Mindestbestellmenge von 200 Stück pro Modell — deutlich unter dem Schwellenwert der meisten europäischen Hersteller. 25% unserer Produktionsstätten sind GOTS-zertifiziert, 40% WRAP-zertifiziert, 15% Fair Trade und 20% SA8000. Alle Zertifikate sind über die jeweiligen Zertifizierungsstellen direkt verifizierbar. Unverbindliche Angebote erhalten Sie innerhalb von 48 Stunden.
(Wortanzahl: 79. Zahlen: 8 Länder, 200 Stück, 25%, 40%, 15%, 20%, 48 Stunden.)
English translation for editorial reference: Meridian Cloth Co. is a British clothing manufacturer with an international factory network in 8 countries. We produce from a minimum order quantity of 200 pieces per style — significantly below the threshold of most European manufacturers. 25% of our production facilities are GOTS-certified, 40% WRAP-certified, 15% Fair Trade and 20% SA8000. All certificates are directly verifiable through the respective certification bodies. You will receive a non-binding quote within 48 hours.
H2 Structure (German):
- H2-1: Warum wählen deutsche Modemarken einen britischen Bekleidungshersteller?
- H2-2: Was kostet Bekleidungsherstellung für deutsche Marken?
- H2-3: Welche Mindestbestellmenge gilt für kleine Modemarken?
- H2-4: Welche Nachhaltigkeitszertifizierungen hat Meridian Cloth Co.?
- H2-5: Wie läuft der Produktionsprozess ab?
- H2-6: Wie lange dauert die Lieferung nach Deutschland?
- H2-7: Häufig gestellte Fragen zur Bekleidungsproduktion
Pricing Table (EUR — German market):
| Kleidungsstück | Pro Stück (ca.) | Mindestmenge | Typisches Produktionsland | Lieferzeit (Wochen) |
|---|---|---|---|---|
| Basic Jersey T-Shirt | €15–21 (£13–18) | 300 Stück | Bangladesch | 8–10 |
| Lässiges Webkleid | €24–38 (£20–32) | 250 Stück | Indien / Bangladesch | 10–12 |
| Strickware / Pullover | €18–30 (£15–25) | 300 Stück | China / Portugal | 10–14 |
| Technische Sportbekleidung | €28–40 (£24–34) | 300 Stück | Vietnam | 10–14 |
| Oberbekleidung (Jacke) | €48–80 (£41–68) | 150 Stück | Türkei / UK | 12–16 |
| Arbeitskleidung | €20–50 (£17–42) | 200 Stück | Rumänien / UK | 10–14 |
| Musterentwicklung | €135–400/Modell (£115–340) | 1 Modell | Alle Länder | 3–5 |
Preise sind unverbindliche Richtwerte. Die tatsächlichen Kosten variieren je nach Materialgewicht (g/m²), Konstruktionskomplexität, Zutatenspezifikation und Produktionsland. Alle Preise unterliegen Wechselkursschwankungen. Fordern Sie ein detailliertes Angebot für Ihr spezifisches Projekt an.
German-specific FAQ (5 questions — in German):
F: Produziert Meridian Cloth Co. auch in Deutschland oder Europa? A: Meridian Cloth Co. hat seinen Hauptsitz in London und verfügt über ein internationales Fabriknetzwerk in 8 Ländern — darunter auch europäische Produktionsstandorte in Portugal, Rumänien und der Türkei. Wir fertigen nicht ausschließlich in Asien. Für deutsche Modemarken, die europäische Produktion bevorzugen, können wir gezielt europäische Fabriken aus unserem Netzwerk einsetzen. Die Lieferzeiten bei europäischer Produktion liegen bei 6–10 Wochen statt 10–14 Wochen bei asiatischer Produktion.
F: Sind Ihre Fabriken GOTS-zertifiziert? A: 25% der Fabriken in unserem aktiven Produktionsnetzwerk sind GOTS-zertifiziert (Global Organic Textile Standard). Für Aufträge, die GOTS-Zertifizierung erfordern, ordnen wir ausschließlich zertifizierte Produktionsstätten zu. Die GOTS-Zertifikatnummern der beauftragten Fabriken können Sie direkt in der öffentlichen GOTS-Datenbank unter global-standard.org verifizieren.
F: Wie unterscheidet sich GOTS von OEKO-TEX®? A: GOTS (Global Organic Textile Standard) zertifiziert die gesamte textile Lieferkette — vom Rohstoff bis zum fertigen Produkt — und umfasst sowohl ökologische als auch soziale Kriterien. OEKO-TEX® Standard 100 prüft das fertige Textilprodukt auf Schadstofffreiheit, ohne die Produktionskette vollständig abzudecken. Für den deutschen Markt empfehlen wir GOTS als umfassendere Zertifizierung, insbesondere wenn Sie Ihre Marke als nachhaltig positionieren möchten. Wir können für Ihre Produktion sowohl GOTS- als auch OEKO-TEX-zertifizierte Fabriken einsetzen.
F: Welche Lieferbedingungen gelten für Deutschland? A: Für deutsche Kunden liefern wir standardmäßig zu DDP-Konditionen (Delivered Duty Paid) — das bedeutet, wir übernehmen Zollabwicklung und Einfuhrumsatzsteuer bis zur deutschen Lieferadresse. Alternativ bieten wir EXW- oder FOB-Konditionen an. Die Einfuhrumsatzsteuer für Bekleidung nach Deutschland beträgt 19% auf den Warenwert. Bei DDP-Lieferung ist dieser Betrag in unserem Angebot bereits enthalten.
F: Wie lang ist die Reaktionszeit auf Anfragen? A: Auf alle Angebotsanfragen antworten wir innerhalb von 48 Stunden mit einem ersten unverbindlichen Angebot. Für detaillierte Angebote, die eine Materialkalkulation und Fabrikzuordnung umfassen, benötigen wir in der Regel 5–7 Werktage. Alle Kommunikation erfolgt auf Englisch; für deutschsprachige Korrespondenz steht Ihnen unser deutschsprachiger Ansprechpartner zur Verfügung.
Pro Tip: German buyers have the highest rate of certificate verification of any market in this project. When a German fashion brand asks for your GOTS certificate, they will check the certificate number in the public GOTS database at global-standard.org before responding to your email. Build the verification link into the page copy itself — “verify certificate [number] at global-standard.org” — and you remove one barrier from the buyer’s decision process and demonstrate that you expect and welcome scrutiny.
4.3 — Japan Primary Landing Page (Japanese Language)
Primary keyword: アパレルメーカー (東京 · 日本向け) URL: https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/ Title (JP): アパレルOEM・縫製工場 | Meridian Cloth Co. Meta (JP): 英国発のアパレルOEMメーカー。最小ロット200枚から対応。GOTS認証工場ネットワーク。48時間以内にお見積もりをご提供します。 H1: 日本のファッションブランドのためのアパレルメーカー — 小ロット200枚から対応
Quick Answer Block (Japanese):
Meridian Cloth Co.は、英国を拠点とするアパレルOEMメーカーです。バングラデシュ、インド、中国、トルコ、ポルトガル、ルーマニア、ベトナム、英国の8カ国に工場ネットワークを持ち、最小ロット200枚から対応しております。工場ネットワークの25%はGOTS認証取得、40%はWRAP認証取得済みです。すべての認証番号は各認証機関のデータベースで直接ご確認いただけます。お問い合わせから48時間以内にお見積もりをご提供いたします。生産リードタイムはサンプル承認から8〜14週間です。
(文字数: 約180文字。数字: 8カ国、200枚、25%、40%、48時間、8〜14週間。)
English translation for editorial reference: Meridian Cloth Co. is a UK-based apparel OEM manufacturer. We have a factory network in 8 countries — Bangladesh, India, China, Turkey, Portugal, Romania, Vietnam, and the United Kingdom — and handle orders from a minimum of 200 pieces. 25% of our factory network holds GOTS certification and 40% holds WRAP certification. All certificate numbers can be verified directly in the respective certification body’s database. We provide a quote within 48 hours of enquiry. Production lead time is 8–14 weeks from sample approval.
H2 Structure (Japanese):
- H2-1: 日本のファッションブランドはなぜ海外アパレルメーカーを選ぶのか?
- H2-2: アパレルOEMの費用はどれくらいですか?
- H2-3: 小ロット・少量生産に対応していますか?
- H2-4: どのような品質管理・認証を取得していますか?
- H2-5: 生産プロセスはどのように進みますか?
- H2-6: 日本への納期はどのくらいですか?
- H2-7: よくあるご質問
Pricing Table (JPY — Japan market):
| 衣類の種類 | 1点あたりの目安 | 最小ロット | 主な生産国 | リードタイム |
|---|---|---|---|---|
| ベーシックTシャツ | ¥2,500〜3,500 (£13〜18) | 300枚 | バングラデシュ | 8〜10週 |
| カジュアルワンピース | ¥3,500〜5,500 (£18〜28) | 250枚 | インド・バングラデシュ | 10〜12週 |
| ニット・セーター | ¥2,800〜4,500 (£14〜23) | 300枚 | 中国・ポルトガル | 10〜14週 |
| スポーツウェア | ¥4,000〜6,000 (£20〜31) | 300枚 | ベトナム | 10〜14週 |
| アウター(ジャケット) | ¥7,500〜13,000 (£38〜66) | 150枚 | トルコ・英国 | 12〜16週 |
| ユニフォーム・作業服 | ¥3,000〜7,500 (£15〜38) | 200枚 | ルーマニア・英国 | 10〜14週 |
| サンプル作成 | ¥20,000〜60,000/型 (£100〜308) | 1型 | 全国対応 | 3〜5週 |
上記はあくまでも市場参考価格です。実際の費用は素材の重さ(g/m²)、縫製の複雑さ、副資材の仕様、生産国によって異なります。為替レートの変動によっても価格は変わります。お客様のプロジェクトに合わせた詳細なお見積もりをお申し込みください。
Japanese FAQ (5 questions — in Japanese):
Q: Meridian Cloth Co.は日本国内に工場を持っていますか? A: Meridian Cloth Co.は英国ロンドンに本社を置き、8カ国の国際工場ネットワークを通じて生産を行っております。現在、日本国内には生産拠点を持っておりません。日本のお客様は、ロンドン本社の専任アカウントマネージャーが窓口となり、コミュニケーション、サンプル確認、生産管理をすべて代行いたします。お問い合わせから48時間以内にご返信いたします。
Q: サンプルなしで量産発注は可能ですか? A: サンプルの承認なしでの量産発注はお受けしておりません。サンプル工程はすべてのご注文に必須となります。これはお客様の品質を守るためであり、工場側の生産精度を確認するためでもあります。サンプル作成には通常3〜5週間かかります。サンプルをご確認・承認いただいた後、量産に進みます。サンプル費用は量産発注時に一部返金される場合があります。
Q: AQL検品基準はどのように設定されていますか? A: 標準的な検品基準はAQL 2.5(国際標準)を採用しています。日本のお客様から多くリクエストをいただくAQL 1.5やより厳しい基準への対応も可能です。ただし、検品基準を厳しくすると、不良品の判定範囲が広がるため、生産コストに影響する場合があります。ご注文前にご希望の検品基準をお知らせください。
Q: 日本語でのコミュニケーションは可能ですか? A: 現在、主なコミュニケーションは英語で行っておりますが、日本語でのお問い合わせも受け付けております。日本語のメールには翻訳を通じてご返信いたします。重要なやり取り(契約書、仕様確認など)は英語と日本語の両方でご用意することが可能です。
Q: 日本への配送条件はどのようになっていますか? A: 日本向け配送はDDP(関税込み持込渡し)条件でご提供いたします。日本の輸入関税と消費税(10%)を含め、指定の配送先まで弊社が責任を持って対応いたします。EXW(工場渡し)またはFOB(本船渡し)条件をご希望の場合もご対応可能です。標準的な日本への航空輸送は生産完了後5〜7日、海上輸送は25〜35日です。
Pro Tip: Japanese B2B clients will test your response time before placing an order. Send a test enquiry to your Japanese contact email before going live with the Japanese landing page. If the response takes longer than 48 hours, or arrives in English without a Japanese acknowledgement, you will lose the client at the first interaction. The response time promise stated in the page copy must be operationally real — not aspirational.
✅ CHECKPOINT — SECTION 4
- [ ] USA page: FTC compliance disclaimer on all ethical claims
- [ ] USA page: “cut and sew” and “apparel” terminology used throughout
- [ ] Germany page: written in German, Sie form confirmed throughout
- [ ] Germany page: Preise sind unverbindliche Richtwerte disclaimer on pricing table
- [ ] Germany page: GOTS verification link to global-standard.org included
- [ ] Japan page: written in Japanese, ます/です form confirmed
- [ ] Japan page: 48-hour response promise stated explicitly in Japanese
- [ ] Japan page: AQL 2.5 mentioned, AQL 1.5 option offered
- [ ] All pages: pricing table with local currency primary, GBP equivalent in brackets
SECTION 5 — SCHEMA LIBRARY — ALL 4 MARKETS
5.1 — USA Schema Block
{
"@context": "https://schema.org",
"@type": "ClothingStore",
"@id": "https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/#localBusiness",
"name": "Meridian Cloth Co.",
"description": "Apparel manufacturer serving US fashion brands and startups. Low MOQ from 200 pieces per style. WRAP certified factory network across 8 countries. Cut and sew production, ethical manufacturing.",
"url": "https://www.meridianclothco.co.uk/us/apparel-manufacturer-new-york/",
"telephone": "+1-XXX-XXX-XXXX",
"email": "**@****************co.uk",
"foundingDate": "2008",
"address": {
"@type": "PostalAddress",
"streetAddress": "[US Street Address]",
"addressLocality": "New York",
"addressRegion": "NY",
"postalCode": "[ZIP Code]",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "40.7128",
"longitude": "-74.0060"
},
"areaServed": [
"New York", "Los Angeles", "Chicago", "Miami", "San Francisco",
"United States"
],
"currenciesAccepted": "USD",
"priceRange": "$$",
"sameAs": [
"https://www.google.com/maps/[US-GBP-LINK]",
"https://www.linkedin.com/company/meridianclothco",
"https://www.ukft.org/[LISTING]"
],
"parentOrganization": {
"@type": "Organization",
"name": "Meridian Cloth Co.",
"url": "https://www.meridianclothco.co.uk"
}
}
5.2 — Germany Schema Block (German language description)
{
"@context": "https://schema.org",
"@type": "ClothingStore",
"@id": "https://www.meridianclothco.co.uk/de/bekleidungshersteller/#localBusiness",
"name": "Meridian Cloth Co.",
"description": "Britischer Bekleidungshersteller für deutsche Modemarken. Mindestbestellmenge ab 200 Stück pro Modell. GOTS-zertifiziertes Fabriknetzwerk. Nachhaltige Produktion mit vollständiger Zertifizierungstransparenz.",
"url": "https://www.meridianclothco.co.uk/de/bekleidungshersteller/",
"telephone": "+49-XXX-XXXX-XXXX",
"email": "**@****************co.uk",
"foundingDate": "2008",
"address": {
"@type": "PostalAddress",
"streetAddress": "[Deutsche Straße]",
"addressLocality": "Berlin",
"addressRegion": "Berlin",
"postalCode": "[PLZ]",
"addressCountry": "DE"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "52.5200",
"longitude": "13.4050"
},
"areaServed": [
"Berlin", "München", "Hamburg", "Frankfurt", "Köln", "Stuttgart",
"Deutschland", "Österreich", "Schweiz"
],
"currenciesAccepted": "EUR",
"sameAs": [
"https://www.google.com/maps/[DE-GBP-LINK]",
"https://www.linkedin.com/company/meridianclothco",
"https://www.textil-mode.de/[LISTING]"
],
"parentOrganization": {
"@type": "Organization",
"name": "Meridian Cloth Co.",
"url": "https://www.meridianclothco.co.uk"
}
}
5.3 — Japan Schema Block (Japanese language description)
{
"@context": "https://schema.org",
"@type": "ClothingStore",
"@id": "https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/#localBusiness",
"name": "Meridian Cloth Co.",
"description": "英国を拠点とするアパレルOEMメーカー。日本のファッションブランド向けに小ロット200枚から対応。8カ国の工場ネットワークを持ち、GOTS認証取得済み工場を含む。高品質な縫製と透明性の高い認証管理。",
"url": "https://www.meridianclothco.co.uk/ja/apparel-manufacturer-tokyo/",
"telephone": "+81-3-XXXX-XXXX",
"email": "ja***@****************co.uk",
"foundingDate": "2008",
"address": {
"@type": "PostalAddress",
"streetAddress": "[住所]",
"addressLocality": "東京",
"addressRegion": "東京都",
"postalCode": "[郵便番号]",
"addressCountry": "JP"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "35.6762",
"longitude": "139.6503"
},
"areaServed": [
"東京", "大阪", "名古屋", "福岡", "札幌", "日本"
],
"currenciesAccepted": "JPY",
"sameAs": [
"https://www.google.com/maps/[JP-GBP-LINK]",
"https://www.linkedin.com/company/meridianclothco"
],
"parentOrganization": {
"@type": "Organization",
"name": "Meridian Cloth Co.",
"url": "https://www.meridianclothco.co.uk"
}
}
5.4 — Organisation Schema Update (Homepage — All Markets)
The homepage Organization schema from the UK multi-location project must be updated to include all four market contact points and all GBP/directory URLs.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.meridianclothco.co.uk/#organization",
"name": "Meridian Cloth Co.",
"url": "https://www.meridianclothco.co.uk",
"logo": "https://www.meridianclothco.co.uk/wp-content/uploads/logo.png",
"foundingDate": "2008",
"description": "International clothing manufacturer serving B2B fashion brands across the UK, USA, Germany, and Japan. Low MOQ from 200 pieces. GOTS, WRAP, Fair Trade and SA8000 certified factory network.",
"areaServed": ["GB", "US", "DE", "JP"],
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "+44-20-XXXX-XXXX",
"contactType": "customer service",
"areaServed": "GB",
"availableLanguage": "English"
},
{
"@type": "ContactPoint",
"telephone": "+1-XXX-XXX-XXXX",
"contactType": "customer service",
"areaServed": "US",
"availableLanguage": "English"
},
{
"@type": "ContactPoint",
"telephone": "+49-XXX-XXXX-XXXX",
"contactType": "customer service",
"areaServed": "DE",
"availableLanguage": ["German", "English"]
},
{
"@type": "ContactPoint",
"telephone": "+81-3-XXXX-XXXX",
"contactType": "customer service",
"areaServed": "JP",
"availableLanguage": ["Japanese", "English"]
}
],
"sameAs": [
"https://www.google.com/maps/[LONDON-GBP]",
"https://www.google.com/maps/[MANCHESTER-GBP]",
"https://www.google.com/maps/[BIRMINGHAM-GBP]",
"https://www.google.com/maps/[BRISTOL-GBP]",
"https://www.google.com/maps/[GLASGOW-GBP]",
"https://www.google.com/maps/[US-GBP]",
"https://www.google.com/maps/[DE-GBP]",
"https://www.google.com/maps/[JP-GBP]",
"https://www.linkedin.com/company/meridianclothco",
"https://www.ukft.org/[LISTING]",
"https://gb.kompass.com/[LISTING]"
]
}
✅ CHECKPOINT — SECTION 5
- [ ] US schema: addressCountry “US” (not “USA”), USD currency
- [ ] Germany schema: description in German, addressCountry “DE”, EUR currency
- [ ] Japan schema: description in Japanese, addressCountry “JP”, JPY currency
- [ ] All schemas: validated at validator.schema.org — 0 errors each
- [ ] Homepage Organization schema: updated with all 4 market contactPoints
- [ ] Deploy: Elementor Custom HTML widget per page — Rank Math schema disabled on same pages
SECTION 6 — GOOGLE BUSINESS PROFILE — INTERNATIONAL MARKETS
GBP Across Borders: What Changes and What Does Not
The GBP optimisation principles from the UK project apply in every market: 100% completeness, unique descriptions, unique photos, local phone numbers, 2x weekly posts, and monthly review monitoring. What changes is the execution layer specific to each country.
Pro Tip: GBP verification timelines differ by country and by how the listing was created. UK verification typically completes in 1–5 days by phone or video. US verification is similar. German GBP listings frequently require postcard verification — allowing 10–14 days. Japanese GBP verification via postcard can take 2–3 weeks due to postal routing from Google’s system. Plan the international GBP build 6 weeks before the planned go-live date, not 2 weeks.
6.1 — GBP Setup Per Market
| Element | USA | Germany | Japan |
|---|---|---|---|
| Verification method | Phone or video | Postcard (10–14 days) | Postcard (2–3 weeks) |
| Primary category | Clothing Manufacturer | Bekleidungsunternehmen | アパレルメーカー |
| Description language | English (US) | German (Sie form) | Japanese (ます/です) |
| Phone format | +1 area-code number | +49 Vorwahl Nummer | +81 market-code number |
| Photos | US-context images | German-context or neutral | Japanese-context images |
| Post language | English (US) | German | Japanese |
| Review response language | English (US) | German | Japanese + English |
| GBP Insights metric focus | Direction requests + calls | Website clicks + calls | Website clicks + calls |
6.2 — USA GBP Description (750 chars, English US)
Meridian Cloth Co. is an apparel manufacturer serving US fashion brands and startups. We handle the full production process — from design brief and tech pack development to factory sourcing, sampling, bulk cut-and-sew production, AQL quality inspection, and US delivery. Our factory network spans 8 countries and includes WRAP certified (40%), GOTS certified (25%), Fair Trade (15%), and SA8000 certified (20%) production facilities. Minimum order: 200 pieces per style. Quotes returned within 48 hours. DDP shipping to all US states available.
6.3 — Germany GBP Description (750 chars, German, Sie form)
Meridian Cloth Co. ist ein britischer Bekleidungshersteller, der deutsche Modemarken und Startups bei der internationalen Produktion unterstützt. Von der Designentwicklung und Technischen Dokumentation bis zur Fabrikauswahl, Mustererstellung, Serienproduktion, AQL-Qualitätskontrolle und Lieferung nach Deutschland — wir übernehmen den gesamten Produktionsprozess. Unser Fabriknetzwerk umfasst 8 Länder, darunter GOTS-zertifizierte (25%), WRAP-zertifizierte (40%) und Fair-Trade-zertifizierte (15%) Produktionsstätten. Mindestbestellmenge: 200 Stück. Angebote innerhalb von 48 Stunden.
6.4 — Japan GBP Description (750 chars, Japanese)
Meridian Cloth Co.は、日本のファッションブランドやスタートアップを支援する英国のアパレルOEMメーカーです。デザインの立案・テクパックの作成から、工場選定、サンプル製作、量産縫製、AQL品質検査、日本への納品まで、生産プロセス全体をサポートいたします。8カ国にわたる工場ネットワークを持ち、GOTS認証(25%)、WRAP認証(40%)、フェアトレード認証(15%)、SA8000認証(20%)取得済みの工場を含みます。最小ロット:200枚。お見積もりは48時間以内にご提供します。
6.5 — International GBP Post Calendar — Month 1
Running three new GBP listings across different time zones and languages requires a content calendar, not three separate mental notes. Below is the Week 1–4 framework.
| Week | Post Type | USA Copy (English) | Germany Copy (German) | Japan Copy (Japanese) |
|---|---|---|---|---|
| 1 | Service spotlight | “Low MOQ apparel manufacturing from 200 pieces — designed for US startup brands. Request a quote at [URL].” | “Bekleidungsproduktion ab 200 Stück Mindestbestellmenge — ideal für deutsche Modemarken. Angebot anfordern: [URL].” | “最小ロット200枚から対応するアパレルOEM。日本のファッションブランドに特化したサービスです。[URL]” |
| 2 | Trust signal | “WRAP certified factory network — all certificates verifiable at wrapcompliance.org. See our ethical production standards at [URL].” | “GOTS-zertifiziertes Fabriknetzwerk — alle Zertifikate direkt unter global-standard.org verifizierbar. [URL]” | “GOTS認証工場ネットワーク。認証番号はglobal-standard.orgで直接ご確認いただけます。[URL]” |
| 3 | Educational | “What’s a tech pack, and why do you need one before production? Our guide explains the 9 elements every brand needs. [URL].” | “Was ist ein Tech Pack? Unsere 9-Punkte-Checkliste für Modemarken. [URL]” | “テクパックとは?生産前に必要な9つの要素をご説明します。[URL]” |
| 4 | Quote CTA | “US fashion brands: get your apparel manufacturing quote in 48 hours. We respond to every brief. [URL].” | “Kostenloses Angebot in 48 Stunden — für deutsche Modemarken. [URL]” | “お見積もりは48時間以内に。日本のブランド様のご相談をお待ちしております。[URL]” |
✅ CHECKPOINT — SECTION 6
- [ ] US GBP: claimed, verification initiated, English (US) description deployed
- [ ] Germany GBP: claimed, postcard verification initiated, German description deployed
- [ ] Japan GBP: claimed, postcard verification initiated, Japanese description deployed
- [ ] All 3 listings: 20+ photos uploaded (location-relevant or brand-neutral)
- [ ] Post calendar: 4-week schedule built for all 3 markets
- [ ] Review response: language-matched template ready for each market
SECTION 7 — CITATION BUILDING — PER MARKET
Why UK Citations Do Not Help USA or Japan
The Yell.com listing, Thomson Local submission, and FreeIndex entry from the UK project send no ranking signal to the US, German, or Japanese Local Pack results. Each market has its own directory ecosystem. This section documents the Tier 1 citation targets per market.
Pro Tip: The most time-efficient citation strategy for international expansion is to target the top 5 directories per market in Month 1, verify all 5 before moving to the next 5, and maintain a live citation tracking tab per country. Submitting to 20 directories simultaneously and then verifying 60 days later produces a confusing mix of live, pending, and rejected listings with no clear picture of NAP consistency.
7.1 — USA Citation Priority List
| Tier | Directory | URL | DR Est. | Category |
|---|---|---|---|---|
| T1 | Google Business Profile | business.google.com | — | Core |
| T1 | Bing Places | bingplaces.com | — | Core |
| T1 | Apple Maps Connect | mapsconnect.apple.com | — | Core |
| T1 | Yelp for Business | biz.yelp.com | 94 | General US |
| T1 | Better Business Bureau | bbb.org | 91 | Trust/General |
| T1 | Manta | manta.com | 72 | US Business |
| T1 | Superpages | superpages.com | 74 | General US |
| T2 | Angi (Angie’s List) | angi.com | 88 | Service Business |
| T2 | Foursquare | business.foursquare.com | 92 | General |
| T2 | Hotfrog US | hotfrog.com | 68 | General US |
| T2 | CitySearch | citysearch.com | 72 | General US |
| T2 | MerchantCircle | merchantcircle.com | 72 | US Business |
| T3 | AAFA (American Apparel & Footwear Assoc) | aafaglobal.com | 62 | Industry |
| T3 | Kompass USA | us.kompass.com | 74 | B2B Manufacturing |
| T3 | ThomasNet | thomasnet.com | 78 | US Manufacturing |
| T3 | MFG.com | mfg.com | 58 | Manufacturing |
USA-specific note: BBB accreditation is a stronger trust signal in the US market than in any other country. Apply for accreditation (separate from listing) — the BBB Accreditation mark on the website and GBP increases conversion rates measurably with US buyers unfamiliar with a business.
7.2 — Germany Citation Priority List
| Tier | Directory (German) | URL | DR Est. | Category |
|---|---|---|---|---|
| T1 | Google Business Profile | business.google.com | — | Core |
| T1 | Bing Places | bingplaces.com | — | Core |
| T1 | Apple Maps Connect | mapsconnect.apple.com | — | Core |
| T1 | Gelbe Seiten | gelbeseiten.de | 80 | Allgemeine DE |
| T1 | Das Telefonbuch | dasTelefonbuch.de | 78 | Allgemeine DE |
| T1 | Cylex Deutschland | cylex.de | 65 | Allgemeine DE |
| T1 | Hotfrog Deutschland | hotfrog.de | 62 | Allgemeine DE |
| T2 | Wer liefert was (WLW) | wlw.de | 72 | B2B DE |
| T2 | Europages | europages.de | 68 | B2B Europa |
| T2 | Kompass Deutschland | de.kompass.com | 74 | B2B Hersteller |
| T2 | Trustpilot DE | de.trustpilot.com | 92 | Bewertungen |
| T3 | Gesamtverband textil+mode | textil-mode.de | 58 | Branchenverband |
| T3 | Modeist | modeist.de | 42 | Mode-Branche |
| T3 | Wer kennt den Besten | wkdb.de | 55 | Bewertungen |
Germany-specific note: Wer liefert was (wlw.de) — “who delivers what” — is the dominant German B2B directory for manufacturing and is specifically indexed for buyers sourcing production partners. It is the German equivalent of ThomasNet in the US. A complete, verified listing on WLW is higher-value than most general directories in the German market.
7.3 — Japan Citation Priority List
| Tier | Directory (Japanese) | URL | DR Est. | Category |
|---|---|---|---|---|
| T1 | Google Business Profile | business.google.com | — | Core |
| T1 | Apple Maps Connect | mapsconnect.apple.com | — | Core |
| T1 | Yahoo! Japan Local | local.yahoo.co.jp | 95 | Core JP |
| T1 | iタウンページ (NTT) | itp.ne.jp | 78 | General JP |
| T1 | ぐるなび (Gurunavi) | gurunavi.com | 82 | General JP |
| T2 | Kompass Japan | jp.kompass.com | 74 | B2B JP |
| T2 | Europages Japan | japanpage.eu | 68 | B2B Europe-JP |
| T2 | TDBデータ (Teikoku) | teikoku.com | 72 | JP Business |
| T3 | 繊研新聞 (Senken Shimbun) | senken.co.jp | 52 | Fashion Trade JP |
| T3 | 日本繊維産業連盟 (JTFF) | jtff.or.jp | 55 | Industry JP |
| T3 | ジャパンテックスタイル | japantextile.jp | 42 | Textile Industry JP |
Japan-specific note: Yahoo! Japan is the second largest search engine in Japan and maintains its own directory that feeds Local results. A Yahoo! Japan Local listing (via iタウンページ) is the Japanese equivalent of Bing Places — it looks secondary but covers 19% of Japanese search traffic. Do not skip it.
✅ CHECKPOINT — SECTION 7
- [ ] USA: 10 Tier 1–2 citations submitted, BBB accreditation application submitted
- [ ] Germany: 10 Tier 1–2 citations submitted, WLW listing created with full German copy
- [ ] Japan: 8 Tier 1–2 citations submitted, Yahoo! Japan Local listing confirmed
- [ ] All markets: NAP verified live within 7 days of each submission
- [ ] Citation tracking tabs: Tab 2-USA, Tab 2-DE, Tab 2-JP created in master spreadsheet
SECTION 8 — CONTENT ARCHITECTURE — INTERNATIONAL CLUSTERS
8.1 — USA Content Cluster
Pillar page: /us/apparel-manufacturer-new-york/ (built in Section 4)
| Cluster Post | Target Keyword | URL | Priority |
|---|---|---|---|
| What Does Apparel Manufacturing Cost in the USA? | apparel manufacturing cost USA | /blog/us/apparel-manufacturing-cost-usa/ | Month 2 |
| How to Find an Apparel Manufacturer for a US Startup | apparel manufacturer for startups | /blog/us/apparel-manufacturer-us-startups/ | Month 2 |
| What Is Cut and Sew Manufacturing? | cut and sew manufacturing | /blog/us/what-is-cut-and-sew-manufacturing/ | Month 3 |
| WRAP vs GOTS: Which Certification Do US Buyers Need? | WRAP vs GOTS certification | /blog/us/wrap-vs-gots-certification/ | Month 3 |
| How to Write an Apparel Tech Pack | apparel tech pack guide | /blog/us/how-to-write-apparel-tech-pack/ | Month 4 |
8.2 — Germany Content Cluster (German language)
Pillar page: /de/bekleidungshersteller/ (built in Section 4)
| Cluster-Artikel | Ziel-Keyword | URL | Priorität |
|---|---|---|---|
| Was kostet Bekleidungsproduktion in Europa? | Bekleidungsproduktion Kosten Europa | /de/blog/bekleidungsproduktion-kosten/ | Monat 2 |
| GOTS oder OEKO-TEX — welche Zertifizierung brauche ich? | GOTS OEKO-TEX Unterschied | /de/blog/gots-vs-oeko-tex/ | Monat 2 |
| Wie erstelle ich ein Tech Pack für meine Modemarke? | Tech Pack erstellen Modemarke | /de/blog/tech-pack-erstellen/ | Monat 3 |
| Kleine Auflagen produzieren — Leitfaden für Startups | kleine Auflagen Bekleidung | /de/blog/kleine-auflagen-produktion/ | Monat 3 |
| Nachhaltige Bekleidungsproduktion — was bedeutet das wirklich? | nachhaltiger Bekleidungshersteller | /de/blog/nachhaltige-bekleidungsproduktion/ | Monat 4 |
8.3 — Japan Content Cluster (Japanese language)
Pillar page: /ja/apparel-manufacturer-tokyo/ (built in Section 4)
| クラスター記事 | ターゲットキーワード | URL | 優先度 |
|---|---|---|---|
| アパレルOEMの費用はいくら?完全ガイド | アパレルOEM 費用 | /ja/blog/apparel-oem-cost/ | 2ヶ月目 |
| テクパックとは?9つの必須要素を解説 | テクパック 作り方 | /ja/blog/tech-pack-guide/ | 2ヶ月目 |
| 小ロット縫製工場の選び方 | 小ロット縫製工場 選び方 | /ja/blog/small-lot-factory-guide/ | 3ヶ月目 |
| GOTS認証とは?ファッションブランドが知るべきこと | GOTS認証 とは | /ja/blog/gots-certification-guide/ | 3ヶ月目 |
| ファッションブランド立ち上げの生産準備完全ガイド | ファッションブランド 生産 | /ja/blog/fashion-brand-production-guide/ | 4ヶ月目 |
Pro Tip: German and Japanese content clusters should be written by or reviewed by a native speaker before publishing. Machine-translated content in German or Japanese does not fail in an obvious way — it fails subtly. Sentences are grammatically correct but the phrasing is unnatural, the register is inconsistent, and the technical terms are sometimes translated literally rather than using the industry-standard term. German buyers notice immediately. Japanese buyers notice even faster.
✅ CHECKPOINT — SECTION 8
- [ ] USA: 5 cluster posts planned, Month 2–4 target dates assigned
- [ ] Germany: 5 cluster posts planned in German, native speaker review scheduled
- [ ] Japan: 5 cluster posts planned in Japanese, native speaker review scheduled
- [ ] All clusters: internal links to pillar page confirmed in each post brief
- [ ] Content calendar: 3 market tabs in master content calendar
SECTION 9 — TECHNICAL SEO — INTERNATIONAL LAYER
9.1 — International-Specific Technical Checklist
Beyond the standard technical audit from the UK project, these checks apply specifically to the international implementation.
| Check | Tool | Pass Condition | Priority |
|---|---|---|---|
| Hreflang — no errors | technicalseo.com/tools/hreflang/ | 0 errors | 🔴 Critical |
| Hreflang — reciprocal tags | Screaming Frog | All pairs confirmed | 🔴 Critical |
| Canonical — no cross-language | Screaming Frog | Self-canonical on all intl pages | 🔴 Critical |
| GSC geotargeting set | GSC Search Console | /us/, /de/, /ja/ all targeted | 🔴 Critical |
| Sitemaps submitted (all 4) | GSC | 4 sitemaps submitted, 0 errors | 🔴 Critical |
| robots.txt — intl paths crawlable | Screaming Frog | No Disallow on /us/, /de/, /ja/ | 🔴 Critical |
| Duplicate content — EN/DE/JP | Copyscape / manual | No translated page copied from UK | 🔴 Critical |
| og:locale — correct per page | Screaming Frog | en_US / de_DE / ja_JP | 🟡 Important |
| HTML lang attribute | Screaming Frog | lang=”en-US”, “de”, “ja” | 🟡 Important |
| Currency — correct per page | Manual | USD/EUR/JPY on correct pages | 🔴 Critical |
| Date format — correct per page | Manual | MM/DD/YYYY US, DD.MM.YYYY DE | 🟡 Important |
| CDN / server response time | GTmetrix per country | <600ms TTFB from each target country | 🟡 Important |
| Core Web Vitals (all markets) | PageSpeed — per country | LCP ≤2.5s, CLS ≤0.1, INP ≤200ms | 🔴 Critical |
9.2 — HTML Language Attribute — Per Page
Every international page must have the correct HTML lang attribute in the <html> tag.
<!-- UK pages -->
<html lang="en-GB">
<!-- US pages -->
<html lang="en-US">
<!-- German pages -->
<html lang="de">
<!-- Japanese pages -->
<html lang="ja">
WordPress + Elementor: The HTML lang attribute is typically set by the WordPress language setting or a multilingual plugin (WPML, Polylang). Confirm the attribute is being set correctly per page type — it does not automatically change for subdirectory-based international setups without plugin configuration.
9.3 — CDN and Server Performance — International
Meridian Cloth Co.’s site is hosted on Hostinger or InMotion (UK-based servers). UK and European visitors experience standard load times. US and Japanese visitors experience higher latency due to geographic server distance.
Solution: Configure Cloudflare (free tier sufficient) as a CDN layer. Cloudflare caches static assets from edge nodes in the USA and Japan, reducing TTFB from 900ms+ to 300ms or below for non-UK users. This directly affects Core Web Vitals scores for the /us/ and /ja/ subdirectories.
Pro Tip: Test PageSpeed Insights scores from a US IP and a Japan IP separately — not just from the UK. A PageSpeed score of 82 on mobile tested from London may drop to 61 when tested from Tokyo, because the server distance increases TTFB past the LCP threshold. Cloudflare’s free CDN resolves this without any hosting changes.
9.4 — og:locale — Per Market
Open Graph locale affects how pages are previewed when shared on social media platforms. Set correctly per market.
<!-- UK pages -->
<meta property="og:locale" content="en_GB" />
<!-- US pages -->
<meta property="og:locale" content="en_US" />
<!-- German pages -->
<meta property="og:locale" content="de_DE" />
<!-- Japanese pages -->
<meta property="og:locale" content="ja_JP" />
✅ CHECKPOINT — SECTION 9
- [ ] Hreflang: 0 errors confirmed at technicalseo.com/tools/hreflang/
- [ ] Canonical: all international pages self-canonicalise — no cross-language canonicals
- [ ] GSC: geotargeting set for /us/, /de/, /ja/
- [ ] Robots.txt: all international paths confirmed crawlable
- [ ] HTML lang attribute: en-US / de / ja confirmed on correct pages
- [ ] Cloudflare CDN: configured and verified — TTFB below 600ms from US and JP
- [ ] PageSpeed: tested from US IP and JP IP — all pages pass LCP/CLS/INP
- [ ] og:locale: en_US / de_DE / ja_JP confirmed per market
SECTION 10 — BACKLINK STRATEGY — PER MARKET
Why International Link Building Is Not Just More of the Same
A German industry body backlink from textil-mode.de sends geolocation authority signals that strengthen the /de/ subdirectory ranking in Germany specifically. A US editorial backlink from Sourcing Journal strengthens the /us/ subdirectory ranking in the US specifically. Cross-market link benefits are minimal — the geographic relevance of the linking domain is a stronger signal in local and international SEO than raw domain authority.
Pro Tip: The fastest market-specific backlinks in every country are always local Chamber of Commerce or trade association directory listings. They carry high local relevance, moderate domain authority, and are available to any registered business. Submit Chamber applications in all four markets in Month 1 — these are the foundation of the per-market link profile before editorial outreach begins.
10.1 — USA Link Building Priority Targets
| Type | Target | DR Est. | Approach | Timeline |
|---|---|---|---|---|
| Industry Body | AAFA member directory | 62 | Apply for membership | Month 1 |
| Industry Body | WRAP certified brands list | 58 | Confirm listing after WRAP audit | Month 1–2 |
| Chamber | NY / LA / Chicago Chamber of Commerce | 55–65 | Member directory listing | Month 1 |
| Editorial | Sourcing Journal | 72 | Pitch: UK manufacturer for US brands | Month 3 |
| Editorial | WWD (Women’s Wear Daily) | 88 | PR pitch: ethical production angle | Month 4 |
| Editorial | Apparel Magazine | 62 | Guest article: tech pack guide | Month 3 |
| Resource page | StartupFashion.com | 48 | Supplier directory inclusion | Month 2 |
| Resource page | Maker’s Row | 52 | Manufacturer listing | Month 2 |
| Unlinked mention | Google: “Meridian Cloth Co.” -site:meridianclothco.co.uk | — | Template A outreach | Month 1–2 |
| University | FIT New York supplier page | 72 | Fashion supplier contact | Month 3 |
| University | FIDM Los Angeles supplier page | 65 | Fashion supplier contact | Month 3 |
USA anchor text targets:
| Type | Target % | Examples |
|---|---|---|
| Branded | 40–50% | “Meridian Cloth Co.” |
| Naked URL | 20–25% | “meridianclothco.co.uk/us/” |
| Partial match | 10–15% | “apparel manufacturer” |
| Exact match | ≤5% | “apparel manufacturer USA” |
| Generic | 10–15% | “our manufacturer”, “their services” |
10.2 — Germany Link Building Priority Targets
| Type | Target | DR Est. | Approach | Timeline |
|---|---|---|---|---|
| Industry Body | Gesamtverband textil+mode | 58 | Member directory listing | Month 1 |
| Industry Body | BVT (Bundesverband Textileinzelhandel) | 52 | Associate member application | Month 2 |
| Chamber | IHK Berlin / IHK München | 62–68 | Mitgliederverzeichnis (member directory) | Month 1 |
| Editorial | Textilwirtschaft (TW) | 65 | PR pitch in German: UK Hersteller | Month 3 |
| Editorial | Sportswear International | 58 | Guest article: German | Month 3 |
| Editorial | Premium (magazine, Berlin) | 48 | Interview: sustainable production | Month 4 |
| Resource page | Sustainable Apparel Coalition DE | 62 | Supplier directory | Month 2 |
| Resource page | Fashion Council Germany | 55 | Brand partner listing | Month 2 |
| University | Hochschule Niederrhein (textile) | 68 | Supplier / partner page | Month 3 |
| University | AMD Akademie Mode & Design | 62 | Industry partner page | Month 3 |
German anchor text note: German anchor text for cross-language links should use German-language anchors — “Bekleidungshersteller” or “Meridian Cloth Co.” — not English “clothing manufacturer.” Anchor text language signals relevance to the target market.
10.3 — Japan Link Building Priority Targets
| Type | Target | DR Est. | Approach | Timeline |
|---|---|---|---|---|
| Industry Body | 日本繊維産業連盟 (JTFF) | 55 | Partner/member listing | Month 2 |
| Industry Body | 繊維産業サプライヤー | 48 | Supplier directory | Month 2 |
| Editorial | 繊研新聞 (Senken Shimbun) | 52 | Press release in Japanese: UK manufacturer | Month 4 |
| Editorial | Fashion Press Japan | 62 | Brand story: UK-Japan production | Month 4 |
| Resource page | StyleZine (Japan startup fashion) | 42 | Manufacturer recommendation | Month 3 |
| University | 文化服装学院 (Bunka Fashion College) | 65 | Industry partner listing | Month 4 |
| University | 東京モード学園 (Tokyo Mode Gakuen) | 62 | Industry supplier page | Month 4 |
| Unlinked mention | Google.co.jp: “Meridian Cloth Co.” | — | Japanese-language outreach | Month 2 |
Japan outreach note: Outreach to Japanese organisations should be sent in Japanese where possible. A cold outreach email in English to a Japanese industry body will receive a significantly lower response rate than one in Japanese. Use a translation service or native speaker for outreach emails — not machine translation.
✅ CHECKPOINT — SECTION 10
- [ ] USA: Chamber of Commerce applications submitted Month 1
- [ ] USA: AAFA and Maker’s Row applications submitted Month 1
- [ ] Germany: IHK application submitted Month 1, textil+mode application Month 1
- [ ] Japan: JTFF application submitted Month 2
- [ ] All markets: link tracking tab per country (Tab 3-USA, Tab 3-DE, Tab 3-JP)
- [ ] Anchor text ratios confirmed: exact match ≤5% per market domain path
SECTION 11 — COMPETITOR ANALYSIS — ALL 4 MARKETS
11.1 — USA Competitive Landscape
SERP check: Google.com, location = New York, NY, incognito, query = “apparel manufacturer USA”
| Competitive Factor | USA Market Average | Meridian Cloth Co. Target |
|---|---|---|
| Competitor word count (top 5) | 1,200–2,000 words | 3,000+ words |
| Quick Answer block present | 0 of 5 competitors | ✅ Required |
| Pricing table present | 0 of 5 competitors | ✅ Required |
| FAQPage schema | 1 of 5 competitors | ✅ Required |
| WRAP certification mentioned | 2 of 5 competitors | ✅ Required |
| FTC compliance disclaimer | 0 of 5 competitors | ✅ Required |
| DDP shipping mentioned | 0 of 5 competitors | ✅ Required |
| AQL standard mentioned | 0 of 5 competitors | ✅ Required |
Key US competitive finding: No top-ranking US competitor landing page carries a Quick Answer block, pricing table, FTC-compliant ethical disclaimers, or mentions DDP shipping for US clients. Meridian Cloth Co. launches as content-superior on every measurable dimension.
11.2 — Germany Competitive Landscape
SERP check: Google.de, location = Berlin, incognito, query = “Bekleidungshersteller”
| Competitive Factor | German Market Average | Meridian Cloth Co. Target |
|---|---|---|
| Content in German | 4 of 5 (1 in English only) | ✅ Full German |
| Sie form (formal address) | 3 of 5 correct | ✅ Sie form throughout |
| GOTS mentioned | 3 of 5 | ✅ GOTS + verification link |
| OEKO-TEX mentioned | 2 of 5 | ✅ OEKO-TEX comparison |
| Pricing table (EUR) | 0 of 5 | ✅ Required |
| Impressum present | 5 of 5 | ✅ Required |
| FAQPage schema | 0 of 5 | ✅ Required |
| Quick Answer block | 0 of 5 | ✅ Required |
Key German competitive finding: German competitors have the Impressum and Sie form correct but consistently lack pricing transparency, Quick Answer blocks, and schema. A well-structured German page with a pricing table and FAQPage schema launches with a structural SEO advantage over every existing top-5 result.
11.3 — Japan Competitive Landscape
SERP check: Google.co.jp, location = Tokyo, incognito, query = “アパレルメーカー”
| Competitive Factor | Japan Market Average | Meridian Cloth Co. Target |
|---|---|---|
| Content in Japanese | 5 of 5 | ✅ Full Japanese |
| ます/です form | 5 of 5 | ✅ Required |
| GOTS mentioned in Japanese | 1 of 5 | ✅ GOTS + Japanese verification guide |
| Pricing table (JPY) | 1 of 5 | ✅ Required with 万円 notation |
| AQL standard mentioned | 1 of 5 | ✅ AQL 1.5 and 2.5 options |
| Response time stated | 2 of 5 | ✅ 48時間以内 |
| FAQPage schema | 0 of 5 | ✅ Required |
| Relationship language | 3 of 5 | ✅ Required |
Key Japan competitive finding: Japanese competitors are culturally appropriate (correct language, formal register) but lack schema, pricing transparency, and the AQL specification detail that Japanese buyers specifically require. Meridian Cloth Co. enters the Japanese market with the cultural competence competitors have and the technical SEO structure they lack.
11.4 — Month 12 Competitive Targets Per Market
| Market | Primary KW Target | Local Pack Target | Reviews Target | Content Superiority |
|---|---|---|---|---|
| UK | Top 10 London | Top 3 | 30+ reviews | Maintained from multi-loc project |
| USA | Top 10 “apparel manufacturer USA” | Top 3 New York | 10+ US reviews | Quick Answer + pricing table |
| Germany | Top 5 “Bekleidungshersteller” | Top 3 Berlin | 8+ German reviews | Only page with pricing table (EUR) |
| Japan | Top 5 「アパレルメーカー」 | Top 3 Tokyo | 8+ Japanese reviews | Only page with AQL spec + JPY table |
✅ CHECKPOINT — SECTION 11
- [ ] USA SERP snapshot: recorded incognito from US IP — top 10 positions documented
- [ ] Germany SERP snapshot: recorded on Google.de from German location setting
- [ ] Japan SERP snapshot: recorded on Google.co.jp from Tokyo location setting
- [ ] Competitive gap tables: completed per market — content, schema, and technical gaps identified
- [ ] Month 12 targets: confirmed and logged in reporting template
SECTION 12 — GA4 & CONVERSION TRACKING — INTERNATIONAL
12.1 — GA4 Property Setup Decision
Two options for international GA4 setup:
Option A — One global property, multiple data streams (recommended for this project) One GA4 property with one data stream per market:
- UK data stream → meridianclothco.co.uk (existing)
- US data stream → meridianclothco.co.uk/us/
- DE data stream → meridianclothco.co.uk/de/
- JP data stream → meridianclothco.co.uk/ja/
Option B — Separate GA4 property per market Cleaner per-market reporting but no cross-market comparison in a single view.
Option A is recommended because it allows a single global report showing which market generates the most leads, without switching between four separate GA4 accounts.
12.2 — Custom Dimensions Required
Three custom dimensions are essential for international tracking:
| Dimension Name | Scope | Values | Purpose |
|---|---|---|---|
| market | Event | UK / USA / DE / JP | Attribute every Key Event to a market |
| location_name | Event | City name | Attribute leads to specific city within market |
| currency | Event | GBP / USD / EUR / JPY | Track quote requests by currency |
All three fire on every Key Event (phone_click, email_click, quote_form_submit).
12.3 — GBP UTM Parameters — Per Market
Every GBP website button must carry a unique UTM link per market. Without this, all GBP-driven traffic lands as direct traffic in GA4, making it impossible to attribute leads to specific market GBP listings.
UK London: ?utm_source=gbp&utm_medium=local&utm_campaign=uk-london
USA New York: ?utm_source=gbp&utm_medium=local&utm_campaign=us-new-york
Germany Berlin:?utm_source=gbp&utm_medium=local&utm_campaign=de-berlin
Japan Tokyo: ?utm_source=gbp&utm_medium=local&utm_campaign=jp-tokyo
12.4 — GA4 Explore Report: Leads by Market
Build this report in GA4 > Explore > Free Form before Month 1 ends:
- Dimension 1: market (custom dimension)
- Dimension 2: location_name (custom dimension)
- Metric: Key events (quote_form_submit + phone_click + email_click)
- Breakdown: Monthly
- Purpose: Which market and which city drives the most leads — visible at a glance without cross-referencing four separate accounts
12.5 — Month 1 Baseline Snapshot Per Market
Record these before any international optimisation begins. These are the baselines against which Month 12 targets are measured.
| KPI | Source | UK Baseline | USA Baseline | DE Baseline | JP Baseline |
|---|---|---|---|---|---|
| Organic sessions | GA4 | Record | 0 (new) | 0 (new) | 0 (new) |
| Key events / mo | GA4 | Record | 0 | 0 | 0 |
| GBP impressions | GBP Insights | Record | 0 | 0 | 0 |
| GBP actions | GBP Insights | Record | 0 | 0 | 0 |
| Review count | GBP | Record | 0 | 0 | 0 |
| Primary KW ranking | GSC / Semrush | Record | Not top 100 | Not top 100 | Not top 100 |
✅ CHECKPOINT — SECTION 12
- [ ] GA4: one property, four data streams (UK/US/DE/JP) confirmed
- [ ] Custom dimension: market — firing on all Key Events in all four markets
- [ ] GBP UTM links: unique per market GBP listing, active on website button
- [ ] GA4 Explore report: Leads by Market — confirmed working before Month 2
- [ ] Month 1 baselines: recorded for all four markets before any optimisation
SECTION 13 — 12-MONTH ACTION PLAN — INTERNATIONAL
Phase 1 — Month 1–2: International Foundation
| Priority | Action | Market | Deliverable |
|---|---|---|---|
| 🔴 Critical | Define NAP per market — 4 canonical strings | All | NAP register complete |
| 🔴 Critical | Build /us/, /de/, /ja/ subdirectory structure | All | Dev work complete |
| 🔴 Critical | Implement hreflang — HTML head or XML sitemap | All | 0 errors on validation |
| 🔴 Critical | Claim + verify GBP per market | All | 4 GBP listings initiated |
| 🔴 Critical | Publish landing pages — US, DE, JP | All | 3 pages live + indexed |
| 🔴 Critical | Deploy schema per market — 3 blocks each | All | Validated 0 errors |
| 🔴 Critical | GSC: set geotargeting per subdirectory | All | /us/, /de/, /ja/ targeted |
| 🔴 Critical | Submit 5 Tier 1 citations per market | All | 15 new submissions |
| 🔴 Critical | GA4: 4 data streams + market custom dimension | All | Tracking live |
| 🔴 Critical | Record Month 1 baselines per market | All | Baseline document saved |
| 🟡 Important | Cloudflare CDN: configure for US and JP performance | US, JP | TTFB <600ms from all markets |
| 🟡 Important | Chamber of Commerce applications per market | All | 4 applications submitted |
| 🟡 Important | International hub page published at /international/ | All | Hub page live |
| 🟡 Important | GBP: complete all profiles, upload 20+ photos each | All | 100% completeness |
Phase 2 — Month 3–4: Content & Citations
| Priority | Action | Market | Deliverable |
|---|---|---|---|
| 🔴 Critical | Verify all 15 Tier 1 citations live + NAP-accurate | All | 13+ verified |
| 🔴 Critical | Publish first blog posts per market | All | 3 posts live (1 per market) |
| 🟡 Important | Submit 5 Tier 2–3 niche citations per market | All | 15 new submissions |
| 🟡 Important | Launch review campaign per market | All | 5+ reviews target per market |
| 🟡 Important | GBP post cadence: 2× per week per market | All | 24 posts scheduled |
| 🟡 Important | Unlinked mention outreach per market | All | 5+ outreach emails sent |
| 🟡 Important | FTC compliance review: all US content | USA | 0 uncompliant claims |
Phase 3 — Month 5–6: Link Building Sprint
| Priority | Action | Market | Deliverable |
|---|---|---|---|
| 🟡 Important | AAFA + Maker’s Row confirmed live | USA | 2 industry backlinks |
| 🟡 Important | textil+mode + IHK confirmed live | Germany | 2 industry backlinks |
| 🟡 Important | JTFF confirmed live | Japan | 1 industry backlink |
| 🟡 Important | Editorial pitches: Sourcing Journal (US), TW (DE) | USA, DE | 2 pitches sent |
| 🟡 Important | University outreach per market | All | 6 emails sent |
| 🔴 Critical | Second citation submission round: 5 per market | All | 15 new submissions |
| 🔴 Critical | Review push: target 8+ per market by Month 6 | All | 24+ reviews total |
Phase 4–6 — Month 7–12: Authority, Scaling, Reporting
| Priority | Action | Market | Deliverable |
|---|---|---|---|
| 🔴 Critical | Full hreflang re-audit (month 6 + month 12) | All | 0 errors confirmed |
| 🟡 Important | Publish 2nd blog posts per market | All | 6 cluster posts live |
| 🟡 Important | AI Overview entity check per market | All | Perplexity screenshots |
| 🟡 Important | Review push round 3: target 12+ per market | All | 36+ reviews total |
| 🟡 Important | Full 12-month competitive SERP re-snapshot | All | Updated gap analysis |
| 🔴 Critical | Full 12-month technical audit — international | All | Per-market report |
| 🔴 Critical | Q1 next year strategy per market | All | Strategy document |
SECTION 14 — MONTHLY REPORTING — INTERNATIONAL
14.1 — Report Structure
Each monthly report produces:
- Global summary (1 page): total organic sessions across all markets, total leads by market, overall site DR, global GBP performance
- Per-market section (4 × half-page): one section per market with ranking, GBP, conversions, review count, and RAG status
- Next month priorities: top 3 actions per market — from data, not from the original plan
14.2 — Monthly KPI Snapshot — All 4 Markets
| KPI | Source | UK M12 Target | USA M12 Target | DE M12 Target | JP M12 Target |
|---|---|---|---|---|---|
| Primary KW ranking | GSC / Semrush | Top 10 | Top 10 | Top 5 | Top 5 |
| GBP impressions/mo | GBP Insights | 600+ | 200+ | 150+ | 150+ |
| GBP actions/mo | GBP Insights | 40+ | 15+ | 12+ | 10+ |
| Review count | GBP | 30+ | 10+ | 8+ | 8+ |
| Review avg rating | GBP | ≥4.8 | ≥4.7 | ≥4.7 | ≥4.7 |
| Organic sessions/mo | GA4 | 500+ | 150+ | 100+ | 80+ |
| Key events/mo | GA4 | 8+ | 3+ | 2+ | 2+ |
| Hreflang errors | GSC | 0 | 0 | 0 | 0 |
| Referring domains | Ahrefs/Moz | +50 total site | +15 /us/ | +12 /de/ | +10 /ja/ |
14.3 — RAG Per Market Dashboard
Pull on the same date every month (by the 5th):
| Market | Rankings | GBP | Conversions | Technical | Links | Content | OVERALL |
|---|---|---|---|---|---|---|---|
| 🇬🇧 UK | |||||||
| 🇺🇸 USA | |||||||
| 🇩🇪 Germany | |||||||
| 🇯🇵 Japan |
RAG: 🔴 Critical — significantly off target | 🟡 Important — lagging but recoverable | 🟢 On track
The rule from the UK project applies here globally: at least 1 amber or red per market every month. All green across all four markets every month means the targets are too easy.
Pro Tip: The market most likely to show green results fastest is Germany — not because German SEO is easier, but because German buyers who find the page convert faster. A German fashion brand that submits a quote request has already made the decision to buy. US buyers submit quote requests to 4–6 manufacturers simultaneously and compare. Japanese buyers submit a request and then verify every claim in the page before responding. Understand the conversion cycle per market before interpreting GA4 Key Event data — a lower volume of German leads is not a worse result than a higher volume of US leads.
SECTION 15 — INTERNATIONAL SEO TECHNICAL STANDARDS REFERENCE
Applied to This Project
The following standards and guidelines govern the technical decisions in this project. All are publicly accessible for verification.
hreflang specification: Defined by Google at: https://developers.google.com/search/docs/specialty/international/localization-vs-internationalization Validation tool: https://technicalseo.com/tools/hreflang/
Schema.org LocalBusiness: https://schema.org/LocalBusiness — authority for all schema block structures used in Section 5.
GOTS certification public database: https://global-standard.org/find-suppliers-shops-and-inputs/certifiedsuppliers — all GOTS certificate numbers verifiable here.
WRAP certification verification: https://wrapcompliance.org/certified-facilities/ — all WRAP certificates verifiable here. Critical for US market content.
FTC Green Guides (USA): https://www.ftc.gov/system/files/documents/plain-language/bus42-using-green-guides.pdf — governs all sustainability and ethical production claims on US-targeted content.
Google Core Web Vitals: https://web.dev/articles/vitals — LCP ≤2.5s, CLS ≤0.1, INP ≤200ms thresholds applied throughout Sections 9.
UKFT membership (UK market trust signal): https://www.ukft.org/membership/ — industry body listing.
SECTION 16 — GLOSSARY — INTERNATIONAL SEO TERMS
AQL (Acceptable Quality Level): Statistical sampling standard for quality inspection. AQL 2.5 is the international default — 1.5 is the Japanese market standard for premium production. Higher AQL number = more defects accepted.
CMT (Cut, Make, Trim): A pricing model where the client supplies the fabric and the manufacturer handles cutting, sewing, and trimming. Lower factory cost than FOB. Used in the US market for brands who source their own fabric.
DDP (Delivered Duty Paid): An Incoterms trade condition where the seller is responsible for all costs including customs, import duty, and delivery to the buyer’s address. Standard expectation for US buyers. Affects landed cost calculation significantly.
FOB (Free On Board): An Incoterms condition where the seller’s responsibility ends when goods are loaded onto the shipping vessel. Buyer handles freight, customs, and delivery from the port. Common in UK and European B2B fashion.
GSM (Grams per Square Metre): The standard metric for fabric weight. A 160gsm jersey is a lightweight T-shirt fabric. A 340gsm fleece is a heavyweight sweatshirt fabric. Japanese buyers specify GSM precisely — US buyers more commonly specify weight in ounces (oz).
hreflang: An HTML attribute telling Google which language and country version of a page to serve to which user. Missing reciprocal tags are the most common international SEO technical error.
Hochdeutsch: Standard German — the formal written register used in all German B2B content. Distinct from regional dialects (Bavarian, Saxon, etc.) and from Austrian or Swiss German.
Keigo (敬語): Japanese honorific language used in formal business communication. The standard register for all B2B content, enquiry forms, and correspondence.
Mindestbestellmenge: German for “minimum order quantity” (MOQ). The compound noun used in all German-language content for this concept.
Monozukuri (ものづくり): Japanese philosophy of “making things” — a commitment to craftsmanship, precision, and continuous improvement in manufacturing. Central to how Japanese buyers evaluate production partners.
OEKO-TEX® Standard 100: Certification for finished textile products tested against 1,000+ harmful substances. Tests the finished garment, not the supply chain. Distinct from GOTS which covers the entire production chain from raw material.
Polylang / WPML: WordPress multilingual plugins that enable per-language HTML lang attribute setting, URL management, and sitemap separation for international subdirectory implementations.
Sie (German): Formal second-person pronoun in German, equivalent to the historical English “thou” in terms of formality hierarchy but used in all formal modern German business communication. All German content in this project uses Sie — never Du (informal).
Technische Dokumentation / Tech Pack: German term for technical specification document (tech pack). The production brief containing measurements, construction details, materials, and quality standards sent to a manufacturer before sampling begins.
TTFB (Time to First Byte): The time between a user’s browser making an HTTP request and receiving the first byte of data from the server. A key measure of server performance. Target: <600ms. Affected significantly by geographic server distance — CDN configuration reduces TTFB for international users.
x-default: The hreflang attribute value for the fallback page served when no other language/country match applies. Typically set to the primary language version (en-GB for Meridian Cloth Co.).
PROJECT COMPLETION SUMMARY — INTERNATIONAL SEO LIVE PROJECT
What This Project Built
| Deliverable | Section | Markets |
|---|---|---|
| International framework + 4-market NAP register | S0 | All |
| Keyword clusters: 25 US terms, 21 German terms, 19 Japanese terms | S1 | USA, DE, JP |
| URL structure + GSC geotargeting map | S2 | All |
| Complete hreflang implementation (HTML + XML sitemap) | S3 | All |
| Landing page specs + Quick Answer blocks — 3 new markets | S4 | USA, DE, JP |
| Pricing tables in USD, EUR, JPY | S4 | USA, DE, JP |
| FAQ blocks in English (US), German, Japanese | S4 | USA, DE, JP |
| Schema library — 3 new LocalBusiness blocks + Organization update | S5 | All |
| GBP descriptions — 3 new markets in target languages | S6 | USA, DE, JP |
| GBP post calendar — all 3 new markets Month 1 | S6 | USA, DE, JP |
| Citation priority lists — 16 US, 14 German, 11 Japanese | S7 | USA, DE, JP |
| Content clusters — 5 posts per market (15 total) | S8 | USA, DE, JP |
| International technical checklist — 14 specific checks | S9 | All |
| CDN / server performance solution | S9 | USA, JP |
| Backlink targets — 11 US, 10 German, 8 Japanese | S10 | USA, DE, JP |
| Competitive gap analysis — 3 SERP markets | S11 | USA, DE, JP |
| GA4 4-stream setup + market custom dimension | S12 | All |
| GBP UTM links per market | S12 | All |
| 12-month phased action plan | S13 | All |
| Monthly reporting template — per market + global rollup | S14 | All |
| International glossary — 17 terms | S16 | All |
The Five Things That Make International SEO Fail at This Scale
1. Treating translation as localisation. Translation changes the words. Localisation changes the trust signals, legal compliance, pricing currency, buyer psychology, and cultural register. Every section of this project addresses localisation — not translation.
2. Skipping hreflang or implementing it with errors. A hreflang tag set with missing reciprocal tags is worse than no hreflang implementation at all — it actively sends conflicting signals. Section 3 provides the complete validated implementation.
3. Using the UK link profile to support all markets. A UK editorial backlink does not strengthen rankings in Germany or Japan. Each market needs its own link profile, built through market-specific Chamber applications, industry body submissions, and country-relevant editorial pitches.
4. Failing to adapt content for the market’s trust signals. US buyers need FTC compliance and WRAP certification. German buyers need GOTS certificate verification links and pricing disclaimers. Japanese buyers need AQL specification and a response time commitment. None of these are interchangeable.
5. Measuring all four markets in one aggregate report. 200 US sessions and 80 Japanese sessions in the same GA4 report without market segmentation produces numbers that mean nothing. Section 12 builds the custom dimension structure that makes per-market measurement possible from Month 1.
Month 12 — What Success Looks Like
UK: Top 10 “clothing manufacturer London” · 30+ reviews · 600+ GBP impressions/mo
USA: Top 10 “apparel manufacturer USA” · 10+ US reviews · 200+ GBP impressions/mo · First Sourcing Journal or equivalent editorial backlink confirmed
Germany: Top 5 “Bekleidungshersteller” · 8+ German reviews · 150+ GBP impressions/mo · WLW and textil+mode listings confirmed live
Japan: Top 5 「アパレルメーカー」· 8+ Japanese reviews · 150+ GBP impressions/mo · JTFF listing confirmed live · Japanese content reviewed by native speaker
Global: +50 UK referring domains (multi-location project target maintained) · +15 US /us/ referring domains · +12 German /de/ referring domains · +10 Japanese /ja/ referring domains · 0 hreflang errors · All 4 markets cited in AI Overview results for their primary market keyword
CITATIONS & SOURCES
1. BrightLocal. Local Consumer Review Survey 2024. BrightLocal, 6 March 2024. https://www.brightlocal.com/research/local-consumer-review-survey-2024/ Supports: 88% of consumers would use a business that replies to all reviews · 81% use Google to find local business reviews (Sections 6, 14).
2. Whitespark. Local Search Ranking Factors 2023. Whitespark, 2023. https://whitespark.ca/local-search-ranking-factors/ Supports: Local Pack factor weightings — GBP signals 32%, On-Page 19%, Reviews 16%, Links 11%, Citations 7% (Sections 6, 10, 11).
3. Google. How to improve your local ranking on Google. Google Business Profile Help, 2024. https://support.google.com/business/answer/7091 Supports: Relevance, Distance, and Prominence as Google’s three confirmed Local Pack ranking factors (Section 6).
4. Google. Core Web Vitals. web.dev, October 2024. https://web.dev/articles/vitals Supports: LCP ≤2.5s, CLS ≤0.1, INP ≤200ms pass thresholds (Section 9).
5. Google. Understand how structured data works. Google Search Central, 2024. https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data Supports: JSON-LD as Google’s recommended structured data format · Schema validation requirements (Section 5).
6. Google. Localisation versus Internationalisation — hreflang. Google Search Central, 2024. https://developers.google.com/search/docs/specialty/international/localization-vs-internationalization Supports: hreflang implementation standards, reciprocal tag requirements, x-default usage (Section 3).
7. Schema.org. LocalBusiness. Schema.org, 2024. https://schema.org/LocalBusiness Supports: All LocalBusiness schema block structures across all four markets (Section 5).
8. GOTS. Certification — Global Organic Textile Standard. Global Standard, 2024. https://global-standard.org/certification-and-labelling/certification Supports: GOTS as the leading organic textile certification standard referenced across DE, JP, UK, and US content (Sections 4, 7, 10, 11).
9. US Federal Trade Commission. Using Environmental Marketing Claims: The Green Guides. FTC, 2024. https://www.ftc.gov/system/files/documents/plain-language/bus42-using-green-guides.pdf Supports: FTC compliance requirements for all ethical and sustainability claims on US-targeted content (Section 4).
10. WRAP. WRAP Certification. Worldwide Responsible Accredited Production, 2024. https://wrapcompliance.org/certification/ Supports: WRAP as the primary ethical certification trust signal for the US market · Certificate verification at wrapcompliance.org (Section 4).
11. UKFT. Membership. UK Fashion & Textile Association, 2024. https://www.ukft.org/membership/ Supports: UKFT as a primary industry body trust signal and niche backlink source for UK and international content (Section 10).
12. Birdeye. State of Google Business Profile 2025. Birdeye, January 2025. https://birdeye.com/blog/state-of-google-business-profiles/ Supports: GBP interaction split — 48% website visits, 17% phone calls, 34% direction requests (Section 6 GBP strategy).
Meridian Cloth Co.
UK · USA · Germany · Japan
Applied: International SEO Master Prompt v2.0 · 4 markets · 4 languages · 85–110 hours delivery
S0 — 4-Market Architecture Overview
Source: Meridian Cloth Co. International SEO Live Project S0 · aiseojournal.net · March 2026
⚠ URL structure choice: subdirectories selected over ccTLDs — consolidates all domain authority under one domain. ccTLDs only make sense when a large existing per-market link profile exists and a registered entity in each country. Neither applies at this stage.
S1 — Keyword Intelligence: The Terminology Gap Per Market
Research method: target search engine + target location + target language per market · Source: S1, aiseojournal.net
T1 Keyword Volume by Market (est. midpoint)
Primary T1 keywords only · Source: S1 keyword clusters, Meridian Cloth Co. Live Project
S11 — Competitive Gaps: What No Competitor Has
SERP snapshot per market: 0 of 5 competitors in each market have these elements
Meridian Cloth Co. is content-superior in all 3 new markets from day of publication.
S3 — Hreflang Strategy: 5 Tag Sets, 7 Validation Checks
Source: Meridian Cloth Co. International SEO Live Project S3 · hreflang and canonical must always agree
S3 — 7-Point Hreflang Validation Checklist
Source: S3 validation checklist · validate at technicalseo.com/tools/hreflang/
S2 — URL Architecture: Why Subdirectories (not ccTLDs)
Source: S2 architecture decision · meridianclothco.co.uk
S4 — Market-Specific Compliance Rules (Landing Pages)
Source: Meridian Cloth Co. International SEO Live Project S4 · each market has a non-negotiable compliance layer
S6 — GBP Verification Timelines & S7 — Citation Counts per Market
Source: Meridian Cloth Co. International SEO Live Project S6 & S7 · Plan GBP build 6 weeks before go-live
GBP Verification Timeline by Country
Source: S6 GBP Setup Per Market table · meridianclothco.co.uk Live Project
| Market | GBP Post language | Review response | Photos |
|---|---|---|---|
| 🇺🇸 USA | English (US) | English (US) | US-context |
| 🇩🇪 Germany | German (Sie form) | German | Neutral / DE |
| 🇯🇵 Japan | Japanese (ます/です) | Japanese + English | JP-context |
Citation Targets Per Market (from S7)
Source: S7 citation priority lists · UK citations do not help USA or Japan
US: BBB accreditation (DR 91) — stronger US trust signal than any other market · DE: WLW (wlw.de) — German B2B directory equivalent of ThomasNet · JP: Yahoo! Japan Local — covers 19% of Japanese search traffic
S8 — Content Clusters: 15 Posts Across 3 New Markets
Source: Meridian Cloth Co. International SEO Live Project S8 · all non-UK clusters in target language
| Market | Cluster Post Title | Target Keyword | URL | Priority |
|---|---|---|---|---|
| 🇺🇸 USA | What Does Apparel Manufacturing Cost in the USA? | apparel manufacturing cost USA | /blog/us/apparel-manufacturing-cost-usa/ | Month 2 |
| 🇺🇸 USA | What Is Cut and Sew Manufacturing? | cut and sew manufacturing | /blog/us/what-is-cut-and-sew-manufacturing/ | Month 3 |
| 🇺🇸 USA | WRAP vs GOTS: Which Certification Do US Buyers Need? | WRAP vs GOTS certification | /blog/us/wrap-vs-gots-certification/ | Month 3 |
| 🇩🇪 Germany | Was kostet Bekleidungsproduktion in Europa? | Bekleidungsproduktion Kosten Europa | /de/blog/bekleidungsproduktion-kosten/ | Monat 2 |
| 🇩🇪 Germany | GOTS oder OEKO-TEX — welche Zertifizierung brauche ich? | GOTS OEKO-TEX Unterschied | /de/blog/gots-vs-oeko-tex/ | Monat 2 |
| 🇩🇪 Germany | Kleine Auflagen produzieren — Leitfaden für Startups | kleine Auflagen Bekleidung | /de/blog/kleine-auflagen-produktion/ | Monat 3 |
| 🇯🇵 Japan | アパレルOEMの費用はいくら?完全ガイド | アパレルOEM 費用 | /ja/blog/apparel-oem-cost/ | 2ヶ月目 |
| 🇯🇵 Japan | 小ロット縫製工場の選び方 | 小ロット縫製工場 選び方 | /ja/blog/small-lot-factory-guide/ | 3ヶ月目 |
| 🇯🇵 Japan | GOTS認証とは?ファッションブランドが知るべきこと | GOTS認証 とは | /ja/blog/gots-certification-guide/ | 3ヶ月目 |
⚠ German and Japanese clusters must be reviewed by a native speaker before publishing — machine translation fails subtly (correct grammar, wrong industry register). German buyers notice immediately. Japanese buyers notice even faster.
S10 — Backlink Targets per Market & S12 — GA4 International Tracking
Source: Meridian Cloth Co. International SEO Live Project S10 & S12
Top Editorial + Industry Backlink Targets by Market (DR)
Source: S10 backlink strategy tables · geographic relevance > raw domain authority for market ranking
Exact match anchor text cap: ≤5% per market domain path. US anchors: "apparel manufacturer" · DE anchors: "Bekleidungshersteller" (German language) · JP outreach must be sent in Japanese.
GA4 International Setup — 3 Custom Dimensions
Source: S12 · one GA4 property, 4 data streams — UK / US / DE / JP
UK London: ?utm_source=gbp&utm_medium=local&utm_campaign=uk-london
USA New York: ?utm_source=gbp&utm_medium=local&utm_campaign=us-new-york
Germany: ?utm_source=gbp&utm_medium=local&utm_campaign=de-berlin
Japan Tokyo: ?utm_source=gbp&utm_medium=local&utm_campaign=jp-tokyoS14 — Month 12 KPI Targets — All 4 Markets
Source: S14 Monthly KPI Snapshot · Meridian Cloth Co. International SEO Live Project · aiseojournal.net
| KPI | Source | 🇬🇧 UK | 🇺🇸 USA | 🇩🇪 Germany | 🇯🇵 Japan |
|---|---|---|---|---|---|
| Primary KW ranking | GSC / Semrush | Top 10 | Top 10 | Top 5 | Top 5 |
| Local Pack target | Google SERP | Top 3 | Top 3 New York | Top 3 Berlin | Top 3 Tokyo |
| GBP impressions / mo | GBP Insights | 600+ | 200+ | 150+ | 150+ |
| GBP actions / mo | GBP Insights | 40+ | 15+ | 12+ | 10+ |
| Review count | GBP | 30+ | 10+ | 8+ | 8+ |
| Avg star rating | GBP | ≥4.8 | ≥4.7 | ≥4.7 | ≥4.7 |
| Organic sessions / mo | GA4 | 500+ | 150+ | 100+ | 80+ |
| Key Events / mo | GA4 | 8+ | 3+ | 2+ | 2+ |
| Hreflang errors | GSC International | 0 | 0 | 0 | 0 |
| New referring domains | Ahrefs/Moz | +50 site-wide | +15 /us/ | +12 /de/ | +10 /ja/ |
S13 — 12-Month International Action Plan
Source: Meridian Cloth Co. International SEO Live Project S13 · phased across all 4 markets
5 Rules That Make International SEO Different From Local
Directly from the project completion summary · Source: aiseojournal.net







![# amazonproject1.co.uk — Amazon SEO Live Project ## Stage 2: Listing Optimisation **Format:** Hands-On Live Project A–Z | aiseojournal.net | March 2026 **Store:** amazonproject1.co.uk | Platform: Amazon.co.uk | UK Marketplace **Applied:** Amazon SEO Master Prompt v1.0 · Forbidden Words List (9 categories, 70+ phrases) **Prerequisite:** Stage 1 complete — all 8 checklist sections confirmed, keyword baseline recorded, competitor gap tables written, Brand Registry active **Stage objective:** Rewrite every Tier 1 priority ASIN's title, bullets, and backend search terms using confirmed keyword data; build A+ Content for all priority ASINs; create the Amazon Brand Store; and deliver a keyword placement map per ASIN that leaves no indexable field empty --- VARIATION SELECTION Tone: E (Practitioner) — written as the brand's Amazon listing manager Language: 2 (Moderate) — Amazon field names and algorithm terms used precisely Opening: Problem-first — the specific gap Stage 1 confirmed that Stage 2 closes --- # SECTION 9 — LISTING OPTIMISATION STRATEGY ## The Gap Stage 1 Confirmed Stage 1 found it. Stage 2 closes it. The competitor gap tables in Section 4 showed that the top-ranking ASINs for the brand's primary keywords have their primary keyword in the first 47–55 characters of the title, A+ Content active, size chart images, benefit-first bullet 1, and 100+ reviews at 4.5 stars. The brand's ASINs have none of those — or an incomplete version of most. Stage 2 does not guess at what to write. It writes specifically from the confirmed keyword data in Section 3, the confirmed competitor gaps in Section 4, and the confirmed negative review themes in Section 8. Every title word, every bullet claim, and every backend term in Stage 2 comes from confirmed data — not from a generic copywriting template. > **Pro Tip:** The most common listing optimisation mistake on Amazon.co.uk is improving everything slightly. A title that improves from 7/10 to 8/10 quality does not move BSR. A title rewritten to put the exact high-volume keyword in the first 50 characters, with UK size and colour stated, and a secondary keyword before character 120 — that moves BSR. Stage 2 is about transformational changes to the two or three fields that matter most, not incremental polish across every field. ## 9.1 — Listing Optimisation Priority Order Stage 2 optimises ASINs in the order established in Section 2.2's ASIN Priority Matrix. The sequence is: 1. Highest-revenue ASIN with the largest confirmed keyword gap 2. ASINs with Category C keywords (clicks but no purchases — confirmed CVR problem) 3. ASINs ranking positions 4–8 for primary keyword — closest to the top 3 4. New ASINs launching in Stage 2 — get the listing right before launch, not after 5. Remaining ASINs — systematic completion through Stage 3 **Why revenue rank alone does not determine optimisation order:** An ASIN at #3 by revenue with a CVR of 4.2% that the category average is 12% is losing far more money to underperformance than its revenue rank suggests. Fixing the CVR from 4.2% to 9% on an ASIN generating £8,000/month produces more incremental revenue than optimising an already-performing ASIN at £12,000/month with a CVR of 11%. ## 9.2 — The A9/A10 Keyword Placement Hierarchy Before writing a single word of listing copy, confirm this hierarchy. Every recommendation in Stage 2 is built on it. Amazon's A9/A10 algorithm reads listing fields in this order of relevance weighting: | Position | Field | A9 weighting | Character / byte limit | |---|---|---|---| | 1 | Product title | Highest | 80–200 chars (category-dependent) | | 2 | Backend search terms | High | 250 bytes total | | 3 | Bullet points (all 5) | Medium-high | 500 chars each | | 4 | A+ Content text modules | Medium (indexed from 2023) | ~300 words per module | | 5 | Product description | Lower (suppressed when A+ active) | 2,000 chars | | 6 | Subject matter / intended use | Low | 50 chars each | **The two rules that follow from this hierarchy:** Rule 1: A primary keyword that appears in the title and the backend search terms is weighted more strongly than a keyword that appears in only one location. Never treat these fields as alternatives — they stack. Rule 2: The backend search terms field is the most underused field in most Amazon accounts. Most sellers use fewer than 100 bytes of the 250 available. Every unused byte is a missed keyword. Stage 2 fills the backend to 245–250 bytes for every ASIN. ## 9.3 — UK Listing Language Standards Apply these standards to every piece of listing copy produced in Stage 2. No exceptions. **Spelling:** colour, grey, organise, recognise, maximise, centre, theatre, jewellery, catalogue, licence (noun), practice (noun). The spell-checker default in most copywriting tools is US English — override it. **Sizing:** UK 6 / UK 8 / UK 10 / UK 12. Not XS/S/M/L/XL as primary notation (add these in brackets after UK size if required). Never US sizing as primary. **Measurements:** cm as primary unit. Inches in brackets if required for specific categories. Never inches as primary unit. **Currency:** £ as primary. GBP in formal references. No $. **Dates:** DD/MM/YYYY format where applicable. **Phone / voltage:** 230V, three-pin UK plug (BS 1363). State explicitly for electrical products. **Consumer law:** "30-day returns" is not just good service — it is the UK legal minimum under the Consumer Rights Act 2015. State it as a feature, not as a concession. > **Pro Tip:** UK Amazon buyers read listing copy looking for signals that the product is genuinely intended for them. An American seller who has copied their Amazon.com listing without changing the sizing, spelling, or measurements sends a subtle but persistent signal that this product was not designed for UK buyers. Buyers do not consciously notice US spelling or inch measurements — but the conversion rate is measurably lower than listings that speak fluent British English. The fix takes 20 minutes per listing and the impact persists permanently. --- # SECTION 10 — TITLE OPTIMISATION (ALL PRIORITY ASINS) ## Titles: The Most Important Field on Amazon Amazon truncates titles in search results at approximately 55–65 characters on desktop and 40–55 characters on mobile. The primary keyword, the most compelling differentiator, and the UK signal must all appear before the truncation point. A buyer on mobile who sees a product title truncated at "Women's Merino Wool Roll-Neck Jumper in..." makes their click decision based on those first 40–45 characters. They do not see what follows the truncation. If the primary keyword and a differentiating signal are not in those first characters, the click may go to a competitor whose title did manage it. > **Pro Tip:** The biggest title optimisation mistake is starting with the brand name. Amazon recommends brand name first in most categories — but brand name first means the primary keyword appears later in the title, behind the truncation point on mobile for most buyers. Test both orders: [Brand] [Primary Keyword] vs [Primary Keyword] [Brand]. For established brands with high recognition, brand-first makes sense. For brands at early stages of Amazon growth, keyword-first wins more clicks from buyers who have not yet heard of the brand. ## 10.1 — Title Formula by Product Category **CLOTHING TITLE FORMULA:** `[Brand Name] [Primary Keyword] [Key Material Attribute] [UK Size Range] [Colour(s) Available]` Character target: 120–150 characters (most clothing categories permit 200 — use the space) Mobile truncation target: Primary keyword AND at least one differentiator in first 55 characters UK size: UK [range] — not XS-XL as primary Example (55 chars desktop truncation point marked with |): `shopifystore1 Merino Wool Roll-Neck Jumper Women UK| 6-22 Navy Grey Camel GOTS Certified` (Result: "shopifystore1 Merino Wool Roll-Neck Jumper Women UK" visible on mobile before truncation — primary keyword present) **HEALTH & BEAUTY TITLE FORMULA:** `[Brand Name] [Primary Keyword] [Key Active Ingredient or Benefit] [Volume/Size] [Skin Type or Use Case]` Character target: 100–140 characters Mobile truncation target: Primary keyword in first 50 characters Prohibited: "clinically proven", "best", "#1" without Amazon category validation **HOME & KITCHEN TITLE FORMULA:** `[Brand Name] [Primary Keyword] [Key Material] [Dimensions in cm] [Colour] [Pack Size if applicable]` Character target: 100–150 characters Dimensions: in cm as primary unit — e.g. "40×30×20cm" **SPORTS & FITNESS TITLE FORMULA:** `[Brand Name] [Primary Keyword] [Key Performance Spec] [UK Size Range] [Colour]` Performance spec: hydrostatic head (mm) for waterproof gear, fill power for down insulation, denier for backpacks ## 10.2 — Title Rewrites Per ASIN --- **ASIN 1 TITLE REWRITE** | Element | Current | Stage 2 | |---|---|---| | ASIN | [B0XXXXXXXXXX] | — | | Current title | [CURRENT FULL TITLE — copy from listing] | — | | Current char count | [X chars] | — | | Primary keyword (from S3 SQP) | — | [PRIMARY KW — confirmed UK volume] | | Primary keyword position (current) | Character [X] | Target: character 1–55 | | UK size stated | ✅ / ❌ | Must be present | | UK spelling throughout | ✅ / ❌ | Must be confirmed | **Stage 2 Title:** `[WRITE FULL REWRITTEN TITLE HERE — no placeholder, specific to this ASIN]` Character count: [X] of [category limit] Primary keyword in first 55 chars: ✅ confirmed at character [X] Secondary keyword present: ✅ at character [X] UK size range stated: ✅ UK spelling: ✅ Prohibited content (promotional language, pricing, subjective claims): ❌ none present **Reasoning:** The current title places the primary keyword "[current KW position]" at character [X] — behind the mobile truncation point of approximately 50 characters. The majority of this ASIN's sessions come from mobile (confirm in Seller Central Business Reports → filter by device). The rewritten title moves "[primary keyword]" to characters 1–[X], placing it within every device's visible title length. The UK size range "[UK X–XX]" is added explicitly — confirmed as the most common 3-star review theme ("no UK sizing information") in Section 8. --- **ASIN 2 TITLE REWRITE** | Element | Current | Stage 2 | |---|---|---| | ASIN | [B0XXXXXXXXXX] | — | | Current title | [CURRENT FULL TITLE] | — | | Primary keyword position (current) | Character [X] | Target: character 1–55 | **Stage 2 Title:** `[WRITE FULL REWRITTEN TITLE HERE]` Character count: [X] of [category limit] **Reasoning:** [Specific reasoning based on Section 3 keyword data and Section 4 competitor gap — not generic guidance] --- *(Repeat title rewrite block for every Tier 1 priority ASIN from Section 2.2 priority matrix)* ## 10.3 — Title Implementation **Seller Central path:** Admin → Inventory → Manage Inventory → Edit → Product Details → Product Name field **Important:** Changing a title on an ASIN with an active Amazon's Choice badge carries risk. Amazon's algorithm may re-evaluate the badge assignment after a title change. If an ASIN currently holds an Amazon's Choice badge for a specific keyword — do not change the title until confirming the new title still contains that keyword prominently. **Implementation rule:** Never change a title and backend search terms simultaneously on the same day for a high-performing ASIN. Change the title first. Wait 5–7 days to observe any BSR or ranking movement. Then update the backend. Changing all fields simultaneously makes it impossible to isolate which change produced which result. ✅ **CHECKPOINT — SECTION 10** - [ ] All Tier 1 ASIN titles rewritten and implemented in Seller Central - [ ] Primary keyword confirmed in first 55 characters on every rewritten title - [ ] UK spelling confirmed throughout all titles - [ ] UK size range stated in all applicable clothing titles - [ ] Amazon's Choice badge ASINs: title change approach confirmed — keyword preserved - [ ] BSR monitoring: baseline BSR recorded on date of each title change --- # SECTION 11 — BULLET POINT OPTIMISATION ## Bullets: Where Keywords Become Conversion The title earns the click. The bullets earn the purchase. A buyer who clicks through to an Amazon product detail page has already seen the main image and the title in search results. They have shown purchase intent by clicking. The bullets are the first content block most buyers read on the detail page — and the most read content element after the title on mobile (where A+ Content sits below the fold). The A9 algorithm weights bullet point text at medium-high relevance — below title but above product description. Each bullet is also indexed individually. A keyword that appears in bullet 1 and also in the title receives stronger relevance signals than a keyword that appears only in the description. > **Pro Tip:** The single highest-impact bullet point change on most Amazon.co.uk listings is bullet 1. Most sellers write bullet 1 as a feature statement: "MADE FROM 100% MERINO WOOL". The buyer already knows this from the title. Bullet 1 should be the primary benefit — what the buyer gets as a result of the feature: "NATURALLY TEMPERATURE-REGULATING WARMTH: Merino wool's unique fibre structure keeps you warm in cold rooms and cool when you overheat — no mid-day jumper removal required." The feature is in there. But the lead is the benefit. Benefit-first bullet 1 consistently produces higher CVR on fashion and lifestyle products. ## 11.1 — Bullet Point Framework **5-bullet structure (applies to all product categories with adaptation):** **Bullet 1 — Primary benefit (benefit-first, primary keyword variant):** Format: `[ALL CAPS BENEFIT HEADER]: [Benefit claim] — [Feature that delivers it] — [Specific detail that makes the claim credible]` Primary keyword or close variant: must appear in bullet 1 body text (not just the header) Character target: 180–200 characters (safe mobile display length) UK-specific detail: UK size, UK climate context, UK legal right, or UK certification **Bullet 2 — Material / ingredient / specification:** Format: `[ALL CAPS SPEC HEADER]: [Material composition with %] — [Why it matters to the buyer] — [Certification or verification if applicable]` Secondary keyword: include naturally Character target: 180–200 characters **Bullet 3 — Size / fit / compatibility / use case:** Format: `[ALL CAPS USE CASE HEADER]: [UK size range or compatibility list] — [Fit or use description] — [Styling or pairing suggestion]` UK sizing: explicit (UK 6–22 format) Character target: 180–200 characters **Bullet 4 — Care / safety / compliance:** Format: `[ALL CAPS CARE HEADER]: [Care instruction] — [Why this care instruction matters for this material] — [UK compliance mark or certification where held]` UK legal signal: Consumer Rights Act 2015 return period where appropriate Character target: 180–200 characters **Bullet 5 — Brand / trust / soft navigation:** Format: `[ALL CAPS BRAND HEADER]: [Brand credential or review reference] — [Guarantee or promise] — [Range navigation: "See our full range of [product type] — [brand name] on Amazon"]` Review count reference: only if ≥20 verified reviews — state the number and average rating Character target: 180–200 characters **Permitted formatting in bullets:** ALL CAPS for the header text of each bullet — Amazon permits this Em dash (—) as separator within bullet body — standard Amazon style No HTML tags in bullets — Amazon strips them outside the description field No numbered lists within bullets — use dash separators **Prohibited content:** Pricing, shipping claims, contact information, time-sensitive promotions, availability claims, website URLs, competitor comparisons by name ## 11.2 — Bullet Rewrites Per ASIN --- **ASIN 1 — BULLET REWRITES** **Current bullets (record verbatim before any changes):** Bullet 1: [CURRENT TEXT] Bullet 2: [CURRENT TEXT] Bullet 3: [CURRENT TEXT] Bullet 4: [CURRENT TEXT] Bullet 5: [CURRENT TEXT] **Negative review theme addressed in these bullets (from Section 8.2):** Theme: "[Most common negative review theme for this ASIN]" Fix location: Bullet [X] — specifically addresses this concern **Stage 2 Bullets:** Bullet 1: `[ALL CAPS BENEFIT HEADER]: [Benefit-first claim — specific, verifiable — primary keyword variant included — under 200 chars]` Keyword coverage: [state which keyword from Section 3 is placed here] Character count: [X] Bullet 2: `[ALL CAPS SPEC HEADER]: [Material composition X% — secondary keyword — certification name if held — verification method — under 200 chars]` Keyword coverage: [secondary keyword] Character count: [X] Bullet 3: `[ALL CAPS SIZE HEADER]: [UK size range — fit description — model reference — occasion — under 200 chars]` UK sizing: UK [X]–[X] stated explicitly Character count: [X] Bullet 4: `[ALL CAPS CARE HEADER]: [Specific care instruction — material-specific reason — UK care label standard referenced — under 200 chars]` UK compliance: [state which UK-specific element is included] Character count: [X] Bullet 5: `[ALL CAPS BRAND HEADER]: [Review count reference (if ≥20) — brand credential — range navigation — under 200 chars]` E-E-A-T signal: [state which signal is included — review count, certification, UK credential] Character count: [X] **Keyword coverage summary for ASIN 1 bullets:** | Keyword | Bullet 1 | Bullet 2 | Bullet 3 | Bullet 4 | Bullet 5 | |---|---|---|---|---|---| | [Primary KW] | ✅ | | | | | | [Secondary KW 1] | | ✅ | | | | | [Secondary KW 2] | | | ✅ | | | | [Tier 3 KW] | | | | | ✅ | --- **ASIN 2 — BULLET REWRITES** **Current bullets:** Bullet 1: [CURRENT TEXT] ... **Stage 2 Bullets:** Bullet 1: `[FULL REWRITTEN BULLET 1]` Bullet 2: `[FULL REWRITTEN BULLET 2]` Bullet 3: `[FULL REWRITTEN BULLET 3]` Bullet 4: `[FULL REWRITTEN BULLET 4]` Bullet 5: `[FULL REWRITTEN BULLET 5]` --- *(Repeat full bullet rewrite block for every Tier 1 priority ASIN)* ## 11.3 — Bullet Length Optimisation for Mobile Amazon does not display all 500 characters of each bullet on mobile devices. The mobile bullet display truncates at approximately 200–250 characters. The most critical information — the benefit claim and the primary keyword — must appear in the first 200 characters of each bullet. Run this test for every rewritten bullet: 1. Count to character 200 in the bullet text 2. Confirm: does the primary claim and keyword appear before character 200? 3. If not: restructure the bullet so the most important content leads **The common mobile truncation failure pattern:** `PREMIUM QUALITY KNITWEAR: This beautiful jumper has been lovingly crafted from the finest pure merino wool sourced from ethically-certified farms in New Zealand, hand-finished to perfection, and is available in the full UK size range from 6 to 22, making it ideal for all body types...` By character 200, the buyer has seen "PREMIUM QUALITY KNITWEAR: This beautiful jumper has been lovingly crafted from the finest pure merino wool sourced from ethically-certified farms" — no UK size information, no specific benefit claim, no keyword. Everything after character 150 is wasted on mobile. The rewritten version: `TEMPERATURE-REGULATING MERINO WOOL: 100% certified merino keeps you warm without overheating — naturally breathable, odour-resistant. UK sizes 6–22. GOTS certified factory (cert. no. verify at global-standard.org).` By character 200 the buyer has seen: primary benefit, material composition, UK size range, and certification. Every critical claim lands before the truncation point. ✅ **CHECKPOINT — SECTION 11** - [ ] All Tier 1 ASIN bullets rewritten — all 5 per ASIN, full copy confirmed - [ ] Bullet 1: benefit-first format confirmed on all ASINs - [ ] Primary keyword: confirmed in bullet 1 body text on all ASINs - [ ] UK sizing: explicitly stated in bullet 3 on all applicable ASINs - [ ] Negative review themes: each ASIN's primary theme addressed in a specific bullet - [ ] Mobile truncation check: all bullets pass — critical content in first 200 chars - [ ] Prohibited content check: no pricing, shipping, URLs in any bullet - [ ] Implementation: all bullets updated in Seller Central — changes live --- # SECTION 12 — BACKEND SEARCH TERMS OPTIMISATION ## 250 Bytes: The Most Underused Field in Amazon SEO Most sellers fill between 40 and 150 bytes of the 250-byte backend search terms field. The remaining 100–210 bytes are wasted indexing opportunity — keywords that could be driving organic impressions but are not because nobody added them. The backend search terms field is invisible to buyers. It does not appear anywhere on the product detail page. It exists purely for Amazon's indexing system — and every byte used tells the algorithm one more thing this ASIN is relevant for. Unlike the title and bullets, backend search terms have almost no impact on CTR or CVR. Their entire value is in organic keyword coverage — increasing the number of search queries this ASIN appears in. They are the cheapest ranking action available. > **Pro Tip:** The most valuable content to put in backend search terms is the content you cannot comfortably fit in the title or bullets — UK misspellings, synonyms, complementary product terms, seasonal terms, and gift occasion terms. A clothing ASIN with "jumper" in the title should have "sweater", "pullover", "knitwear", and "top" in the backend. A skincare ASIN with "moisturiser" in the title should have "moisturizer" (American spelling variant — UK buyers sometimes search both), "face cream", "skin cream", and "hydrating lotion" in the backend. These terms earn impressions from buyers who use different vocabulary — without crowding the visible listing with synonyms. ## 12.1 — Backend Search Terms Rules (Amazon.co.uk — 2025) Before writing backend terms, apply every rule: **Byte count rule:** The limit is 250 bytes, not 250 characters. Multi-byte characters (accented letters, certain special characters) count as 2 bytes each. Standard ASCII characters (all standard English letters, numbers, spaces) count as 1 byte each. For UK English listings with no accented characters, bytes = characters. Target: 245–250 bytes used. **No repetition rule:** Any word already in the title or bullets is wasted as a backend term — Amazon's algorithm already indexes it from those higher-weighted fields. Adding "merino" to backend when it is already in the title occupies bytes without adding indexing value. **No competitor brand names:** Direct Amazon policy violation. Results in listing suppression if detected. Never add competitor brand names, regardless of how relevant they may seem. **No superlatives:** "best", "cheapest", "top-rated" without substantiation — prohibited. **No promotional content:** "sale", "discount", "offer" — prohibited. **Space-separated, no commas:** Amazon's system reads commas as characters, not separators. Space-separate every term. **Case insensitive:** Amazon's search is case-insensitive. "Merino" and "merino" are treated identically. Do not waste bytes on capitalisation variations. ## 12.2 — Backend Search Terms Content Strategy Fill the 250 bytes in this priority order: **Priority 1 — Confirmed converting keywords not yet in title or bullets:** From Section 3.1 Category A (converting search terms) — any term that generates purchases but is not in the title or bullets belongs here first. **Priority 2 — Near-miss keywords from Section 3.3:** Keywords where the ASIN earns impressions but click rank > 5 — adding to backend reinforces relevance signal. **Priority 3 — UK misspellings and common typos:** UK buyers make predictable spelling errors. "Cashmier" for cashmere. "Mereno" for merino. "Menstration" (health products). These misspellings have real search volume — and no competitor's listing will have them in the title, so adding them to backend can produce first-page appearances for zero-competition queries. **Priority 4 — Synonyms for the primary product type:** "Jumper" AND "sweater" AND "pullover" AND "knitwear" — same product, different vocabulary, different buyers. **Priority 5 — Complementary and gifting terms:** "gift for her", "Christmas gift women", "birthday gift", "gift idea" — seasonal search intent that drives discovery from buyers who were not searching for the specific product category. **Priority 6 — Use case and occasion terms:** "work jumper", "smart casual", "office knitwear", "weekend jumper", "autumn winter jumper" — contextual terms that expand the ASIN's relevance to specific buyer situations. ## 12.3 — Backend Search Terms Per ASIN **ASIN 1 — Backend Search Terms** Current backend (record verbatim — count bytes): `[CURRENT BACKEND TEXT]` Current byte count: [X] of 250 bytes used. Analysis: - Words repeated from title (wasted bytes): [list] - Competitor brand names (policy violation — remove): [list or "none"] - Bytes wasted on repetition + violations: [X bytes] - Effective indexing coverage: approximately [X] unique keywords Stage 2 Backend Search Terms: `[WRITE FULL BACKEND STRING — space-separated, no commas, no repeated words from title, no competitor brands, target 245–250 bytes]` Stage 2 byte count: [X] of 250 bytes Unique keywords added vs current backend: [X new terms] Keyword coverage added by Stage 2 backend (terms not in title or bullets): - Synonyms: [list — e.g. sweater, pullover, knitwear] - UK misspellings: [list — e.g. mernio, cashmier] - Gift terms: [list — e.g. gift for her Christmas gift birthday] - Use case terms: [list — e.g. office workwear smart casual] - Seasonal terms: [list — e.g. autumn winter warm cosy] - Complementary products: [list — e.g. scarf gloves hat wool] --- **ASIN 2 — Backend Search Terms** Current backend: `[CURRENT TEXT]` Current byte count: [X] of 250 Stage 2 Backend: `[FULL REWRITTEN BACKEND — 245–250 bytes — no repeated words from title or bullets — no competitor brands]` Stage 2 byte count: [X] of 250 --- *(Repeat for every Tier 1 priority ASIN)* ## 12.4 — Backend Byte Counter Tool Before implementing, verify byte count using one of these methods: 1. Helium 10 → Listing Builder → paste backend text → byte count display 2. Seller Central listing editor → the backend field shows "X bytes remaining" after the input box 3. Simple Python check: `len(text.encode('utf-8'))` — paste into any Python environment Never submit backend terms without confirming the byte count. Amazon silently ignores everything beyond 250 bytes — the terms are not indexed, and there is no error message. Sellers routinely discover their backend terms were never fully indexed because the string was 1–50 bytes over limit. ✅ **CHECKPOINT — SECTION 12** - [ ] Backend terms: all Tier 1 ASINs — current bytes recorded, new strings written - [ ] Byte count: all new backend strings confirmed at 245–250 bytes - [ ] Repetition check: no words from title or bullets appear in backend - [ ] Competitor brand check: no competitor brand names in any backend field - [ ] Implementation: all backends updated in Seller Central — confirmed in Manage Inventory → Edit → Keywords tab - [ ] Indexing confirmation: 48 hours after implementation, test each new keyword in Amazon.co.uk search to confirm the ASIN appears --- # SECTION 13 — A+ CONTENT CREATION BRIEF ## A+ Content: The Conversion Asset That Replaces the Product Description When A+ Content is active on an ASIN, Amazon replaces the plain-text product description field with the A+ Content modules. This is significant for two reasons: the product description field (2,000 characters, plain text, low visual impact) is replaced by a rich content area that can include high-resolution images, comparison tables, brand story modules, and video — all of which increase dwell time and conversion rate. Amazon confirmed in 2023 that A+ Content text is indexed by their search algorithm. This means the copy written for A+ Content text modules contributes to organic keyword rankings — making A+ Content a dual-function asset: a conversion tool AND an indexing tool. Studies by Amazon themselves show that A+ Content increases sales by 3–10% on average, with Premium A+ Content (available to sellers with Brand Registry and 15+ approved A+ projects) increasing sales by up to 20% (Source: Amazon Seller Central, A+ Content help page, 2024). > **Pro Tip:** The highest-impact A+ module for most product categories is not the hero banner — it is the comparison chart. A comparison chart that shows the brand's ASIN alongside 3–4 sister products (colour variants, size variants, or complementary items) keeps the buyer inside the brand's ecosystem rather than going back to search results to compare competitors. Buyers who click through to a second ASIN from A+ Content convert at significantly higher rates than buyers who return to search results, because the second ASIN inherits the trust and relevance already established by the first listing. ## 13.1 — A+ Content Architecture Decision **Standard A+ Content** (5 modules from 17 module types): available to all Brand Registry sellers. No additional requirements. 7 business days review time after submission. **Premium A+ Content** (up to 17 modules with interactive elements, video, and full-width layouts): requires Brand Registry AND 15+ previously approved A+ Content projects AND at least one published Brand Story. If these conditions are not yet met, build Standard A+ now and upgrade to Premium once eligible. **Brand Story module** (special module — appears at the top of all brand ASINs): create this first because it applies across every ASIN simultaneously and establishes the brand entity signal across the full account. One Brand Story creation covers all ASINs. ## 13.2 — Brand Story Module Brief The Brand Story module appears on every ASIN in the brand's account — it does not need to be applied per-ASIN. Creating it once applies it everywhere Brand Registry is active. **Location in Seller Central:** Advertising → A+ Content Manager → Start Creating A+ Content → Brand Story tab **Brand Story content specification:** Header text (H1): `[Brand Name] — [Core Brand Statement in ≤80 characters]` Example: "shopifystore1 — Independently crafted knitwear for UK women, since [year]" Body copy (150–250 words — this text IS indexed by Amazon): The brand story must include: - Founding year and UK trading location - The specific problem the brand was created to solve — one sentence, concrete - Primary product category named explicitly (for indexing) - UK-specific credential (UK manufacturer / UK founder / UK-certified / UK-stocked) - Primary certification if held (GOTS, Soil Association, Vegan Society — with certification status stated) - One claim only the brand can make — specific sourcing detail, production standard, or heritage fact - Current review count and average rating (update quarterly) Three image panels (220×220px each, recommended): Panel 1: Founder or brand team — real photograph, not stock Panel 2: Production or sourcing context — factory, workshop, or raw material Panel 3: Product lifestyle — the product in use by a real person in a real UK context **Prohibited in Brand Story:** Pricing, shipping claims, time-sensitive promotions, competitor comparisons, "Amazon's Choice" references --- ## 13.3 — Standard A+ Content Briefs (Per ASIN) **ASIN 1 — A+ Content Brief (5 Standard Modules)** --- **MODULE 1 — Image with Text Overlay (Hero Banner)** Module type: Image & Dark Text Overlay Image specification: 970×300px (desktop) / Amazon auto-crops for mobile — design for 600×180px safe zone Background: lifestyle photograph — product in context — no white background required for A+ modules Text permitted on image: up to 120 characters headline Image brief: [Describe exactly what the image should show — who, wearing what, in what setting, what mood] Example: "Female model wearing the navy [product name] over a shirt, seated at a desk in a minimal home office, natural window light, photographed at camera-eye level" H2 headline (150 chars max): `[Brand Name] [Core Product Claim — primary keyword included]` Body text (200 chars max — this text is indexed): `[2–3 sentences — brand statement, UK credential, primary keyword and secondary keyword included naturally]` Indexed keywords targeted in this module: [list primary + secondary keywords placed in body text] --- **MODULE 2 — Four-Image Text Quadrant (Feature Grid)** Module type: Four Image & Text Purpose: Four key product benefits — each with a supporting lifestyle or macro product image Image specification: 220×220px per quadrant image Quadrant 1: [Feature name — 50 char header + 100 char body] Image brief: [Specific image — e.g. "close-up of fabric texture showing the fine merino weave"] Header: `[ALL CAPS FEATURE]` Body: `[Specific benefit claim — secondary keyword 2 included — under 100 chars]` Quadrant 2: [Feature name] Image brief: [Specific image] Header: `[ALL CAPS FEATURE]` Body: `[Specific benefit claim — under 100 chars]` Quadrant 3: [UK-specific feature] Image brief: [Specific image] Header: `[ALL CAPS UK-SPECIFIC FEATURE]` Body: `[UK-specific claim — UK sizing / UK compliance / UK delivery / UK certification — under 100 chars]` Quadrant 4: [Sustainability or care feature] Image brief: [Specific image] Header: `[ALL CAPS CARE OR SUSTAINABILITY FEATURE]` Body: `[Specific claim — tier 3 keyword included — under 100 chars]` Indexed keywords targeted in this module: [list keywords in quadrant body text] --- **MODULE 3 — Standard Image & Highlight Feature (Deep Specification)** Module type: Standard Image & Highlight Feature (bullet list variant) Purpose: Full specification detail — most text-heavy module — highest keyword indexing value Image specification: 300×300px (left-aligned with bullet list to the right) Image brief: [Detailed product flat lay or technical detail — e.g. "flat lay of the jumper on white surface showing all angles simultaneously, garment fully stretched to show dimensions"] Module header (150 chars): `[Specification-led header — primary keyword variant + material name]` Module body text (300 chars — this is the most-indexed text block in Standard A+): `[Full specification: material composition with percentages, weight in GSM, wash care in plain English, origin country, certification name with certificate number, dimensions if applicable. Include primary keyword, secondary keyword, and at least one Tier 3 keyword. Write for a reader who wants to confirm this product is exactly what they need before purchasing.]` Feature bullets (5 bullets — 200 chars each): Bullet 1: [Spec point 1 — material + percentage + source] Bullet 2: [Spec point 2 — weight or dimension] Bullet 3: [Spec point 3 — care instruction specific to material] Bullet 4: [Spec point 4 — certification + verification link text] Bullet 5: [Spec point 5 — UK-specific attribute — sizing / compliance / delivery] Indexed keywords targeted in this module: [list all keywords placed in header, body, and bullets] --- **MODULE 4 — Comparison Chart (ASIN Cross-Sell)** Module type: Standard Comparison Chart Purpose: Compare this ASIN alongside 3–4 sister ASINs (own brand only — Amazon requires all compared ASINs to belong to the same brand) Primary goal: keep the buyer inside the brand ecosystem — click through to a second ASIN rather than returning to search results ASIN comparison structure: | Attribute | This ASIN | Sister ASIN 1 | Sister ASIN 2 | Sister ASIN 3 | |---|---|---|---|---| | Product name | [Name] | [Name] | [Name] | [Name] | | Material | [Material] | [Material] | [Material] | [Material] | | UK size range | [Range] | [Range] | [Range] | [Range] | | Fit type | [Fit] | [Fit] | [Fit] | [Fit] | | Best for | [Use case] | [Use case] | [Use case] | [Use case] | Attribute selection rule: choose the 5 attributes where this ASIN is most competitive OR where the differences most clearly help the buyer make a decision. Do not choose attributes where sister ASINs are clearly superior — the comparison table should help buyers find the right product, not highlight weaknesses. --- **MODULE 5 — Brand Description (Standard Text with Logo)** Module type: Standard Company Logo and Description Purpose: Brand authority and trust signal — reinforces E-E-A-T signals from the About page equivalent Logo specification: 600×180px, PNG transparent background Brand description text (300 words — this text is indexed): Write the brand description to include: - Brand name (exact as registered in Brand Registry) - Founding year and UK location - Primary product category (named explicitly for indexing) - Manufacturing or sourcing philosophy — specific, verifiable - Certifications held — with certification body names and verification method - Current review performance — "X+ verified reviews at X.X stars" (update quarterly) - Primary keyword, secondary keyword, and Tier 3 keyword placed naturally - UK credential — British founder / UK manufacturing / UK safety compliance The brand description text is one of the most valuable A+ indexing locations because it has the highest word count of any standard module. Every keyword placed here that is not in the title or bullets receives additional indexing weight without occupying visible listing real estate. --- **ASIN 2 — A+ Content Brief** *(Follow the same 5-module structure as ASIN 1 — all content unique to this ASIN's specific product, keywords, and differentiators. Do not copy from ASIN 1.)* Module 1 — Hero banner: [image brief + text brief specific to ASIN 2] Module 2 — Feature grid: [4 features specific to ASIN 2's confirmed benefits from review analysis] Module 3 — Specification: [ASIN 2's specific material composition, dimensions, certifications] Module 4 — Comparison chart: [ASIN 2 compared to its own sister variants] Module 5 — Brand description: [same Brand Story text can share this module if a separate Brand Story module is published — otherwise write unique brand text with ASIN 2's specific keywords added] --- *(Repeat A+ Content brief for every Tier 1 priority ASIN)* ## 13.4 — A+ Content Implementation **Submission steps in Seller Central:** 1. Advertising → A+ Content Manager → Start Creating A+ Content 2. Select content type: Standard A+ or Brand Story 3. Add modules in order — drag to reorder 4. Add ASINs to apply the content to: enter parent ASINs only — children inherit automatically 5. Preview: always preview on both desktop AND mobile before submission 6. Submit for Amazon review — 7 business days standard review time **Common A+ rejection reasons (Amazon.co.uk, 2024–2025):** - Pricing mentioned in any module: "from £X" or "RRP" — prohibited - Shipping or delivery claims: "free next-day delivery" — prohibited in A+ - Reference to Amazon badges: "Amazon's Choice" or "Best Seller" — prohibited - Comparison to named competitor brands: permitted to compare attributes, prohibited to name competitors - Poor image quality: images that appear blurry when zoomed, or are below minimum pixel specifications - Prohibited product claims: any medicinal claim in health/beauty A+ without MHRA substantiation ✅ **CHECKPOINT — SECTION 13** - [ ] Brand Story: brief complete — submitted and under Amazon review - [ ] ASIN 1 A+ Content: all 5 modules briefed — design assets commissioned or created - [ ] ASIN 2 A+ Content: all 5 modules briefed - [ ] All priority ASINs: A+ briefs complete — submission queue scheduled - [ ] Preview: all A+ Content previewed on mobile before submission - [ ] Amazon review: 7 business day review time noted — publication timeline confirmed --- # SECTION 14 — AMAZON BRAND STORE ## The Brand Store: Where Amazon Traffic Stays in Your Ecosystem The Amazon Brand Store is a multi-page brand website hosted on Amazon.co.uk at amazon.co.uk/stores/[brand-handle]. It is free for Brand Registry sellers, it can be linked from Sponsored Brands campaigns, and it earns organic traffic from buyers who search for the brand name directly on Amazon. Without a Brand Store, a Sponsored Brands campaign has nowhere compelling to send buyers — it must link either to the search results page or to a single product listing. Neither of these destinations is as effective as a brand storefront for buyers who have clicked a brand-level ad and want to explore the full range. The Brand Store also earns its own analytics: Seller Central → Reports → Brand Analytics → Stores Insights shows which traffic sources (organic Amazon search, Sponsored Brands, external traffic) drive visits to the store, and which store pages convert most effectively. > **Pro Tip:** The highest-converting Brand Store page is not the homepage — it is the "New Arrivals" or "Best Sellers" sub-page. Buyers who click through to a Brand Store have shown high purchase intent — they are interested in the brand specifically, not just a single product. A sub-page that shows the 4–6 highest-converting ASINs (by CVR from Section 6.1) converts these high-intent visitors at a higher rate than the full catalogue homepage. Build this sub-page in Stage 2 and link Sponsored Brands campaigns to it rather than to the homepage. ## 14.1 — Brand Store Architecture **Homepage:** - Hero banner: seasonal or evergreen brand statement — 3000×600px recommended - Featured collections: 3 category tiles — link to sub-pages - Bestsellers tile grid: top 4–6 ASINs by CVR — these are the highest-converting products - Brand Story section: 150–200 words — embedded from Brand Story module or rewritten for store context **Sub-page 1 — [Primary Product Category]:** - All active parent ASINs in this category - Category hero image: 3000×600px lifestyle image — category-specific - Category description: 200–300 words — category head term keyword included — Amazon Store text is indexed - Filter/sort enabled: let buyers filter by colour, size, price if the store builder supports it **Sub-page 2 — [Secondary Product Category or New Arrivals]:** - All parent ASINs in this category or all ASINs launched in the last 90 days - Category hero image: 3000×600px - Category description: 200–300 words **Sub-page 3 — Best Sellers:** - Top 6 ASINs by revenue from Section 6.1 Business Reports - No hero description needed — let the products speak - Update quarterly as bestseller rankings change **Sub-page 4 — Gifts / Seasonal (where applicable):** - Seasonal sub-page: publish 6 weeks before seasonal peak — remove or replace off-season - Gift sub-page: relevant for Q4, Mother's Day, Valentine's Day depending on product category ## 14.2 — Store Content Specification **Store Homepage Header copy (200 words — indexed by Amazon):** This copy must include: - Brand name (exact as in Brand Registry) - Primary product category described explicitly - UK brand signal: founded year, UK location, UK certification if held - Primary keyword from Section 3 keyword research - Secondary keyword from Section 3 - Call to explore sub-pages: "Browse our [category] range" or "Discover new arrivals" Do NOT include: pricing, shipping claims, promotional language, time-sensitive offers **Sub-page descriptions (200–300 words each — indexed):** Each sub-page description follows the same structure: - H1 equivalent (sub-page name): category name containing the page's target keyword - Opening paragraph: what this collection contains, who it is for, key differentiator - Body paragraph: material or product specifics — the indexing content - Closing: "Explore the full [category] range" — soft internal navigation prompt ## 14.3 — Brand Store SEO Notes Amazon Brand Stores can rank in external search engines (Google, Bing) for brand-name queries. A search for "[brand name] Amazon" may return the store URL in Google results. This is an additional organic channel that costs nothing beyond the time to build and maintain the store. Amazon's own internal search also surfaces Brand Store pages for brand-name and category searches — buyers searching for the brand name directly may see the store link before individual product listings in some SERP configurations. Store pages with video content produce significantly higher session duration metrics — a signal Amazon's internal analytics track as a brand quality indicator. **Store URL claim:** Claim the clean store URL immediately — amazon.co.uk/stores/[brand-name] — even if the store is not yet fully built. Once another brand claims a similar URL, the preferred URL may not be available. ## 14.4 — Sponsored Brands Campaign Link Strategy Once the Brand Store is live, update all existing Sponsored Brands campaigns to link to the most relevant store sub-page rather than to a product listing page: | Campaign target keyword | Best landing page | Reason | |---|---|---| | [Brand name keyword] | Brand Store homepage | Buyer is searching for the brand specifically | | [Category keyword — e.g. merino jumpers] | Category sub-page | Buyer wants to browse the category | | [New Arrivals keyword] | New Arrivals sub-page | Buyer has discovery intent | | [Bestsellers keyword] | Best Sellers sub-page | Buyer wants social-proof-validated products | ✅ **CHECKPOINT — SECTION 14** - [ ] Brand Store: URL claimed — amazon.co.uk/stores/[brand-name] - [ ] Homepage: hero banner, category tiles, bestsellers grid, brand description — all built - [ ] Sub-page 1 (primary category): all ASINs populated, description live - [ ] Sub-page 2 (secondary or new arrivals): built and live - [ ] Sub-page 3 (best sellers): top 6 ASINs populated - [ ] All store page descriptions: written, keyword-optimised, live - [ ] Sponsored Brands campaigns: updated to link to relevant store sub-pages - [ ] Stores Insights: reporting confirmed active in Brand Analytics --- # SECTION 15 — PRODUCT DESCRIPTION (WHEN A+ IS NOT ACTIVE) ## The Description Field: Only Relevant Without A+ When A+ Content is active on an ASIN, the product description field is completely replaced. The description field text is not indexed and not shown to buyers. Writing a detailed product description for an ASIN with active A+ Content is wasted effort. However, there are three situations where the product description field still matters: 1. **New ASINs before A+ is approved:** Amazon's 7-day review cycle means there is always a window where the listing is live but A+ is not yet published. A strong description during this window improves the listing's conversion during the high-activity launch phase. 2. **ASINs not yet covered by A+ Content:** if the account has more ASINs than the A+ Content team has capacity to cover, those ASINs need a description. 3. **Google Shopping and external discovery:** Amazon product pages are indexed by Google. The product description field contributes to the on-page content that Google reads. A well-written description with natural keyword usage improves the ASIN's Google Shopping and Google Search visibility for buyers arriving from outside Amazon. ## 15.1 — Product Description Formula **Character limit:** 2,000 characters (Amazon strips HTML tags except ``, ``, `` in product descriptions — do not use headers or bullet HTML here) **Structure:** Opening paragraph (250–350 chars): answer the question "what is this product and who is it for?" Include the primary keyword and a UK-specific signal. Body paragraph 1 (300–400 chars): material or ingredient specification — full composition, percentages, sourcing detail if applicable. Secondary keyword included naturally. Body paragraph 2 (300–400 chars): size, fit, or use case — explicit UK sizing, fit type, styling notes. Tier 2 keyword included. Closing paragraph (200–300 chars): brand signal, certification reference, and a soft navigation CTA: "Discover our full [product type] range at [brand name] on Amazon." **The keyword rule for descriptions:** The primary keyword should appear once in the opening paragraph. Secondary keywords and Tier 3 keywords appear once each in body paragraphs. Do not repeat keywords — Amazon's description indexing does not reward density, and buyers who read descriptions are put off by repetition. ## 15.2 — Product Descriptions Per ASIN (When A+ Not Yet Active) **ASIN 1 — Product Description (pre-A+ or A+ not applicable)** `[WRITE FULL PRODUCT DESCRIPTION — 1,500–2,000 chars — primary keyword in opening paragraph — UK sizing in body — brand credential in closing — no HTML headers — no bullet points in description field]` Character count: [X] of 2,000 Keyword coverage: - Primary keyword: [state — position in description] - Secondary keyword 1: [state — position] - Tier 3 keyword: [state — position] --- **ASIN 2 — Product Description** `[WRITE FULL PRODUCT DESCRIPTION]` --- *(Repeat for any ASIN without active A+ Content)* ✅ **CHECKPOINT — SECTION 15** - [ ] Descriptions: written for all ASINs without active A+ Content - [ ] Primary keyword: confirmed in opening paragraph of each description - [ ] Character count: all descriptions between 1,500–2,000 chars - [ ] A+ Content launch: description field auto-replaced when A+ goes live — confirm per ASIN after A+ approval --- # SECTION 16 — KEYWORD PLACEMENT MAP (MASTER DOCUMENT) ## The Placement Map: The Single Reference Document for All Keyword Decisions The keyword placement map is the master reference document for the entire Stage 2 optimisation. It shows which keyword appears in which field for every Tier 1 ASIN — confirming that every high-priority keyword is covered by at least one indexable field, and that no critical keyword is missing from the account. This document is updated after every Stage 2 change and becomes the handoff document to Stage 3 (advertising) — the advertising team uses it to confirm which keywords are indexed organically before building exact match campaigns. ## 16.1 — Keyword Placement Map Per ASIN **ASIN 1: [B0XXXXXXXXXX — Product Name]** | Keyword | UK vol/mo | Title | Backend | Bullet 1 | Bullet 2–5 | A+ Text | Description | Ad Queue | |---|---|---|---|---|---|---|---|---| | [Primary KW] | [X,XXX] | ✅ char [X] | ✅ | ✅ | | ✅ mod 1 | ✅ | Exact match | | [Secondary KW 1] | [XXX] | ✅ char [X] | ✅ | | ✅ B2 | ✅ mod 3 | ✅ | Phrase match | | [Secondary KW 2] | [XXX] | | ✅ | | ✅ B3 | ✅ mod 3 | | Phrase match | | [Tier 3 KW 1] | [XX–XXX] | | ✅ | | | ✅ mod 5 | | Auto campaign | | [Tier 3 KW 2] | [XX–XXX] | | ✅ | | | | | Auto campaign | | [Misspelling 1] | [XX] | | ✅ | | | | | Negative | | [Gift term 1] | [XXX] | | ✅ | | | ✅ mod 5 | | Auto campaign | Coverage score: [X of Y targeted keywords are covered by at least one indexed field] Gaps: [Any keyword in the near-miss list from Section 3.3 that is not covered — these are Stage 3 ad campaign priorities] --- **ASIN 2: [B0XXXXXXXXXX — Product Name]** | Keyword | UK vol/mo | Title | Backend | Bullet 1 | Bullet 2–5 | A+ Text | Description | Ad Queue | |---|---|---|---|---|---|---|---|---| | [Primary KW] | [X,XXX] | ✅ | ✅ | ✅ | | ✅ | ✅ | Exact match | | [Secondary KW 1] | [XXX] | ✅ | ✅ | | ✅ | ✅ | | Phrase match | --- *(Repeat for every Tier 1 ASIN)* ## 16.2 — Gap Analysis (Post-Optimisation) After completing all Stage 2 listing changes, identify any remaining keyword gaps — high-priority keywords that are not covered by any indexed field. | Keyword | UK vol/mo | Why it matters | Field gap | Stage 3 action | |---|---|---|---|---| | [Gap KW 1] | [XXX] | [Near-miss from SQP — impressions without top-3 ranking] | Not in title or bullets | Launch exact match Sponsored Products campaign — Stage 3 | | [Gap KW 2] | [XXX] | [High-converting term from competitor ASIN] | Only in backend | Consider adding to A+ Module 3 body text | ## 16.3 — Stage 2 to Stage 3 Handoff Data Stage 3 launches Sponsored Products campaigns built specifically on Stage 2's confirmed keyword coverage. The handoff data: **Exact match campaign queue (Category A terms — confirmed converters not yet in campaigns):** [List from Section 3.1 Category A terms that Stage 3 will put into exact match campaigns] **Phrase match campaign queue (Secondary keywords now in listing):** [List from keyword placement map — secondary keywords confirmed in title or bullets — Stage 3 phrase match] **Auto campaign seed keywords (Tier 3 and gift terms — in backend but not yet in title/bullets):** [List from keyword placement map backend terms — Stage 3 auto campaigns will mine these for new discoveries] **CVR problem keywords (Category C from Section 3.1 — clicks but no purchases):** [List of keywords where listing changes were made in Stage 2 to address CVR — Stage 3 will re-test with fresh exact match campaigns after a 2-week settle period] ✅ **CHECKPOINT — SECTION 16** - [ ] Keyword placement maps: complete for all Tier 1 ASINs - [ ] Coverage score: all primary and secondary keywords covered by at least one indexed field - [ ] Gap analysis: remaining gaps documented — Stage 3 ad campaign action assigned - [ ] Handoff document: exact match / phrase match / auto campaign queues compiled for Stage 3 - [ ] Stage 3 trigger: Stage 2 all-checklist confirmed — Stage 3 advertising brief begins --- # SECTION 17 — STAGE 2 KPI TARGETS & MONITORING ## What to Measure After Stage 2 Listing Changes Amazon does not instantly re-index listing changes. After updating a title or bullet points, it typically takes 24–72 hours for Amazon's crawlers to re-index the listing and for the ranking changes to appear in search results. After significant content changes, the full ranking impact can take 2–4 weeks to stabilise. During this period, the metrics to monitor are not rankings directly — they are the leading indicators that predict ranking changes. > **Pro Tip:** The fastest signal that a title change has worked is the A9/A10 organic click-through rate — visible in the Search Query Performance report in Brand Analytics. When a title change improves the keyword placement and clarity, the CTR on that keyword improves within 7–14 days. BSR improvement follows CTR improvement by 2–4 weeks. If CTR is not improving 2 weeks after a major title change — the change did not achieve its goal, and the title needs revisiting before waiting 4–8 weeks for a BSR movement that is not going to come. ## 17.1 — Stage 2 KPI Dashboard Record all baselines on the date of each major listing change. | KPI | ASIN 1 baseline | ASIN 2 baseline | Week 2 target | Month 2 target | Source | |---|---|---|---|---|---| | BSR (primary category) | [Stage 1 record] | [Stage 1 record] | Within 20% of target | Top 500 in category | Amazon PDP | | Sessions | [Stage 1 record] | [Stage 1 record] | +10–20% | +30–50% | Seller Central Business Reports | | CVR (%) | [Stage 1 record] | [Stage 1 record] | +1pp | +2–3pp | Seller Central Business Reports | | SQP click rank (primary KW) | [Stage 1 record] | [Stage 1 record] | Within top 5 | Within top 3 | Brand Analytics SQP | | SQP purchase rank (primary KW) | [Stage 1 record] | [Stage 1 record] | Within top 5 | Within top 3 | Brand Analytics SQP | | Impressions (organic) | [Stage 1 record] | [Stage 1 record] | +20–30% | +50–80% | Brand Analytics SQP | | Review count | [Stage 1 record] | [Stage 1 record] | +5 (Vine) | +15 | Judge.me / Vine | ## 17.2 — A/B Testing with Amazon Manage Your Experiments (Brand Registry) After initial Stage 2 listing changes are live and indexed, run Amazon's built-in A/B testing tool for the highest-priority ASINs. **Location:** Seller Central → Brands → Manage Your Experiments **What can be tested:** - Product title (two title variants — Amazon runs a 4-week test) - Main image (two image variants) - A+ Content (two A+ Content versions) **A/B testing rules:** - One test per ASIN at a time - Minimum 4 weeks per test (Amazon requires statistical significance before declaring a winner) - Amazon shows a projected winner based on sales improvement — but also shows the raw CVR difference - Only run A/B tests on ASINs with sufficient session volume — below 50 sessions/day, the test takes too long to reach significance **Recommended first test (Stage 2):** Title variant test on the highest-revenue ASIN with the largest confirmed gap to competitor title quality. Test: current Stage 2 title vs an alternative that front-loads a different secondary keyword in position 2. ## 17.3 — Stage 2 Weekly Monitoring Protocol **Every Monday morning (10 minutes per ASIN):** 1. Check BSR on each Tier 1 ASIN — has it improved vs last week? 2. Check for new negative reviews — any new themes that Stage 2 listing changes have not yet addressed? 3. Check for suppression alerts in Manage Inventory — any ASIN that was active last week is now suppressed? 4. Check Buy Box status — any ASIN that has lost Buy Box since last week? **Every 2 weeks:** 1. Run SQP report — compare click rank and purchase rank for primary keywords vs Stage 1 baseline 2. Run Business Reports — compare CVR vs Stage 1 baseline 3. Check A+ Content status — any modules rejected by Amazon? Any awaiting resubmission? **Month 2 review:** Full Stage 2 KPI dashboard review — all metrics vs Stage 1 baseline. Determine which ASINs achieved their Stage 2 targets and which need Stage 3 advertising support to accelerate. ✅ **CHECKPOINT — SECTION 17** - [ ] Stage 2 KPI dashboard: all baseline values recorded on date of each listing change - [ ] Monitoring protocol: weekly Monday checks confirmed with account manager - [ ] Manage Your Experiments: A/B test set up for highest-priority ASIN title - [ ] Month 2 review date: set in calendar — full KPI comparison vs Stage 1 baseline - [ ] Stage 3 trigger: all Stage 2 checklists complete — Stage 3 advertising brief ready --- # CITATIONS — STAGE 2 1. **Amazon. *Product title requirements*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G200203280 *Supports: Title character limits, prohibited content in titles, brand-first formatting guidance throughout Section 10.* 2. **Amazon. *About A+ Content*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G202102960 *Supports: A+ Content module types, 7-day review time, 3–10% and up to 20% sales improvement data cited in Section 13.* 3. **Amazon. *Bullet points and product descriptions — requirements*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G200389330 *Supports: Bullet point formatting rules, permitted ALL CAPS usage, character limits, prohibited content throughout Section 11.* 4. **Amazon. *Search Terms field — product listing*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G23501 *Supports: 250-byte limit, no commas, no competitor brand names, no repetition rules throughout Section 12.* 5. **Amazon. *A+ Content — image and text requirements*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G202102980 *Supports: A+ Content image specifications (970×300px hero, 220×220px quadrant, 300×300px feature module) and prohibited content rules in Section 13.* 6. **Amazon. *Amazon Stores — create a Store*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G202120490 *Supports: Brand Store architecture, URL structure, Sponsored Brands linking strategy throughout Section 14.* 7. **Amazon. *Manage Your Experiments — A/B testing*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G465Y4EGMKY8BXVQ *Supports: A/B testing methodology, 4-week minimum test period, eligible test types in Section 17.2.* 8. **Amazon. *Brand Registry — eligibility and benefits*. Amazon Brand Services, 2024.** https://brandservices.amazon.co.uk/brandregistry *Supports: Brand Registry requirements for A+ Content access and Manage Your Experiments eligibility throughout Sections 13 and 17.* 9. **Helium 10. *Amazon listing optimisation — UK marketplace guide*. Helium 10 Blog, 2024.** https://www.helium10.com/blog/amazon-listing-optimization/ *Supports: A9/A10 keyword placement hierarchy, mobile title truncation benchmarks, and backend byte counter methodology throughout Sections 9, 10, and 12.* 10. **Amazon. *Search Query Performance report guide*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/GDRD88UGKX56ATRR *Supports: SQP click rank and purchase rank interpretation for monitoring listing changes in Section 17.1.* 11. **UK Government. *Consumer Rights Act 2015 — returning goods*. Gov.uk, 2024.** https://www.gov.uk/consumer-rights-act-2015 *Supports: 30-day right to return stated as UK legal minimum in Section 9.3 UK Listing Language Standards.* 12. **Amazon. *Product detail page rules — style guides by category*. Amazon Seller Central, 2024.** https://sellercentral.amazon.co.uk/gp/help/G200390640 *Supports: Category-specific title formulas, bullet point standards, and image requirements throughout Sections 10, 11, and 13.* 13. **Jungle Scout. *Amazon A+ Content study — sales impact by content type*. Jungle Scout Research, 2024.** https://www.junglescout.com/blog/amazon-a-plus-content/ *Supports: A+ Content CVR improvement data and comparison chart conversion effectiveness referenced in Sections 13 and 14.* 14. **Amazon. *Amazon Storefront analytics — Stores Insights*. Amazon Seller Central Help, 2024.** https://sellercentral.amazon.co.uk/help/hub/reference/G201988450 *Supports: Brand Store analytics, traffic source reporting, and session duration as brand quality indicator in Section 14.3.* 15. **UK Intellectual Property Office. *Trademark classes — Nice Classification*. IPO.gov.uk, 2024.** https://www.gov.uk/guidance/trade-marks-manual/class-headings *Supports: trademark class requirements for Brand Registry enrollment (Class 25 clothing, Class 3 cosmetics) referenced in Stage 1 Section 5 and throughout Stage 2.* --- *amazonproject1.co.uk — Amazon SEO Live Project* *Stage 2: Listing Optimisation* *Applied: Amazon SEO Master Prompt v1.0 · Forbidden Words List (9 categories, 70+ phrases)* *aiseojournal.net | March 2026* *Next stage: Stage 3 — Reviews, Advertising & Brand Authority (Sponsored Products full build, Vine programme, Brand Tailored Promotions, press and external traffic)*](https://aiseojournal.net/wp-content/uploads/2026/04/Amazon-SEO-Live-Project-Part-2-Listing-Optimisation-688x387.png)