Fix the crawl and indexation issues holding your Magento catalogue back from organic revenue in Australia

Magento layered navigation is the faceted filter system that lets shoppers narrow a category page by product attributes — colour, size, price, brand, material. For every filter combination a shopper can select, Magento generates a unique URL. An Australian homewares retailer with 10 filterable attributes across 100 categories can produce millions of crawlable filter pages. Most duplicate the parent category content. Google crawls them instead of your priority pages, wasting crawl budget and suppressing the rankings of pages that actually deserve to rank. The solution is a deliberate URL parameter strategy — blocking, canonicalising, or noindexing filter URLs based on their SEO value.

Duplicate content in Magento comes primarily from two sources: layered navigation filter URLs and the configurable/simple product relationship. For filter URLs, we implement a parameter-by-parameter strategy — block high-volume junk parameters via robots.txt, noindex low-value combinations, and canonicalise the remainder to the parent category. For configurable/simple products, we implement canonical tags on simple product URLs pointing to the parent configurable product, remove simple products from the sitemap, and in some cases apply noindex where simple product pages have no independent ranking value.

Magento 2 has significantly better default SEO capabilities — cleaner URL structures, improved canonical tag handling, better sitemap configuration, and a more performant architecture that makes Core Web Vitals compliance achievable. Magento 1 reached end-of-life in June 2020. For Australian retailers still on Magento 1, migration to Magento 2 or Adobe Commerce is both a security and SEO priority. A well-managed migration preserves — and often improves — organic search performance. A poorly managed one can cost 20–40% of organic traffic in the months following relaunch.

Both share the same core architecture and the same SEO challenges. Adobe Commerce adds enterprise features — B2B catalogue management, advanced content staging, Page Builder, and cloud-hosted infrastructure. For SEO, the most relevant difference is Adobe Commerce Cloud's preconfigured CDN and caching, which reduces the server-response performance gap that Open Source stores face on Australian hosting. The SEO work required is substantively the same on both editions.

A thorough Magento SEO audit of an Australian store with up to 5,000 SKUs takes 5–7 business days. Catalogues above 10,000 SKUs, or stores with complex layered navigation and multi-store configurations, require 10–14 days. Magento 1 migration audits take an additional 2–3 days for URL mapping and redirect strategy. We scope accurately upfront — you know what you are getting before work begins.

Magento SEO engagements for Australian retailers typically start from AUD 3,000–5,500 per month as an ongoing retainer, depending on catalogue size, whether the store is on Open Source or Adobe Commerce, and the number of active markets. Magento 1 migration SEO projects are scoped separately as a fixed-scope engagement. The best starting point is a search diagnostic — it identifies exactly what your store needs before any retainer commitment.

Seasonal SEO on Magento requires two things: content prepared and indexed before the season, and category page authority built over the preceding months. For EOFY (June), Boxing Day, and Click Frenzy, we identify the commercial keywords Australian shoppers use during those periods, ensure category pages targeting those terms are indexed and content-rich before the season, and monitor rankings and crawl health during the high-traffic period. Magento's sitemap and caching configuration also need to be stable under high traffic load — we check this as part of the pre-season audit.

Magento's multi-store and multi-website features allow separate storefronts for different regions — Australia, New Zealand, the UK, the US — each with their own URL, currency, and language settings. For SEO, this requires a correctly configured hreflang strategy across all storefronts: self-referencing tags, cross-referencing tags for all regional variants, and x-default handling. Without hreflang, Google may rank the wrong regional storefront for international searchers. We design and implement hreflang for every active Magento market.