Frequently asked questions

It records the 404 requests your site receives, compares the requested address against your site's current catalog, and finds the closest valid address. If the match is strong enough, the visitor is redirected there.

If it isn't strong enough, no404 does nothing: the page stays a 404. We deliberately do not send every 404 to the homepage — search engines treat that as a soft 404, and it works against you.

Through Google Search Console. You connect your account, pick one of your verified properties, and no404 reads the catalog from the sitemap you submitted for it.

There is deliberately no "type a URL and a sitemap" form: without proof of ownership, anyone could add a site they do not own.

Yes. On the bulk matching screen you can upload a file or paste a list of addresses, and pull in the 404s that still get Google traffic plus the unmatched paths from the last 30 days with one click.

no404 shows the target it suggests for every row and you approve it. You can also export the result as .csv, .xlsx, .htaccess or nginx rules if you would rather keep the redirects on your own server.

Indefinitely. It includes 1 website, 500 requests per month, a catalog of up to 250 addresses and 30 days of event history. We don't ask for a card and your account doesn't expire.

When the limit is reached, resolution stops; the counter resets at the start of the next month.

Every resolution request made with your key — visitor or bot — plus every address you scan in bulk matching. The counter is account-wide and resets at the start of each month. Paid plans get a 10% tolerance.

We don't exclude bots, because telling a bot from a human relies on what the caller reports about the browser; leaving a class uncounted would open the door to "just label the traffic as a bot". You still see the breakdown in your reports.

An upgrade takes effect immediately and the difference is invoiced. A downgrade takes effect at the end of the period you already paid for — you keep your current plan until then.

In both cases your catalog is re-synced against the new ceiling; if you upgraded, a larger part of your sitemap is read.

You can cancel from the dashboard at any time. Cancellation takes effect at the end of the period you've paid for; your access continues unchanged until then and no further payment is taken.

The cases in which a payment is refunded are listed item by item in the Refund & Cancellation Policy. If we reduce what a plan includes, an annual subscription keeps the year you paid for.

Yes — the yearly price is lower than 12 months of the same plan. The exact amount and what you save appear on the pricing cards when you flip the monthly/yearly switch; the discount is calculated from the difference between the two prices, not stored as a fixed percentage.

Paying yearly only changes the billing period; your request allowance still works monthly.

No. There are ready integrations for WordPress, PrestaShop, Laravel and Node.js; all four produce a real server-side 301 and only need your API key.

If none of them fit your stack, a small JavaScript snippet works on any site. The one difference: the page's HTTP status stays 404 and only the visitor's browser is redirected. A REST endpoint is available if you prefer to call it from your own server.

The no404 call is fail-open: if no answer arrives within 1.5 seconds the integration gives up quietly and your page serves its usual 404. Your site keeps working even if no404 is unreachable.

The ready-made plugins and packages also cache per path, so repeat visitors to the same broken address trigger no request at all.

You decide. Redirects you define by hand are always 301. A match found in your catalog gets a 301 when it is above the permanence threshold in your site settings, and a 302 when it is below — the default threshold is 0.5.

If you want to be careful you can set it to "only my manual redirects are 301"; every automatically found target then returns 302 and search engines keep the old address indexed.

By default, nothing. The page stays a 404 and the event is recorded in your dashboard.

If you prefer, there are two more options: send the visitor to the closest parent path in your catalog (a category page for a deleted product), or fall back to an address you choose. Requests that have nothing to do with your catalog — bot scans — are never redirected in any mode.

Raw IP addresses are not stored. The address is first truncated to its /24 network (/48 for IPv6) and then hashed irreversibly with a key specific to your site. What you see in the dashboard is that truncated, hashed form.

With the WordPress, PrestaShop and Shopify integrations the full IP never leaves your server: the truncation happens there.

Read-only. We read your list of verified properties, the sitemaps you submitted for them, and the search traffic going to addresses that return 404.

We never write anything to Search Console and never change your site. You can disconnect at any time from your account settings.

Retention for your 404 events depends on your plan: 30 days on Free and Starter, 90 days on Pro, 180 days on Growth, and 365 days on Business and Agency. Expired records are deleted automatically.

If you delete your account, your websites, redirects and event history go with it; the account record itself is kept with personal details stripped so historical statistics stay consistent.