Last week, OpenAI challenged Google with its new AI-powered search engine ChatGPT Search. ChatGPT Search, which cleans Google’s search results from ads and SEO content and provides users with direct and simple answers, has also shown success in detailed and research-intensive topics. However, when it comes to daily and short keyword searches, ChatGPT Search has yet to replace Google. Here are the details
ChatGPT Search, expected to rival Google, fell short of expectations
Technology writer Maxwell Zeff observed this closely while testing ChatGPT Search. For example, with a short query like “Denver Nuggets score,” ChatGPT misrepresented the result of an NBA game. Similarly, when entering a simple prompt like “financial report today,” ChatGPT presented data that had been released the day before.
Zeff said he had to go back to Google every time because of such incomplete or incorrect results. This incompleteness of ChatGPT Search in keyword-based searches is a big disadvantage for users who want to find information quickly. Of course, ChatGPT Search also has its strong points. It can offer a successful experience especially for long and research-intensive questions.
For example, for questions such as “What is the most diverse sports league in the US?”, it can provide a better answer than Google and present the information gathered from different sources to the user in a comprehensible format. However, it is not as reliable as Google for basic queries that users use every day, such as “cafes near me” or “weather”. In short, ChatGPT still has shortcomings for daily searches where short and fast information is needed.
OpenAI is aware of these problems and announced that it continues to work to improve ChatGPT Search. In the future, OpenAI’s ability to better support short keyword searches may increase its chances of becoming an alternative to Google. For the time being, however, ChatGPT Search has created a niche market focusing on complex and detailed questions, but it has not reached the convenience of Google in daily use.
{{user}} {{datetime}}
{{text}}