The team was not short of ideas. They were short of a diagnosis telling them which of three overlapping problems was causing the other two.
What the client was dealing with
An established edible oil company had a site that was slow, poorly structured and not ranking. Each of those three was being blamed for the others, and no one had established the causal order.
Slow pages were suppressing crawl efficiency and engagement. Poor structure meant category pages competed with each other. Thin content was the symptom that got the most attention and mattered least at that point.
How the engagement ran
01 Discover
Opened with a working call involving the marketing head and the people who owned the site day to day, then pulled the analytics, search and technical baseline.
02 Diagnose
Established the causal order: performance first, information architecture second, content third. Reversing that order is why previous attempts had not moved anything.
03 Design
Within two working days our lead was on site with a written strategy and execution roadmap agreed with their team rather than presented to it.
04 Deliver
Rebuilt the site, resolved the technical debt, restructured categories and ran content work against the corrected architecture.
05 Develop
Set a standing operating rhythm: weekly meetings and written status reports, so leadership could see progress without chasing it.
06 Demonstrate
Reported against the agreed baseline monthly, which is what kept scope discipline when new requests arrived mid-build.
Engagement detail
| Field | Detail |
| Sector | FMCG · Consumer |
| Market | India, national |
| Duration | Six months |
| Services | Website rebuild, technical SEO, content, reporting cadence |
| Systems | GA4, Search Console, PageSpeed Insights |
| Handover | In-house team operating the content workflow |
A slow site is rarely just a slow site
If three problems are blamed for each other, the fix is a diagnosis, not a redesign.
Client anonymised at the client's request.
Related service: If your website is the bottleneck, see how we approach website design and development.
Frequently asked questions
What was wrong with the company’s website?
It was slow, poorly structured and not ranking, and each problem was being blamed for the others.
In what order should site problems be fixed?
Performance first, information architecture second and content third; reversing that order is why earlier attempts had not moved anything.
How was progress reported?
Through weekly meetings, written status reports and monthly reporting against an agreed baseline.
