Find broken product links. Before a customer hits a 404.

Scan your shop’s internal links and add old addresses from Google Search Console. See which links fail, where they are linked and whether redirects reach a working page.

Internal links + sitemaps. Up to 5,000 URLs. No account with us.

Do you have old URLs from Google?

Upload a Google Search Console CSV export or paste the addresses. This includes old product links that have disappeared from your shop’s navigation and sitemaps.

Help with the free Search Console export

We respect robots.txt. Reports stay temporarily in server memory for no more than one hour. Use public addresses without login details or private tokens.

Check one specific address

Use this to see every step in a particular redirect chain or verify a fix.

One public HTTP or HTTPS address. No account required.

The URL is sent to our checker and the destination website. We do not save entered URLs or results. Use public addresses without login details.

Include Google URLs — free of charge

  1. Open your property in Google Search Console. Under Indexing → Pages, export examples from Not found (404).
  2. You can also export the Pages tab under Performance → Search results to check addresses that previously received search traffic.
  3. Download the CSV file, open the import field above and choose the file. Only URL addresses are imported; traffic metrics from the file are not used.

A crawl cannot discover an old address that no page or sitemap links to anymore. Importing helps close that gap. Search Console exports have their own coverage limits and are not a complete list of current Google results.

Google Search Console: Help with the free Search Console export

What does the response mean?

200: the server returned a successful response. Open the page and check its content; a successful code alone does not prove that the page is useful or indexable.

301 / 308: permanent redirects. 302 / 303 / 307: other redirect responses, with temporary handling relevant to the site’s workflow. Review the destination and why the rule exists.

404 / 410: the requested resource is not found or is gone. This can be correct when there is no relevant replacement. 403 / 429: the site may be blocking or limiting the checker.

Use it alongside your Shopware workflow

Start with old product addresses from Search Console and the 404 errors found by the scan. Choose a relevant replacement product or category, then check the result after changing the redirect.

Product 404 Redirects is my Shopware extension for relevant deleted product addresses. Automatic recovery of an older address depends on data still present in the shop. Unknown addresses need review; neither the tool nor the plugin guarantees a Google position.

What the check covers

The scanner follows public HTML links from page to page on the same hostname and its www equivalent. Sitemaps and sitemap indexes add discovery sources; they are not the only source. Each visited address and redirect destination is checked against robots.txt. A missing or unreadable robots file, or rules blocking the scanner, prevent crawling.

Checkout, login, account and action URLs are skipped. The scanner does not execute JavaScript, use login credentials or inspect every image, script and other file. Each scan is limited to 5,000 discovered URLs and 20 minutes. Limits and unreadable pages are clearly identified in the report.

Google URLs are checked when you import them. The tool does not run an automatic Google search. A 301/308 ending in an HTTP 200 response demonstrates a working permanent HTTP redirect; still open the destination and review whether the product or category is relevant.

Discuss your Shopware project

Send your Shopware version, sales channels and the task you need to solve. We can define the next useful step.