Key Takeaways
- A 410 Gone tells Google a URL has been permanently removed — faster de-indexing than a 404
- Shopify doesn’t have a native 410 setting; most merchants use plain 404s which work fine
- Use a 301 redirect when a relevant replacement page exists — preserves link equity
- Use 410 (or let Shopify return 404) when you intentionally want the URL removed from search results
- Never redirect to an unrelated page to mask a deletion — it creates a soft 404
When you delete a product, page, or collection on Shopify, you have a decision to make: redirect the URL, let it return a 404, or signal to Google that the content is permanently gone. Most merchants only know about two of those options. The third — the 410 status code — is useful to understand even if you rarely use it directly.
What the 410 Status Code Means
HTTP status codes in the 400 range indicate that something went wrong with the request, from the client side. You’re probably familiar with:
- 404 Not Found: No page exists at this URL right now
- 410 Gone: This URL has been permanently removed and will not return
The practical difference is in how Google responds:
With a 404: Google records the URL as not found and may continue to check it periodically, in case the content returns. For URLs that were popular or well-linked, Google can take months to fully remove them from its index.
With a 410: Google treats this as a definitive signal that the content is gone forever. It de-indexes the URL faster — typically within days rather than weeks or months.
For most deletions on Shopify, this speed difference doesn’t matter much. But for URLs that were heavily crawled or well-indexed, a 410 can accelerate the clean-up of your index.
Does Shopify Support 410 Status Codes?
Shopify doesn’t have a native setting to return 410 for specific URLs. When you delete a page, Shopify returns 404 by default.
To return a 410, you’d need to use a custom app or a Shopify Function that intercepts requests to specific URLs and returns the correct status. This is a technical implementation that most merchants don’t need.
For practical purposes: a 404 on a deleted URL is fine. Google understands content gets removed. The 410 is a faster signal, but not a necessary one for typical Shopify use cases.
The decision that actually matters for SEO is not 404 vs 410 — it’s whether to redirect at all.
The Real Decision: Redirect vs Delete
When you delete content on Shopify, this is the question to ask:
Does a relevant replacement page exist?
If yes → Set up a 301 redirect to that page before deleting. If no → Let the URL return 404 (or 410 if you’ve set that up).
This is the entire decision tree for most cases. The reasoning behind it matters:
When to Redirect
A redirect makes sense when the URL has accumulated value — backlinks from other sites, internal links from your content, search rankings — and there’s a live page that would be a relevant replacement for people who find the old URL.
Examples:
- Discontinued product → redirect to the closest alternative or the parent collection
- Deleted blog post → redirect to a newer, more comprehensive version of the same topic
- Removed collection → redirect to the most relevant live collection
The redirect transfers most of the link equity from the old URL to the new one, and users land somewhere useful rather than a dead end.
When Not to Redirect
Redirecting makes sense only when there’s a genuinely relevant destination. Two things that are not valid redirect destinations:
Your homepage. Redirecting a specific product URL to your homepage creates a soft 404 — Google recognises the irrelevance and doesn’t transfer authority. The deleted product URL will still be treated as a broken URL, just more slowly. Redirecting 404s to your homepage is an SEO mistake, not a fix.
A vaguely related page. “Redirect to the general category page” is fine when no specific alternative exists. But redirecting a boots product to a bags collection just to avoid a 404 is not useful to users or search engines.
When there’s no relevant destination, an honest 404 is better than a misleading redirect.
The URL Had No Real Value
Not every deleted URL needs a redirect. A URL that was:
- Never indexed by Google
- Never linked to from anywhere
- A duplicate or near-duplicate of another page
…can simply be deleted. The 404 will be crawled once, recorded, and that’s the end of it.
What About Internal Links?
Here’s what redirects and 404s both miss: the internal links in your content that point to the deleted URL.
Whether you redirect or delete, any blog post or product description that links to /products/old-boots still contains that broken link. A redirect means users and Google end up in the right place — but the broken link itself still exists in your content.
Over time, stores that only add redirects without fixing source links accumulate:
- Redirect chains (old redirect points to another redirect)
- Unnecessary redirect load on the server
- Content that looks internally inconsistent to search engines
The clean approach is to update the link in the content itself. Change the blog post to point to the correct URL — then you may not even need a redirect (for internal links, at least).
Relink finds every internal link in your Shopify store that points to a broken or deleted URL. Instead of just managing redirects indefinitely, you can fix the source — update the blog post, the product description, the page — and keep your internal link structure clean.
Status Code Quick Reference
| Status | Meaning | Google behaviour | When to use on Shopify |
|---|---|---|---|
| 301 | Moved permanently | Transfers authority, updates index to new URL | Deleted content with a relevant replacement |
| 302 | Moved temporarily | Keeps authority at old URL, doesn’t update index | Temporary redirects only (A/B tests, seasonal) |
| 404 | Not found | Keeps URL in index for a while, eventually removes | Deleted content with no relevant replacement |
| 410 | Gone permanently | Fast de-indexing | Intentional permanent removal — rarely needed on Shopify |
| Soft 404 | Returns 200 but looks empty | Treats as missing, hard to detect | Never do this intentionally — avoid by not redirecting to irrelevant pages |