Software Development Blog

Visualsoft to Shopify URL redirects: a full SEO mapping playbook

At a glance

URL redirects are the single most important technical job in a Visualsoft to Shopify migration, and the easiest one to get wrong. Done properly, your search rankings stay where they are and customers with old bookmarks land where they expect to. Done as an afterthought, organic traffic can drop sharply in the weeks after launch and take months to recover. This guide walks through how Visualsoft and Shopify URLs differ, how we map them, and what to watch for on the way.

Why redirect mapping is the highest-stakes part of any migration

A 301 redirect tells search engines and browsers that a page has permanently moved to a new address. Every URL on your old store has potentially been earning trust with Google for years. Backlinks from other sites, organic rankings, and direct customer traffic all rely on those URLs continuing to resolve. If they 404 instead, that trust evaporates.

The damage from a poor redirect plan is rarely visible on launch day. It shows up two or three weeks later, when rankings start drifting, organic visits start dropping, and customer service starts fielding "your site is broken" emails because someone's bookmarked product page now returns an error. By the time it is obvious, recovery takes months.

The good news is that redirect mapping is a known, solvable problem. It just needs to be treated as a first-class part of the project rather than a tickbox at the end.

How Visualsoft URLs are structured

Visualsoft URLs follow a few recognisable patterns, and understanding them is the first step. The exact format varies by store and contract age, but most fall into these shapes:

• Product URLs. Typically include both a slug and an internal product ID, in formats like /p/product-name/12345 or /product/12345-product-name. The numeric ID is what Visualsoft uses internally, and it is often baked into the URL.
• Category URLs. Multi-level paths like /c/womens/dresses/midi/ reflect the category tree directly. Some stores have three or four levels of nesting.
• Brand pages. Usually under a separate path such as /brands/brand-name/, treated as a different entity from categories.
• Filtered category URLs. Faceted filter selections often appear as query strings, for example /c/dresses/?size=10&colour=red.
• CMS pages. Static content pages sometimes carry a file extension, such as /about-us.html or /delivery-info.html.
• Blog posts. Often sit under /blog/post-name, sometimes with a date in the path.
• Custom URL aliases. Visualsoft allows custom URLs to be set on individual pages, so some stores have non-standard one-off URLs that need to be hunted down.

The point is, Visualsoft URLs can carry a lot of variation. Crawling the whole site is the only reliable way to find every pattern in use.

How Shopify URLs are structured

Shopify takes a more opinionated approach. The URL patterns are fixed and not customisable, which surprises some merchants on first contact:

• Products. Always /products/product-handle, with no parent collection in the path.
• Collections. Always /collections/collection-handle, regardless of how the collection is structured internally.
• Pages. Always /pages/page-handle, no file extension.
• Blog posts. Always /blogs/blog-handle/post-handle, with the blog parent in the path.
• Filtered collections. Filters apply via query string parameters, not separate URLs.

This rigidity is sometimes frustrating, but it has an upside. Once you know the patterns, the mapping job becomes systematic.

The mapping job: typical Visualsoft to Shopify redirects

Most URL mappings follow predictable patterns. Here is a starting point we use as the baseline before customising for each store:

The mappings get more interesting at the edges, which is where most projects need real thought.

Filtered URLs and what to actually do with them

Faceted filter URLs are the part of any Visualsoft migration that needs the most pragmatic decision-making. Stores typically have thousands of these, generated by every combination of size, colour, price band, and brand filter. The honest truth is that most of them are not worth preserving as redirects, because the equivalent filtered view in Shopify uses query strings rather than indexed URLs.

The right approach is to identify the small subset of filtered URLs that genuinely have SEO value (typically the ones with backlinks or measurable organic traffic) and redirect those to the parent collection. Everything else either resolves naturally to the new collection page or is safe to let drop. Trying to map every filter combination is wasted effort and usually creates worse SEO than simply pointing them home.

Discovery: finding every URL that matters

The mapping table above is the easy part. The harder part is making sure no important URL gets missed. We pull URLs from five sources and reconcile them:

1. The Visualsoft sitemap. Usually at /sitemap.xml, this is the canonical list of URLs Visualsoft considers public.
2. A full Screaming Frog crawl. Catches URLs that are linked internally but not in the sitemap, including legacy pages and orphaned content.
3. Server access logs. Show every URL that has actually been requested in recent months, which often surfaces URLs nothing else knows about (old campaign landing pages, deprecated promo URLs, scraped feed endpoints).
4. Google Search Console. Lists every URL Google has indexed and every URL receiving organic traffic. This is the SEO-critical list.
5. A backlink tool (Ahrefs, Semrush, or Majestic). Identifies URLs with external links pointing to them. These are the URLs where a missed redirect costs the most.

Reconciling these five sources gives a master list. Every URL on that list either gets a redirect target, or gets a documented reason for not having one. Nothing gets left to chance.

Implementation in Shopify

Shopify handles redirects natively, but the implementation has quirks worth knowing:

• Bulk redirect import. Shopify admin accepts CSV uploads of redirects (URL Redirects under Online Store > Navigation). For most migrations this is the primary tool. Larger lists may need to be split across multiple imports.
• App-based redirect tools. For redirect lists running into tens of thousands, apps like Easy Redirects or Traffic Control offer better bulk handling and reporting.
• Theme-level handling for edge cases. A small number of redirects need conditional logic (for example, query string preservation for paid campaigns) and these are best handled in theme Liquid or via metafield-driven rules.
• No server-level redirects. Shopify does not expose .htaccess or equivalent, so every redirect lives in the platform itself. This means there is no way to do regex-based bulk rules, which is why upfront mapping matters.

Post-launch monitoring

Redirects are not a fire-and-forget job. The first six weeks after launch are when missed mappings surface, and the right monitoring catches them before they cost rankings:

• Search Console coverage report. Watch for "Not found (404)" entries climbing. Each one is either a missed redirect or a low-value URL that was correctly let drop. Triage weekly.
• Backlink reports. Run a fresh Ahrefs or Semrush crawl two weeks after launch and check that every backlinked URL still resolves to a live Shopify page.
• Top 50 rankings tracker. Set up rank tracking on your highest-value commercial keywords before launch. Day-one rankings should match pre-launch, and any drift in the first month gets investigated.
• 404 logs. Shopify's own 404 reporting plus a third-party tool (Plerdy, Hotjar, or a dedicated 404 monitoring app) catches user-facing breakage that search engines have not noticed yet.

Common mistakes that cost rankings

The same mistakes show up again and again in poorly executed migrations. Worth being explicit about each one:

• Redirecting everything to the homepage. The single fastest way to destroy SEO. Google treats homepage redirects as effectively a soft 404 and drops the ranking entirely. Every URL needs a relevant target, even if the relevance is "the parent collection" rather than "the exact equivalent page".
• Redirect chains. If URL A redirects to B which redirects to C, search engines pass less authority through each hop and may stop following entirely. The mapping job should always go straight to the final destination.
• Forgetting trailing slash variants. If /products/example/ and /products/example both have backlinks, both need to resolve. Shopify normalises these, but the source list needs both.
• Forgetting HTTPS and www variants. Especially relevant for older Visualsoft stores that may have been HTTP-only or used www inconsistently. Each variant of every URL needs verifying.
• Dropping query strings on URLs that need them. Paid campaigns, affiliate links, and email tracking often rely on query string parameters. Shopify preserves them by default on most redirect types, but it is worth verifying for high-value campaign URLs.
• Treating it as a launch task rather than a discovery task. The redirect map should be 80 percent complete before the new theme is even built. Leaving it to the final week guarantees missed URLs.

The specialist difference

A good Visualsoft to Shopify migration treats the redirect map as a deliverable in its own right, with its own discovery, testing, and sign-off. The mapping spreadsheet typically runs to thousands of rows, every row is justified, and post-launch monitoring is built into the project plan rather than added as an extra.

This is exactly the level of detail our migration process is designed around. Read more about how we handle Visualsoft to Shopify migrations, including SEO preservation as a first-class concern.

Key takeaways

• Redirect mapping is the highest-stakes part of any Visualsoft to Shopify migration, and the easiest to underdeliver on
• Visualsoft URL patterns are predictable, but every store has edge cases that only a full crawl will surface
• Filtered category URLs rarely need preserving, but the ones with backlinks absolutely do
• Discovery should pull from sitemap, crawl, server logs, Search Console, and backlink data, all reconciled into one master list
• Shopify implementation is straightforward, but it has no server-level fallback, so the mapping needs to be right before launch
• Post-launch monitoring catches what the mapping missed, and should run for at least six weeks after go-live

Considering a migration from Visualsoft to Shopify and worried about SEO? We have mapped tens of thousands of redirects across multiple Visualsoft migrations and treat URL preservation as a project-critical deliverable. Get in touch for a no-pressure conversation about your store.