Resinex (Ravago Group):
How Komate fixed the SEO architecture of Resinex.
Resinex distributes polymers and plastics across more than 30 countries and is part of the Ravago Group. With ~5,800 products and a website serving 31 countries and languages, there is a lot at stake when the digital presence fails to deliver.
Results that speak.
The platform was in good shape: Next.js, Contentful, server-side rendering without issues. Yet Google was indexing a mere 11.7% of ~359,000 pages, with only 4.7% non-branded traffic. Not a matter of poor content or missing metadata. The problem ran deeper, it was in the architecture itself.
Komate mapped out the full picture:
- 11.7% → 30–40% expected indexation rate after corrections
- 18% → <1% server 5xx errors eliminated
- 5.8 million hreflang signals streamlined to ~3.7 million validatable signals
- 87% refresh / 13% discovery crawl budget, a fully reversed ratio as the target
- 27,000 "Google chose different canonical" conflicts resolved to near zero
18% of all crawl requests ended in a 5xx error. The average server response time was 5.23 seconds. Google had already lost trust in the site, not because the content was poor, but because the system was unreliable. Komate dug in down to the code level, identified the root causes, and designed a phased approach that restores routing without changing a single URL.
31 countries, 20 languages, one shared codebase and 5.8 million hreflang signals Google could not validate. On top of that, self-referencing canonicals that actively reinforced duplicate content. Google was fighting itself. Komate mapped the full signal architecture and defined a setup that brings the noise down from 5.8 million to ~3.7 million clean, validatable signals.
Eight websites, one codebase. Every change rolls out across all sites simultaneously, which rules out any classic redirect-based approach straight away. Komate designed a solution that works entirely through Contentful configuration: no URL changes, no redirects, and reversible at any point. Resinex goes first.
The core of the problem.
The problem at the root of Resinex's underperformance wasn't about SEO optimisation. The international routing system was generating conflicting signals on three fronts simultaneously:
- URL chaos: Template variables that failed to resolve, fallback slugs silently rerouting to English on non-English URLs, invalid locale combinations throwing 5xx errors. The foundation was not stable.
- Destruction of crawl trust: 18,687 server 5xx errors, 18% of all crawl requests. An average server response time of 5.23 seconds, while Google expects under 800ms. Triple redirect chains on legacy domains. Google had penalised the site a long time ago.
- Signal chaos: 5.8 million hreflang signals Google could not validate. Self-referencing canonicals on all 31 country variants actively reinforcing duplicate content. Google was trying to consolidate, and losing to the system itself.
Extra challenge: shared codebase.
8 websites, one codebase, one Contentful environment. Whatever you change on Resinex automatically rolls out across all other sites. What is a duplicate here may be meaningful content there. URL removal or redirects were therefore not an option. The solution had to work without removing anything, without redirects, and be reversible at any point.
Solutions.
1. Technical SEO audit.
Komate carried out an in-depth audit across all layers of the SEO architecture: indexation & crawl analysis, GSC performance, URL architecture, on-page SEO, structured data, competitor benchmarking, codebase review, legacy domains, and redirects.
How?
The audit combines Google Search Console data, direct crawl analyses, and codebase inspection. Every problem was investigated to its root, including a structural bug in cross-culture sales-terms URLs.
The result?
A fully documented roadmap across four phases, prioritised by impact and implementation risk, starting from system correctness, not SEO signals.
2. Structured approach in 4 phases.
Restore deterministic routing. Eliminate 5xx generation. Resolve template placeholders. Fix invalid locale-route combinations. Reduce redirect chains from 3 hops to 1.
Straighten out the canonicals: secondary cultures point to the primary URL. Clean up hreflang: full culture codes for all 31 locales on the primary pages, bringing signals down from 5.8M to ~3.7M. Adjust the sitemap so every URL returns a clean 200.
Set up a dedicated `primaryLocaleMapping` per site in Contentful. Resinex goes first as the pilot, the other sites follow. No URL changes, no redirects, and reversible at any point.
Add structured data (Product, Organization, WebSite). Develop a content strategy. Refine title and metadata patterns.
3. Keyword & on-page SEO analysis.
Alongside the technical audit, Komate carried out a comprehensive functional and on-page SEO analysis: keyword research, locale comparisons across 31 markets, and a roadmap for functional optimisations.
The result?
A fully integrated SEO roadmap addressing both technical correctness and commercial search intent, per market, per product category.