Scaling jewelry: the Farida Gupta Shopify story

How it started

Growth had stalled at Farida Gupta. Ad costs were climbing, the jewelry category was getting more competitive, and every extra pound of traffic was landing on pages that had never been built to convert.

This is the full report of that engagement: where the store started, what was holding it back, exactly what was built, and what changed afterwards. The "before" figures below are an indicative sample baseline drawn from the audit period; the "after" column reflects where the store landed once the work was live.

Meet Farida Gupta

Farida Gupta is a jewelry retailer trading from United Kingdom at faridagupta.com. The brand has been selling since 2009 and reached me with a catalogue that had outgrown the storefront around it.

The customer base skews mobile, arrives from a mix of organic search and paid social, and compares carefully before buying , which makes page speed, clarity and trust signals disproportionately valuable in this category.

Before and after

The Before column is an indicative sample baseline captured during the audit period. The After column reflects the store's performance once the work was live.

The challenge

The audit surfaced five issues that between them explained most of the lost revenue. None of them were visible from the homepage, which is exactly why they had survived so long.

• Search and filtering that returned irrelevant results on large collections
• Paid traffic pointed at the homepage instead of intent-matched landing pages
• Mobile layout collapsed on key product templates, where most traffic landed
• Internationalisation handled by redirects, hurting both UX and indexation
• Abandoned cart flows either missing or firing at the wrong moment

The work, step by step

The engagement ran as a single programme rather than a list of tickets: fix the foundation first, then layer acquisition and retention on top of a store that can actually hold the traffic.

1. 01

   Technical audit and baseline

   Before touching a single template I benchmarked the store: Core Web Vitals, crawl health, funnel drop-off by device, app-script weight and revenue per session. Everything that followed was measured against that baseline.

2. 02

   Analytics and attribution rebuild

   GA4, server-side events and Shopify's own reporting were reconciled so every conversion is counted once. Dashboards were built around revenue per session, not vanity traffic.

3. 03

   Accessibility and QA pass

   Contrast, focus states, keyboard navigation and screen-reader labelling were corrected across templates, then the full purchase path was tested on real devices before release.

4. 04

   Theme rebuild on a clean foundation

   The theme was rebuilt around a lean section architecture. Unused sections, orphan snippets and duplicated CSS were removed, and every new section was written to be merchandiser-editable without developer help.

5. 05

   Technical SEO and structured data

   Canonicals, sitemaps, internal linking and metadata were corrected across templates, and Product, Breadcrumb, FAQ and Organization schema were added so search engines and AI assistants can read the catalogue accurately.

6. 06

   Checkout and payments optimisation

   Shipping rules were simplified and surfaced earlier, express wallets were enabled, and the checkout was stripped of every field that was not strictly required. Fewer surprises, fewer drop-offs.

7. 07

   App stack rationalisation

   Overlapping apps were removed and their functionality moved into native theme code where it made sense , lighter pages, lower monthly spend and fewer conflicts after Shopify updates.

8. 08

   Content and merchandising

   Titles, descriptions and buying guides were rewritten for both shoppers and search. Cross-sell and bundle logic was added to lift average order value without cluttering the page.

9. 09

   Search and filtering

   On-site search was tuned with synonyms, typo tolerance and merchandising rules, and faceted filters were added to the largest collections so deep catalogues stay browsable.

10. 10

    Internationalisation

    Markets, currencies and language routing were configured properly with hreflang, so each region has an indexable storefront rather than a redirect.

11. 11

    Paid traffic alignment

    Campaign traffic was redirected from the homepage to intent-matched landing pages and feeds were cleaned so Shopping and Performance Max served accurate titles, pricing and availability.

How the project ran

The results

The takeaway

Farida Gupta did not need a bigger budget. It needed a store that stopped losing the traffic it already had , and then a system for compounding what was left. That order matters, and it is the same order I would apply to your store.