News

Google claims AI is making Search better, not worse

The company asserts that AI is actually "driving more queries and higher quality clicks"

For a while now, internet users and analysts alike have expressed concerns about how Google’s AI tools in Search could negatively impact websites. After all, if Search’s AI Overview feature can generate (supposedly accurate) synopses of websites, then why would you need to click through to any?

Now, however, Google is refuting reports that AI is having a negative impact on web traffic in Search in a new blog post titled “AI in Search is driving more queries and higher quality clicks” by Liz Reid, the company’s VP of Search. According to Reid, the organic click volume has remained “relatively stable year-over-year,” while average click quality has actually “increased,” and Google is “sending slightly more quality clicks to websites than a year ago.” The company says “quality clicks” refers to a site that a user actually stays on for a little while instead of quickly clicking back once directed.

“This data is in contrast to third-party reports that inaccurately suggest dramatic declines in aggregate traffic — often based on flawed methodologies, isolated examples, or traffic changes that occurred prior to the roll out of AI features in Search,” says Reid.

One such third-party report came recently from the well-regarded Pew Research Center. In a study published on July 22, the institution compared click rates between searches with and without AI Overviews and found a nearly 50 per cent drop in situations where the feature was enabled. The study also found that users were more likely to end their browsing session after clicking on a link provided by AI Overviews — the complete opposite of the “quality clicks” that Reid talked about.

It should also be noted that the blog post, which Google itself notes at the top is just a three-minute read, is very brief and doesn’t actually contain any factual data to back up Reid’s claims. Pew, meanwhile, naturally provided a comprehensive breakdown of how it gathered all of its data.

The other key part of the equation, beyond site traffic, is, of course, accuracy. Indeed, AI has long had problems with “hallucinations,” the phenomenon in which the technology produces outputs that are incorrect or nonsensical. For instance, Tom’s Hardware published a great round-up a few months back of nearly 20 strange to flat-out dangerous AI Overviews, from the suggestion that eating boogers will boost your immune system to the feasibility of using gasoline in a food recipe.

Reid’s blog post doesn’t address these concerns outside of a larger sentiment about its commitment to continuing to expand upon AI tools in Search. “We believe that AI will be one of the most expansionary moments for the web, empowering us all to ask vastly more questions and creators to reach more deeply engaged audiences,” she wrote. Sure…

Image credit: Shutterstock

Source: Google

MobileSyrup may earn a commission from purchases made via our links, which helps fund the journalism we provide free on our website. These links do not influence our editorial content. Support us here.

Related Articles

Fatal error: Uncaught Aws\S3\Exception\PermanentRedirectException: Encountered a permanent redirect while requesting https://ms-staging-baselayer-static-assets.s3.ca-central-1.amazonaws.com/?list-type=2&delimiter=%2F&prefix=uploads%2Fwpcf7_uploads%2F. Are you sure you are using the correct region for this bucket? in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php:49 Stack trace: #0 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(209): Aws\S3\PermanentRedirectMiddleware->Aws\S3\{closure}(Object(Aws\Result)) #1 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(158): GuzzleHttp\Promise\Promise::callHandler(1, Object(Aws\Result), NULL) #2 /var/www/html/vendor/guzzlehttp/promises/src/TaskQueue.php(52): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}() #3 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(163): GuzzleHttp\Promise\TaskQueue->run() #4 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(189): GuzzleHttp\Handler\CurlMultiHandler->tick() #5 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(251): GuzzleHttp\Handler\CurlMultiHandler->execute(true) #6 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(227): GuzzleHttp\Promise\Promise->invokeWaitFn() #7 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #8 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #9 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #10 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #11 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(69): GuzzleHttp\Promise\Promise->waitIfPending() #12 /var/www/html/vendor/aws/aws-sdk-php/src/AwsClientTrait.php(58): GuzzleHttp\Promise\Promise->wait() #13 /var/www/html/vendor/aws/aws-sdk-php/src/ResultPaginator.php(151): Aws\AwsClient->execute(Object(Aws\Command)) #14 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(52): Aws\ResultPaginator->valid() #15 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(69): Aws\map(Object(Aws\ResultPaginator), Object(Closure)) #16 [internal function]: Aws\flatmap(Object(Aws\ResultPaginator), Object(Closure)) #17 /var/www/html/wp-content/plugins/s3-uploads/inc/class-stream-wrapper.php(695): Generator->valid() #18 [internal function]: S3_Uploads\Stream_Wrapper->dir_readdir() #19 /var/www/html/wp-content/plugins/contact-form-7/includes/file.php(362): readdir(Resource id #734) #20 /var/www/html/wp-includes/class-wp-hook.php(322): wpcf7_cleanup_upload_files() #21 /var/www/html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #22 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #23 /var/www/html/wp-includes/load.php(1280): do_action('shutdown') #24 [internal function]: shutdown_action_hook() #25 {main} thrown in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php on line 49