Google Search Console
JetOctopus
Asaxiy is one of Uzbekistan’s leading eCommerce platforms, offering a wide range of products, from electronics and home appliances to books and personal care items.
Asaxiy began experiencing a surge in 5хx errors, as detected in Google Search Console and JetOctopus. These server errors indicated potential issues affecting website stability, crawling efficiency, and search engine indexing. The Promodo SEO team had to find the problem and eliminate it.
Key factors to consider:
Addressing these technical issues was critical to maintaining Asaxiy’s search performance, ensuring uninterrupted access for users, and preventing potential SEO setbacks.
To resolve the issue, we conducted an in-depth technical analysis to identify the root cause of the 5xx errors.
A recent update mistakenly added an extra "/uz" segment in some URLs within the hreflang tags.
This led to a large number of broken URLs, causing server errors and disrupting search engine crawling. We corrected the hreflang syntax, ensuring that each language version referenced the correct URL.
😔 However, after fixing this issue, we expected the errors to disappear—but they continued to appear, indicating deeper underlying problems.
While investigating further, we found URLs with a non-existent "/oz" language version on the site. We were puzzled, as there was no such version on the website anymore. Initially, we thought the issue was related to another recent update, but the cause turned out to be more interesting.
The client’s development team informed us that this "/oz" version once existed but was removed long ago with a redirect set up. Despite this, search engine bots were still attempting to crawl these outdated URLs.For example, the URL https://asaxiy.uz/oz/product/stiralnaya-mashina-hofmann-hw-610fw-belaya-6-kg would trigger a redirect for users, but not for bots.
💡 The issue arose due to Cloudflare settings, which caused the bot to receive a 5xx error instead of the proper 301 redirect.
Working closely with the client’s development team, we reconfigured Cloudflare to ensure that the bot received the correct response. This fixed the issue of the bot crawling non-existent URLs, and this part of the problem was resolved.
😲 But that wasn’t the end of it.
After some time, we discovered another reason behind the generation of incorrect URLs, which were causing the bot to receive 500 errors.
💡 The login button on the site contained a "#" symbol, which was appended to the current URL when clicked.
For users, everything functioned as expected: clicking the button triggered a popup for registration or login. However, for the bot, this caused a problem. The bot kept trying to crawl the URL with the "#" symbol, which led to a 500 error since the URL wasn’t resolving correctly.
After weeks of collaboration and fine-tuning, we were able to resolve the issues and eliminate over 100,000 pages that were returning 5xx errors.
Through a combination of technical analysis, hreflang corrections, Cloudflare adjustments, and optimizing the login button behavior, we successfully restored proper site functionality and ensured that the bot could crawl the website without encountering errors.
These efforts led to:
This project demonstrated the importance of thorough technical SEO audits and close cooperation with the client’s development team to overcome complex SEO challenges.
Case studies
Check out how we help companies like yours overcome challenges and rise to the next level.
Conversions
Revenue
of new users stayed active
.webp)
.svg){kind=logo}
