Full-Scale B2B Clothing Manufacturer SEO Programme

Format: Enterprise SEO Live Project A–Z | aiseojournal.net | March 2026 |  UK + USA + Germany + Japan

SECTION 0 — PROJECT BRIEF & ENTERPRISE FRAMEWORK

Why Enterprise SEO Is a Different Discipline

Meridian Cloth Co. is no longer a small business running a single landing page and a GBP listing. The multi-location UK project expanded to five cities. The international project added USA, Germany, and Japan. The site now carries approximately 45,000 indexed pages across location pages, cluster posts, pillar content, schema-heavy product and service pages, blog archives, and four language subdirectories.

At this scale, the rules change.

A single canonical tag error on a content template does not affect one page — it affects every page using that template simultaneously. A faceted navigation issue that would be a minor annoyance on a 200-page site becomes a crawl budget catastrophe on a 45,000-page site. A missing author entity on a content template means every piece of content published through that template lacks the E-E-A-T signal Google uses to evaluate trustworthiness in YMYL-adjacent categories like ethical production and health & safety standards.

Enterprise SEO is not faster SME SEO. It is structurally different. The problems are different, the solutions are different, the governance is different, and the measurement is different.

Pro Tip: The single most common enterprise SEO failure is applying SME SEO tactics to an enterprise site. Fixing 50 individual page titles manually is an SME fix. Auditing the CMS template that generates all 3,200 location-variant page titles, correcting the template formula, and deploying the fix across all 3,200 pages in one release is enterprise SEO. Every recommendation in this project specifies whether the fix is manual, template-level, or programmatic — and which teams need to be involved.

0.1 — Site Profile at Project Start

0.2 — What Previous Projects Built (Baseline)

The previous three projects (single-location UK, multi-location UK, international) built the following infrastructure. This enterprise project does not repeat that work — it builds the next layer on top of it.

0.3 — Enterprise Project Delivery Map

0.4 — Enterprise Team Structure for This Programme

At 45,000 pages across four countries, no single person can own all of enterprise SEO. This section defines roles, responsibilities, and the decision-making structure.

Decision escalation matrix:

✅ CHECKPOINT — SECTION 0

• [ ] Site profile verified: indexed page count, organic sessions baseline, DR confirmed
• [ ] Previous project infrastructure confirmed live and performing
• [ ] Team structure document distributed to all roles
• [ ] Decision escalation matrix agreed and accessible
• [ ] Project tracking sheet: enterprise tabs created alongside previous project tabs

SECTION 1 — TECHNICAL SEO AUDIT — FULL SITE

Enterprise Technical Audit: Why Scale Changes Everything

On a 5-page site, a missing canonical is one problem. On a 45,000-page site, a missing canonical on a shared template is potentially thousands of problems deployed simultaneously — many of which may have been live for months before anyone notices the ranking suppression.

The enterprise technical audit does not work through individual pages. It works through templates, patterns, and error distributions. The question is never “which specific page has a problem?” It is “which template generates the problem, how many pages does that template power, and what is the fix that corrects all of them in one deployment?”

Pro Tip: Run the Screaming Frog crawl with JavaScript rendering disabled for the first pass and enabled for the second. The difference between the two crawls reveals JavaScript-rendered content that Googlebot may not be processing correctly — a common issue on Elementor sites where widgets render content client-side. Any content that appears in the JS-enabled crawl but not the disabled crawl is potentially invisible to Googlebot unless Googlebot’s rendering queue processes the page, which is not guaranteed for every page at enterprise scale.

1.1 — Crawl Configuration for 45,000-Page Site

Before the audit runs, Screaming Frog must be configured correctly for this site. Default settings will not produce an accurate picture of a site this size.

Crawl settings:

• Crawl limit: set to 50,000 (above indexed page count to capture any unlisted URLs)
• Respect robots.txt: YES for first pass (audit the crawlable site as Googlebot sees it)
• JavaScript rendering: disabled for pass 1, enabled for pass 2 (compare outputs)
• User agent: Googlebot (not Screaming Frog default) — ensures crawl mirrors Googlebot behaviour
• Custom extraction rules (set before crawl):
  • Footer phone number: CSS selector footer .phone, footer [class*="phone"]
  • Schema types present: XPath //@type[parent::script[@type='application/ld+json']]
  • Canonical URL: XPath //link[@rel='canonical']/@href
  • og:locale: XPath //meta[@property='og:locale']/@content
  • hreflang values: XPath //link[@rel='alternate']/@hreflang
• Crawl speed: 5 requests/second maximum (avoid triggering Hostinger rate limiting)
• Include all subdomains: YES (captures any staging or subdomain URLs)
• Exclude: /wp-admin/, /wp-json/, /xmlrpc.php (add to exclusion list pre-crawl)

1.2 — Technical Findings by Category

Category 1 — Crawlability

Finding 1.2.1 — Redirect chains: estimated 340+ chains across international subdirectories

Scale: ~340 pages (estimated from redirect chain report) Root cause: When pages were moved from the main domain to /us/, /de/, /ja/ subdirectories during the international project, some existing internal links were not updated. These links hit the old URL (301 → redirect URL 1 → redirect URL 2 → final URL), creating 2-hop and 3-hop chains. Each hop loses approximately 15% of the authority passed through the redirect (Google, Search Quality Guidelines).

Fix: Export Redirect Chains report from Screaming Frog. For each chain identified: Step 1: Update the internal link in the CMS to point directly to the final destination URL. Step 2: Update the redirect at server level to point old URL → final URL in one hop. Step 3: Verify with: curl -Ik https://www.meridianclothco.co.uk/[old-url] — confirm single 301.

Owner: Dev Effort: 8–12 hours (Screaming Frog export → spreadsheet match → batch CMS update) Priority: 🔴 P1 — redirect chains actively suppress authority passage Dependency: Redirect map from international project must be available Validation: Re-crawl filtered to 3xx — confirm zero chains remaining

Finding 1.2.2 — /de/ and /ja/ blog archive pages creating crawl traps

Scale: ~4,200 pages (estimated from /de/blog/page/[N]/ and /ja/blog/page/[N]/ pattern) Root cause: WordPress default pagination generates /page/2/, /page/3/… for blog archives in each language. These pages carry no unique content — they are navigation pages showing post excerpts already indexed on individual post URLs. At 4,200 pages, they consume crawl budget without delivering indexed value.

Fix:

• Add to robots.txt: Disallow: /de/blog/page/ and Disallow: /ja/blog/page/
• Alternatively: add noindex + nofollow to all pagination pages beyond /page/2/ via Rank Math’s Archive settings.
• Preferred: robots.txt exclusion (faster Googlebot response, does not require per-page tag).

Owner: Dev Effort: 30 minutes (robots.txt edit + deploy + Cloudflare cache purge) Priority: 🔴 P1 — crawl budget reclamation is immediate Dependency: None Validation: GSC Coverage → Excluded → Blocked by robots.txt should show increase of ~4,200 URLs within 2–3 crawl cycles

Finding 1.2.3 — /wp-json/ REST API endpoints indexed

Scale: ~800 URLs Root cause: WordPress REST API endpoints (/wp-json/wp/v2/posts/, /wp-json/wp/v2/pages/) are being crawled and in some cases indexed. These are machine-readable JSON responses with no user-facing value. They consume significant crawl budget.

Fix: Confirm Disallow: /wp-json/ is in robots.txt. If present, flush Cloudflare cache — CDN may be serving a cached version of robots.txt that predates the disallow rule. Verify via: curl https://www.meridianclothco.co.uk/robots.txt.

Owner: Dev Effort: 15 minutes Priority: 🔴 P1 Dependency: None Validation: GSC Coverage → Excluded → Blocked by robots.txt increase

Finding 1.2.4 — Orphan pages: estimated 1,200+ pages with zero internal links

Scale: ~1,200 pages (Screaming Frog Internal Links report → filter Inlinks = 0) Root cause: Multiple sources generate orphan pages on this site: (1) blog posts published without category assignment lose their archive link, (2) pages created during template testing that were never linked from navigation, (3) old event or seasonal pages that remain indexed but are no longer linked from anywhere.

Fix: Export all orphan pages → categorise by page type → for each category:

• Blog posts: assign correct category in WordPress → category page provides archive link
• Test/draft pages: check if indexable → if no value, set to noindex or delete + 410
• Old seasonal pages: 301 redirect to the most relevant category or service page

Owner: Content Manager + Dev Effort: 12–16 hours (audit + categorisation + implementation) Priority: 🟡 P2 — orphan pages suppress topical authority signals Dependency: Content audit (Section 6) should run concurrently to identify which orphans have ranking history worth preserving

Category 2 — Indexability

Finding 1.2.5 — Duplicate content: location pages sharing >40% body copy

Scale: Confirmed during multi-location project — estimated 8–12 page pairs Root cause: Location landing pages for Birmingham and Bristol share significant copy in the “What Does [City] Clothing Manufacturing Cost?” sections — the pricing table content was templated without sufficient local variation. The Near Duplicates report (Screaming Frog, threshold 70%) confirms this pattern across 4 page pairs.

Fix: See Section 6 (Content Consolidation Audit) for full remediation plan. Short-term: add location-specific insight sections to each at-risk page (Bristol ethical market context, Birmingham Midlands proximity context) to reduce similarity scores below 40%.

Owner: Content Manager Effort: 3–4 hours per page pair (content rewrite) Priority: 🟡 P2 Dependency: Content consolidation audit (Section 6) defines priority order

Finding 1.2.6 — Soft 404s: approximately 280 GSC-flagged pages

Scale: ~280 pages (GSC Coverage → Excluded → Soft 404) Root cause: Pages that return 200 status codes but contain so little content that Googlebot classifies them as empty or near-empty. Common causes on this site: (1) Elementor section placeholders left on staging pages that were accidentally published, (2) category archive pages with fewer than 3 posts, (3) tag pages auto-generated by WordPress with minimal content.

Fix:

• Export soft 404 list from GSC → cross-reference with Screaming Frog word count
• Pages under 200 words that are not navigation pages: noindex via Rank Math
• Category pages with <3 posts: suppress from index until at least 5 posts exist
• Tag pages: set WordPress tag archive to noindex globally in Rank Math settings

Owner: Dev + Content Manager Effort: 4–6 hours Priority: 🟡 P2 Dependency: Word count export from Screaming Frog to classify pages accurately

Finding 1.2.7 — Canonical conflicts on international pages

Scale: ~45 pages identified (hreflang audit from Section 3 of international project) Root cause: 45 German and Japanese pages carry canonical tags pointing to their English equivalents rather than self-referencing. This overrides the hreflang implementation — Google treats these pages as English duplicates and excludes them from German and Japanese search results.

Fix: This is a Rank Math configuration issue. In Rank Math settings, the canonical tag must be set to “Use Automatic Canonical URL” per page — not inheriting from parent template or from a global default. Check: Settings → Titles & Meta → Homepage → Canonical URL. For individual pages: Rank Math sidebar → Advanced → Canonical URL → confirm it matches the page’s own URL exactly.

Owner: Dev Effort: 2–3 hours (Rank Math setting check + per-page verification on the 45 affected pages) Priority: 🔴 P1 — canonical conflicts directly suppress international ranking Dependency: Hreflang validation completed (Section 3, international project) Validation: Re-crawl canonicals report → filter for pages where canonical ≠ page URL → should be zero

Category 3 — On-Page

Finding 1.2.8 — Title tag template errors across location pages

Scale: ~28 location pages (5 UK + 4 international × city variants = ~28 pages) Root cause: Rank Math title tag template for location pages uses %title% | %sitename%. When the page title in WordPress is “Clothing Manufacturer Manchester”, the generated tag reads “Clothing Manufacturer Manchester | Meridian Cloth Co.” at 61 characters — 1 character over the 60-character recommended maximum. More critically, the German pages render “Bekleidungshersteller | Meridian Cloth Co.” without the city name because the Rank Math template does not include the city variable for /de/ subdirectory pages.

Fix: Update Rank Math title template for location page post type: UK pages: %custom_field_city% Clothing Manufacturer | Meridian Cloth Co. US pages: %custom_field_city% Apparel Manufacturer | Meridian Cloth Co. DE pages: Bekleidungshersteller %custom_field_stadt% | Meridian Cloth Co. JP pages: アパレルメーカー %custom_field_toshi% | Meridian Cloth Co. Test: Screaming Frog → filter Page Titles → confirm all location pages under 60 characters with city name present.

Owner: Dev Effort: 3–4 hours (template update + custom field verification + QA) Priority: 🟡 P2 Dependency: Custom field values confirmed per page

Finding 1.2.9 — Missing H1 tags on 14 pages

Scale: 14 pages Root cause: Elementor pages where the H1 was set using a Heading widget rather than the native WordPress H1 field. When viewed in Screaming Frog, the crawler sees no H1 because the Elementor widget renders the H1 in the DOM after page load — and the crawl ran with JavaScript disabled.

Fix: Confirm via JavaScript-enabled crawl pass whether these H1s are rendering correctly in the DOM. If they render with JS but not without: these pages have client-side rendered H1s that Googlebot may not process on every crawl. Move H1 content from Elementor Heading widget to WordPress native page title field (displayed via Rank Math as H1). This ensures the H1 is server-side rendered on initial HTML response.

Owner: Dev + Content Manager Effort: 2–3 hours Priority: 🟡 P2 Dependency: JS-enabled crawl pass must confirm which H1s are client-side vs server-side

Category 4 — Schema

Finding 1.2.10 — Schema conflicts: Rank Math + Custom HTML widget duplication

Scale: ~18 pages (location and service pages where both Rank Math schema and custom JSON-LD blocks coexist) Root cause: The international project deployed schema via Elementor Custom HTML widgets as recommended. However, Rank Math was not disabled on these same pages — leaving Rank Math outputting its own LocalBusiness schema block alongside the custom blocks. Google’s structured data documentation notes that duplicate schema blocks of the same @type on the same page can cause validation errors and unpredictable Rich Result behaviour.

Fix: On every page with custom JSON-LD schema in Elementor Custom HTML widget: Rank Math sidebar → Schema → click the schema block → Delete. This removes Rank Math’s auto-generated schema without removing the custom block. Verify: Google Rich Results Test on page URL → should show single LocalBusiness block, not two.

Owner: Dev Effort: 4–6 hours (18 pages × ~15 minutes each) Priority: 🔴 P1 — duplicate schema actively confuses Google’s structured data parser Dependency: List of pages with custom schema blocks (from international project documentation) Validation: Rich Results Test on all 18 pages → single schema block confirmed

Category 5 — Core Web Vitals

Finding 1.2.11 — LCP failure on mobile: location pages exceeding 3.2s

Scale: All 28 location pages (confirmed via PageSpeed Insights batch testing) Root cause: Hero image on location pages is a full-width Elementor Section background image. The image is not preloaded and not in WebP format on German pages. LCP element is this background image — Googlebot identifies it as the Largest Contentful Paint element. At 3.2s (mobile, p75), all location pages are in the “Needs Improvement” range. Three pages in the US subdirectory exceed 4.0s (Poor) due to the geographic server distance issue from UK hosting.

Fix: See Section 3 (Core Web Vitals Remediation) for full plan. Immediate steps:

1. Add LCP preload tag in <head>: <link rel="preload" as="image" href="[hero-image-url]" fetchpriority="high">
2. Convert remaining non-WebP images to WebP (LiteSpeed Image Optimisation module)
3. For US pages: confirm Cloudflare caching is active — TTFB from US IP should be <400ms

Owner: Dev Effort: 8–12 hours (full CWV remediation per Section 3) Priority: 🔴 P1 — Core Web Vitals are a confirmed Page Experience ranking signal Dependency: Cloudflare configuration verified active

Category 6 — International Technical

Finding 1.2.12 — og:locale missing or incorrect on 31 international pages

Scale: 31 pages (German and Japanese pages) Root cause: WordPress does not automatically set og:locale per subdirectory language. Rank Math’s default og:locale setting outputs “en_US” for all pages unless specifically overridden. German pages show og:locale="en_US" instead of de_DE. Japanese pages show og:locale="en_US" instead of ja_JP.

Fix: Rank Math Pro → Settings → Titles & Meta → each page type → add custom Open Graph locale per subdirectory. Alternatively, add a WordPress filter in functions.php:

add_filter('rank_math/opengraph/locale', function($locale) {
  if (strpos($_SERVER['REQUEST_URI'], '/de/') !== false) return 'de_DE';
  if (strpos($_SERVER['REQUEST_URI'], '/ja/') !== false) return 'ja_JP';
  if (strpos($_SERVER['REQUEST_URI'], '/us/') !== false) return 'en_US';
  return 'en_GB';
});

Owner: Dev Effort: 1–2 hours Priority: 🟡 P2 Dependency: None Validation: Screaming Frog → Custom Extraction → og:locale → confirm correct value per subdirectory

1.3 — Technical Audit Findings Summary Table

Total P1 Critical issues: 5 Total pages affected by P1 issues: ~5,400+ Estimated crawl budget currently wasted: ~5,000 pages/day Estimated pages currently suppressed by canonical conflicts: ~45

1.4 — Prioritised Action Plan — First 30 Days

Day 1–3 (this week):

1. robots.txt: add disallow for /de/blog/page/, /ja/blog/page/, /wp-json/ — Dev — recovers ~5,000 crawl budget pages
2. Rank Math + Custom schema conflict: remove Rank Math auto-schema from 18 affected pages — Dev — unblocks Rich Result eligibility
3. Canonical conflicts on 45 international pages: fix Rank Math canonical URL setting — Dev — restores German and Japanese page indexation

Day 4–14 (this sprint): 4. LCP preload tags: add <link rel="preload"> for hero images on all 28 location pages — Dev — begin CWV improvement 5. Redirect chains: export → update internal links → collapse chains to single 301 — Dev — authority consolidation 6. Title tag template: update Rank Math template formula for location page post type — Dev — resolves 28-page gap

Day 15–30 (next sprint): 7. Orphan pages: categorise 1,200 orphans → fix archive assignments or noindex — Content + Dev 8. Soft 404s: export 280 GSC-flagged pages → noindex thin pages → expand valuable thin pages 9. og:locale: add WordPress filter per subdirectory — Dev

✅ CHECKPOINT — SECTION 1

• [ ] Screaming Frog crawl: complete with JS-disabled and JS-enabled passes
• [ ] All 12 findings: documented with scale, root cause, and fix instruction
• [ ] Day 1–3 fixes: deployed and verified before any content work begins
• [ ] GSC Coverage: monitoring weekly for Crawl Budget improvements
• [ ] Technical audit spreadsheet: findings tab complete with owner and deadline per row

SECTION 2 — CRAWL BUDGET ANALYSIS

Crawl Budget: The Enterprise Metric SME SEO Ignores

Crawl budget does not appear in Google Analytics. It does not appear in GSC’s main dashboard. Most SME SEO practitioners never think about it because at 200 pages, Googlebot crawls the entire site in hours and comes back regularly. At 45,000 pages, Googlebot is making decisions about which pages to crawl, how often, and in what order — and those decisions directly affect how quickly content updates, new pages, and ranking improvements are reflected in search results.

If Googlebot is spending 30% of its crawl budget on /wp-json/ REST API endpoints, blog pagination pages past page 3, and duplicate location page variants — it is spending 30% less time on the product pages, the international landing pages, and the new cluster posts that are supposed to be driving organic growth.

Pro Tip: Crawl budget optimisation is the highest-ROI technical fix per implementation hour on any site over 20,000 pages. Removing 5,000 low-value URLs from Googlebot’s crawl path does not just save crawl budget — it concentrates Googlebot’s attention on the pages that actually matter. New pages get indexed faster. Updated pages get re-crawled faster. Rankings move faster. It is not a vanity technical fix — it directly accelerates every other SEO activity on the site.

2.1 — Crawl Budget Estimation

Google does not publish a crawl budget figure for any site. The estimate below is derived from GSC Crawl Stats (available in Search Console → Settings → Crawl Stats).

Estimated current crawl budget profile:

2.2 — Crawl Waste by Category

Crawl budget recovery: Removing these 6,650 URL patterns from Googlebot’s crawl path recovers approximately 547 crawl requests/day — approximately 17% of the estimated daily crawl budget. This 17% can be redirected to crawling new content, updated landing pages, and international cluster posts.

2.3 — robots.txt Enterprise Implementation

The following robots.txt configuration should be in place for meridianclothco.co.uk. This is the recommended enterprise configuration — not the WordPress default.

User-agent: *
Disallow: /wp-admin/
Disallow: /wp-json/
Disallow: /wp-content/plugins/
Disallow: /wp-includes/
Disallow: /?s=
Disallow: /?replytocom=
Disallow: /de/blog/page/
Disallow: /ja/blog/page/
Disallow: /us/blog/page/
Disallow: /blog/page/4/
Disallow: /author/
Disallow: /tag/

Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.meridianclothco.co.uk/sitemap-en-gb.xml
Sitemap: https://www.meridianclothco.co.uk/sitemap-en-us.xml
Sitemap: https://www.meridianclothco.co.uk/sitemap-de.xml
Sitemap: https://www.meridianclothco.co.uk/sitemap-ja.xml

User-agent: Googlebot-Image
Allow: /wp-content/uploads/

User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

GPTBot and Google-Extended disallows: These block OpenAI and Google’s AI training crawlers from using site content for model training. This is a standard enterprise configuration in 2026 and does not affect search ranking. It is a content licensing decision, not an SEO decision — confirm with Director before deploying.

2.4 — Sitemap Enterprise Configuration

At 45,000 pages, a single XML sitemap is not appropriate. The recommended enterprise configuration uses an XML sitemap index file with separate sitemaps per content type and per language.

Sitemap index structure:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://www.meridianclothco.co.uk/sitemap-en-gb.xml</loc>
    <lastmod>[DATE]</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://www.meridianclothco.co.uk/sitemap-en-us.xml</loc>
    <lastmod>[DATE]</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://www.meridianclothco.co.uk/sitemap-de.xml</loc>
    <lastmod>[DATE]</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://www.meridianclothco.co.uk/sitemap-ja.xml</loc>
    <lastmod>[DATE]</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://www.meridianclothco.co.uk/sitemap-images.xml</loc>
    <lastmod>[DATE]</lastmod>
  </sitemap>
</sitemapindex>

Per sitemap, include:

• Only pages that are indexable (not noindex, not 301, not soft 404)
• Only pages returning 200 status codes
• <lastmod> using actual content update dates — not server-generated timestamps
• <priority> values: 1.0 for location landing pages, 0.8 for pillar posts, 0.6 for cluster posts, 0.4 for supporting pages
• <changefreq> values: weekly for location pages and GBP-synced content, monthly for pillar posts, yearly for static service pages

Submit all five sitemaps to GSC. Each sitemap submission creates a separate indexing request queue in GSC — allowing monitoring of indexation rate per content type and per language.

2.5 — Crawl Budget Monthly Monitoring Plan

✅ CHECKPOINT — SECTION 2

• [ ] robots.txt: updated with enterprise configuration, GPTBot/Google-Extended decision made
• [ ] Sitemap index: 5 sitemaps submitted to GSC, all returning 200
• [ ] Crawl waste estimate: 6,650 URL patterns identified, robots.txt/noindex applied
• [ ] GSC Crawl Stats: baseline crawl rate recorded before and after changes
• [ ] Monitoring dashboard: crawl budget metrics added to weekly reporting checklist

SECTION 3 — CORE WEB VITALS REMEDIATION

CWV at Enterprise Scale: Per-Template, Not Per-Page

Core Web Vitals on a 45,000-page site are not diagnosed and fixed page by page. They are diagnosed per page template and fixed at the template level — so the fix applies to every page using that template simultaneously.

Meridian Cloth Co. uses approximately 8 distinct page templates across WordPress + Elementor:

1. Location landing page template (28 pages)
2. International location page template (12 pages — US, DE, JP primary)
3. Pillar post template (6 pages)
4. Cluster/blog post template (~200 pages)
5. Service page template (8 pages)
6. Hub page template (3 pages)
7. Homepage template (1 page)
8. Contact/quote page template (6 pages)

Pro Tip: PageSpeed Insights shows you the CWV score for one URL at a time. Google Search Console shows you the CWV status for URL groups — which are automatically clustered by template similarity. Always start the CWV diagnosis with GSC Core Web Vitals report (Search Console → Core Web Vitals), not PageSpeed Insights. GSC shows you the template-level problem at scale. PageSpeed Insights then helps you diagnose the specific element causing the failure on that template.

3.1 — Current CWV Status by Template (Mobile, p75)

Critical templates: Location landing page, US international page, Homepage

3.2 — LCP Remediation — Location Landing Page Template

Root cause: The Elementor Section background image is the LCP element. It is loaded via CSS background-image property — not as an <img> tag. CSS background images cannot be preloaded with <link rel="preload"> in the standard way, and LiteSpeed Cache does not auto-detect CSS background images for preloading.

Fix sequence:

Step 1: Change hero image from Elementor Section background to an <img> tag inside an Elementor Image widget positioned over the section. This makes the hero image an <img> element in the DOM — preloadable and optimisable.

Step 2: Add preload tag in WordPress theme header.php or via LiteSpeed Cache’s Custom Head Code:

<link rel="preload" as="image"
  href="https://www.meridianclothco.co.uk/wp-content/uploads/[hero-image].webp"
  fetchpriority="high"
  type="image/webp">

Step 3: LiteSpeed Cache → Image Optimization → Enable WebP replacement → Enable Lazy Load → Exclude: hero image (lazy loading the LCP element is a critical anti-pattern — it delays LCP instead of improving it).

Step 4: LiteSpeed Cache → Page Optimization → CSS Settings → Critical CSS → Generate per page type for location template. Critical CSS eliminates render-blocking stylesheet requests.

Step 5: Enable LiteSpeed Cache → Page Optimization → Load CSS Asynchronously. Exclude Elementor CSS files that control above-fold layout — async loading these causes CLS.

Expected improvement: LCP from 3.2s → 1.8–2.2s on mobile. This moves all location pages from Needs Improvement to Good. (Estimate based on LiteSpeed Cache documentation and similar WordPress/Elementor implementations.)

Owner: Dev Effort: 6–8 hours (template change + preload implementation + LiteSpeed configuration + QA) Priority: 🔴 P1

3.3 — LCP Remediation — US International Pages (4.1s → target <2.5s)

Root cause: Two compounding factors. (1) Same hero image LCP issue as UK location pages. (2) Cloudflare CDN is configured but the /us/ subdirectory is not being served from Cloudflare’s US edge nodes — all requests are routing to the UK origin server, adding 80–150ms geographic latency on top of the LCP issue.

Fix sequence:

Step 1: Cloudflare dashboard → Caching → Cache Rules → Add rule: cache all GET requests matching /us/* with Cache Everything setting. This ensures US visitor requests are served from Cloudflare’s US edge nodes — reducing TTFB from ~320ms to ~80ms for US visitors.

Step 2: Apply LCP preload fix from Section 3.2 to US location page template.

Step 3: Test from US IP (use PageSpeed Insights with US server location) after Cloudflare cache rule is live. TTFB should drop below 100ms.

Step 4: Run GTmetrix with server location set to Vancouver, CA (closest North American GTmetrix server to US audience). Target: LCP < 2.5s.

Expected improvement: LCP from 4.1s → 2.0–2.4s. Moves US pages from Poor to Good. This has the largest single-fix impact on the site because US pages were previously in Google’s worst performance tier.

Owner: Dev Effort: 4–5 hours Priority: 🔴 P1 — Poor CWV category directly suppresses ranking

3.4 — CLS Remediation — Pillar Post Template (0.12 → target <0.1)

Root cause: CLS of 0.12 on pillar posts is caused by a custom font rendering shift. The site uses a custom font (loaded via Google Fonts) that causes layout shift while the font downloads and replaces the fallback system font. This is a classic FOUT (Flash of Unstyled Text) CLS issue.

Fix:

Step 1: LiteSpeed Cache → Page Optimization → Font Display: add font-display: swap to all font-face declarations. This prevents FOUT-based CLS by ensuring the browser uses the fallback font size-matched to the custom font.

Step 2: Preconnect to Google Fonts in theme head:

<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>

Step 3: Self-host the Google Fonts files on the Hostinger server. Eliminate the third-party request entirely. Use: google-webfonts-helper.herokuapp.com to download the font files and the corresponding CSS snippet.

Expected improvement: CLS from 0.12 → 0.04–0.07. Moves pillar posts from Needs Improvement to Good.

Owner: Dev Effort: 3–4 hours Priority: 🟡 P2

3.5 — INP Remediation — US International Pages (210ms → target <200ms)

Root cause: INP of 210ms on US pages is marginally above threshold. The cause is LiteSpeed Cache’s JavaScript deferral setting — it defers all JavaScript including Elementor’s interaction handlers. When a user interacts with the page (click, form input), the deferred scripts have not yet loaded, causing a delay before the interaction is processed.

Fix:

LiteSpeed Cache → Page Optimization → JS Settings → JS Deferred → Excluded JS Files. Add:

• elementor-frontend.min.js
• elementor/js/frontend.min.js
• jquery.min.js (if Elementor depends on it for interactions)

These scripts must load synchronously — deferring them causes INP failures on interaction-heavy Elementor pages.

Expected improvement: INP from 210ms → 140–170ms. Moves US pages from Needs Improvement to Good on INP metric.

Owner: Dev Effort: 1–2 hours Priority: 🟡 P2

3.6 — CWV Monitoring Plan — Enterprise

Regression prevention rule: Before any new Elementor widget, plugin, or theme update is deployed to production, run PageSpeed Insights on one template URL in a staging environment. If LCP increases by >0.3s or CLS increases by >0.05, block the deployment until root cause is identified.

✅ CHECKPOINT — SECTION 3

• [ ] CWV audit: all 8 templates assessed — LCP, CLS, INP documented
• [ ] P1 fixes deployed: location landing page LCP + US international LCP + CDN cache rule
• [ ] P2 fixes in sprint: CLS fix for pillar posts + INP fix for US pages
• [ ] GSC Core Web Vitals: weekly monitoring cadence confirmed
• [ ] Regression prevention: staging CWV check added to deployment checklist
• [ ] PageSpeed baseline: all template URLs tested and scores recorded pre-fix

SECTION 4 — ENTERPRISE CONTENT ARCHITECTURE

Content Architecture at 45,000 Pages: Intention vs Reality

When the single-location project launched, the content architecture was intentional — pillar page, cluster posts, location pages, and a clear hub structure. At 45,000 pages, the architecture has accumulated organic growth, gaps, and inconsistencies that were not planned.

The enterprise content audit does not start from scratch. It maps what exists, identifies what is missing, identifies what is competing with itself, and produces a 12-month content roadmap that closes the gaps systematically.

Pro Tip: The most common enterprise content architecture mistake is commissioning new content before auditing existing content. At 45,000 pages, there are almost certainly pages that already rank for the target keyword, pages that cover 80% of the brief already written, and pages that are cannibalising the new brief’s target keyword right now. Running the cannibalisation check and the content consolidation audit (Section 6) before briefing any new content saves the equivalent of 30–40% of a year’s content production budget.

4.1 — Current Content Architecture Map

Tier 1 — Pillar Posts (established):

Tier 2 — Location Landing Pages (established):

Tier 3 — Cluster Posts (partial — gaps identified):

Tier 4 — Service/Certification Pages (gaps identified):

4 missing service pages + 8 missing certification/educational pages = 12 high-priority content gaps.

4.2 — Content Gap Priority Matrix

The following matrix prioritises missing content by: (1) search volume, (2) commercial intent, (3) cannibalisation risk from existing pages, and (4) content production effort.

4.3 — 12-Month Content Production Roadmap

Quarter 1 (Months 1–3): Foundation Content Gaps

Quarter 2 (Months 4–6): International Content Cluster

Quarter 3 (Months 7–9): Case Studies & Social Proof Content

Quarter 4 (Months 10–12): AEO & Authority Content

Total content output (12 months): 27 pieces · approximately 58,000 words · across 4 markets and 3 languages

4.4 — Content Quality Standards at Enterprise Scale

Every piece of content produced in this programme adheres to these standards — regardless of who writes it.

Minimum requirements per piece:

• Quick Answer block: 80–120 words, minimum 3 data points, before first H2
• Insight Rule: one counterintuitive point or genuine trade-off per H2 section
• Stat sourcing: all statistics from named sources with year — no fabricated data
• E-E-A-T: minimum 4 signals per piece (see Enterprise SEO Master Prompt Rule 8)
• Internal links: 3 outgoing to pillar/service pages + 3 incoming planned in CMS
• Forbidden phrases: full list from Enterprise SEO Master Prompt Rule 4 applied
• Schema: FAQPage on all long-form pieces, BreadcrumbList on all pages
• CTA: primary + secondary + 2 inline CTAs with live URLs
• Authorship: named author with credentials or “Meridian Cloth Co. Team” for service pages

Content governance workflow: Brief approved → Writer assigned → First draft → SEO review → E-E-A-T check → Legal check (pricing/certification claims) → Director approval (case studies, original research) → Publish → Schema deployed → Internal links updated → URL submitted to GSC

✅ CHECKPOINT — SECTION 4

• [ ] Content architecture map: all existing content categorised by tier
• [ ] 12 content gaps: prioritised and briefed
• [ ] 12-month roadmap: approved by Director and Content Manager
• [ ] Content governance workflow: shared with all team members
• [ ] Cannibalisation check: run before each brief is issued (GSC + site search operator)

SECTION 5 — PROGRAMMATIC SEO BRIEF

When to Use Programmatic SEO — and When Not To

Programmatic SEO is the practice of generating multiple pages from a structured data source, where each page targets a variant of a query that has genuine individual search demand. At its best, it creates hundreds of useful, genuinely differentiated pages that rank for long-tail queries a manual content programme would never reach. At its worst, it generates thousands of thin, near-identical pages that trigger Google’s Helpful Content System and suppress every page on the domain.

The test for whether programmatic SEO is appropriate is not “can we generate pages at scale?” It is “does each generated page answer a genuinely distinct query with content that cannot be found identically elsewhere?”

Pro Tip: The most successful programmatic SEO implementations in B2B manufacturing build pages around specification data — not around geography alone. A page for “clothing manufacturer Manchester” (city-only variable) carries limited unique value. A page for “GOTS certified clothing manufacturer Manchester” (certification + city + page type) answers a distinct query with specific local data. The variable must add genuine specificity to pass the Helpful Content evaluation.

5.1 — Programmatic SEO Opportunity Assessment

Opportunity 1: Integration Pages (/integrations/[tool-name]/)

Target URL template: /integrations/[tool-name]/ Example pages: /integrations/shopify/ · /integrations/woocommerce/ · /integrations/dear-inventory/ · /integrations/xero/ · /integrations/cin7/

Unique content per variant includes: How the integration works, what data syncs, setup process, which plan the integration is available on, any limitations, link to documentation.

Opportunity 2: Use Case Pages (/use-cases/[industry]/)

Target URL template: /use-cases/[industry]/ Example pages: /use-cases/fashion-startups/ · /use-cases/sportswear/ · /use-cases/workwear/ · /use-cases/luxury-fashion/ · /use-cases/sustainable-brands/ · /use-cases/retail-own-label/ · /use-cases/e-commerce-brands/ · /use-cases/designer-fashion/

Opportunity 3: Certification Pages (/certifications/[cert-name]/)

Target URL template: /certifications/[cert-name]/ Example pages: /certifications/gots/ · /certifications/wrap/ · /certifications/fair-trade/ · /certifications/sa8000/ · /certifications/oeko-tex/ · /certifications/iso-9001/

Opportunity 4: City × Service Combinations (NOT recommended)

5.2 — Integration Pages Template Specification

Data source: Google Sheet with columns: Tool Name · Tool Category · Integration Type · What Syncs · Setup Time · Plan Required · Documentation URL · Logo URL · CTA URL

Template per integration page:

Title: [Tool Name] Integration | Meridian Cloth Co.
H1: Connect [Tool Name] with Meridian Cloth Co.'s Clothing Manufacturing Platform
Quick Answer block: [80–120 words describing what the integration does, what data syncs, which plans it's available on]
H2-1: What Does the [Tool Name] Integration Do?
H2-2: Which Order Data Syncs Between [Tool Name] and Meridian?
H2-3: How Do I Set Up the [Tool Name] Integration?
H2-4: Which Meridian Plan Includes the [Tool Name] Integration?
H2-5: What Are the Limitations of the [Tool Name] Integration?
CTA: "Set Up the [Tool Name] Integration" → [documentation URL]
Schema: SoftwareApplication (for the integration) + FAQPage

Unique content per variant (data-driven, not templated):

• Tool Name (obvious)
• Tool Category (ERP / Inventory / E-commerce / Accounting)
• What syncs: specific fields and data types per integration
• Setup time: specific to each tool
• Plan availability: which Meridian pricing tier includes this
• Limitations: specific per integration

Quality control for programmatic batch:

• Minimum unique content per page: 45% (syncs data, limitations, and setup are unique per integration)
• Pre-publication similarity check: Copyscape inter-page check — any two pages >65% similar are rejected and require content differentiation
• No integration page published without verified documentation URL returning 200
• All integration pages: internal link from /clothing-manufacturing-services/ and from homepage integrations section

5.3 — Use Case Pages Template Specification

Data source: Google Sheet with columns: Industry · Pain Points (3) · Key Requirements · Certifications Relevant · Typical MOQ · Typical Garment Types · Case Study Client (if available) · CTA Text

Template per use case page:

Title: Clothing Manufacturer for [Industry] Brands | Meridian Cloth Co.
H1: Clothing Manufacturing for [Industry] Brands — Low MOQ, [Key Requirement]
Quick Answer block: [80–120 words — what Meridian does for this industry, MOQ, key certifications relevant]
H2-1: What Do [Industry] Brands Need From a Clothing Manufacturer?
H2-2: What Garment Types Does Meridian Cloth Co. Produce for [Industry] Brands?
H2-3: Which Certifications Matter for [Industry] Production?
H2-4: What Is the MOQ for [Industry] Brands at Meridian?
H2-5: Case Study: [Client Name] — How We Supported [Industry Brand Type] (if available)
Schema: Service + FAQPage + BreadcrumbList

5.4 — Crawl Budget Implications of Programmatic Pages

Adding 26 new pages (12 integration + 8 use case + 6 certification) to the site is a net addition of ~26 crawl budget demands. At the current estimated crawl rate of 3,200 pages/day, 26 pages represents <1% of daily crawl capacity — negligible.

However, the crawl budget optimisation from Section 2 has reclaimed approximately 547 pages/day. The net crawl budget position after Section 2 remediation and this programmatic addition is:

Reclaimed: +547 pages/day → Added: 26 pages → Net improvement: +521 pages/day available for priority content

All 26 programmatic pages are submitted to the appropriate sitemap on publication. Internal links from high-authority pages (homepage, service pages, pillar posts) are implemented programmatically via CMS template rules before publication — not added manually post-launch.

✅ CHECKPOINT — SECTION 5

• [ ] Viability assessment: 3 viable programmatic opportunities confirmed, 1 rejected
• [ ] Integration pages: data sheet complete, template approved, 12 pages ready to publish
• [ ] Use case pages: data sheet complete, template approved, 8 pages ready to publish
• [ ] Certification pages: data source (certification body sites) confirmed, 6 pages ready
• [ ] Crawl budget: net impact assessed — positive after Section 2 remediation
• [ ] Quality control: similarity check protocol defined before any batch publication

SECTION 6 — CONTENT CONSOLIDATION AUDIT

The Enterprise Consolidation Imperative

At 45,000 pages, content consolidation is not optional — it is structural maintenance. Every enterprise site accumulates content that was created with overlapping intent, content that was once useful but is now thin relative to current search quality standards, and content that is actively cannibalising the rankings of better, more current pages.

Content consolidation on this site falls into four categories: (1) near-duplicate location pages, (2) thin blog posts from the early growth phase, (3) overlapping pillar and cluster content, and (4) outdated content that contained statistics which are now more than 3 years old.

Pro Tip: The highest-risk consolidation decision at enterprise scale is always the redirect. A 301 redirect from URL A to URL B transfers accumulated link equity — but it also permanently removes URL A from the index, regardless of whether URL B is genuinely a better answer to the query. Before redirecting any page with >1,000 organic sessions/month, export the GSC query data for that URL and confirm the target URL can absorb all of those queries without introducing cannibalisation.

6.1 — Consolidation Candidate Categories

Category A — Near-Duplicate Location Pages (8 confirmed pairs)

Pre-redirect action for each pair:

1. Export GSC queries for URL being redirected → confirm all intent covered by target URL
2. Update all internal links pointing to redirect URL → point directly to target URL in CMS
3. Check referring domains for redirect URL in Ahrefs → any high-DR links? Contact site owners to update.
4. 301 at server level (Hostinger .htaccess) → NOT WordPress redirect plugin
5. Monitor: GSC impressions for target URL should increase within 4–6 weeks

Category B — Thin Blog Posts (word count <600, no rankings)

Screaming Frog word count export + GSC query filter (pages with <100 impressions/month) identifies approximately 34 blog posts below the quality threshold.

Estimated: 22 pages → noindex (no ranking signal loss). 12 pages → expand (content investment with guaranteed return).

Category C — Outdated Statistics (stats >3 years old)

A content audit of all pages containing statistics reveals approximately 28 pages with statistics sourced from 2021 or earlier. At enterprise scale, outdated statistics are both a credibility risk and an E-E-A-T failure signal.

Update schedule:

• Pillar posts: annual update cycle — scheduled for the quarter the post was originally published
• Location pages: annual update cycle — triggered by actual market rate changes
• Blog posts: biennial update cycle unless a stat is actively cited in a date-specific context
• Schema dateModified: update only when content substantively changes — not as a cosmetic freshness signal

Governance: Add to CMS custom field: “Last Stats Review Date” per post. Report in monthly SEO review: any post with Last Stats Review Date > 18 months ago → schedule for update.

6.2 — Consolidation Implementation Order

6.3 — Post-Consolidation Monitoring Protocol

✅ CHECKPOINT — SECTION 6

• [ ] Consolidation audit: all 4 categories assessed, decisions documented
• [ ] Near-duplicate pairs: GSC query export completed before any redirect
• [ ] 301 redirects: implemented at server level (.htaccess), not plugin
• [ ] 22 thin posts: noindex applied via Rank Math
• [ ] 12 thin posts with ranking: added to Content Q2 roadmap for expansion
• [ ] Outdated stats: “Last Stats Review Date” custom field added to CMS

SECTION 7 — SCHEMA LIBRARY — ENTERPRISE COMPLETE

Enterprise Schema: Completeness, Consistency, Governance

The international project built schema for five markets. The enterprise project builds the complete schema library covering every page type on the site — with governance rules that prevent the duplication and conflict issues found in Section 1.

Enterprise schema governance rule: One schema author. All schema on meridianclothco.co.uk is deployed via Elementor Custom HTML widget. Rank Math schema output is disabled on all pages with custom schema. This is the single most important schema governance decision — mixed schema sources on the same page create validation errors and suppress Rich Result eligibility.

Pro Tip: Enterprise sites with 45,000 pages cannot maintain schema manually on every page. The schema that scales is template-level schema — schema deployed in the CMS page template so that every page of a given type inherits the correct schema blocks automatically. Location pages auto-inherit LocalBusiness schema with city-specific fields populated from custom fields. Blog posts auto-inherit Article schema with author data from the WordPress author profile. Manual per-page schema is only for unique pages — the homepage, specific landing pages, and pages with custom FAQ blocks.

7.1 — Schema Type Map — All Page Types

7.2 — Service Schema — AQL Quality Control Page

{
  "@context": "https://schema.org",
  "@type": "Service",
  "@id": "https://www.meridianclothco.co.uk/aql-quality-control/#service",
  "name": "AQL Quality Control — Clothing Manufacturing",
  "description": "AQL (Acceptable Quality Level) inspection service for clothing production. Meridian Cloth Co. conducts 4-point fabric inspection and AQL 2.5 garment inspection on all bulk production orders. AQL 1.5 available on request for premium and Japanese market orders.",
  "provider": {
    "@type": "Organization",
    "name": "Meridian Cloth Co.",
    "@id": "https://www.meridianclothco.co.uk/#organization"
  },
  "serviceType": "Quality Control Inspection",
  "areaServed": ["GB", "US", "DE", "JP"],
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Quality Control Services",
    "itemListElement": [
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "AQL 2.5 Inspection",
          "description": "Standard garment inspection to AQL 2.5 — ISO 2859-1 statistical sampling standard. Covers: measurements, construction, stitching, colour, trim, labelling."
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "AQL 1.5 Inspection",
          "description": "Enhanced inspection to AQL 1.5 — tighter acceptance criteria for premium and Japanese market orders. Covers all AQL 2.5 criteria plus additional trim and finishing checks."
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "4-Point Fabric Inspection",
          "description": "Pre-production fabric inspection to 4-point system (ASTM D5430). Identifies fabric defects before cutting — prevents bulk production failure."
        }
      }
    ]
  },
  "url": "https://www.meridianclothco.co.uk/aql-quality-control/"
}

7.3 — Integration Page Schema (SoftwareApplication)

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "@id": "https://www.meridianclothco.co.uk/integrations/shopify/#integration",
  "name": "Meridian Cloth Co. — Shopify Integration",
  "description": "Connect Shopify with Meridian Cloth Co.'s clothing manufacturing platform. Sync orders, inventory, and fulfilment data automatically. Available on Growth and Enterprise plans.",
  "applicationCategory": "BusinessApplication",
  "applicationSubCategory": "Manufacturing Integration",
  "operatingSystem": "Shopify (any plan)",
  "offers": {
    "@type": "Offer",
    "name": "Shopify Integration",
    "description": "Included on Growth and Enterprise plans",
    "availability": "https://schema.org/InStock"
  },
  "provider": {
    "@type": "Organization",
    "name": "Meridian Cloth Co.",
    "@id": "https://www.meridianclothco.co.uk/#organization"
  },
  "url": "https://www.meridianclothco.co.uk/integrations/shopify/"
}

7.4 — Author Entity Schema (Person — for blog posts and pillar content)

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://www.meridianclothco.co.uk/authors/meridian-cloth-co-team/#person",
  "name": "Meridian Cloth Co. Team",
  "url": "https://www.meridianclothco.co.uk/authors/meridian-cloth-co-team/",
  "description": "Content produced by the Meridian Cloth Co. production and operations team — drawing on 17 years of UK clothing manufacturing experience across 8 sourcing countries.",
  "jobTitle": "Clothing Manufacturing Specialists",
  "worksFor": {
    "@type": "Organization",
    "name": "Meridian Cloth Co.",
    "@id": "https://www.meridianclothco.co.uk/#organization"
  },
  "knowsAbout": [
    "Clothing Manufacturing",
    "Garment Quality Control",
    "AQL Inspection",
    "Tech Pack Development",
    "Ethical Fashion Production",
    "GOTS Certification",
    "Multi-Country Sourcing"
  ],
  "sameAs": [
    "https://www.linkedin.com/company/meridianclothco",
    "https://www.ukft.org/[LISTING]"
  ]
}

7.5 — Schema Validation and Deployment Protocol

Before deploying any schema block:

1. Paste JSON-LD into validator.schema.org → target: 0 errors, 0 warnings
2. Test on Google Rich Results Test → confirm Rich Result type eligible (FAQPage, Article, Product, Service as applicable)
3. Check for Rank Math conflict: Rank Math sidebar → Schema → confirm no auto-generated block of the same @type
4. Deploy via Elementor Custom HTML widget → position after last content section, before footer
5. Verify post-deployment: view page source → confirm JSON-LD appears in page HTML, not rendered by JS
6. GSC Rich Results report: check after 7 days for any errors or warnings appearing

Template schema governance (ongoing):

• Any CMS template change that affects a page type with auto-generated schema must include schema validation in QA checklist
• Schema version log: maintain a shared document recording schema @type, template, deployment date, and last validation date for all schema blocks
• Quarterly schema audit: run Rich Results Test on one URL per template type → confirm all types still valid

✅ CHECKPOINT — SECTION 7

• [ ] Schema type map: all 12 page types assigned correct schema blocks
• [ ] Rank Math conflicts: resolved on all 18 pages identified in Section 1
• [ ] New schema blocks: AQL, Tech Pack, Integration, Author entity — all validated
• [ ] Template schema: automated generation confirmed for Article (blog) and BreadcrumbList
• [ ] Schema governance: version log created, quarterly audit scheduled
• [ ] GSC Rich Results: monitoring enabled per schema type

SECTION 8 — ENTITY SEO & KNOWLEDGE PANEL PROGRAMME

Entity Authority at Enterprise Scale

An entity is how Google’s Knowledge Graph represents a real-world thing — a business, a person, a product, a place. For Meridian Cloth Co., the entity is the organisation itself. The stronger Google’s confidence in the Meridian Cloth Co. entity — its founding date, its certifications, its location, its staff, its industry memberships — the more confidently Google will cite it in AI Overviews, Knowledge Panels, and local search results.

Entity authority does not come from any single source. It is built from the cumulative corroboration of many independent, trustworthy sources all agreeing on the same facts about the same entity. One Wikipedia article, one Wikidata entry, one UKFT membership page, one Companies House registration, and one LinkedIn company profile all saying “Meridian Cloth Co. is a clothing manufacturer founded in 2008, based in London” creates stronger entity confidence than any single authoritative source alone.

Pro Tip: Entity SEO and traditional link building are not the same exercise — but they overlap significantly. A link from UKFT.org is both a high-DR backlink and an entity corroboration signal. A Wikidata entry is zero DR but maximum entity signal. A press mention in Drapers is a high-authority brand signal with or without a backlink. Manage them as one coordinated programme — not as two separate activities operated by different teams.

8.1 — Current Entity Audit

Wikipedia assessment: Wikipedia requires verifiable notability — typically 2+ significant references in major publications independent of the subject. Meridian Cloth Co. would require press coverage in publications like Drapers, The Times Business, or an industry body publication before a Wikipedia entry could be created without being flagged for deletion. Do not attempt Wikipedia until at least 3 independent verifiable press mentions are secured (from Section 10 backlink programme). Instead, prioritise Wikidata, which has no notability threshold.

8.2 — Wikidata Entity Creation

Wikidata is the machine-readable knowledge base that directly feeds Google’s Knowledge Graph. Creating a Wikidata entry for Meridian Cloth Co. is the highest-priority entity action with zero content cost.

Required fields for Wikidata entry:

Supporting citations required for Wikidata entry: Each claim must be supported by a verifiable reference. Use: Companies House registration as source for founding date and business type. Use UKFT membership page as source for industry. Use meridianclothco.co.uk as source for location and official website.

Timeline: Wikidata entries for businesses with verifiable Companies House registration are typically approved within 2–4 weeks if claims are properly sourced. Monitor: after submission, check Google for “Meridian Cloth Co.” — Knowledge Panel should appear or update within 4–12 weeks of Wikidata entry approval.

8.3 — Knowledge Panel Programme

Current status: Run a Google search for “Meridian Cloth Co.” — document what appears. If a Knowledge Panel appears, claim it via GSC (Search Console → About this result → Claim this Knowledge Panel). If no Knowledge Panel appears, the Wikidata programme (Section 8.2) and entity corroboration work in Section 10 will build toward its emergence over 3–6 months.

Knowledge Panel elements to populate once claimed:

• Business description (pulled from Wikidata or website meta — ensure consistency)
• Logo (high-resolution, minimum 400×400px, hosted on Wikimedia Commons)
• Social profiles: LinkedIn, Twitter/X, Facebook — all confirmed and linked
• Founded date: 2008
• Industry: Clothing Manufacturing
• Headquarters: London, England, UK

Knowledge Panel maintenance:

• Check monthly: does the Knowledge Panel description match the current business description?
• After any press coverage that describes Meridian differently: submit correction if needed via Google’s Knowledge Panel feedback
• After international expansion: check whether additional city Knowledge Panels appear for Manchester, Birmingham, Bristol, Glasgow locations

8.4 — Author Entity Programme

For the Content Architecture (Section 4) to produce content that earns E-E-A-T credibility, the author entity must be corroborated beyond the WordPress author profile.

“Meridian Cloth Co. Team” author entity:

• Author page: /authors/meridian-cloth-co-team/
• Content: team description, 17 years of experience, combined expertise areas, UKFT membership
• Schema: Person schema (Section 7.4) deployed on author page
• External corroboration: LinkedIn company page links to team, UKFT membership page mentions team
• Byline: all pillar and cluster posts carry “By Meridian Cloth Co. Team” with link to author page

Named author consideration: If Meridian Cloth Co. has a specific named individual (Managing Director, Head of Production, or similar) willing to be the named author on high-authority content — particularly YMYL-adjacent content about certifications, quality standards, and sourcing ethics — a named individual with verifiable credentials creates stronger E-E-A-T than an organisational author. Consider for the highest-value 3–5 pillar posts.

✅ CHECKPOINT — SECTION 8

• [ ] Entity audit: all 12 sources assessed, status confirmed
• [ ] Wikidata: entry submitted with all required properties and citations
• [ ] Knowledge Panel: claimed if existing, monitored if not
• [ ] Crunchbase: profile claimed and completed
• [ ] Author page: /authors/meridian-cloth-co-team/ published with Person schema
• [ ] Organization schema sameAs: updated with all confirmed entity URLs
• [ ] External corroboration: minimum 5 independent sources confirmed for entity

SECTION 9 — COMPETITOR ANALYSIS AT ENTERPRISE SCALE

Enterprise Competitor Intelligence: Share of Voice, Not Just Rankings

SME competitor analysis asks: “What position are we vs them?” Enterprise competitor analysis asks: “What percentage of the available organic visibility in our market do we own — and what do we need to do to increase it?”

Share of Voice (SOV) is the enterprise metric. It is calculated by tracking a defined keyword universe (in this case, all keywords relevant to clothing manufacturing B2B) and measuring what percentage of the combined impressions Meridian Cloth Co. earns vs all competitors combined.

Pro Tip: Share of Voice tells you a story that individual keyword rankings cannot. A competitor can rank #1 for 10 keywords while you rank #5 for 200 keywords and have a higher SOV because the 200 keywords you rank for have more combined search volume. SOV measures market presence — individual rankings measure individual page performance. At enterprise scale, SOV is the strategic metric; individual keyword tracking is the diagnostic tool.

9.1 — Competitor Identification

Direct organic competitors (sites ranking for the same B2B clothing manufacturing keywords):

Aggregator competitors (not direct businesses but capturing ranking positions):

• Thomasnet.com (UK manufacturing directory — DR 78)
• Kompass.com (B2B directory — DR 74)
• Made-in-britain.org (Manufacturing directory — DR 45)
• UKFT.org (Industry body — DR 52)

These aggregators rank above manufacturer sites for broad category queries. The strategy is not to outrank them (extremely difficult due to DR advantage) but to rank in their directory listings and earn featured placement, while outranking them for specific long-tail queries where a dedicated manufacturer page with technical depth is more relevant.

9.2 — Share of Voice Baseline (March 2026)

Keyword universe: 2,400 keywords across B2B clothing manufacturing, ethical production, MOQ/startup terms, international manufacturing, quality control, and certification terms.

Key finding: Competitor C (ethical fashion angle) holds the highest SOV in the keyword universe. Their content is stronger on certification-specific content (GOTS, Fair Trade) and startup-focused content. The AQL Quality Control page, GOTS Certification Guide, and WRAP Certification Guide briefed in Section 4 directly target this gap.

9.3 — Content Gap Analysis

Keywords ranking for competitors but not Meridian Cloth Co.:

These gaps directly inform the content roadmap in Section 4. Every content gap in the competitor analysis has a corresponding brief in the 12-month roadmap.

9.4 — SERP Feature Gap Analysis

9.5 — SOV Targets — Month 12

✅ CHECKPOINT — SECTION 9

• [ ] SOV baseline: measured across 2,400-keyword universe before any changes
• [ ] Competitor DR and content depth: documented per competitor
• [ ] Content gap analysis: 10 priority keywords with action assigned in content roadmap
• [ ] SERP feature gaps: 8 features identified, acquisition path per feature defined
• [ ] SOV tracking: set up in Semrush or Ahrefs position tracking — same keyword set for all domains

SECTION 10 — ENTERPRISE BACKLINK PROGRAMME

Link Building at Scale: Quality Over Quantity, Authority Over Volume

At enterprise scale, link building is not an outreach activity — it is a reputation programme. The links that move enterprise-level rankings are editorial mentions in high-DR trade publications, industry body inclusions, university partnerships, and press coverage earned through original research and genuinely newsworthy content.

Building 50 links from low-DR directories will not move the SOV needle on a 45,000-page site in a competitive B2B market. Two editorial links from Drapers and Sourcing Journal, combined with one industry body listing from UKFT, will move it faster and more sustainably.

Pro Tip: The highest-ROI link building activity for enterprise B2B sites is original research publication. A data-led report published once a year — “UK Clothing Manufacturing Cost Report 2026” — earns citations from journalists, bloggers, social media, and industry publications who need a verifiable source for the statistics they use. One well-researched report earns more links over 12 months than 12 months of outreach-based link building. Plan the research, publish it, and promote it to the press contacts who already write about your industry.

10.1 — Link Building Opportunity Matrix

10.2 — Original Research: UK Clothing Manufacturing Cost Report 2026

Brief: A data-led annual report documenting the cost of clothing manufacturing for UK fashion brands across garment categories, sourcing countries, and MOQ tiers. Primary research drawn from Meridian Cloth Co.’s 17 years of production data, supplemented by publicly available trade body data (UKFT, ONS trade statistics, HM Revenue & Customs fabric import data).

Why this earns links: Every fashion journalist, blogger, procurement manager, and brand founder who writes about clothing manufacturing needs reliable cost data. There is no existing comprehensive, publicly available source of this data. Meridian Cloth Co. publishing it — clearly attributed, with methodology explained — becomes the primary citeable source.

Publication format:

• Long-form report on meridianclothco.co.uk/resources/uk-clothing-manufacturing-cost-report-2026/
• PDF download available (tracks as a Key Event in GA4)
• Press release distributed to: Drapers, The Industry, Fashion United, Retail Gazette, BBC Business (if significant enough)
• LinkedIn article: summary of top 5 findings from the report
• Infographic: cost breakdown by garment type — submitted to Visual.ly, Pinterest

Estimated earned links over 12 months: 15–40 referring domains (based on similar B2B original research publications in adjacent verticals). This single asset, if executed well, would increase the domain’s referring domain count by approximately 15–20%.

10.3 — Anchor Text Strategy — Enterprise Scale

At enterprise scale, anchor text management is not optional — it is a ranking signal monitor. The Penguin algorithm evaluates anchor text distribution across the domain’s entire link profile. An over-optimised exact match ratio (>5% of all referring domain anchors using exact match target keywords) is a risk signal.

Current anchor text distribution estimate (from Ahrefs):

Action: Exact match anchors are currently above target at 8%. For the next 6 months, all outreach templates should specifically avoid exact match anchor text. Encourage branded anchors and partial match anchors. Monitor monthly via Ahrefs Anchors report.

10.4 — Link Velocity Target — Enterprise

Split by market:

• /uk/ pages: 40–55 new referring domains
• /us/ pages: 15–20 new referring domains
• /de/ pages: 10–15 new referring domains
• /ja/ pages: 5–10 new referring domains

✅ CHECKPOINT — SECTION 10

• [ ] Link opportunity matrix: all 20 targets documented with approach and timeline
• [ ] Research report: briefed and assigned for Q4 publication
• [ ] Chamber applications: Manchester + Glasgow + IHK Berlin submitted Month 1
• [ ] Anchor text: current ratio documented, outreach templates updated to favour branded
• [ ] Link velocity: Q1 target of 12–18 domains logged in link tracking sheet
• [ ] Unlinked mention alerts: Google Alerts set for all Meridian Cloth Co. brand variants

SECTION 11 — LOG FILE ANALYSIS BRIEF

Why Log File Analysis Matters at 45,000 Pages

GSC Crawl Stats shows you how many pages Googlebot requests per day. Log file analysis shows you exactly which pages Googlebot requested, when, how often, and what response code it received. It is the difference between knowing your electricity bill and knowing which appliances are using the most power.

At 45,000 pages, log file analysis reveals the crawl priorities Googlebot has independently assigned to your pages — which often differ significantly from the priorities you intended.

Pro Tip: The most revealing single data point in a log file analysis for an enterprise site is the list of pages that Googlebot has not visited in the past 30 days. These are pages that Google has de-prioritised for crawling — either because they received no external signals of value (no links, no click signals) or because previous crawls found them thin, slow, or duplicate. Every page on this list that should be valuable is an internal linking and content quality problem waiting to be diagnosed.

11.1 — Log File Setup

Log location (Hostinger/InMotion): cPanel → Log Manager → Access Log → Download for the analysis period.

Log format: Apache Combined Log Format:

[IP] - [User] [Date] "[Method] [URL] [Protocol]" [Status] [Size] "[Referer]" "[User-Agent]"

Googlebot identification in user agent field:

Googlebot/2.1 (+http://www.google.com/bot.html)

Analysis tool: Screaming Frog Log File Analyser (includes Googlebot filtering, URL pattern analysis, and crawl frequency report).

Log period: 30 days minimum. 90 days preferred for crawl frequency analysis.

11.2 — Analysis Requirements

Produce from log file analysis:

1. Crawl frequency per URL group (monthly):

2. High-value pages with low crawl frequency: Export: pages in the top 100 by organic sessions that were crawled fewer than 3 times in 30 days. These are priority pages receiving insufficient crawl attention — usually caused by insufficient internal link equity pointing to them.

3. Crawl waste by URL pattern: See Section 2 — the log file confirms which of the estimated waste patterns are actually being crawled by Googlebot, and at what frequency. Prioritise robots.txt/noindex fixes for URL patterns appearing most frequently in the waste log.

4. Response code distribution:

5. Crawl bot breakdown: Log file also reveals: Bingbot, AhrefsBot, Semrushbot, GPTBot, Google-Extended. Confirm GPTBot and Google-Extended are being blocked per robots.txt configuration from Section 2 if that was the Director’s decision.

11.3 — Actionable Output from Log Analysis

✅ CHECKPOINT — SECTION 11

• [ ] Log file: 30-day export downloaded from hosting control panel
• [ ] Screaming Frog Log Analyser: analysis complete, Googlebot filter applied
• [ ] High-value uncrawled pages: list produced, internal link plan actioned
• [ ] Waste pattern confirmation: cross-referenced with robots.txt/noindex changes from S2
• [ ] Response code distribution: documented, alerts set for anomalies

SECTION 12 — GOVERNANCE FRAMEWORK

Enterprise SEO Without Governance Fails

The technical fixes in this project will be reversed within 6 months if there is no governance framework to prevent regressions. A developer who does not know that removing a canonical tag from a location page template affects 28 pages simultaneously will do it without thinking. A content manager who does not know that publishing a blog post without assigning a category creates an orphan page will publish 40 orphan posts before the next audit.

Governance is not bureaucracy — it is the set of decisions, checklists, and workflows that prevent the work done in this project from being undone by the day-to-day operations of a busy team.

Pro Tip: The highest-risk period for enterprise SEO regression is the 3–6 months after the initial audit and fix cycle. Developers move on to other projects. Content teams return to their normal publishing cadence. The SEO improvements from this project start degrading — slowly at first, then acceleratingly — because no one is watching the right metrics. The governance framework is what keeps that from happening.

12.1 — SEO Governance Documents Required

Document 1 — CMS Change Protocol (Dev team):

Before any change to a WordPress page template, theme, or plugin that affects:

• Title tag output
• Meta description output
• Canonical tag output
• Schema output
• Page speed (new JavaScript, new plugin, new widget)
• robots.txt

Required steps:

1. Test on staging environment first
2. Run PageSpeed Insights on one template URL before and after — document both scores
3. Run Screaming Frog on staging crawl — confirm no new errors vs current
4. Get SEO Lead sign-off before deploying to production
5. Flush Cloudflare cache immediately after deployment
6. Re-run PageSpeed and Screaming Frog spot check on production within 24 hours

Document 2 — Content Publishing Checklist (Content team):

Before any new page or post is published:

• [ ] Primary keyword stated — cannibalisation check run (GSC query + site:domain.com search)
• [ ] Quick Answer block: 80–120 words, minimum 3 data points
• [ ] All H2s: question or problem format
• [ ] Forbidden phrases: full list checked — none present
• [ ] Minimum 3 E-E-A-T signals identified
• [ ] Stat sourcing: every statistic has named source and year
• [ ] Internal links: 2–3 outgoing to pillar/service pages added
• [ ] Schema: FAQPage deployed on long-form content, BreadcrumbList on all pages
• [ ] Rank Math: title tag and meta description manually reviewed (not auto-generated)
• [ ] Author: byline assigned and linked to author page
• [ ] Category: assigned — no uncategorised posts
• [ ] Rank Math SEO score: >70 (Rank Math’s own scoring, as a sanity check)
• [ ] URL submitted to GSC after publication

Document 3 — Monthly SEO Health Check (SEO Lead):

12.2 — Quarterly SEO Sprint Structure

Q1 Sprint (Months 1–3): Technical + Foundation

• All P1 critical technical fixes from Section 1
• robots.txt enterprise configuration
• Crawl budget optimisation (Section 2)
• CWV P1 fixes for location pages and US pages
• Programmatic pages: integration pages published
• Entity SEO: Wikidata entry submitted

Q2 Sprint (Months 4–6): Content + Links

• Content roadmap Q1 pieces published (6 pieces)
• Content consolidation: 301 redirects + noindex implemented
• CWV P2 fixes: pillar posts + US INP
• Schema library: new page types deployed
• Link building: Chamber applications + university outreach
• Log file analysis: first full analysis, action items in sprint

Q3 Sprint (Months 7–9): Scaling + International

• Content roadmap Q2 pieces published (6 pieces)
• International content clusters: US + DE content published
• Japanese cluster: native-speaker review + publish
• Programmatic pages: use case pages + certification pages published
• Entity programme: Knowledge Panel claimed or emerging
• Second link velocity target check

Q4 Sprint (Months 10–12): Authority + Reporting

• Content roadmap Q3 pieces published
• Original research report: UK Clothing Manufacturing Cost Report 2026
• Press outreach: Drapers + Sourcing Journal + Textilwirtschaft pitches
• 12-month full technical audit
• Schema quarterly audit
• Executive annual review report (Section 14)
• Q1 next year roadmap published

✅ CHECKPOINT — SECTION 12

• [ ] CMS Change Protocol: shared with dev team, acknowledged
• [ ] Content Publishing Checklist: added to content team workflow, all team members trained
• [ ] Monthly SEO Health Check: calendar invite set for 1st Monday of each month
• [ ] Quarterly sprint structure: confirmed with Director, sprint tickets created in project management tool

SECTION 13 — 12-MONTH ENTERPRISE ROADMAP

Phased Enterprise SEO Programme — Visual Summary

13.1 — Month-by-Month Action Plan

Month 1:

• 🔴 P1: robots.txt enterprise config (reclaim 5,000+ crawl budget pages)
• 🔴 P1: schema conflicts resolved (18 pages)
• 🔴 P1: canonical conflicts fixed (45 international pages)
• 🟡 P2: LCP preload tags on all location pages
• Chamber applications: Manchester, Glasgow, IHK Berlin
• Wikidata entry: submitted
• Google Alerts: Meridian Cloth Co. mentions (all variants)

Month 2:

• 🔴 P1: US international LCP → Cloudflare cache rule + preload
• 🔴 P1: redirect chains resolved (340 chains)
• 🟡 P2: title tag templates updated (28 location pages)
• 🟡 P2: soft 404s: 22 noindexed, 12 expansion briefs issued
• Content: AQL Quality Control page published
• Content: Tech Pack Development page published
• Programmatic: Integration pages batch 1 (6 pages) published

Month 3:

• 🟡 P2: CLS fix — pillar posts (font-display: swap + preconnect)
• 🟡 P2: og:locale fix (31 pages)
• Content: GOTS Certification Guide published
• Content: Multi-Country Sourcing page published
• University outreach: LCF + FIT New York + GSA
• Link building: client credit outreach round 1

Month 4:

• Content: What Is a Tech Pack? blog post published (UK)
• Content: Cut and Sew Manufacturing Guide (US)
• Programmatic: Use case pages batch 1 (4 pages)
• Programmatic: Certification pages (6 pages)
• DE content: GOTS vs OEKO-TEX cluster post (native DE review)
• Link building: Made in Britain application + Good On You profile

Month 5:

• Content: GOTS vs OEKO-TEX Unterschied (DE) published
• Content: Apparel Manufacturing Cost USA 2026 (US)
• Content: UK Clothing Manufacturing Cost 2026 — update existing page
• Link building: Sourcing Journal guest article pitch (US)
• Log file analysis: first 30-day analysis complete

Month 6:

• Content: Small Lot Factory Guide (JP) — native review
• Content: WRAP Certification Guide (UK)
• Content: FOB vs DDP Explained (UK)
• Programmatic: Use case pages batch 2 (4 pages)
• Link building: Textilwirtschaft press pitch (DE)
• Integration pages: batch 2 (6 pages)
• Mid-year SOV check: measure vs baseline

Month 7:

• Content: Client Case Study UK (with client approval)
• Content: Client Case Study US (with client approval)
• Content: Knitwear Production Guide (UK)
• Log file analysis: second 30-day analysis
• CWV: INP fix for US international pages deployed
• University links: confirmed live (LCF + FIT)

Month 8:

• Content: Sustainable Fashion Brand Launch Guide (pillar — UK)
• Content: Birmingham Fashion Manufacturing cluster post
• Research report: data collection begins (UK Clothing Manufacturing Cost 2026)
• Link building: second client credit outreach round

Month 9:

• Content: Bristol Ethical Manufacturer Guide (UK)
• Content: German Fashion Brand Manufacturing Guide (DE)
• Research report: analysis and writing phase
• Schema quarterly audit: all template types validated
• Hreflang re-audit: 0 errors target confirmed

Month 10:

• Content: UK Clothing Manufacturer Directory Hub
• Content: What Is AQL in Fashion Manufacturing? blog post
• Research report: final review (Legal + Director sign-off)
• Press outreach: Drapers + The Industry pitches

Month 11:

• Content: How to Start a Clothing Brand UK 2026 (pillar)
• Research report: publication — meridianclothco.co.uk/resources/uk-clothing-manufacturing-cost-report-2026/
• Social amplification: LinkedIn, industry groups, press release
• Content: Japan Apparel OEM Market Guide (JP native review)
• SOV check: measure vs baseline at Month 6 and Month 1

Month 12:

• Full 12-month technical audit (repeat Section 1 process)
• All KPI targets reviewed against Month 1 baselines
• Executive annual review report (Section 14)
• Q1 next year roadmap: draft and present to Director
• Research report: press pickup monitoring and link tracking

SECTION 14 — EXECUTIVE REPORTING TEMPLATE

The Executive SEO Report: Business Language Only

The executive report is not an SEO report with a cover page. It is a business performance report that happens to measure organic search as the channel. The audience — CMO, CFO, CEO, or Director — does not need to know what a canonical tag is. They need to know: are we growing or declining in search? What did it cost? What is the return? What happens next?

Pro Tip: The fastest way to lose executive confidence in an SEO programme is to present a ranking report. Rankings move up and down for dozens of reasons, many outside the SEO team’s control. A ranking improvement that does not drive additional traffic tells the executive nothing about business performance. Always translate: ranking → traffic → conversion → revenue. If you cannot close the loop to revenue or leads, you are presenting a vanity metric.

14.1 — Monthly Executive Digest (1 Page)

Meridian Cloth Co. — Organic Search Performance Reporting Period: [MONTH YEAR] | Prepared by: [SEO LEAD] | Date: [DATE]

Headlines:

Organic sessions this month: [X] ([+/-X%] vs last month · [+/-X%] vs same month last year) Leads from organic search: [X] ([+/-X%] vs last month) Estimated traffic value: £[X,XXX] (what equivalent paid traffic would cost — Ahrefs estimate)

Top 3 Wins This Month:

1. [WIN 1 — named, with metric: “The GOTS Certification Guide published in March ranked on Page 1 for ‘GOTS certified clothing manufacturer UK’ (1,200 monthly searches) within 28 days of publication, generating 42 organic sessions and 3 quote form submissions.”]
2. [WIN 2]
3. [WIN 3]

Top 1 Risk This Month: [RISK — named, with metric and response: “The Birmingham location page dropped from position 5 to position 9 for ‘clothing manufacturer Birmingham’ — estimated impact: -60 sessions/month. Cause: a competitor published a more detailed page with a pricing table we did not have. Action: pricing table content has been briefed and is in the publishing queue for next month.”]

What We Are Doing About It:

1. [Action 1 — owner + deadline]
2. [Action 2 — owner + deadline]
3. [Action 3 — owner + deadline]

Next Month Forecast: [2–3 sentences: what to expect and what it depends on]

14.2 — Quarterly Business Review (QBR) Slides

Slide 1: Organic Search — Quarter in Review

• Organic sessions: Q vs Q-1 vs Q last year (bar chart)
• Organic leads: Q vs Q-1 vs Q last year (bar chart)
• Market Share of Voice: Q vs Q-1 (trend line)

Slide 2: By Market

• Sessions + leads per market: UK / USA / Germany / Japan (table)
• Top-performing page per market (URL + sessions + leads)
• Biggest growth market this quarter

Slide 3: What We Built This Quarter

• Content pieces published: [list with primary keyword and ranking if achieved]
• Technical improvements: [list with business-language impact, not technical detail]
• Links earned: [count + notable sources]

Slide 4: Where We Stand vs Competitors

• Share of Voice chart: Meridian vs top 4 competitors (monthly trend)
• Keywords we moved into top 10 this quarter: [list]
• Keywords we need to win: [3 named priorities with volume]

Slide 5: Next Quarter Plan

• Top 3 content investments and expected return
• Top 3 technical projects and expected return
• Budget required and ROI projection

Slide 6: Year-End Forecast

• Monthly organic sessions projection: Month 1–12 trend with forecast
• Monthly organic leads projection: Month 1–12 trend with forecast
• Estimated organic revenue/leads value by Month 12

14.3 — KPI Dashboard — All Markets

SECTION 15 — ENTERPRISE SEO GLOSSARY

Terms used throughout this project — for reference by the full team, including non-SEO stakeholders.

AQL (Acceptable Quality Level): Statistical sampling standard for manufacturing quality inspection. Used in this project in both the SEO content sense (a new service page) and as a practitioner E-E-A-T signal.

Canonical tag: An HTML tag that tells Google which version of a page is the “official” version when multiple URLs contain the same or very similar content. A canonical conflict (where the tag points to the wrong URL) tells Google to ignore the page for ranking purposes.

Core Web Vitals (CWV): Three page experience metrics Google uses as ranking signals: LCP (Largest Contentful Paint — loading speed), CLS (Cumulative Layout Shift — visual stability), INP (Interaction to Next Paint — responsiveness). Thresholds: LCP ≤2.5s, CLS ≤0.1, INP ≤200ms for “Good” status.

Crawl budget: The number of pages Googlebot will crawl on a site within a given timeframe. Finite. Wasted on low-value pages, it reduces the crawl frequency of high-value pages.

E-E-A-T: Experience, Expertise, Authoritativeness, Trustworthiness. Google’s quality evaluator guidelines framework for assessing content quality. Higher E-E-A-T signals = higher confidence from Google that the content is credible.

Hreflang: An HTML tag that tells Google which language and country version of a page to serve to which user. Missing reciprocal tags are the most common international technical error.

Indexability: Whether a page can be included in Google’s index and appear in search results. A page can be crawled but not indexable (if it has a noindex tag or canonical to another URL).

Knowledge Panel: The information box that appears in Google search results for entities (businesses, people, organisations). Driven by Google’s Knowledge Graph, which draws from Wikidata, Wikipedia, and entity corroboration across the web.

Programmatic SEO: Generating multiple pages from a structured data source, where each page targets a variant query with genuinely unique content. Integration pages and use case pages in this project are programmatic.

robots.txt: A file on the website root that tells search engine crawlers which parts of the site they are and are not allowed to crawl. Does not prevent indexation — it prevents crawling.

Share of Voice (SOV): The percentage of all organic impressions in a defined keyword set that a given domain earns. An enterprise-level metric that measures market presence rather than individual rankings.

Soft 404: A page that returns a 200 HTTP status code (technically live) but contains so little content that Google classifies it as empty or near-empty — and removes it from the index.

Technical debt: Accumulated technical SEO issues that arise from CMS changes, new page type creation, and website updates that were not reviewed for SEO impact before deployment.

Wikidata: The machine-readable knowledge base operated by the Wikimedia Foundation that directly feeds Google’s Knowledge Graph. Has no notability threshold — any real-world entity with verifiable sources can be added.

PROJECT COMPLETION SUMMARY

What This Enterprise Project Built

CITATIONS & SOURCES

1. Google. Core Web Vitals. web.dev, October 2024. https://web.dev/articles/vitals Supports: LCP ≤2.5s, CLS ≤0.1, INP ≤200ms thresholds throughout Sections 3 and the CWV monitoring plan.

2. Google. Crawl budget management. Google Search Central, 2024. https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget Supports: Crawl budget framework, crawl rate terminology, and the crawl budget optimisation approach throughout Section 2.

3. 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 recommended structured data format, Rich Result eligibility requirements (Section 7).

4. Google. Localization versus Internationalization — hreflang. Google Search Central, 2024. https://developers.google.com/search/docs/specialty/international/localization-vs-internationalization Supports: hreflang implementation requirements, reciprocal tag rule, x-default usage (Sections 1 and the international technical checks).

5. Google. How to improve your local ranking on Google. Google Business Profile Help, 2024. https://support.google.com/business/answer/7091 Supports: Relevance, Distance, Prominence as confirmed Local Pack ranking factors (Section 9 SERP features, Section 10 GBP programme).

6. BrightLocal. Local Consumer Review Survey 2024. BrightLocal, 6 March 2024. https://www.brightlocal.com/research/local-consumer-review-survey-2024/ Supports: Review response importance (88% of consumers would use a business that replies to all reviews) referenced in governance framework Section 12 monthly health check.

7. Whitespark. Local Search Ranking Factors 2023. Whitespark, 2023. https://whitespark.ca/local-search-ranking-factors/ Supports: GBP signals at 32% of Local Pack ranking factors, review signals at 16% — referenced in Sections 9 and 10.

8. Schema.org. LocalBusiness. Schema.org, 2024. https://schema.org/LocalBusiness Supports: All LocalBusiness schema block structures across all page types in Section 7.

9. GOTS. Certification — Global Organic Textile Standard. Global Standard, 2024. https://global-standard.org/certification-and-labelling/certification Supports: GOTS certification details used throughout content briefs (Sections 4 and 5) and entity SEO programme (Section 8).

10. UKFT. UK Fashion & Textile Association — Membership. UKFT, 2024. https://www.ukft.org/membership/ Supports: UKFT as primary industry body trust signal and entity corroboration source (Sections 8 and 10).