Home goods e-commerce / Technical SEO + content recovery
NordHaus
Recover visibility with a backlog engineering could actually deliver.
Recovery under engineering constraints
March–November 2025 · Project-owner operating record
01 / The assignment
Project facts
- Period
- March–November 2025
- Primary recovery
- March–September 2025
- Retainer
- ~$2,791 / month
- Owner workload
- 12–15 hours / week
- Markets
- Poland + Germany
- Catalog
- ~4,200 SKUs
Starting point & challenge
During the six-week period surrounding the March 2025 Google Core Update, monthly organic visits declined from 148K to 81K, approximately 45%. Organic revenue fell approximately 38%.
The decline occurred during that period and correlated with the update. This does not establish that the update caused the decline. The audit focused on weaknesses that may have increased the site’s vulnerability.
02 / Responsibility
Owned, delegated, client-side
Project owner
SEO strategy and project leadership. The lead does not speak Polish; the working language was English.
Tomasz · client developer
Engineering implementation alongside other product priorities.
Magda · Polish copywriter
Polish content and native-language editorial review.
Jan · native German editor
German editorial review. All Polish and German content received native-language review.
03 / Work log
How the work unfolded
March–April 2025
Audit vulnerability, not an assumed algorithmic cause
Five competitors that maintained or improved visibility supplied the comparison set. The audit identified thin categories, critical content available only after JavaScript execution, excessive indexed filters, canonical problems, cannibalization and weak informational-to-commercial links.
Engineering capacity was constrained, so estimated commercial impact helped rank the SEO backlog rather than treating every audit item as equally urgent.
Recovery phase · March–September
Make important categories accessible and distinct
Critical category content moved to server rendering. Canonicals were corrected, most low-value filters received noindex and 12 commercially valuable facet pages stayed indexed with unique content. Performance work reduced reported LCP p75 from 4.3 to 2.2 seconds.
Reporting separated release dates from the later movement of field data. The record does not supply a device split or field-data export, so no additional Core Web Vitals claims are made.
Recovery phase · content consolidation
Replace volume with useful commercial information
Approximately 60 weak articles were consolidated into 12 substantial guides, with redirects for retired URLs. Twenty important category pages were reworked.
Generic “wide selection at low prices” copy gave way to fabric density, weave comparisons, care guidance and product-comparison tables. Approximately 300 support tickets supplied real questions for FAQ development.
During recovery · engineering constraint
Protect a minimum delivery rate
For approximately three weeks, product engineering was occupied by marketplace functionality. SEO implementation slowed. A minimum throughput agreement of two SEO tasks per week was introduced.
The backlog considered potential impact, cost, implementation difficulty and dependencies. Project leadership owned prioritization; implementation depended on the client developer’s available capacity.
September 2025
Recovery exceeds the former traffic baseline
Monthly organic traffic reached 253K against the April low of 81K and the former 148K baseline. The latter comparison is approximately 70.9% growth; it is not the growth percentage from the low. Indexation errors fell to 176.
October 20–November 2025
Black Friday: useful, but late
The Black Friday landing page was delayed by the engineering backlog and went live on October 20. It generated approximately 9,400 organic visits in its first three weeks.
This was a partial success. The page added organic traffic, but late deployment likely sacrificed some available demand. The amount of missed traffic or revenue cannot be quantified from this record.
04 / Operating infrastructure
What made the work repeatable
Ranked SEO backlog
Impact, cost, difficulty and dependency ranking; minimum delivery agreement of two tasks per week.
Indexation rules
Canonical fixes, low-value filter exclusion and 12 retained commercial facet pages.
Content and redirect inventory
Approximately 60 articles consolidated into 12 guides, retired-URL redirects and 20 reworked categories.
Native editorial review
English project coordination with Polish and German editorial review, rather than claiming the lead wrote in either language.
05 / The difficult part
Failures, constraints & corrections
A comparison-heavy category template failed
The new template was tested on three categories. Engagement decreased and average tracked ranking declined by approximately two positions. It was rolled back after one week and remained in monthly reporting. The short observation window does not prove that the template alone caused the ranking movement.
Engineering priorities delayed implementation
Marketplace work occupied the client team for approximately three weeks. The response was a minimum throughput agreement, not a claim that SEO controlled the engineering schedule.
Seasonal deployment came too late
October 20 was later than planned for the Black Friday page. Its 9,400 visits were not presented as proof that the timing was optimal.
06 / Reported outcomes
Before & after
Monthly organic visits
81K · April low
253K · September
Versus former 148K baseline
Approximately −45%
+70.9%
Indexation errors
1,940
176
LCP · p75
4.3 seconds
2.2 seconds
40 tracked clusters
Broad losses
3 categories top 3; 14 top 10
From this record to your scope
What would fit your business?
This historical engagement had its own team, budget and scope. Paid acquisition, CRM projects and technical SEO described in these records are not automatically included in today’s monthly publishing package. Past outcomes are not a forecast.
Explore managed social media operations · See the $399 monthly scope and exclusions · Review the material, approval and publishing process