Table of contents
Wix gets the status code right and leaves the page empty. Request a URL that does not exist on a Wix site and you get a genuine 404, but the body is a script-built shell with no text and no links in the HTML. A browser fills it in. A crawler or agent that does not run scripts finds nothing to follow. This guide shows what nine live Wix sites return, how to add a 404 page with real links in the Editor, and the redirect habit that quietly turns good 404s into soft ones. Checked on 15 October 2026.
Quick summary
| Situation | What you get | Fix |
|---|---|---|
| Default Wix 404 | 404, about 2.2 KB, 0 links, noindex | Add a custom 404 page |
| Custom 404 page | You control text and links (premium plan) | Link to pages people want |
| Old URL redirected to the homepage | A 200 that is not the page asked for | Redirect to a matching page, or let it 404 |
| Slug changed on a Blog post | No automatic redirect | Add a 301 by hand |
Fastest route: run npx aiscan-cli yoursite.com and read E1, Correct 404 handling (Discoverability). The by-hand check is in Step 4.
What the default Wix 404 actually is
I requested a made-up path on nine Wix sites: five on wixsite.com addresses and four on custom domains. All nine answered 404 text/html. The response was between 2,204 and 2,505 bytes, carried <meta name="robots" content="noindex">, and had the title "404 Error: Page Not Found". Inside the body there is one <div id="root"></div> and a script that draws the message. There were zero <a> tags in any of them.
So the status is correct, and RFC 9110 defines 404 as exactly this signal. AIScan scored one of those sites (a Wix manufacturer's site) as a pass on E1, with the evidence line HTTP 404, 2206 bytes. What it cannot give a script-less reader is a way out. E1 also looks at the body: AIScan's E1 description says full credit needs a body that names the site and links somewhere useful.
None of the nine sites had a custom 404 page, so I could not measure one. Step 1 builds it, and Step 4 tells you what to look for.
Step 1: Add a 404 page with links
Per Wix's own help article, a custom 404 page needs a premium plan. In the Editor:
- Click Pages & Menu on the left.
- Click Add Menu Item at the bottom of the panel.
- Click New Page, then (404) Error Page.
- Hover a template, click Add Page.
- Edit the text, add your site menu, and add links to the sections visitors look for.
- Click Publish.
Wix notes that you can change the page title in Page Settings, but the page URL always contains error404. Write the sentence in your own words and name the site: "This page is not on example.com. Try the pricing page, the blog or the contact page." Use text links, not only buttons or an image.
Step 2: Do not redirect dead URLs to the homepage
The Wix URL Redirect Manager creates 301 redirects, and it is easy to point every retired URL at /. Google's status code guidance says a 200 whose content suggests an error or an empty page shows up in Search Console as a soft 404. A homepage served for a retired product URL is that pattern from the reader's side. Redirect an old URL to its closest replacement, and when there is none, leave it to 404.
Limits from Wix's redirect article:
- 301 redirects only work with a custom domain. A free
wixsite.comaddress cannot have them. - You cannot create a redirect whose source is your homepage.
- A site can hold at most 5,000 redirects.
- Wix creates a redirect automatically when you change an Editor page slug. Blog pages are the exception: change a blog slug and you must add the 301 yourself, or the old URL 404s.
Step 3: Check the layers in front of Wix
If you put a CDN or proxy in front of a custom domain, it can replace a 404 with a friendly 200. Test the live domain, not only the Wix preview.
Step 4: Verify the fix
With AIScan (default): run npx aiscan-cli yoursite.com, open Discoverability and find E1, Correct 404 handling. It reads pass when the status is 404. Watch the body evidence too.
By hand with curl:
curl -s -o /dev/null -w '%{http_code} %{content_type}\n' https://yoursite.com/this-page-does-not-exist-9f3a
curl -s https://yoursite.com/this-page-does-not-exist-9f3a | grep -o '<a ' | wc -l
Expected: 404 text/html, then a link count above zero. On the default Wix page I measured 0. If the first line prints 200 after you add your page, the status is wrong, and Wix support is the next stop. I found no live Wix site with a custom page to measure, so this command is the test, not my word.
Edge cases
- A redirect conflict can arise when a page and a redirect claim the same URL. Wix's redirect article has a section on resolving it.
- Deleted pages return the 404 page, which is correct. Do not redirect them out of habit.
Next step
Run the scan, check E1 on your own domain, and read the rest of the series in AIScan's guides. Related reading: why soft 404s mislead agents, the Webflow version of this fix, AI readiness setup on Wix, and the Discoverability checks.
Frequently asked questions
Does Wix return a real 404 for a page that does not exist?
Yes. On nine Wix sites I tested, a made-up path returned 404 text/html with a noindex tag. The weak spot is the body: the default page is a script-built shell with no links in the HTML.
AIScan passes E1 on my Wix site but I still want to change the 404 page. Why?
E1 reads the status line first and the body second. A 404 body with no text or links leaves an agent with nowhere to go, so a custom page with real links is worth adding even when the status check passes.
The Pages & Menu panel has no (404) Error Page option. What now?
Wix says a custom 404 page needs a premium plan. Check your plan first, then retry Pages & Menu > Add Menu Item > New Page and look for (404) Error Page in the list.
My custom domain URL still shows a Wix 404 instead of my page. What is wrong?
Publish the site after adding the page, then test the live domain rather than the editor preview. If a CDN or proxy sits in front of the domain, test the origin too.
I changed a blog post slug and the old URL now gives a 404. How do I fix it?
Wix does not create a redirect automatically for Blog pages. Open the URL Redirect Manager and add a 301 from the old slug to the new one. This needs a custom domain.
Can I redirect every old URL to my homepage to avoid 404s?
You can, but it is a bad idea. Google treats a 200 whose content does not match the request as a soft 404. Redirect to the closest matching page, or let a retired URL return 404.
Why can I not set up a 301 redirect on my free wixsite.com address?
Wix states that 301 redirects only work with custom domains. Connect a domain first, then add redirects in the URL Redirect Manager.
What does the Wix 404 page URL look like?
Wix says the page URL always contains error404, though you can change the page title in Page Settings. A made-up path on a live site is still the quickest way to see the page visitors get.
Related guides
What a Failing AIScan Check Really Says: 2,961 Fail Lines Audited
A failing check on a scan report is supposed to be an instruction. The site owner reads the line, knows what the scanner asked for, knows what came back, and knows what to change. We audited whether…
Which Agent-Readiness Checks Travel Together: 739 Sites, Three Bundles
Fix one agentreadiness check and a second one often moves with it. Fix another and nothing else changes. A scan report lists every check as its own line, so the reader cannot see which lines are…
How to return a real 404 with a recoverable body on Docusaurus
Docusaurus builds a real 404.html for you, and then the place you test it hides it. Run npm start, type a madeup URL and you get a friendly page with a 200 status. The production build behaves…
How to return a real 404 with a recoverable body on Lovable
Lovable can return a real 404 or a soft 200 for the same missing URL, and which one you get depends on the stack your project was built on. AIScan check E1 Correct 404 handling grades both the status…
