# Pulse · August 24, 2026

> Google sets a 500x500 minimum for Merchant Center images, Mueller says AI search needs no separate GEO tactics, and a favicon bug gets fixed.

Canonical: https://brandonlazovic.dev/pulse/2026-08-24/  
Author: Brandon Lazovic  
Published: 2026-08-24

## Google sets a 500x500 pixel minimum for Merchant Center product images, effective January 31, 2027

Status: Confirmed  |  Topics: product-feeds-shopping

Google emailed Merchant Center advertisers and updated its product-image help documentation to confirm a new minimum size of 500x500 pixels for all product images, effective January 31, 2027. Google still recommends 1500x1500 pixels or larger for best performance across listing formats. Images already below the 500x500 floor now trigger an "Image too small" or "Image too small due to upcoming policy changes" warning inside Merchant Center accounts.

In plain terms: Merchant Center is Google's product-data feed portal for Shopping ads and free listings, and a minimum image size just sets the smallest a product photo's width and height can be before Google stops treating it as usable.

Why it matters: Any merchant still feeding lower-resolution product images has until January 31, 2027 to fix them, and the warning already showing in accounts today is the advance notice.

Our take: Just over five months is a short runway for a catalog-wide image swap, and the smaller catalog owners who never revisit legacy product images are exactly the ones who will hit this floor first with no warning beyond an account-level notice easy to miss.

- [Google Merchant Center Help: Image requirements](https://support.google.com/merchants/answer/6324350?hl=en)
- [Search Engine Roundtable: Google Merchant Center Product Images Minimum Size Will Be 500x500 Pixels](https://www.seroundtable.com/google-merchant-center-product-images-update-41924.html)

## Google's John Mueller says AI search responses need no tactics beyond regular SEO

Status: Confirmed  |  Topics: ai-overviews-ai-mode, organic-search-core

Replying on Bluesky August 20 to a question about whether industries like adult or gambling content can skip GEO (generative engine optimization) entirely, Google Search Advocate John Mueller wrote: "there's nothing really special you need to do for generative AI responses in search." Search Engine Journal surfaced the exchange August 24. Mueller left unanswered a follow-up asking whether Google ranks those verticals differently under the hood.

In plain terms: GEO is the marketing term for tactics aimed specifically at showing up in AI-generated answers like AI Overviews or ChatGPT, rather than traditional blue-link rankings, and Mueller's answer says Google does not treat it as a separate discipline.

Why it matters: A direct, on-record answer from Google's own advocate undercuts any pitch that a site needs a separate GEO tactic stack distinct from standard SEO fundamentals.

Our take: Mueller's answer lines up with Google's standing position that AI Overviews and AI Mode draw from the same crawled index used for standard rankings, so a wholesale rebrand from SEO to GEO reads more like vendor positioning than a technical requirement Google has confirmed.

- [John Mueller reply thread on Bluesky](https://bsky.app/profile/galloni.net/post/3mtiocsxjic2a)
- [Search Engine Journal: Google Answers If Some Sites Can Ignore GEO And Just Focus On SEO](https://www.searchenginejournal.com/google-answers-if-some-sites-can-ignore-geo-and-just-focus-on-seo/586737/)

## Google confirms the favicon-disappearing bug is fixed, and a separate Crawl Stats data gap also clears

Status: Confirmed  |  Topics: crawling-indexing-rendering, measurement-analytics

Google VP of Engineering for Search Rajan Patel confirmed on X August 22 that the favicon-swapping bug covered here August 20 was being fixed, telling a practitioner "not fixed yet, but should be in the next 12 hours or so"; replies show favicons returning for some sites within a day, though not for all. Search Engine Roundtable separately reported the two-day Crawl Stats gap covered here August 22 also cleared that weekend, though unconfirmed by Google.

In plain terms: A favicon is the small site icon shown next to a result's title in search, and Crawl Stats is the Search Console report charting how often Googlebot requests your pages each day, so a gap there is a dashboard display problem, not proof Google stopped crawling.

Why it matters: Both bugs could look like a real ranking or crawl problem to anyone unaware they were platform-side, so confirmation the favicon fix shipped closes that debugging path for good.

Our take: Two platform-side data bugs clearing in the same weekend after roughly a week of unexplained noise is a reminder to check Google's own social channels for a known issue before spending time debugging a fetch or rendering problem that may not exist on your end.

- [Rajan Patel (Google VP, Engineering for Search) on X](https://x.com/rajanpatel/status/2091179760332530102)
- [Search Engine Roundtable: Google Fixed Favicon Bug & Crawl Stats Missing Data](https://www.seroundtable.com/google-fix-favicon-crawl-stats-41928.html)