From F&B to fintech, clinics to law firms, startups to enterprise. If your customers search on Google, we make sure they find you first, not your competitors.
One specialist team, focused only on the organic rankings that put you in front of ready-to-buy Singapore customers.
A clear, sequenced path from audit to rankings. You always know what we’re doing and why it matters for your leads.
Quick answer: The best ecommerce seo company for a catalogue is the one that scores highest on three axes: the shape of the team that will actually touch your store, demonstrable depth on your platform rather than familiarity with it, and reporting that attributes organic sessions to SGD revenue by landing page.
The basics of provider selection are well covered and not the point of this post. Assume you already know to ask for references, to make a provider look at your store before pricing, and to be sceptical of guaranteed rankings. This one goes underneath that layer, into the three things that actually determine whether a catalogue engagement performs and which almost never appear on a comparison checklist: who is on the team and in what ratio, whether platform experience is real or decorative, and whether the reporting can survive contact with your accounts. It ends with a weighted scorecard you can run across a shortlist. The framing is deliberately mechanical, because buying decisions made on rapport are the ones most often regretted at month nine. If you want to see what a catalogue scope looks like written out, our e-commerce SEO page is the comparison point.
Every provider in this market is articulate. That is the job. The consequence for a buyer is that the pitch stage compresses real differences into a narrow band of impressions, and the differences reappear in month four when the impressions have worn off.
A weighted scorecard forces you to decide what matters before you are influenced. Write the weights first, then meet people. If you cannot bring yourself to assign a weight to something, it was not a real criterion.
It also exposes the trade you are actually making. No provider is strong on every axis. An organisation with deep engineering capacity is usually less nimble on content production. A small senior team is faster and more expert per hour but has fewer hours. A larger agency covers more disciplines with more handoffs between them. These are genuine trade-offs with reasons behind them, not flaws, and a scorecard lets you choose the trade deliberately instead of discovering it.
Score on evidence, not on claims. Every row below has an evidence test attached. If a row cannot be evidenced, score it zero rather than average, because an unverifiable strength is not a strength you can plan around.
Most agencies will encourage you to weight chemistry heavily, and chemistry does matter for a two-year relationship. It is just not predictive of catalogue outcomes, and weighting it above 10 per cent is how buyers end up with pleasant quarters and flat revenue.
This is the axis with the largest effect on outcome and the least visibility during selection.
A catalogue engagement needs four capabilities, and they rarely sit in one person. Technical search capability that can read a crawl, write an index plan and specify template changes. Catalogue strategy that can read commercial data and make create, merge or filter decisions. Production capacity for category copy, product tiers and guides. And account capability that can hold the commercial argument and escalate when the developer queue stalls. Ask which named individual holds each, and how many other accounts each of them carries.
Account load is the number that predicts service quality. A senior technical lead spread across fifteen accounts is a reviewer, not a practitioner. Ask directly: how many stores does the person specifying my template changes currently work on, and what is the most they have carried. Anyone unwilling to answer has given you the answer. In our experience this is the question that reorders a shortlist most often, because it is the one nobody rehearses.
Watch for seniority decay. The senior people who scope the work are frequently not the ones who run it from month two. That is not inherently wrong, because senior time is expensive and junior execution under a good specification is fine. What matters is whether the handover is planned and documented, and whether the senior person stays on review at a stated frequency. Ask for the name of the person who will run month seven.
Establish where engineering sits. Three arrangements exist: the provider implements directly in your platform, the provider specifies and your developer implements, or the provider has its own development capacity that can be bought as a separate line. Each works. What kills timelines is when nobody decided, and the index plan sits unenforced for a quarter while two parties wait for each other.
Ask about the bus factor. If the person who knows your facet rules leaves, what survives? Documented index plans and template change logs survive. Knowledge held in one person’s head does not. Providers who document well will tell you so quickly, because it is expensive to build and they know it is a differentiator. We publish how our own engagements are structured on the about page for the same reason.
Specialisation is a deliberate trade, and you should ask about its shape either way. A practice concentrated on search buys depth in the decisions that only occur on catalogues; a broader agency buys coordination across channels under one contract. The right answer depends on whether your bottleneck this year is technical depth or channel coordination, and a provider who can articulate which one they are built for is telling you something useful.
Platform experience is the most claimed and least verified criterion in this market. Every provider has used your platform. Very few know what it does badly.
Test depth with constraint questions, not experience questions. Do not ask whether they work with your platform. Ask what your platform makes difficult for SEO and what the standard workaround is. Someone with real depth answers in under ten seconds and names something specific. Someone without will say the platform is fine and move to the next slide. Every platform has at least two irritating constraints, and knowing them in advance is the difference between a plan and a surprise.
Then test enforcement depth. For each of the following, ask how it is done on your specific build: controlling which filter combinations are crawlable, setting a canonical that differs from the platform default, changing a title pattern across a template, adding a field to product structured data, and generating a sitemap that excludes non-canonical URLs. These five cover most of what an index plan requires. On some platforms three of them are settings and two are code. Knowing which is which for your build is exactly what you are paying for.
Migration history outweighs platform history. A provider who has moved a catalogue between platforms without losing traffic has been forced to understand URL mapping, redirect chains, template parity and index recovery at depth, because a migration punishes shallow knowledge immediately. If a replatform is even possible in the next eighteen months, weight this heavily.
Ask what they would refuse to do on your platform. A provider with depth will name something: a URL structure they would not attempt, an app or plugin they will not work around, a rendering approach they require. Refusals are evidence of experience. Unlimited flexibility is evidence of a sales conversation, and we have reviewed enough written submissions to say that this one item separates candidates faster than any other on the page.
Check whether they can read the platform’s data, not just its admin panel. Server log access, crawl stats, structured data validation and feed diagnostics behave very differently across hosted and self-hosted builds, and the provider’s method has to fit what your build actually exposes. This is the practical boundary between search advice and technical SEO capability, and it is worth establishing before the contract rather than in month three.
Ranking reports on a store are reports on an input. The axis that keeps an engagement honest is whether organic effort can be traced to money, and it is testable before you sign.
Require revenue by landing page, with entry page attribution. Last-click attribution on a store credits the final touch, which on a returning customer is frequently a branded search or a direct visit, and it systematically undervalues the category page that started the journey. Entry page revenue is the number that tells you which pages earn. Ask how they configure it and in which tool.
Ask what they do about the orders analytics cannot see. In Singapore this matters more than the global playbooks suggest. A meaningful share of orders on smaller stores arrive by WhatsApp, by phone, by bank transfer or PayNow after an enquiry, or through a sales rep for B2B accounts. If the reporting counts only completed online checkouts, whole categories can look unprofitable while quietly generating the pipeline. A provider with local catalogue experience raises this unprompted. The B2B version, where the order lands weeks later and offline, is the case we set out in our B2B e-commerce results write-up.
Ask how marketplace cannibalisation will be handled in the numbers. If a shopper finds you through organic search and then buys the same item on Shopee because it is a familiar checkout, your own site records a visit and no revenue. That is not a reporting failure, it is a real commercial effect, and a provider who pretends it does not exist will misread every quarter.
Insist on a frozen tracked set plus a separate additions list. Tracked keyword lists that quietly change composition between months are the oldest way to manufacture an improving trend.
Require indexation coverage and crawl allocation by template. Aggregate coverage is nearly meaningless on a catalogue. The useful statement sets the share of products indexed against the share of categories that are not, because a healthy product figure can hide missing categories. Where we have audited stores whose reporting stopped at rankings, we found that nobody on either side could name the categories carrying the margin.
Test the reporting before you sign. Ask for a redacted sample report from a real store account of roughly your size. Not a template, an actual month, with the client details removed. What you are reading for is whether anything in it goes down, and whether there is a written argument rather than a summary. A report that explains a decline and states the fix is worth more than a report that never has one.
Run this across every provider on the shortlist. Score each row 0 to 5 on evidence only, multiply by the weight, and total.
| Criterion | Weight | What a 5 looks like | What a 0 looks like |
|---|---|---|---|
| Named technical lead and their account load | 15 | Named person, under roughly eight accounts, available on the call | No name, or load undisclosed |
| Month seven team named and handover documented | 10 | Named, with a stated senior review cadence | Pitch team only |
| Platform constraints named unprompted | 15 | Two or more specific constraints and standard workarounds | Platform described as fine |
| Enforcement path for the five index-plan actions | 10 | Says which are settings and which are code on your build | Generic assurance |
| Migration experience with a catalogue | 5 | A described migration with the URL mapping approach | None, or not raised |
| Revenue by landing page with entry attribution | 15 | Configured as standard, explains the model | Rankings and sessions only |
| Handling of offline, WhatsApp and PayNow orders | 5 | Raised unprompted with a measurement approach | Not considered |
| Marketplace effect acknowledged in the numbers | 5 | Treated as a real commercial effect | Ignored or promised away |
| Redacted real report supplied | 10 | Real month, contains a decline and an argument | Template deck |
| Documentation that survives staff change | 10 | Index plan and change log shown or described | Knowledge in one head |
Two rules make the scorecard work. Score zero for unevidenced claims rather than splitting the difference, and do the scoring within a day of each meeting rather than at the end of the process, because impressions decay unevenly and the last provider you saw will otherwise win. In our experience the ranking changes materially when buyers score immediately and then compare, and it changes again when the branding is removed from the written submissions.
Weight the rows for your situation before you use them. A store facing a replatform should move migration experience to 15 and drop content production weight. A store with a strong in-house writer should move production weight into technical and reporting. The weights above are a starting point for a mid-sized local catalogue, not a law. Where the totals sit close together, the pricing difference between providers becomes the tiebreak rather than the decision.
Score this separately, because it is the part buyers regret skipping.
You should own every account. Analytics property, Search Console, merchant centre, rank tracking project, and any tooling licences bought on your behalf, with the provider added as a user. Assets created under an agency account mean you lose every historical benchmark on the day you leave, which is a retention mechanic rather than an administrative detail.
Ask what the handover pack contains. A good answer is specific: index plan, architecture decision list, template change log, tracked set, open tickets, and the reasoning behind the last three significant decisions. A provider confident in the work will describe this easily.
Look at contract shape rather than length. Six to twelve months is a fair minimum because catalogue work compounds slowly and the first quarter is corrective. What matters is a defined review point, a notice period you can realistically use, and clarity on who retains the content and documentation.
Ask what month nine looks like. Front-loaded technical work runs out by design. A provider who can describe the later phase in concrete terms has a plan; one who cannot has a template. The way a catalogue scope is meant to re-weight over time is set out on our e-commerce SEO services in Singapore page.
The highest score in the abstract is not always the right hire. Segment first.
Catalogue under about 150 products on a hosted platform. Your constraints are differentiation, category structure and local visibility rather than crawl mechanics. A strong generalist with retail experience can serve this well, and the work looks much closer to small business SEO than to enterprise catalogue engineering.
Two hundred to a few thousand products. The classic catalogue case and where the three axes above discriminate most sharply. Weight technical lead account load and reporting heavily, because this is the band with the widest quality variance in the local market.
Above ten thousand products, or a headless build. The comparison shifts from deliverables to engineering collaboration. Team composition and enforcement path become the dominant rows, and content production weight falls.
Mid-replatform or replatforming within a year. Hire for migration specifically. The migration is the whole risk, and ongoing retainer capability is a secondary question you can revisit after launch.
Majority of revenue through marketplaces. The first question is strategic: what can your own domain do that a marketplace cannot, and is that worth funding this year. A provider who frames the engagement around that gap rather than promising to outrank a marketplace on generic product queries is reading your business correctly.
Field notes: In our ecommerce case study, the three axes in this post are all visible in the work itself. The platform was named and its main constraint addressed first: on a WooCommerce store, three years of faceted navigation URLs had created thousands of duplicate pages, so robots.txt rules blocked 14 parameter combinations and product indexation moved from 34% to 79% by the end of Month 2. The technical work was specific, including Product schema on all 200+ product pages with custom overrides for edge cases. And the reporting tracked organic monthly revenue, which went from S$8,400 to S$28,600 over nine months, not just traffic. When you score a shortlist, look for submissions that can describe work at that level of detail about your own platform and catalogue.
Choosing the best ecommerce seo company is a scoring exercise, not a chemistry test, and three axes carry most of the predictive weight. Who touches your store and how thinly they are spread. Whether platform experience is deep enough to name constraints and enforcement paths. And whether the reporting ends in SGD attached to a landing page rather than in a ranking chart.
Write the weights before you meet anyone, score on evidence within a day of each meeting, and read the written submissions with the branding removed. Three weeks spent this way will tell you more than any amount of review-site reading, and it makes the decision defensible to whoever signs the invoice.
The position worth holding is that depth in the catalogue-specific decisions is what a premium buys. Index plans, variant strategy, template governance and revenue attribution are the places where outcomes are made or lost, and they reward a team that does this work often. If your bottleneck this year is genuinely merchandising or conversion rather than search, the honest scorecard will show it, and you will have saved yourself a retainer. Our e-commerce SEO results case study is written to show the baseline as well as the change, which is the shape you should demand from every provider you score.
Three things, in this order. The shape of the team that will actually run the account, which means named individuals and their account loads rather than a company headcount. Genuine platform depth, testable by asking what your platform does badly and how each index-plan action is enforced on your build. And reporting that attributes organic sessions to revenue by landing page. Everything else, including deck quality, responsiveness and office location, correlates far more weakly with catalogue outcomes than buyers expect.
Ask constraint questions rather than experience questions. What does this platform make difficult for SEO, and what is your standard workaround. Then walk through five specific actions on your build: controlling crawlable filter combinations, setting a non-default canonical, changing a title pattern across a template, extending product structured data, and generating a sitemap that excludes non-canonical URLs. A provider with depth will tell you which of those are settings and which are code within a minute. A provider without will describe the platform as flexible.
There is no universal number, but ask for it and treat the willingness to answer as part of the signal. As a working guide, a senior technical lead running specification and review across more than roughly eight to ten stores is functioning as a reviewer rather than a practitioner, which is fine if junior execution under a good specification is what you are buying and is being priced as such. What you want to avoid is paying senior rates for review time while assuming senior attention.
It depends on which bottleneck you have this year. A search-focused practice buys depth in the decisions that only occur on catalogues, such as facet policy, variant strategy and template governance. A broader agency buys coordination across search, paid media and creative under one contract, which is worth real money when those channels keep colliding. Diagnose your bottleneck honestly first. Buying breadth to solve a depth problem, or the reverse, is the most common mis-hire in this category.
Organic revenue and transactions by landing page with entry page attribution, indexation coverage segmented by template type, crawl allocation across URL patterns, ranking movement on a frozen tracked set with a separate additions list, and a written interpretation. Ask for a redacted real report from a comparable account, not a template. Read it for whether anything declines and whether the decline is explained. A report that never contains bad news is not reporting, it is selection.
Raise it during selection and make the provider answer it. Many smaller Singapore stores and most B2B catalogues take a meaningful share of orders outside the online checkout, through WhatsApp enquiries, phone calls, quotations or PayNow transfers after a conversation. If those are invisible in the reporting, categories that generate enquiries rather than direct checkouts will look unprofitable and get defunded. Workable approaches include enquiry tracking with source capture, offline conversion import, and unique contact routes per category.
Team composition matters, size is a proxy for it. Above roughly ten thousand products the work shifts towards systems: crawl shaping, log analysis, template governance and engineering collaboration. What you need is access to people who can write specifications a developer will accept and read data at that scale, which some small senior teams do better than large ones. Ask who would sit in a technical call with your engineers, and judge on that person rather than on the company headcount.
The index plan, the architecture decision list, the template change log, the frozen tracked set, any content produced, open tickets with context, and the reasoning behind the last three significant decisions. You should already own the analytics property, Search Console, merchant centre and rank tracking project, with the provider as a user. Confirm all of that in the contract rather than at the exit, because the moment you need it is the moment goodwill is lowest.
Yes, when the scope genuinely matches a smaller catalogue. Under about 150 products on a clean hosted platform, a smaller retainer spent on category differentiation, product tiering and local signals can outperform a larger one spent on crawl mechanics you do not need. The mistake is buying a low fee for a large catalogue, because facet policy, variant strategy and template work have a minimum viable hour count and a fee below it simply omits them.
Three to five weeks is realistic and enough. One week to write the weighted scorecard and the brief, two weeks for meetings and written submissions scored within a day of each, and one to two weeks for a short paid diagnostic if the top two are close. Faster than that and you are buying on impression. Much slower and the incumbent situation deteriorates while you deliberate, which quietly costs more than the difference between the candidates.
If you are scoring a shortlist and want a fourth data point, we will run a free initial review of your store and send back the three things we would prioritise, the platform constraints we would expect to hit, and how we would attribute revenue, all in writing. Score it against everyone else on the same rows. Get in touch with your store URL, product count and platform, and we will be specific about where the fit is strongest.
Natalie leads SEO strategy at Singapore SEO Agency, helping local and regional businesses build organic search programmes that drive qualified leads. She specialises in technical SEO and content-led authority building for Singapore SMEs.
Get a free SEO audit for your Singapore website — we'll show you exactly where you stand, what's holding you back, and what it would take to rank on page 1.
Get Your Free SEO Audit →
Google analytics consulting services for Singapore SMEs: what consultants do, indicative SGD costs, deliverables to demand and red flags. Buy the right scope.
Bounce rate in GA4 is not the old Universal Analytics number. Learn what it measures now, why old benchmarks fail and how to judge each page by its job.
Yoast SEO helps most when its site-wide settings are right. See which settings to choose, what the traffic lights really mean and the mistakes to avoid.
Which free keyword research tool should a Singapore clinic, firm, contractor or tutor use? Combine five free tools to find your first 30-50 keywords. See how.
SEO vs SEM is usually the wrong question. Learn what the terms really mean and how to use ads and Search Console data to decide which searches to earn or buy.
Google Search Console login problems usually start with verification and ownership. Learn how to get in, fix access errors and offboard agencies safely.
Fast, no obligation. We reply within 24 hrs.
Singapore’s specialist SEO agency for SMEs. We rank your business on Google — and only Google. No distractions, just results.
© 2026 Singapore SEO Agency. All rights reserved.