Russian service hub
74 → 118 clicks
11,867 → 57,432 impressions · position 13.49 → 10.21
Public verified case study
Multilingual SEO Growth Across Spain
How Lemon SEO developed multilingual search visibility for Traductor Jurado Ruso through commercial pages, content architecture, internal links, template performance and measurement.
Translation and sworn-document demand across informational, document and city-based journeys.
Google Search Console
Two Non-Overlapping 90-Day Periods
Previous: 2026-01-13 to 2026-04-12 · Current: 2026-04-13 to 2026-07-11
1,525
Clicks
Previous period: 658 → Current period: 1,525 +131.8%
250,675
Impressions
Previous period: 102,001 → Current period: 250,675 +145.8%
8.85
Average position
Previous period: 10.38 → Current period: 8.85 Improved by 1.54
0.61%
CTR
Previous period: 0.65% → Current period: 0.61% −0.04 percentage points
Google Search Console measures search visibility and clicks, not leads or revenue. The result reflects combined content, commercial-page, internal-linking, technical and measurement work and does not attribute growth to a single change.
Context
A Multilingual Service With Mixed Search Journeys
The site serves clients across Spain in Russian, Spanish and English. Search demand ranges from broad legalisation and document questions to sworn-translation services and city-specific commercial needs.
Constraint
Visibility Needed Better Commercial Routing
Informational pages created reach, while commercial pages showed uneven visibility and needed clearer routing. The project needed stronger landing pages, internal paths, crawl coverage, template performance and clearer measurement.
Work completed
Five Connected SEO Workstreams
Commercial landing pages
Document, legalisation, sworn-translation and city demand mapped to focused service pages.
Multilingual content architecture
Russian, Spanish and English coverage connected informational subintents to relevant services.
Internal linking
Blog visibility routed toward commercial hubs and supporting document pages.
Template performance
Layout work improved the mobile performance baseline before production QA.
Crawl and measurement
Sitemaps, indexation signals, page visibility and Search Console trends were checked as one operating loop.
Page-level evidence
Growth Appeared Across Different Page Types
Valencia city page
41 → 99 clicks
1,129 → 2,320 impressions · position 12.85 → 8.84
Russian apostille page
34 → 51 clicks
2,127 → 3,771 impressions · position 7.21 → 6.91
Implementation evidence
A Faster Mobile Template Baseline
Test-environment measurements recorded the implementation change before release QA. These measurements support the technical workstream but are not presented as the sole cause of search growth.
- Mobile PageSpeed
- 64 → 90
- Mobile LCP
- 6.42s → 2.98s
- Mobile FCP
- 3.91s → 1.92s
Interpretation
What This Evidence Proves — and What It Does Not
Supported
- More Google Search clicks and impressions across the site.
- Improved aggregate average position.
- Growth across hub, city and document-related pages.
Not claimed
- No verified lead or revenue attribution.
- No guarantee that the same result applies to another site.
- No claim that one technical or content change caused the outcome.
Reviewed 2026-07-14. Source: Google Search Console property https://traductor-jurado-ruso.com/. Query-level data may omit anonymized low-volume searches.
- Tools
- Google Search Console
- PageSpeed
Case Studies
- Healthcare
MedTech Marketplace: 10x Organic Growth
Led SEO for a healthcare platform managing 10+ diverse projects simultaneously. Built multi-domain/subfolder architecture with 5,000+ pages across medical verticals. Implemented automated content QA and technical audit pipelines.
+940%
Organic Traffic
- E-Commerce
E-Commerce: AI Content Pipeline at Scale
Deployed an LLM-assisted content workflow for a large product catalog. Automated content QA using Claude API, reduced manual production load, and built custom Python pipelines for metadata optimization.
+320%
Indexed Pages
Plan the next growth system
Need Evidence-Led SEO Work?
Start with the constraint, connect implementation to measurement, and document what changed.