A homeware brand in Bristol got in touch in the summer with a familiar complaint. She'd written sixteen blog posts over the previous year, category guides, gift guides, "best of" roundups, the full content calendar a course had told her to build. Organic traffic had barely moved. Meanwhile her product pages, the ones actually generating revenue, sat stuck ranking for nothing beyond her own brand name.
That's the question underneath technical seo vs content seo ecommerce uk, and it's the one most new store owners get backwards. They assume content is always the starting point because that's what blog-first SEO advice tells everyone. For an ecommerce catalogue, that's often exactly wrong.
There's no universal order. Diagnose first. Then sequence based on what's actually broken.
Why The Two Get Confused In The First Place
Technical SEO and content SEO solve different problems. Ecommerce advice online treats them as interchangeable because most of it is written by people who've only run blogs or SaaS sites, where the stakes and the fixes both look different.
Technical SEO asks a narrow question: can Google crawl, index, and understand your pages at all? Site speed, duplicate URLs from colour and size variants, broken canonical tags, thin or duplicate category pages. These are plumbing issues. Good writing can't fix a page Google can't properly index.
Content SEO asks a different question. Once a page is indexable, does it actually answer what the searcher wanted? Product copy that just lists specs. Category pages with two sentences above a product grid. Buying guides that don't exist yet. These are relevance gaps rather than visibility gaps, and the fixes for each look completely different.
A store can have brilliant content sitting on a technically broken foundation. It can also have flawless technical health with thin, generic copy that nothing ranks for. Work out which gap is costing you more right now, before you spend a weekend fixing the wrong one.
The Five-minute Technical Audit That Tells You Where To Start
Before writing a single word of content, run through this list. It takes under an hour and tells you which bucket your store falls into.
- Check your indexed page count against your actual catalogue. In Google Search Console, compare pages indexed to products listed. If you have 340 products and only 90 indexed pages, you have a technical problem, not a content problem.
- Search
site:yourdomain.comand scroll past page two. If you see dozens of near-identical URLs (the same product with different colour or size parameters), your faceted navigation is generating duplicate content that dilutes everything. - Run a free PageSpeed Insights check on three product pages. A Largest Contentful Paint over 4 seconds on mobile is a real ranking and conversion drag, not a cosmetic nitpick.
- Pull up any category page and count the words above the product grid. If it's a sentence or two of boilerplate, that's a content gap, not a technical one, and it's the kind of SEO work covered in Yellow Octo's technical and content SEO approach for store owners juggling both at once.
If the first three checks turn up problems, you have a technical priority. If indexing and speed look clean but category and product copy are thin, you're in content territory. Most stores have a bit of both. That's exactly where sequencing matters.
When To Fix Technical Issues First
Technical debt compounds differently to content gaps. A duplicate content problem from variant URLs won't sit still. It actively confuses Google about which version of a page deserves to rank, and the confusion grows as you add more product variants.
Fix technical issues first when any of these are true. Your indexed page count is badly out of step with your catalogue. Your site speed scores are genuinely poor, not just imperfect. You've recently migrated platforms and have a mess of old URLs still live without redirects.
The fixes themselves won't make a good case study. Canonical tags on variant URLs. A sensible robots.txt that stops Google crawling filtered and sorted versions of the same collection. Image compression. Redirect mapping for anything that's moved. Dull work, but it's the plumbing everything else depends on.
One caution worth naming here: technical fixes are also where DIY store owners do the most accidental damage. A badly configured canonical tag or an overzealous robots.txt rule can deindex pages you actually wanted ranked. If you're not confident reading a crawl report, this is the stage worth a second pair of eyes, even if you keep the content work in-house.
When Content Is Actually The Bottleneck
If your technical health checks out, more content won't help a crawl problem you don't have. It fixes something else entirely: pages that are indexable, yet have nothing worth ranking for.
Content is the priority when product pages read like manufacturer spec sheets. When category pages are a title and a grid, nothing more. When there's zero supporting content answering the questions buyers search before purchasing: sizing, materials, "is this suitable for", comparisons against competitors' products.
The highest-value content work for ecommerce tends to follow a set order. Category page introductions that actually describe the range and who it's for. One buying guide per major category. Rewritten product descriptions, starting with your twenty best-selling items rather than all three hundred at once.
Start where the revenue already sits. That's the kind of prioritisation ecommerce content SEO should be built around, rather than a blanket rewrite of the whole catalogue in one go. Our case studies walk through what that sequencing looked like for other founders once it had actually paid off.
A Worked Example With Real Numbers
Take the Bristol homeware brand mentioned earlier. Turnover around £680,000 a year, 340 SKUs, Shopify Plus, decent product photography already in place.
Her technical audit came back mostly clean, Core Web Vitals were fine, indexing matched her catalogue closely. The actual problem was content: category pages with a single sentence of boilerplate, and product descriptions copied almost verbatim from supplier spec sheets.
She spent six weeks rewriting her twelve category page introductions and the product copy for her forty best-selling items, plus two buying guides covering her two highest-traffic categories. No technical work was needed beyond fixing three broken canonical tags her Shopify theme update had introduced.
Organic sessions moved from roughly 1,100 a month to 2,400 over the following four months. The category pages and buying guides drove most of the long-tail growth. Her ad spend dropped by about £400 a month too, because paid traffic was now topping up organic sessions that were already converting on their own.
No agency retainer required. Just a correct diagnosis, made before a single hour of writing started.
A Simple Sequencing Framework
Run the audit, then follow this order rather than trying to do everything simultaneously.
First, fix anything actively blocking indexation: broken canonicals, accidental noindex tags, a robots.txt that's crawling the wrong things. This is urgent regardless of catalogue size, because nothing else matters if Google can't see the page.
Second, address site speed if it's genuinely poor rather than merely imperfect. A 2.8 second load time doesn't need weeks of engineering time diverted from content; a 7 second load time does.
Third, once the technical foundation is sound, move to content, starting with your highest-revenue category and product pages rather than the full catalogue. Expand outward as time allows.
Fourth, revisit technical health every quarter as you add products. Faceted navigation and variant URLs quietly regenerate duplicate content problems, even on a site that started out clean.
Skip straight to content on a technically broken site, and the writing gets wasted. Skip content entirely on a technically sound site, and ranking potential sits there untouched. Sequencing is what moves the needle here, more than the binary choice between the two camps. Worth comparing against how a small team weighs SEO against other channels before committing a quarter's hours to either direction, or reading about how agencies and generalist shops differ if you're weighing outside help at all.
Why This Trips Up More Stores Than It Should
The reason this mistake is so common comes down to an excess of the wrong kind of advice, rather than a shortage of it.
Most SEO content aimed at small business owners is written for a single-location service business, or a blog, where the content-first instinct is usually correct because there's rarely much technical complexity to begin with. One site, a handful of pages, no faceted navigation.
An ecommerce catalogue breaks that assumption completely. Even a modest 200-product store can generate thousands of crawlable URL variants once filters, sorting, and pagination parameters are factored in. A blog never faces that problem, so blog-first SEO advice never had to solve for it.
That mismatch is exactly why a generic course or template rarely fits an ecommerce store cleanly. The audit at the top of this piece exists because guessing which bucket you're in, based on advice written for a different kind of site, is how founders end up spending six months on the wrong half of the problem.
The 20-minute Version
If you only do one thing after reading this: open Search Console, compare your indexed pages to your product count, and run PageSpeed Insights on three product pages. That tells you, in under twenty minutes, which half of this framework your store actually needs first.
If the diagnosis points to a technical mess bigger than a free afternoon can fix, or you'd rather have someone map the sequencing properly before you spend six weeks writing in the wrong direction, you can book a free 30-minute call and we'll tell you honestly which bucket your store falls into.