Why Wix Users need this
You renamed a page, moved your blog over from another platform, or switched domains, and now you are guessing whether the old addresses still land anywhere useful. On Wix that guess carries extra weight. One hands-on review found Wix server response slower than on some competing builders, so each extra hop in a redirect chain adds to a wait that may already start heavy. And any link you placed yourself, in a menu, a button or a custom JSON-LD block, still points at the old address until you change it. Cryptic image file names are another reminder that Wix decides some things for you, which makes the page URLs you do control worth getting right. The Redirect & HTTP Status Checker takes one old URL, follows it hop by hop, and shows the status code of every step plus the final address. Paste a /post/ link from your old blog, a renamed service page, or the plain http version of your domain, and read what a crawler would see.
Wix Users specific guidance
Pick the old URLs worth testing first
Open your Wix dashboard, go to the SEO tools and open the URL Redirect Manager (menu names shift with dashboard updates), then copy the old paths you entered there. Test the full address one URL at a time, for example https://www.yourdomain.com/old-services/web-design. Start with the ten addresses that had real links or bookmarks: your best blog posts under /post/, renamed service pages and the bare http version of the homepage. A URL typed without a scheme is tested as http://, so the HTTP to HTTPS step shows up as well. The result proves what the server answers right now for that exact address. It does not prove the rule is saved the way you intended inside the manager, because the tool only reports the answer and does not read Wix settings.
Read the Final URL before the status code
Compare the Final URL with the page you meant to send people to; the tool cannot judge whether a destination is the right one, so that comparison is yours. Then read the Chain Checks: Final status is 200 OK, Short redirect chain (≤2 hops) and Final URL uses HTTPS. Redirect Path labels each hop as 301 permanent, 302 temporary, 307 temporary or 308 permanent. For a page you moved for good, expect permanent labels all the way. A clean 200 does not prove Google has noticed the move or will index the new page, and it says nothing about how quickly that page loads or whether its structured data is valid.
Fix in this order inside the Redirect Manager
Deal with a 404 or a loop first, because those send visitors and crawlers nowhere. Next collapse chains: if an old blog URL points to a renamed URL that itself redirects, edit the original rule so it points straight at the final address. Save the change (and publish, if you also renamed or moved pages), then run the same URL again and confirm a single permanent hop ending in 200. Since server response on Wix may already be on the slow side, shortening chains is one of the cheaper gains you control. A fixed redirect does not repair thin pages, missing alt text or image file names; those need their own checks afterwards.
Example scenarios
1. Blog imported from another platform
- Situation
- Illustrative example: a shop owner moved 40 posts from an old blog to Wix and entered one rule per post in the URL Redirect Manager, but typed three of the new paths with a typo.
- Input
https://www.example.com/2022/03/how-to-choose-a-yoga-mat- Reading the result
- A good result shows one 301 permanent hop to a /post/ address and a Final status of 200 OK. A typo in the rule would instead end at the Wix 404 page, so Final status is 200 OK would fail and the Final URL would not be the post you meant.
2. Page renamed twice in a year
- Situation
- Illustrative example: a plumber renamed a services page in spring, then again in autumn, and Wix kept the first redirect pointing at the middle name.
- Input
- example.com/our-services
- Reading the result
- Typed without a scheme, it is tested as http://, so Redirect Path could show a 301 permanent hop to the https www address, then 301 permanent to the spring name, 301 permanent to the autumn name, and the newest page answering 200. That is 3 redirect hops, so the Short redirect chain (≤2 hops) check would warn. Edit the first rule so it points straight at the newest address.
3. Plain http homepage
- Situation
- Illustrative example: a photographer is unsure whether visitors typing the domain without https reach the secure site after connecting a custom domain.
- Input
- example.com
- Reading the result
- Entered without a scheme, it is tested as http://, so the summary should show an HTTP to HTTPS upgrade, a Final URL that uses HTTPS and a 200 status. One hop (or two, if the www and https steps are handled separately) is fine; a 302 temporary label on the first hop would be worth a second look.
Common mistakes
- Assuming a saved rule works. A rule in the URL Redirect Manager only counts once the old address really answers with a 301 on the live site. Always test the live URL, not the dashboard.
- Chaining renamed pages. Each rename that adds a new rule on top of the last creates another hop. Point the oldest rule straight at the current page instead of stacking them.
- Sending everything to the homepage. Redirecting every deleted blog post to the homepage hides the problem behind a 200. Compare the Final URL with the specific page that replaced the old one.
- Using a temporary redirect for a permanent move. If Redirect Path shows 302 temporary on a page you moved for good, the signal is wrong. Recreate the rule as a 301.
- Testing only the www version. Old links exist in http, https, www and non-www forms. Trace at least the http and the preferred form so the scheme step is covered too.
Frequently asked questions
Does Wix redirect the old URL automatically when I change a page URL?
Wix can offer to set up a 301 when you edit a page's URL slug, but you should not assume that for every change, such as deleted pages, imported blog posts or a domain switch. Anything you add by hand goes into the URL Redirect Manager in the SEO tools. After saving and publishing, run the old address through the checker and confirm it ends in a 200 on the page you meant.
How many redirect hops are too many on a Wix site?
The tool's Short redirect chain check passes at two hops or fewer and warns at three or more. On Wix, the usual cause is a page renamed more than once, or an http address that jumps to https and then to another path. Each hop adds waiting time, so edit the first rule to point at the final page and rerun the URL to confirm.
Why does my old Wix blog post URL end in a 404?
Usually the rule is missing, has a typo in the old or new path, or the renamed page was not published. Blog posts live under /post/ on Wix, so a rule written for a different folder will not match. Trace the exact old address; if Final status is 200 OK fails, correct the path in the URL Redirect Manager, publish, and test again.
Is a 302 from my Wix site a problem for SEO?
A 302 or 307 tells search engines the move may be reversed, so it suits short-term changes rather than a permanent rename or migration. If Redirect Path labels a moved page as temporary, recreate the rule as a 301 in the URL Redirect Manager. The tool shows the type of each hop, but it cannot tell you how Google will treat the page afterwards.
Can this check the redirects set inside Wix settings or meta refresh?
It reports only what the server answers when it requests the URL, following Location headers up to ten hops. It does not read your Wix dashboard rules, and it does not see meta refresh or JavaScript redirects. So treat it as proof of the live behaviour for that address, and use the URL Redirect Manager to review which rules you have actually created.
Reference: The Ahrefs guide to Wix SEO limitations lists cryptic image file names, limited control over multilingual URLs and a hard-to-edit automatic sitemap among the platform's constraints.