A Shopify SEO agency makes sure search engines crawl and index the right pages of a store and match them to the right queries. Our work covers four areas: indexing and canonicals, the structure of collections and internal links, redirects whenever URLs move, and the markup for several languages and countries. We write copy where a collection page has to answer a buyer's question.
The work happens in the theme, in the Shopify settings and in Search Console. A finding ends as a change in code or URL structure that goes live on its own and carries a date. NICCOS has been a Shopify Plus Partner since April 2022 and holds 19 reviews with a 5.0 rating in the Shopify Partner Directory.
This page covers classic search. Being named in the answers of AI assistants is a separate discipline, described under Shopify GEO. What a store needs so that AI agents can buy from it is covered under agentic commerce.
After the project, Sphen.ai keeps catalogue fields and content in shape. The app is a joint product of getSichtbar and NICCOS. In the project we put structure, indexing and redirects in order. Sphen.ai then audits the product catalogue and storefront signals for gaps in search and AI visibility, drafts changes at field level and gives the evidence for each. Your team reviews and approves every change before it is applied and can revert it. Search Console and GA4 can be connected. The app is installed from the Shopify App Store. Our technologies and apps page describes what the app does.
You need three decisions: a subfolder or a separate domain per market, complete hreflang markup, and a fallback address for everyone else. The domain decision comes first because it affects every URL. Changing it after the content is written means redirecting the whole store a second time.
hreflang only works when every language version points to all the others and to itself. If one return link is missing, Google ignores the annotation. We avoid automatic redirects by IP address, because crawlers then see a single language version. A translated page also needs its own titles and collection copy written for how people search in that language.
Gusti Leder sells handmade leather goods across Europe and came from Shopware with a fragmented international setup. Shopify Markets now runs DACH, France, the UK and further European markets with local tax, currency and domain logic. We mapped all Shopware URLs and redirected them with 301s. The Gusti Leder case study reports more than 1,000 migrated products and a 45% higher conversion rate. Our page on Shopify internationalisation covers markets, currencies and domains.
Language versions multiply the work in a migration. Each version has its own URLs, and each of those URLs needs its own redirect target in the same language. A German product page that redirects to the English homepage loses its ranking in Germany.
Rankings hold when every old URL has a target with matching content before go-live, the redirects have been tested against staging, and someone works through the 404 errors after launch. No platform change comes with a guarantee, because Google evaluates the new store again. Our responsibility is that no address ends nowhere.
Kanela shows how large such a list can get. The Swiss online pharmacy moved from PrestaShop with more than 40,000 products. We analysed 337,891 product-category relationships and created 147,753 legacy URL mappings across four language versions. Every mapping was read back after import and checked against the actual state of the store. The figures are in the Kanela case study.
Mintkind combined migration, redesign and SEO protection in one project. The Hamburg label moved from Shopware 6 to Shopify Plus and went live 90 days after discovery with no downtime. A complete URL and redirect strategy protected the existing rankings, as the Mintkind case study describes.
If the move is still ahead of you, the migration audit checks beforehand where the risks are. The page on Shopify migration describes the full course of a platform change.
Shopify takes care of hosting, the sitemap and basic markup. Three things still need steering: duplicate product addresses, filter pages and the fixed URL structure.
A product is reachable under /products/ and also under the path of every collection it belongs to. Shopify sets a canonical to the main address, but many themes link internally to the address with the collection path. Google then receives two signals that contradict each other. We switch internal links to the main address.
Filters and sort orders create parameter URLs without limit. We decide per combination. Where search demand exists, the combination becomes a collection of its own with its own content. Where none exists, it stays out of the index. The paths /products/, /collections/ and /pages/ cannot be changed, which is no disadvantage as long as every old address points to its new counterpart. Load time belongs to the technical basis as well and is covered under Shopify performance.
Technical SEO achieves little while the platform decision is open. You would be working on a structure that no longer exists after the move. It also achieves little when visitors already arrive and do not buy. In that case we start with conversion optimisation.
We tell you in the first conversation if search demand in your range is too small to justify the effort. The basis is your own Search Console data and not estimates from a tool.
We run our own crawl against the sitemap and the indexing report and establish which pages Google knows, which it ignores and which it never reaches.
URLs change with every platform move. We build the redirect list in full, test it before go-live and work through 404 errors afterwards.
Domains or subfolders, hreflang and a fallback address are set up so that each market sees the version written for it.
Shopify also serves products under the collection path. If the theme links to that address, two URLs compete for the same page.
Filter parameters create any number of combinations. Once indexed, they spread crawling across variants nobody searches for.
If page 2 and the following pages of a collection are not linked, products further down are crawled rarely or not at all.
Redirected, delisted or noindexed URLs in the sitemap send contradictory signals and make troubleshooting harder.
Every page gets a canonical URL that points to itself. Internal links use this address only.
Filter combinations with search demand become collections of their own. All others stay out of the index.
Collections, pagination and internal links are built so that every product can be reached from the homepage in a few clicks.
200, 301, 404 and 410 are assigned deliberately. We resolve redirect chains and empty pages that still report 200.
On a fixed date we save impressions, clicks and positions per URL group from Search Console. Without this value no effect can be proven later.
Our own crawl is set against the sitemap and the indexing report. This shows which pages Google knows and which it never reaches.
Every finding is weighted by the share of revenue affected and the search demand available. The page types your business depends on come first.
Changes are built in a copy of the theme and go live one at a time with a date. Bundled changes cannot be told apart later.
After the recrawl we set the values per URL group against the baseline. That decides what goes into the next round.
Countries run through subfolders or separate domains. The decision is made before content work starts.
Every language version points to all the others and to itself. A missing return link makes the annotation ineffective.
A fallback address catches visitors whose language or country is not covered.
Forced redirects by location stop crawlers from seeing every language version.
You are adding a market
A new country or language is coming, and domains, hreflang and translated collections have to be decided before launch.
A relaunch is coming
As soon as URL structure, theme or platform change, the preparation decides whether your visibility survives the move.
The range grows, the index does not
You keep adding products and collections, but the number of indexed pages in Search Console stays flat or falls.
Search Console reports exclusions
Messages such as “Discovered, currently not indexed” affect whole page types in your store and not single pages.
The platform decision is open
As long as it is undecided whether and where you migrate, work on a structure that will not exist afterwards does not pay off.
To the migration auditYour pages load too slowly
If your mobile field data is in the red, load time is the more urgent problem.
To Shopify performanceVisitors arrive but do not buy
If your collection and product pages already have visitors who do not buy, more visibility mainly brings more bounces.
To CRO & conversion optimisationYou need a diagnosis first, want to secure a move, or are looking for ongoing support. That gives three shapes of collaboration.
For stores that should rank and do not, while nobody on the team can name the cause.
Ends with a prioritised list of measures your team can work through without us.
For relaunches and platform changes where revenue depends on the existing visibility.
Ends when the URL groups that carry revenue are stable again after the recrawl.
For stores with a changing range, where collections and content are added or removed all the time.
Results in visibility that survives a theme update or a change of range.
Every figure appears in the case study, where you can verify it.
Groundies, MYCR7 and Gusti Leder are three of thirteen projects we have published with starting point, delivery and result.
We look at Search Console, indexing and URL structure and tell you which change comes first.
NICCOS
The page could not be loaded.
Please reload the page. If an update has just gone live, this will load the latest version.
