404 and redirects internationally: Error pages that retain users

Fundamentals of international error and redirect strategies

International websites face particular challenges when building a consistent error and redirect strategy: each market can have its own URLs, language versions, and regional specifics. An inadequate strategy leads to lost users, declining conversion, and negative search engine signals. The fundamental distinction is between temporary (302) and permanent (301) redirects. For permanently moved pages, use a 301 redirect; for A/B tests or temporary changes, use a 302. For deleted content, status code 410 (Gone) is preferred to a 404, as it signals to the crawler that the page was intentionally removed.

A central element of the international strategy is the correct linking of hreflang annotations with redirects. If you automatically redirect users to the appropriate language version, ensure the target page contains the corresponding hreflang tag. Otherwise, you risk sending conflicting signals to Google. Also avoid language detection based solely on IP address. Offer the user a manual selection option when in doubt. For all markets, set up a consistent 404 page that is not served as a soft-404 (status 200 with error text).

It is advisable to centrally manage all redirects in a table (e.g., via .htaccess, Nginx configuration, or CMS plugin). For each removed or redirected URL, maintain the target market and language version. Perform regular tests with tools like Screaming Frog: check that 301 redirects have not been changed to 302 and that no redirect chains are created. For the 24 markets of Baduno localization, an automated monitoring system that validates the status codes of key pages per market every two weeks is recommended.

Legally, check that your error pages contain links to all relevant language versions so that users do not end up in a dead end. Note: the specific design of the pages may affect different imprint requirements from country to country. Consult a legal advisor if in doubt.

Designing Multilingual 404 Pages: Content and User Guidance

A multilingual 404 page is far more than an error message: it determines whether a visitor leaves or continues browsing. Design it user-friendly and language-conscious. The first step is dynamically serving the correct language version – based on the browser's preferred language or a previously set cookie. Falling back to English is acceptable but not optimal. Include a search function on the error page that searches the respective market index, as well as direct links to main categories in the corresponding language.

The navigation should include the most important paths: home page, contact, help/FAQ, and the language selector. Avoid clichés like "Page not found"; instead use a clear, active sentence: "The requested page is no longer available. Perhaps you can find what you are looking for here:". Use visual cues like icons, but without excessive branding. For example, an online shop with 24 EU languages can display the most searched product categories per country on its 404 page – e.g., "Popular categories in France".

Technical implementation requires storing the language and country codes in the URL (e.g., example.de/404-fr for French). Ensure the error page itself returns status code 404 and not 200 with a redirect. Use consistent paths such as /404 for all markets and internally redirect based on language. For 24 markets, an API solution that generates the appropriate page from the user agent or cookie is suitable.

Recommendation: Regularly test your 404 pages with users from different markets. Have participants run through typical error scenarios and measure bounce rates. Adjust content if certain language groups bounce more frequently. Important: the 404 page must not pose phishing risks – so no requests for entering personal data. Legal review is advisable in each market, as error pages are considered part of the online presence and are subject to imprint requirements.

Avoiding Redirect Chains: Building Clean Redirects

Redirect chains occur when a URL is redirected not directly to the final destination but via multiple intermediate stops. Each intermediate stop costs load time, can dilute link properties, and makes the website prone to errors. In an international setup with 24 markets, these problems multiply: a chain across different language versions can lead to long load times or even infinite loops. Avoid this by pointing each redirect to the final destination.

A typical example: you redirect /de/produkt-alt to /de/produkt-neu, which in turn points to /en/produkt-neu. Better: direct 301 from /de/produkt-alt to /de/produkt-neu (or the corresponding language version). Use relative paths only within the same domain; for cross-language redirects, use absolute URLs with the correct language code. Maintain a central redirect table from which you generate automated test runs. A script or crawler should log each redirect sequence and mark chains longer than two steps.

Special caution is required when combining redirects with hreflang. If a redirected URL lacks hreflang for the target language, Google may lose the assignment. Therefore, after each change, check using Google Search Console or an hreflang checker to ensure consistency. Also, using 303 or 307 for temporary redirects can create chains if later changed to 301. Decide on a clear status code per market and do not change it without review.

Practical recommendation: Set up automated monitoring for your 24 markets. A simple script (e.g., with Python and Requests) can retrieve all important paths once a week and output status code chains. Complement this with a log check of the web servers: look for 302 redirects that have been active for longer than a week – this often indicates a forgotten temporary redirect. Note: In some markets, special rules apply for redirects for legal reasons (e.g., trademark infringements). Seek legal advice before dissolving chains. With a clean, direct redirect structure, you improve user experience and facilitate search engine indexing of your international pages.

Permanent vs. temporary redirects across multiple language versions

When internationalizing your website, redirects play a central role for user experience and SEO. The choice between permanent (301) and temporary (302) redirects depends on the context – and this across different language versions. A 301 status code signals to search engines that a resource has permanently moved, while 302 indicates a temporary shift. In practice, use 301 for restructuring, new language subdomains, or consolidated content. Example: If you move your German product page from /produkt-alt to /produkt-neu, set a 301. For temporary actions like a brand switch or seasonal landing pages, use 302 so that search engines retain the original index.

Problems arise when you use different redirect types for different language versions. A typical mistake: you use a 301 for the German version but a 302 for the French because the translation is not yet ready. Search engines interpret this inconsistently and may pass on incorrect rankings. Avoid this by using the same status code for each language version when content is moved in parallel. If a version is not yet ready, temporarily redirect with 302 to a generic error page or another appropriate page – but with a note that the content will be available soon.

Another aspect: the correct chaining of redirects. Never set a 302 to a URL that later redirects via 301. This can confuse search engines and result in no page being ranked. Therefore, regularly check your redirect maps for all 24 markets. Tools like Screaming Frog or Ahrefs help identify redirect chains. Also note that for country-specific domains (e.g., French .fr) you apply the same redirect logic as for subdomains or paths. Consistency is key.

Recommendation: Define a global redirect strategy for all language versions. Document each redirect with status code, reason, and date of change. Regularly test that all redirects work as intended, especially after migrations. Avoid temporary solutions without a date – they become permanent solutions that impair user experience. (Note: Seek legal advice if redirects have contractual or trademark relevance.)

Handling deleted content: 410 Gone instead of 404

A 410 Gone response is stronger than a 404 because it explicitly signals that the resource has been permanently removed and will not return. For multilingual websites, it is advisable not to respond to deleted content with a mere 404, but to set a 410 when you are sure the content is no longer needed. This helps search engines remove the URL from the index faster and avoids repeated crawls of the page. A typical scenario: a product is discontinued, a job posting has expired, or a campaign ends – in such cases, use 410.

In international practice, you may encounter hurdles: deleted content in one language version that still exists elsewhere. For example, you remove the German description of a product, but the French version remains online. If you set a 410 only for the German page, you do not redirect the user; they land on a 410 page saying in German: “This content has been deleted.” This can be frustrating if the visitor actually wants to find the French page. Better: redirect the user with a 301 to the appropriate alternative page in the same language – for instance, the category overview. Only set a 410 if there is no meaningful alternative.

Also consider the logic for deleted content that existed in multiple languages. If you have deleted a press release in 24 languages, set a 410 for each language version, not just the main language. Otherwise, search engines may still display the undeleted versions. Check whether the deleted URLs were previously linked – a 410 does not remove these backlinks, but the link value decays faster than with a 404.

Recommendation: Create a list of all deleted content by language version. For each entry, decide: Is there a meaningful 301 redirect? If not, set 410. Monitor HTTP status codes with monitoring tools (e.g., Checkmk, UptimeRobot) for all 24 markets. Document the deletion date and reason. (Note: Legal documentation obligations may exist for deleted content – consult your legal department.)

Localize error pages: cultural and legal considerations

A 404 page is not just a technical error, but also an opportunity to retain users. In internationalization, you must consider cultural and legal differences. Culturally: In Germany, users expect a factual, informative message. A brief notice “Page not found” suffices, complemented by a search function or links to the homepage. In Japan, however, politeness is important – a too direct tone can be perceived as rude. Here the error page should include a formal apology, such as “We sincerely apologize that this page is not available.” In the USA, a more humorous tone is acceptable as long as navigation remains clear. Test your error pages with native speakers to avoid cultural pitfalls.

Legally: Error pages must meet the same legal requirements in all languages. This includes the imprint, privacy policy, and possibly cookie notices, which must be accessible from every page. Ensure your 404 page also contains these links. In Germany, the Telemediengesetz (TMG) is relevant; in France, the RGPD implementation. With deleted content, you may be required to redirect users to an alternative information page – for instance, for official announcements. Check for each market: Is the error page allowed to be ad-free? Advertising on a 404 page is unregulated in some countries, but may be considered misleading in others.

Language itself is also a factor: Avoid automatic translations of error texts that sound unnatural. Have the 404 page created by a professional translator who understands cultural nuances. Also use hreflang tags so that search engines deliver the correct language version for error pages. If a user lands on a wrong URL, the error page should appear in their preferred language – this requires detecting the language via URL or browser settings.

Recommendation: Develop a template for 404 pages that is adapted for each market. Keep the translation up to date and review it regularly. Test the error pages for spelling, cultural appropriateness, and complete legal links. Monitor user behavior: How many visitors leave the page after a 404? Use heatmaps or analytics to analyze behavior and optimize pages. (Note: Consult a local legal advisor for each market to ensure compliance.)

Redirects for country and language switching: best practices

When switching between countries and languages, redirects must be designed to not impair user experience while remaining search-engine friendly. In practice, it is advisable to implement country and language switching via explicit user selection (e.g., a dropdown menu with country flag and language code) rather than relying solely on automatic redirects based on IP address or browser settings. Automatic redirects should only be used when a clear geographic or linguistic assignment is possible – otherwise, errors such as so-called “geo-fencing” can occur, where users land on a version that is not relevant to them.

A key best practice is the use of hreflang tags to signal the correct language and country assignment to search engines. These tags do not replace redirects but complement them. When a user manually changes country or language, the URL should be updated accordingly (e.g., via parameters like `?lang=de` or subdomains like `de.example.com`). It is important to ensure that the redirect to the new URL uses a 302 status (temporary) to avoid confusing search engines. A permanent 301 code would be inappropriate here, as the user’s choice should not be considered a permanent change to the page structure.

In practice, it has proven effective to always consider the current URL structure when switching between countries and languages. For example, if a user switches from the German product page `/produkt-a` to the English version, they should not land on the homepage `/en/` but on the corresponding product `/en/product-a`. This requires a consistent URL pattern and the implementation of redirects that carry forward the path structure. Avoid redirects that redirect users to a different level without apparent reason – this typically leads to high bounce rates.

Implementation recommendations: Use client-side detection for country and language switching that directs the user to the appropriate version after explicit selection. For server-side redirects based on IP detection, use a 302 status. Test all redirects regularly across different market combinations to ensure no unintended chains occur. A good approach is to perform the redirect only on the first navigation and then give the user the option to permanently stay on a different version – this preference should be stored in a cookie.

Monitoring Errors and Redirects Across 24 Markets

Monitoring errors and redirects across 24 EU markets is a complex task that can quickly become confusing without structured monitoring. In practice, it has proven effective to use centralized dashboards covering all country and language versions. These should capture not only 404 errors but also redirect chains and too many redirect steps (more than three). Useful tools include log file analysis combined with crawling solutions that regularly scan all 24 market variants.

A specific indicator of problems with international redirects is the occurrence of 301 redirects on pages that should actually return 404 or 410. If a deleted page incorrectly redirects to another page, it can confuse both users and search engines. Therefore, you should set up monitoring that records the HTTP status codes of all URLs in each market and logs changes. For example, use Google Search Console for each country separately, but supplement this with custom crawler jobs that search log files for specific patterns.

In practice, companies often overlook the impact of internal redirect chains across different language versions. A German visitor might end up on a Spanish page via an English page if the redirects are not correctly limited to the target language. Implement checks that ensure a redirect keeps the user within the same language group, unless the switch is explicitly desired. Use metrics such as the number of hop destinations per user session and the bounce rate after a redirect.

A practical approach is to evaluate the most important metrics for each market on a monthly basis: number of 404 errors, average number of redirect steps, share of direct accesses to correct versions (without redirect), and response time for language switching. These values should be visualized in a dashboard that highlights deviations from the average. Only then can problems in individual markets be detected and fixed early. Also remember to configure custom alerts for sudden increases in 404 errors or unusually high numbers of 301 redirects.

Tools and Metrics for Detecting Redirect Issues

To identify problems with redirects in international projects, there are several proven tools and metrics. A good starting point is using crawling tools like Screaming Frog or Xenu, which can be configured individually for each language version. Ensure consistent configuration of the domains to be crawled (e.g., de.example.com, fr.example.com). These tools not only show 3xx status codes but also the redirect chains. In practice, it is advisable to limit the maximum number of redirect steps to three – anything above that is typically devalued by search engines.

Another important metric is the number of “internal” redirects within the same language version. If a German page redirects to another German page, this should generally be a 301 code, but the target URL must be consistent. A problem arises when a 301 redirect points to another 301 redirect, creating a chain. Tools like “Redirect Path” (browser extension) can quickly help by visualizing the entire chain. However, for the volume of 24 markets, you should use automated solutions such as logfile-based analyses with ELK Stack or similar systems.

A metric that is often underestimated is the proportion of sessions with more than one redirect step. If this value exceeds 10% in a specific market, it indicates a need for optimization. The distribution of HTTP status codes in the log file is also revealing: a high proportion of 404 errors combined with 301 redirects can be a sign of outdated links. Also use the “Page errors” reports in Google Search Console, but note that these only apply to indexed pages – not all errors are captured there.

Practical recommendations are: conduct a full crawl of all 24 markets monthly and export the redirect chains into a table. Then manually check the first ten suspicious chains per market. Install a monitoring tool that sends a notification whenever the redirect structure changes – e.g., via a webhook when a new 301 code is added to the .htaccess file. Additionally, regularly test switching between languages and countries, noting the number of redirects. This way, you can ensure that the user never needs more than two steps to reach the desired version.

SEO Impact of Incorrect Redirects on International Visibility

Incorrect redirects can significantly impair the visibility of your international websites. For example, if a 301 redirect goes from a German to an English page, Google interprets this as a signal that the target page is the more relevant version – with the consequence that the German page may lose ranking potential. Additionally, redirect chains (A → B → C) cause link equity not to be fully transferred and waste search engine crawl budget. In practice, we observe that such chains can delay indexing by weeks, which is critical for 24 markets.

Another common problem is the use of the wrong redirect type: a temporary 302 redirect, intended for surveys or maintenance, is not recognized by search engines as a permanent transfer of rankings. Ignoring hreflang tags after a redirect can also lead to duplicate content issues. If you redirect a French page to a generic English page but do not adjust the hreflang, you signal conflicting language signals – search engines then do not know which version should serve which country.

To minimize these risks, we recommend a multi-step approach: first, conduct a comprehensive audit of your redirects, ideally with a tool that traces the entire redirect chain. Each redirect should point to the linguistically and content-equivalent page in the target market – not to a generic landing page. Use 301 redirects exclusively for permanent redirects and 302 for temporary ones. Also monitor your crawl statistics in Search Console: a sudden increase in 404 errors or a decreasing indexing rate may indicate faulty redirects.

Specifically, maintain a separate redirect map for each market, which is updated immediately when structure changes occur. Automate the checking across all 24 markets, e.g., through regular scripts that verify HTTP status codes and target URLs. Also test redirects in different browsers and devices, as browser caching can treat temporary redirects differently. Only then can you ensure that your international SEO strategy is not undermined by invisible redirect issues.

User Experience on Error Pages: Alternatives and Search Functions

A well-designed 404 page can turn frustration into an opportunity to keep users on your website. It is crucial that you not only communicate the error technically but also offer the visitor concrete courses of action. This includes a clear search function integrated directly on the error page – ideally with autocomplete to compensate for typos. Additionally, you should place links to the most important categories or homepages of the respective language version. In practice, it has proven effective to automatically display the three most visited subpages of each market based on your analytics data.

A critical point is language adaptation: do not simply show a generic English 404 page for all markets, but adapt the text to the user's language. If a visitor receives a 404 on the German version, the message should be in German and refer to other German content. The same applies to cultural differences: in some countries, a humorous tone is welcome, in others less so – test this with local native speakers. Legally relevant is that the error page must at least contain a link to the imprint and the privacy policy to meet compliance requirements (see next chapter).

Furthermore, you can actively use the error page to improve user experience: for instance, offer the option to report the missing content or directly contact customer support. An alternative is to display a “suggestions” box with similar articles, fed by an internal search or recommendation system. However, ensure you do not offer too many options, as this can lead to decision paralysis. A maximum of five clear calls to action have proven effective: search, homepage, contact, sitemap, and a category overview.

Measure the success of your error pages by time spent and click-through rates on offered links. Use heatmaps to see where users click. If many visitors leave the website after the 404 (high bounce rate), you should revise the content. Conduct regular A/B tests, e.g., with different placements of the search bar or different tones. Remember: a good 404 page is not a necessary evil but part of your customer journey that should be consistently optimized across all 24 markets.

Legal Notices for Error Pages and Redirects (Liability, Data Protection)

When designing error pages and redirects, you must observe legal requirements in individual markets that go beyond mere functionality. For example, Section 5 TMG in Germany stipulates that the imprint must be easily recognizable and directly accessible on every commercial website – including on a 404 page. The same applies to the privacy policy according to the GDPR, which must be linked whenever personal data is collected (e.g., through tracking on the error page). In practice, we often see that companies forget these links on error pages, which can become costly in the event of a warning letter.

With redirects, liability issues arise in particular: if you permanently redirect a German page to an English one, you could in certain circumstances be held jointly responsible for the content of the target page if illegal content appears there. Therefore, especially with 301 redirects, take a careful look at the target page. Temporary 302 redirects are legally considered less problematic since they are not interpreted as a permanent takeover – nevertheless, you should ensure that no legal violations occur during the redirect period. It is advisable to seek legal advice to assess the specific risks for your 24 markets.

Another aspect concerns data protection in error handling: if your 404 page loads external resources (e.g., Google Fonts or analytics scripts), you must provide a privacy policy and, if necessary, obtain consent – especially in the EU. Cookies on the error page are only permissible if they are either technically necessary or the user has consented. To simplify this, you can intentionally keep the error page lean and forego tracking scripts, or use a privacy-friendly solution such as Matomo (self-hosted) without cookie consent.

Practical recommendations: integrate the links to imprint and privacy policy on all error pages via a footer module that is automatically pulled from your CMS. Check the legal responsibility for each redirect and document the reason for the redirect. Conduct an annual legal audit across all 24 markets – ideally with the support of local attorneys. Also note that in some countries (e.g., France) additional information such as the SIRET number is required. Only in this way can you avoid warning letters and fines that could jeopardize your international expansion.

Integration of Error Pages into Your Content Management System

The integration of error pages and redirects into your content management system (CMS) requires a well-thought-out multilingual architecture. Start by creating separate 404 and 410 templates for each language version. These templates should not only contain static text in the respective language but also dynamic elements such as a locally adapted search, a sitemap link, or contact information. In a CMS like WordPress or TYPO3, this can be realized via language containers or multisite installations. Ensure that the templates automatically select the correct language based on the URL structure (e.g., /de/404 or /fr/410).

For redirects, a central plugin or module is recommended that manages all redirects and enables logging for each market. Avoid static .htaccess files, as they quickly become confusing with 24 language versions. Instead, store redirects in the database with fields for source and target URL, status code (301/302/410), and language identifier. The CMS should automatically check when content changes whether old URLs need to be redirected—for instance, when an article is moved to another category. Use hooks or events that are triggered when saving a post.

For the error pages themselves, a modular structure is recommended: the header and footer of each language are loaded from the global template, the middle part is language-specific. Also include alternative navigation suggestions, e.g., the three most visited pages of the respective market. Check whether your CMS correctly sets the HTTP status code (404/410)—some themes accidentally overwrite it with 200. Test this with a tool like httpstat.us or a browser plugin. Also document the workflow: Who is allowed to create redirects? What checks are necessary before a redirect is activated?

A practical tip: Set up an internal error page that shows the editorial team the last 404 errors. This page is only visible in the admin area and lists the failed URLs, the number of requests, and the associated market. This way you can quickly see if a redirect is necessary. Link the error statistics to your CMS dashboard—for example, via a widget that displays the most common 404 errors of the last 30 days. In this way, optimization becomes part of the editorial workflow without relying on external tools.

Checklist: From analysis to continuous optimization

A systematic approach ensures that error pages and redirects function consistently across 24 markets. Use the following checklist as a guide, starting from the initial analysis to ongoing improvement.

**1. Analysis and inventory:** - Crawl all 24 language versions with a tool like Screaming Frog or Sitebulb. Pay attention to 4xx and 5xx status codes as well as redirect chains. - Identify the ten most common 404 errors for each market. List whether these URLs previously had valid content or never existed. - Check whether your redirects are language-specific: does /de/alte-seite correctly redirect to /de/neue-seite and not to the English version? - Document existing redirect chains (e.g., 301 → 302 → 301) and plan their resolution.

**2. Implementation of basic measures:** - Set up custom 404 and 410 pages for each market as described in the previous chapter. - Create a redirect for each known outdated URL—preferably with 301 (permanent) or 410 (deleted). - Avoid redirect chains by setting each redirect directly to the final destination. Use your CMS module or a central table. - Test the redirects manually on a staging environment for all languages.

**3. Monitoring and continuous optimization:** - Set up weekly monitoring of server logs or a tool like Google Search Console for each market. Filter for 404 and 410 errors. - Check monthly whether new 404 errors have occurred—for example, through external links to old URLs. Respond within 48 hours with an appropriate redirect. - Verify that temporary 302 redirects do not accidentally remain permanent. Set reminders in the CMS for redirects with expiration dates. - Conduct a full crawl of all 24 markets quarterly to uncover redirect chains and dead links.

**4. Quality assurance and training:** - Document all processes in an internal wiki. Record who is responsible for maintaining redirects and what escalation paths exist for problems. - Train your editors on using the redirect module: they should know how to create and test a new redirect. - Use a ticket system for reported 404 errors. Each entry should include the market, the faulty URL, and the processing status. - Conduct a comprehensive review of all redirects once a year. Remove redirects that are no longer needed and update targets if content has evolved.

Common pitfalls with international redirects and error pages

Even with careful planning, several common pitfalls lurk in practice that can impair user experience and international visibility. A frequent issue is the use of client-side redirects (e.g., via JavaScript or meta refresh) instead of server-side HTTP status codes. Search engines often do not interpret these methods as definitive redirects, which can lead to both URL versions remaining indexed or link equity not being properly transferred. This is especially critical for language switching when users land on the wrong language version and are only redirected via JavaScript – bots may overlook this redirect.

Another pitfall is inconsistent country assignments in hreflang tags and redirects. For instance, if you set up a separate redirect to a .ch domain for Switzerland but reference the .de domain in the hreflang tag, a contradiction arises that confuses search engines and leads to ranking losses. Neglecting language variants (e.g., de-CH vs. de-DE) on error pages is also problematic: a Swiss user encountering a generic 404 page in High German may feel unaddressed. Here, dynamically adjusting the language based on the Accept-Language header or visitor location helps.

A third, often overlooked point is the lack of monitoring of redirect chains across multiple language versions. For example, an old product page (www.example.com/product) might be redirected to a new category page (www.example.com/category) without updating the parallel pages in other languages (e.g., www.example.fr/produit). This creates dead links or infinite loops for French users. To avoid these pitfalls, we recommend performing a full crawl before launching all language versions using a tool like Screaming Frog, and specifically checking: status codes, redirect chain length, alignment of hreflang with target URL, and error page display in each language. Also schedule regular audits, as redirects can shift due to content changes.

Collaboration with Service Providers and Budget Planning for Internationalization

Implementing an international error page and redirect strategy often requires collaboration with multiple external partners: translation agencies for multilingual 404 content, SEO agencies for technical implementation, and developers for CMS integration. Without clear agreements, inconsistencies and extra work quickly arise. We recommend creating a central document (e.g., a Confluence page) containing all specifications: required status codes (301, 302, 410), mapping tables for old and new URLs per language, design guidelines for error pages, and legal requirements (imprint, privacy policy) per market. This document serves as a binding foundation for all parties.

When budgeting, consider not only one-time setup costs but also ongoing costs for translations (new error page texts due to content changes), tool licenses (crawlers, monitoring), and personnel resources for regular audits. In practice, maintaining redirects in 24 languages can quickly consume 10–20% of the total SEO budget if not systematically organized. Translation costs for dynamic error page elements (e.g., search field labels, contact forms) are also a factor. Ensure your translators are familiar with technical constraints, such as character limits in certain CMS fields.

A common objection from service providers is the high effort of manually maintaining redirect mappings. You can save time by using patterns (wildcard redirects) or Excel templates that are automatically generated per language. However, manual quality control remains essential, as automated solutions cannot detect cultural errors (e.g., wrong currency symbols on error pages). Therefore, allocate sufficient time in the budget for correction cycles after launch. For continuous optimization, we recommend defining a monthly report showing the number of 404 errors per market, user dwell time on the error page, and conversion rate of alternative suggestions. This way, you can prioritize improvements together with your partners.