Ecommerce SEO Company: How to Pick One for Your Catalogue

Quick answer: Judge an ecommerce seo company on catalogue evidence rather than general SEO credentials. Ask how they handle faceted navigation, variants and out-of-stock URLs on your platform, insist on seeing a store crawl before pricing, and check whether their reporting ties organic sessions to revenue rather than rankings.

Search optimisation for a shop is a different job from search optimisation for a website, and a provider can be genuinely excellent at the second while having no method at all for the first. The problem for a buyer is that this gap is invisible in a pitch. Every proposal contains the same nine phrases, and the language used to describe a catalogue engagement is identical to the language used for a brochure site. What this post gives you is a set of questions that cannot be answered convincingly by someone who has never worked on a catalogue, plus the platform-specific realities that determine how much of the work is even possible. We read a lot of competitor proposals during SEO audit and consulting engagements, and the tells are consistent enough to write down.

What Actually Separates a Catalogue Provider From a General One

Start by accepting that most of the SEO craft is transferable. Nobody needs a specialist to write a title tag. Specialisation earns its premium on a narrow set of decisions that only occur on stores, and those decisions are where money is made or lost.

The first is a facet policy. Does the provider have a repeatable method for deciding which filtered URLs are indexed, which are canonicalised, and which are blocked from crawling? A general provider will either apply one blanket rule or not raise the subject at all. Ask them to describe the rule they would apply to a brand filter versus a price filter, and listen for whether the answer distinguishes between them at all.

The second is variant handling. Colour, size and bundle variants are a URL strategy decision with revenue attached. The right answer depends on whether people search for the variant, which means the provider has to have looked at demand before answering. Anyone who gives you a confident universal rule in the first thirty seconds has not.

The third is stock lifecycle. Ask what happens to a URL when an item sells out, and what happens when it is discontinued. There are four distinct scenarios and each has a different correct handling. A provider who treats them as one question has not run a catalogue through a full year.

The fourth is revenue attribution. Can they tie organic sessions to transactions by landing page, and do they report that way by default? In our experience this is the line that predicts whether an engagement stays honest, because a provider reporting revenue cannot hide a quarter behind rising impressions. Reporting rankings on a store is reporting an input. Most agencies will report visibility because it moves earlier and more pleasantly than revenue does.

The fifth is feed and marketplace awareness. Your product feed and your organic listings share data. A provider who has never looked at a merchant feed will miss price and availability mismatches that cost you rich results.

Platform Experience: Which Parts Genuinely Matter

Platform experience is oversold and under-specified. What matters is not whether someone has used your platform, it is whether they know the specific constraints that platform imposes on the work you need doing.

The question that separates real platform experience from a logo on a slide is about limitations. Ask what your platform cannot do well for SEO. Someone who has genuinely worked on it will answer immediately and specifically. Someone who has not will say the platform is fine and move on. Every platform has at least two irritating constraints, and knowing them in advance is what stops a project from stalling in month three.

Watch for the implementation boundary. On a hosted platform a competent provider can usually implement most changes directly. On a self-hosted store they may need plugin access, and on a custom build they will almost always be writing tickets for your developer. That is a legitimate way to work, but it means your timeline is your developer’s queue rather than the agency’s, and it should be written into the proposal rather than discovered later. Our own technical SEO scope states who is pushing changes for exactly this reason.

Migration history is worth more than platform history. A provider who has taken a catalogue from one platform to another without losing traffic has been forced to understand URL mapping, redirect logic and index recovery at depth. If you are considering a replatform in the next year, this is the single most valuable line on their record.

Nine Questions That Expose Whether They Have Done Catalogue Work

Use these in the first call. They are unpleasant to answer from a script.

1. What proportion of our URLs would you expect to remove from the index, and how would you decide? A catalogue answer includes a range and a method. A general answer talks about adding content.

2. Which of our filters would you index, and why those? They should ask to see the site before answering. If they answer without looking, that is the answer.

3. What is your rule for a product that is temporarily out of stock versus discontinued? Four scenarios, four handlings.

4. How would you report on this engagement? Look for revenue by landing page, indexation coverage by template type, and crawl allocation. Rankings should appear, but not lead.

5. What would you do about our marketplace listings? A provider with local experience will treat this as a strategic question about where to compete rather than a threat to eliminate.

6. What do you need from our developer, and how often? This exposes whether they implement or advise.

7. Which of our product pages would you not touch? Prioritisation by revenue is the correct answer. Anyone proposing to rewrite the entire catalogue is either quoting for something you cannot afford or is not thinking.

8. How do you handle seasonal ranges? Keeping URLs live across cycles rather than deleting and recreating them is a small answer that reveals a long time horizon.

9. What will you do in month nine? Front-loaded technical work runs out. A provider who cannot describe the later phase has a template rather than a plan.

Ask for a store reference specifically, not a client reference. We have sat in enough handover calls to know that the portfolio slide and the delivered work are often different eras of the same company. Ask to speak to a store of roughly your catalogue size, and ask that reference what changed in month four rather than month one. Where we discuss our own work, the e-commerce SEO results case study is written to show the baseline as well as the change, and you should demand the same shape from everyone you speak to.

The Diagnostic Test: Make Them Look Before They Price

The single most useful filter costs you nothing. Send your store URL and ask for three observations before any proposal is written.

A provider who has done this work will come back with specifics within a day or two. They will have crawled you, or at least run a few queries, and they will name things: the number of indexable URLs against your product count, a category that is being outranked by your own filter page, a template-level title problem, a schema mismatch on price. None of that requires access to your analytics.

A provider who has not will come back with a scope and a price. The tell is not speed, it is specificity. A fast answer full of generic best practice is worse than a slow answer that names one real problem.

If the shortlist is close after that, pay two or three of them for a short diagnostic. Budget SGD 800 to SGD 2,000 each for a two-week catalogue diagnostic, scaled to your product count. Give every provider the identical brief: here is the store, here are the three ranges that matter commercially, tell us the three highest-impact changes and why, in four pages or fewer. Paid work is produced by the delivery team. Free work is produced by the sales function, and the difference shows.

Score the outputs with the branding removed if you can. Deck polish correlates poorly with the quality of thinking, and in our experience buyers reverse their preference surprisingly often once the logo comes off. What you are looking for is disagreement between the responses. Convergence tells you a problem is obvious. Divergence tells you where judgement lives, and the reasoning that survives your own scrutiny is the one to weight up.

Pricing in SGD and What Each Band Realistically Buys

These are market observations rather than a price list, and any provider can sit anywhere on the quality distribution within its band.

Below SGD 1,500 a month you are buying a package: reporting, light on-page work and possibly outsourced content. For a store under 200 products with a clean platform, that can be adequate. It will not fund facet work or a variant strategy.

SGD 2,000 to SGD 4,000 is where most Singapore store retainers sit. Expect technical correction in the first quarter, category work, a modest content volume and a named contact. The quality variance inside this band is the widest of any, which is exactly why the diagnostic test matters most here.

SGD 4,500 to SGD 9,000 should buy senior strategic input, implementation rather than recommendations alone, and work that extends into feeds, internal linking at template level and structured content production. If it does not, you are paying the band above for the band below.

Above SGD 9,000 you are into multi-market, large-catalogue or heavily technical engagements, and the comparison shifts from deliverables to team composition. Our pricing page exists so that this conversation starts from a number rather than circling one, and we would encourage you to ask every provider on your list for the same clarity.

Be sceptical of keyword-count pricing on a store, more than anywhere else. A catalogue does not rank by keyword, it ranks by template. Twenty terms priced as a package tells you nothing about whether the provider will touch your filter rules, your variants or your stock logic, and those are the things that decide the outcome. Price against scope, hours and named deliverables instead.

Look hard at the contract shape rather than its length. Six to twelve months is a fair minimum because this work compounds slowly, and we say so about our own engagements. What matters is whether there is a defined review point, a usable notice period, and clarity that you keep the content, the documentation and the accounts if you leave.

A good diagnostic connects findings to revenue rather than listing them. In our ecommerce case study, the initial audit of a WooCommerce home and lifestyle store did not stop at uncontrolled faceted navigation. It also showed that three years of short-form blog posts had zero internal links pointing to product or category pages, so the authority they earned was going nowhere commercial. That link between a technical fault and the pages that sell is what you are paying a provider to find in the first fortnight.

Red Flags Specific to Store Engagements

Some of these apply to any provider, including us, and you should test us on them too.

Guaranteed rankings on product terms. Nobody controls the results page, and product queries in particular are dominated by marketplaces whose position is not something a retainer can dislodge on schedule.

A proposal that leads with content volume. Twelve blog posts a month on a store with uncontrolled faceted navigation is spending your budget on the wrong layer entirely. Content matters, but sequencing matters more.

No mention of your platform’s constraints. If nothing in the document acknowledges what your setup makes difficult, the document was not written for your store.

Reporting built on metrics that cannot fall. Impressions, tracked keyword counts and visibility scores drift upward on their own as a catalogue ages. Insist that revenue or transactions appear.

Volume-priced link packages aimed at product pages. Links to individual product URLs are rarely the constraint on a store, and a fixed monthly number describes a supply chain rather than a strategy.

No negative anywhere in the proposal. If nothing in it tells you that something you are currently doing is wrong, you are reading a sales asset. The providers willing to risk a negative during a pitch should score higher, not lower.

When a Specialist Is the Wrong Answer

Segmentation is more useful here than a blanket recommendation, so here is the honest version.

If your catalogue is under about 100 products and your platform is hosted and clean, a generalist who understands local search may serve you better and cheaper than a catalogue specialist, because your bottleneck is likely to be local visibility and differentiation rather than crawl mechanics. Our small business SEO work is shaped for exactly that situation.

If your revenue is overwhelmingly from marketplaces and your own domain is a shopfront, the first question is whether an owned-channel strategy is worth funding at all this year. Sometimes the answer is no, and a provider who says so is worth remembering for when it becomes yes.

If you are mid-replatform, hire for migration experience specifically and treat ongoing retainer capability as secondary. The migration is the whole risk.

If you have an in-house marketer who publishes well but has no technical depth, a hybrid arrangement works: external specialist for audit, architecture and technical direction, internal team for production. That is a common and sensible shape for Singapore SMEs, and it usually costs less than a full retainer. You can see how we structure that split on our about page.

Field notes: In our B2B ecommerce case study, the scope for a wholesale kitchenware supplier in Ubi was led by catalogue architecture, not article volume. The single catalogue was rebuilt into 14 category pages with full specifications, minimum order quantities and lead times, plus 6 industry vertical pages, before and alongside 8 trade buyer content pieces. Over eight months, monthly trade enquiries from organic moved from 5 to 28. A proposal for your store should read the same way: if it leads with a monthly article count and never mentions filters, variants or stock handling, it has not looked at the catalogue.

Our Take

An ecommerce seo company is worth its premium only on the decisions that do not occur anywhere else: which URLs exist, which get indexed, what happens when stock moves, and how revenue is attributed back to templates. Everything else is ordinary SEO and can be bought from a wider pool.

Our clients with the largest catalogues get the clearest return from a specialist precisely on the four decisions that generalist SEO rarely touches: URL existence, indexation policy, stock-change handling and template-level revenue attribution.

So test for those decisions directly. Send the store, ask for three observations before pricing, ask the nine questions, and pay a short shortlist for parallel diagnostics. Three weeks and a few thousand SGD spent this way will tell you more than six months of reading review sites, and it removes the formatting advantage that well-designed proposals otherwise enjoy.

We are a search specialist rather than a full-service agency, which is a deliberate choice: catalogue work rewards depth in one discipline more than breadth across five. If your problem is genuinely a merchandising or conversion problem, we will say so rather than sell you a retainer. If you want to see how the scope looks when it is written for a store rather than a website, our e-commerce SEO services in Singapore page sets it out line by line.

Frequently Asked Questions

Do I need an e-commerce specialist or will a general SEO agency do?

It depends on your catalogue size and platform. Under roughly 100 products on a clean hosted platform, a strong generalist is often the better value, because your constraints are differentiation and local visibility rather than crawl mechanics. Above a few hundred products, or on a custom build, the specialist decisions around faceted navigation, variants and stock lifecycle start to dominate the outcome, and a provider without a method for those will spend your budget on the wrong layer.

How do I check whether a provider has genuinely done catalogue work?

Ask process questions that have no generic answer. What proportion of URLs would you deindex and how would you decide. Which of our filters would you index. What is your rule for a discontinued product with no replacement. What do you need from our developer and how often. A provider with real catalogue experience answers these quickly and specifically, and usually asks to look at the site before committing to any of them.

Should I pick a company that specialises in my platform?

Platform familiarity is useful but it is not the top criterion. What matters is whether they know your platform’s specific SEO constraints, which you can test by asking what it does badly. Migration experience is worth more than platform loyalty, because a provider who has moved a catalogue between platforms without losing traffic has had to understand URL mapping, redirects and index recovery properly.

How much should a Singapore online store budget monthly?

Most local store retainers sit between SGD 2,000 and SGD 4,000 a month. Stores under 200 products on a clean platform can see progress from around SGD 1,500. Catalogues above a few thousand products, or those needing implementation rather than recommendations, generally sit between SGD 4,500 and SGD 9,000. Below roughly SGD 1,200 there are not enough hours to cover technical work, category development and content at the same time.

Is it worth paying several providers for a trial diagnostic?

For retainers above roughly SGD 3,000 a month, usually yes. Budget SGD 800 to SGD 2,000 per provider for a focused two-week piece on your store. The total is roughly one month of retainer spent to avoid a twelve-month mistake, and paying changes what you receive, because unpaid pitch work is produced by the sales function rather than the people who would do the job.

What reporting should I insist on for a store?

Organic revenue and transactions segmented by landing page, indexation coverage broken out by template type, crawl allocation across URL patterns, and a written interpretation of anything unusual. Rankings can appear, but they should support the revenue picture rather than lead it. If your report is a dashboard export with no narrative, or the tracked keyword list changes quietly between months, you are being shown activity rather than progress.

Should the provider handle my product feed as well?

It is frequently excluded and should be clarified in writing. Feed quality and organic product data overlap heavily, since price, availability and identifiers are shared, and mismatches between the page and the feed cause rich result losses. Many providers treat feeds as a paid media task. Either arrangement is workable, but somebody needs to own it, and discovering in month four that nobody does is a common and avoidable outcome.

How long should the contract be?

Six to twelve months is a reasonable minimum, because catalogue work compounds slowly and the first quarter is usually corrective. The length matters less than the shape. Look for a defined review point, a notice period you can realistically use, and explicit confirmation that you retain the content, documentation, analytics properties and any tooling projects created during the engagement.

What if my store sells mainly through regional marketplaces?

Then the first question is strategic rather than technical: what can your own domain do that a marketplace cannot. Usually the answer involves considered or technical purchases, bundles, warranty and service, and buying guides that shorten a decision. A provider worth hiring will frame the work around that gap rather than promising to outrank a marketplace on generic product queries with the same supplier descriptions.

Can I run store SEO in-house instead?

Partly, and a hybrid is common in Singapore. An in-house marketer can own category copy, product differentiation and publishing effectively. The parts that are difficult to hold internally are facet policy, template-level technical decisions and migration risk, because they are occasional, high-consequence and easy to get wrong once. Many retailers buy external direction and audit while keeping production internal, which costs considerably less than a full retainer.