Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

The WooCommerce Store Handbook: 29 Guides by Stage

An index to 29 guides on migrating, speeding up, indexing and selling cross-border on WooCommerce, organised by the order the problems arrive rather than by topic.

This is the index to everything we have written about running a WooCommerce store that sells across borders. Twenty-nine guides, organised by the stage of the problem rather than by topic, because that is how the decisions arrive.

If you are starting from a specific symptom — a slow store, a migration that lost traffic, a checkout that declines cards — skip to the stage that matches. If you are planning a store, read in order.

Stage 1: moving platforms

Migrations are the highest-risk change a store makes, and the failures are predictable. Almost none of them happen during the import; they surface weeks later, in search visibility, in stock discrepancies, in customers who cannot log in.

Start with the mechanics: migrating SKUs, variants and URLs from OpenCart, which covers why options and variations behave differently and why a redirect map is not optional.

If the source is Shopify rather than OpenCart, what migrates and what does not sets expectations honestly, including what cannot be transferred at all.

Before touching the export, run the catalogue cleanup. Deleting zombie SKUs, duplicates and orphan images before export is a day of decisions; the same work after launch is weeks of firefighting.

Then the two data types that are always underestimated: product images — sizes, formats, alt text and the three systems that consume them invisibly — and customers and orders, where the question is not how to migrate but whether to.

Close the loop with the pre-launch checklist, then read recovering organic traffic after a migration in advance rather than after the drop.

Stage 2: the store is slow

Performance work fails when it starts with a plugin. It succeeds when it starts with a measurement.

Six measurements before you change anything separates server time from browser time, and identifies which of four page types is actually the problem. Most stores find their bottleneck in the first three steps.

If the conclusion is “a plugin”, finding the plugin that is slowing down your store gives you a method rather than a guess — and lists four pieces of conventional advice that waste time.

Then the two structural layers: images (four separate decisions, not one) and the four caching layers, including why checkout is never fixed by caching.

For measured user experience, Core Web Vitals on WooCommerce maps each metric to the template responsible. Three templates cause most failures.

Stage 3: the store is not being found

Technical SEO on a store is mostly about what you decide not to expose.

Product structured data covers the seven failures that break rich results, including the two that only appear on variable products and multilingual stores.

Category page SEO handles the commercial pages — pagination rules that keep products indexed, sorting parameters, and the internal links that actually move rankings.

Faceted navigation and index bloat is where a 900-product catalogue becomes 40,000 URLs, with a three-tier model and two rules that cut the count by an order of magnitude.

If indexing is slow or partial, crawl budget explains when it is genuinely your constraint and when it is a distraction — plus the tag, archive and historical URL problems that consume it.

Two essentials that break silently: hreflang reciprocity, where one missing annotation voids the set, and sitemap strategy, where the count comparison diagnoses most indexation problems in a minute.

Stage 4: selling across borders

This is where stores lose money in ways that do not appear in analytics.

Currency first: seven configuration mistakes in multi-currency checkout, starting with the difference between displaying a currency and settling in it.

Structure second: subdirectory, subdomain or country domain, framed as an operations decision rather than an SEO one.

Then payments — choosing gateways for cross-border sales, where decline rate matters more than published fees — and fulfilment: shipping, duties and the rules that quietly lose money, including volumetric weight and zones built from carrier costs rather than maps.

Compliance: EU VAT and OSS, covering the 10,000 EUR threshold and the per-line VAT storage that quarterly reporting depends on. And eight Merchant Center disapprovals, where the reported reason is rarely the real one.

If you serve wholesale buyers, B2B pricing covers the four models and why wholesale is not D2C with a discount role.

Stage 5: keeping it running

The unglamorous work that prevents certain bad days.

Backups are not recovery — RPO, RTO, the four ways backups fail, and the quarterly restore test that turns a hypothesis into a fact.

Security hardening covers the four ways stores actually get compromised, and the configuration that blocks them. None of it is sophisticated.

Choosing plugins gives six checks before installing anything, including the lock-in question most stores never ask.

Finally, what a maintenance contract should cover — written for both sides of the agreement, with the gaps where disputes start.

What the sequence implies

Three things follow from organising the work this way.

Order matters more than effort. Optimising a store that is about to be migrated wastes both. Fixing images on a store whose server takes 900ms to respond changes nothing measurable. The stages above are ordered by dependency, not by difficulty.

Most problems are decisions, not techniques. Whether to migrate customer accounts, whether to index a facet, whether to offer net terms — each is a business decision with a technical implementation. The articles are written to make the decision clear first.

The invisible work has the highest return. Redirect maps, restore tests, hreflang reciprocity, VAT stored per line. None of it demoes well, and all of it prevents failures that cost more than the work.

Where to start

If you are unsure which stage applies, two questions usually locate it:

  1. Has the store changed platform, theme or URL structure in the last twelve months? If yes, start at stage 1.
  2. Does a category page with a clear cache take longer than 500ms to return HTML? If yes, start at stage 2.

If neither applies and traffic is simply flat, the answer is usually content coverage and internal linking rather than a technical fix — which is a different conversation, and one worth having before commissioning development work.

The related service pages are WooCommerce development, OpenCart development and rescue, speed optimisation, technical SEO and site maintenance. If you would rather have the diagnosis done for you, start there; each of those begins with an assessment rather than a proposal.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote