Welcome to this week’s Pulse: Image generation comes to AI previews, Mueller weighs in on a plan to hide a homepage link, and Google places an outer limit on the duration of a content-based canonical fix.
This is what matters to you and your work.
Google adds image generation to AI previews
Google is adding AI image generation to AI previews and rebuilding the Google Images homepage, both timed for the service’s 25th anniversary.
Highlights:
Image generation in AI Overviews turns a text prompt into a custom image built with Google’s Nano Banana model, the image system that Google expanded to Search and Chrome this year. The redesigned Images home page is a searchable gallery of images from around the web that updates in real time, tailored to your interests while you’re logged in, with saved collections appearing as tabs above the gallery. Both will be rolled out in the coming weeks.
Why it matters
AI previews already answer many queries without a click. The images generated give this surface one more thing it can produce on its own, in a place that has turned people towards images from the web. The redesigned home page adds a starting point that isn’t a query at all, a custom feed next to the search box.
Read our full coverage: Google adds image generation to AI previews and reorders images
Mueller responds to plan to hide homepage link
Google Search advocate John Mueller responded to a plan to prevent a homepage button from being a link, so that a better-worded link further down the page would count instead. He suspects the person behind this is thinking too much about it.
Highlights:
THE r/bigseo thread describes a homepage that links to the same services page twice: once via a Services button at the top and once via an FAQ link written the way the poster wants Google to read it. The plan was to make the button stop being a link while still working when clicked, leaving the FAQ link as the only regular link pointing to that place. Mueller said he didn’t expect to see any visible change and suggested using CSS or JavaScript to position elements on the page.
Why it matters
Internal anchor text has been an optimization technique for years, which is why a plan like this seems reasonable. What it costs is a home page where the main button is no longer a link. What he buys, from Mueller’s reading, is nothing you can measure. Its alternative keeps both links and only moves their order in the code.
Read our full coverage: Google’s Mueller on First Link Priority and Link Obfuscation
Mueller on long A/B tests
SEJ’s Roger Montti reviewed Mueller’s response on A/B testing lasting six to twelve months and found that it appears to contradict Google’s own written guidelines.
Highlights:
Asked on Bluesky how Google handles long-term resistance in a market with tens of millions of pages, Mueller said that depending on the configuration, one version or another is used for indexing and that variants that are sufficiently different from each other could appear in search results. Pressed on whether ever-changing HTML could cause pages to be deleted, he said that, to his knowledge, there was no penalty or demotion for variable content, although it could make content harder to debug and monitor if it was constantly changing.
Why it matters
Montti’s reading is that Mueller answered the indexing question twice and that the actual question asked, about tests run over the better part of a year, remained intact each time. That leaves a Googler’s answer and Google’s own documentation pointing in different directions, and only one of the two is a published guide. The guidelines are also the more specific of the two, warning against running an experiment for longer than necessary, particularly when a variant reaches a high percentage of users.
Read our full coverage: Google says there is no SEO penalty for 1 year A/B testing?
Google says content-based canonical fixes can take two weeks
Google added a section to its canonicalization troubleshooting guide setting expectations for how long it takes for a content fix to appear in search.
Highlights:
The guide states that pages can remain in a duplicate cluster for up to two weeks after content is fixed, and that they can split more quickly when the new content is more distinct from the rest of the cluster. Google groups pages it reads as having the same or very similar primary content and then selects one as canonical. The two-week window covers content fixes rather than redirects, a rel=”canonical” fix, or server misconfiguration, which the guide lists as separate issues.
Why it matters
The number gives you something to say to a customer who asks why the fix hasn’t been found yet, and it limits the wait to content changes rather than every canonical issue. Two weeks is the outer limit, not the standard wait. Whether Google comes around to your preferences in the end is another question.
Read our full coverage: Google says canonical re-evaluation can take up to two weeks
Theme of the week: You get a vote, not a veto
Three of the four stories this week are about the same thing. You provide input and Google has final say on how it is read.
The Canonization Guide’s starting position is that Google’s choice might be best, and it asks you to weigh that before resolving anything. Mueller’s response to the homepage button boils down to a change he wouldn’t expect anyone to see. His answer on A/B testing was that one version or another can be used for indexing, depending on how the test is set up.
The Images ad is next to it rather than inside it. This is a product change, not a statement about how Google reads your pages. This indicates the same thing, however, since the generated images give Search one more thing it can do internally besides what it finds on the web.
The leverage you always hold is the quality of what you offer. Pages can separate faster from a duplicate cluster when the content is clearly different and appropriate. elements give Google links it can crawl. Google is still deciding what to do with the two.
Best stories of the week:
More resources:
Featured image: PeopleImages/Shutterstock
