Shopify myshopify.com URLs appear in search results
Check Shopify's primary domain, redirects, market paths, and canonical output when old myshopify.com URLs keep appearing for your storefront.
By Crawlito · 5 min read
In short
- Shopify's primary domain determines the main address shown for the online store.
- Changing the primary domain can also change market subfolder URLs.
- A current redirect and canonical response can be verified before search results refresh.
On this page
- Identify the exact storefront URL in the result
- Verify the primary domain and connected domains
- Trace redirects for a real product
- Inspect canonical and outgoing references
- Verify markets and customer journeys
- Check an app that generates absolute links
- Frequently asked questions
- Check the final storefront URL
If search displays your store's myshopify.com address after you connected a custom domain, inspect Shopify's primary domain and fetch the old product URL through to its final destination. Check the canonical on the resulting page and the links your theme or apps publish. Shopify documents redirecting other connected domains to the online store's primary domain. Shopify’s primary-domain guidance
Identify the exact storefront URL in the result
Copy the full result URL, including product path, locale prefix, and query parameters. A screenshot showing only the hostname can hide a redirect or an old market path. Open the link as a new visitor and record the final address and product selection.
Distinguish the public online-store domain from administrative or account-related URLs. A merchant may still use the original store identity for platform access or integrations while customers browse a custom domain. Investigate the particular public result instead of assuming every occurrence of the original hostname is an error.
Choose a small sample with the homepage, a product, a collection, and a localized route if your store uses markets. A homepage that redirects correctly does not prove that deep links preserve their paths. Include an old product handle if the catalog has recently changed, since a domain redirect and a product redirect may both be involved.
Verify the primary domain and connected domains
Open the store's current domain settings and identify the primary domain for the online-store target. Check that the custom domain is connected and ready for its intended use. If a change is needed, follow Shopify's supported domain workflow with the person responsible for the store and domain configuration.
At the time of writing, Shopify's guidance says a primary-domain change redirects other connected domains to the new primary and changes market subfolder URLs based on that primary domain. Record those market paths before a planned change. A French Canadian route, for example, may keep its subfolder while gaining a different host.
Avoid inferring the setting solely from a theme link or browser bookmark. A theme can hardcode the custom domain even while the platform's primary domain remains different. Conversely, a correctly configured primary domain can coexist with old hardcoded links in an app. The configuration and the emitted page output both deserve inspection.
The Shopify readiness guide covers the surrounding storefront checks. Here the focus is the public host relationship and the route a visitor follows from an old address.
Trace redirects for a real product
Capture the old URL's initial response, then follow its chain to the final page. Keep the exact product path rather than testing only the homepage. Verify the final product name or SKU so a success status from a generic fallback does not pass unnoticed.
curl -sS -D old-domain-headers.txt -o /dev/null https://example-store.myshopify.com/products/field-kit
curl -sSL -D storefront-chain.txt -o product.html https://example-store.myshopify.com/products/field-kitCheck for loops involving www, the bare custom domain, HTTPS, or a locale redirect. If the chain changes the selected variant or market, document where that happens. A link can reach a visually similar product page while losing the configuration the search result described.
For an older product handle, confirm the final replacement is relevant. A domain change should not accidentally send every missing product to the homepage. The redirect testing guide explains how to record each hop and distinguish a route repair from a generic success response.
Inspect canonical and outgoing references
Read the canonical link on the final product page and compare it with the intended public address. A theme or app may emit a duplicate canonical using a hardcoded domain. Find all canonical entries and identify the component generating each. Correct the owning template or configuration rather than appending another competing tag.
Inspect structured product URLs, social metadata, feed links, and important internal navigation. A store can redirect old addresses correctly while continually distributing them in product cards or marketing widgets. Update sources you control so new readers follow the maintained destination directly.
| Reference | What to compare |
|---|---|
| Product canonical | Current intended product URL |
| Collection card | Final public product destination |
| Structured Offer URL | Correct product and market |
| Sitemap entry | Maintained canonical address |
| Market selector | Equivalent product in the selected market |
The canonical guide helps assess conflicts among these signals. Keep product variants and market rules in context; several URL forms may have deliberate roles within the storefront.
Verify markets and customer journeys
Test a direct visit to each important market path without a saved country or language preference. Record the final domain, selected market, currency, product availability, and canonical. An old market link should lead to an understandable equivalent or a clear supported fallback.
Follow a product link from a collection and from a publicly available marketing page. Compare those routes with the old search-result URL. If one still uses the old host, locate the stored link in the app, content field, or template that supplies it. A broad database replacement can alter unrelated integration identifiers, so use the owning system's supported settings.
Check the custom domain's HTTPS behavior and public reachability after the change. A browser with cached redirects can hide a problem encountered by a new visitor. The domain migration guide provides a way to track the old and new addresses as distinct observations.
Record the release date and the current response chain. Search results can continue displaying an earlier address while the live route already redirects correctly. Use the appropriate verified Search Console properties and indexed URL details to follow the search state. The existence of an old result alone does not tell you whether today's storefront configuration is still wrong.
Keep the tested URL matrix with the store's operational notes. Domain changes often involve marketing links, market configuration, app-generated metadata, and catalog routes maintained by different people. A shared sample makes future regressions much easier to reproduce.
Check an app that generates absolute links
Choose a public widget such as a product recommendation or comparison table maintained by an installed app. Copy one of its product links and compare it with the same product's native theme link. An app can retain the original storefront host in its own configuration after Shopify's primary-domain setting changes.
Find the supported domain setting or refresh process for that app and test a newly generated widget after correction. A hand-edited existing link can hide the problem until the next widget refresh. Include a localized product when the app supports markets, since a corrected host can still lose the market prefix.
Inspect the app's structured output too if it emits product data. The visible link, offer URL, and image references may be built by separate routines. Record which values changed and verify the resulting product page through a fresh request from the widget itself.
Frequently asked questions
Should I remove the original myshopify.com identity?
Follow Shopify's domain model and supported settings. The public redirect behavior is the part to verify for an old storefront result.
Why does the custom domain work while search shows the old one?
Compare the current redirect and canonical with the indexed observation date. A stale result and an active configuration fault require different evidence.
Can changing the primary domain affect localized links?
Shopify documents that market subfolders based on the primary domain change their host with it. Test representative market URLs and their final product selection.
Check the final storefront URL
Run the free page check on a representative product at the custom domain. Pair it with the old-domain redirect trace to verify the complete public journey.
Filed under Platform guides. Topics: shopify, canonical, redirects, domains