Firstly, it is essential to verify whether redirects function when using a GET parameter. This check helps to rule out the influence of caching on the module's operation. To do this:
- Open the page for which the redirect is configured.
- Append a GET parameter to the URL, such as ?testredirect (e.g., http://domain.com?testredirect). You can use any text after the question mark to trigger the GET parameter.
If redirect works using the GET parameter, it defines that caches affect the module behavior and further configuration is required on the server side.
2. Check GeoIP Data Import
Ensure that the GeoIP data is imported correctly in Amasty > Geoip Data > Configuration. When clicking the "Download and Import" button, the system should display the message: "GeoIP data is up-to-date." This confirms that the necessary data is present for location-based redirects.
3. Ensure Redirects for Specific Countries
Check your store views to ensure redirects are appropriately set up for specific countries. It is necessary to switch to the relevant store view to verify that the redirect settings correspond to the intended countries within the Affected Countries field.
4. Check Force IP Settings
If a client reports that redirects, despite being configured for different URLs, always lead to the same website, it is important to examine whether an IP address has been added that "tricks" the module. These settings are located in:
To verify an IP's association with a specific country, you can use the IP lookup tools.
5. Add Store Codes to URLs
For the Geoip Redirect module to function correctly, store codes must be enabled in the website's URL. To activate this setting:
- Navigate to Stores > Configuration > General > Web > URL Options
- Enable "Add Store Codes to URLs"
By following this checklist, you may ensure that your website's redirects are configured and functioning as intended. If issues persist after these checks, consider contacting our support team for further investigation.