TL;DR
- Google will stop approving product images below 500 x 500 pixels in Merchant Center from 31 January 2027, PPC Land reported on 23 August 2026.
- The requirement arrived with the product data specification update of 14 April 2026, and Merchant Center has shown warnings in Needs attention since then.
- Google separately recommends 1500 x 1500 pixels or above for performance, and keeps the existing 64 megapixel and 16 MB ceilings.
- A replacement image at a new unique URL is recrawled in 24 to 72 hours; the same URL changed in place can take up to six weeks.
- The requirement is global with no Thailand-specific date, and Google has not said how already-disapproved items are treated before the deadline.
Google will stop approving product images smaller than 500 x 500 pixels from 31 January 2027. PPC Land reported on 23 August 2026 that the Merchant Center Help entry for the image link [image_link] attribute now carries a standing notice at the head of the page setting that date, and quotes Google saying it recently announced new image size requirements of at least 500 x 500 pixels for all products, beginning on 31 January 2027. After that date a product whose main photograph falls under the floor is disapproved, which removes it from Shopping ads and from cost-free listings at the same moment.
The rule was not announced this week. It arrived with the annual product data specification update published on 14 April 2026, and Merchant Center has been surfacing warnings for non-compliant images in the Needs attention section since that date. What changed is where the deadline sits. It now has an Important flag on the attribute page that feed managers open most often, which is why it started circulating outside the feed specialist community in August. Roughly five months separate the current state of the documentation from enforcement, according to PPC Land.
Two numbers, one deadline
The same paragraph of documentation carries a second figure that is easy to read past. Google recommends images of 1500 x 1500 pixels or above to ensure best performance in all listing formats. That is a recommendation. The 500 x 500 pixel minimum is the approval floor, and 1500 x 1500 is what Google says its surfaces work best with. A merchant who re-exports a catalogue at exactly 500 x 500 will pass the check on 31 January 2027 while sitting at a third of the linear resolution Google points to for performance. Where a re-export is happening anyway, aiming at the higher number usually costs the same afternoon of work.
What image link actually requires
Image link is required for every product and it accepts one value. Where a merchant holds several photographs of one item, the main photograph goes into image link and every other shot belongs in additional image link [additional_image_link]. According to the documentation, any subsequent values placed in the field are ignored rather than rejected loudly, which is the kind of failure that hides for months inside a feed that looks healthy.
The formatting rules are narrow, and more feed errors come from them than from the pixel count:
- The value is a URL starting with http or https, restricted to ASCII characters, compliant with RFC 3986, and between 1 and 2,000 characters long.
- Accepted formats are JPEG, WebP, PNG, GIF, BMP and TIFF.
- The file extension has to match the real format of the file. A mismatch returns an Unsupported image type error rather than falling back silently to something that works.
- Symbols inside the URL need percent-encoding. An ampersand becomes %26 and a comma becomes %2C.
- robots.txt has to allow both Googlebot and Googlebot-image, and a change to that file takes 24 to 48 hours to register after the product data source is re-uploaded or reprocessed.
Google names third-party platforms as a common source of the extension mismatch and tells merchants who sync images from external systems to verify that those systems produce correct image URLs and formats. Products failing any of these tests are disapproved, and the reason appears in the Diagnostics section of the account.
The recrawl schedule decides how long a fix takes
The most actionable fact in the documentation has nothing to do with pixels. According to Google, submitting a new and unique URL for a replacement image signals a change and prompts a faster recrawl, typically within 24 to 72 hours. Updating the image content while keeping the same URL can take up to six weeks before the system detects the new file and recrawls it. During the window after a new URL is submitted the product is listed as Under review, and the previous image keeps serving until the new URL processes successfully. For a product being added for the first time, the image is typically crawled within three days.
Read against a calendar, that asymmetry moves the deadline. A merchant whose content management system overwrites files in place and keeps the same paths is not working towards 31 January 2027. They are working towards a date roughly six weeks earlier, because six weeks is the stated ceiling on how long Google may take to notice a replacement at an unchanged address. A merchant whose export writes fresh filenames has a working window of a few days and can leave the job later, at the price of a larger last-minute batch.
A second instruction pulls the other way. The documentation warns against unstable URLs carrying timestamps or components that change on every submission, because each change forces a recrawl and loads the merchant's own servers. A bulk migration therefore has to be sequenced rather than run in one pass: one deliberate URL change per product to trigger the recrawl, then stable paths afterwards. Google also points merchants at the URL inspection tool in Search Console to test a sample of image links before pushing a large batch through.
The figures that decide the work fall into two groups: what an image has to be, and how long a change to it takes to land.
| Item | Figure | What it governs |
|---|---|---|
| Minimum image size | 500 x 500 pixels | Approval floor for image link from 31 January 2027 |
| Recommended image size | 1500 x 1500 pixels or above | Google recommendation for performance across listing formats |
| Recrawl at a new unique URL | 24 to 72 hours | Typical time for a replacement image to be picked up |
| Recrawl at the same URL | Up to six weeks | Time before an in-place image change is detected |
| Existing ceilings | 64 megapixels and 16 MB | Upper bounds that continue to apply alongside the new floor |
Ceilings still apply
The 500 x 500 pixel minimum arrives alongside two upper bounds that already existed: no image above 64 megapixels, and no file above 16 MB. A catalogue moving from thumbnails to full-resolution assets is working inside a defined band rather than uploading the largest file on the shelf. Merchants replacing tens of thousands of images with camera originals should test the 16 MB ceiling before the batch runs, because a job that fails at the top end burns the same recrawl time as one that failed at the bottom end, and the second attempt starts the clock again.
Who is covered automatically and who is not
Google said in the specification update of 14 April 2026 that some smaller images will be optimised automatically to meet the new requirement, avoiding disapproval without action from the merchant, with those images marked by a warning inside Merchant Center. The scope of that coverage has not been published. No threshold has been given for which images qualify and which fall through to product image disapproval, so the warning flag in the Needs attention section remains the only account-level signal available before enforcement starts. Planning a catalogue around automatic optimisation means betting on an unpublished number.
Automated handling of merchant imagery has a mixed record on the platform. Smart cropping, an account-level default that crops or zooms product images, was documented in November 2025 with no opt-out available in the interface, and merchants had to contact support to switch it off. The image link page confirms the underlying behaviour, noting that images may be cropped automatically while Google experiments with display options. A merchant who uploads a compliant 1500 x 1500 asset can still see it presented in a form they did not choose.
One disapproval removes a product from more than Shopping ads
Product imagery feeds more surfaces than it did when the 500 x 500 threshold was first discussed. The Shopping Graph, which Google has said contains more than 50 billion product listings, supplies free listings, AI Mode, Gemini shopping experiences, virtual try-on in Google Lens and standard Shopping ads from the same product data. A disapproved image takes the product out of all of them at once rather than out of one campaign type, so the reach of an image problem is wider than a Shopping ads report will show.
Measurement moved at the same time, which makes a drop harder to read. Merchant Center free listing reporting changed on 24 August 2026, splitting YouTube affiliate traffic out of organic totals and shifting the organic figures. A brand visibility report for AI Mode arrived in May 2026 with an attribute completeness score. Anyone comparing traffic before and after a feed change over the next few months is comparing against a baseline that has been redefined in the interval.
The deadline also lands in a busy compliance calendar. Google forced retailers to split product IDs for online and in-store items from March 2026, tightened the out-of-stock buy button rule in the same month, dropped the Next branding from the platform in July 2026 and consolidated two Shopping policy sets in September 2026. Several of those changes reached merchants through a documentation edit rather than a direct notification, which is the same route the image deadline took.
What this means for Thai marketers
Nothing in the documentation is specific to Thailand. The requirement is global, it applies to every Merchant Center account in every market where Shopping ads and cost-free listings run, and the source gives no separate Thai date and no regional exemption. The exposure here is structural rather than regional, and it is worth labelling the next part as analysis rather than as reporting: a large share of Thai Shopping feeds are generated from marketplace exports or from ERP systems whose image fields were sized for a marketplace product card, not for a Google listing. Those exports frequently carry 300 or 400 pixel thumbnails, because that is what the upstream platform stores as its working copy. Where that is the case the fix is a re-export from the original assets, not an edit made inside Merchant Center.
The second piece of analysis follows from the recrawl rule. Many Thai feed setups serve images from a fixed CDN path built out of the SKU, which means a replacement lands on the same URL and inherits the six-week detection ceiling. Changing the path pattern once, so that the re-export writes new unique URLs, turns a six-week wait into one measured in days. Teams running e-commerce marketing programmes with a product feed at the centre of them should treat that as a scheduling decision to make now, not a technical detail to settle in January.
Four checks are worth running in the account this week. Open Diagnostics and read the image warnings already sitting in Needs attention, since they have been accumulating since April 2026. Pull the image URLs out of the feed and measure the real pixel dimensions of a sample instead of trusting the template, because a template can declare a size the stored file does not have. Confirm whether the store platform writes a new URL on image replacement or overwrites in place, which is a question for whoever maintains the store rather than for the ads team. Then check the original assets exist at a usable resolution at all, because a catalogue whose masters were discarded after the first upload has a photography problem rather than a feed problem. For Shopify catalogues the image pipeline and the feed app are often configured by different people, and Shopify SEO work touches the same asset library the Shopping feed reads from.
What the source did not say
Several things sit outside the documentation and should not be filled in by inference. Google has not said what happens to items that are already disapproved on image size before 31 January 2027, nor whether the existing warning state converts to disapproval on that date or on the next crawl after it. It has not quantified how many undersized images will be optimised automatically. It has not published a test that separates an acceptable enlargement from an unacceptable one, which matters because the best practices section tells merchants not to scale up an image or submit a thumbnail, while Google itself ships a resolution increase function inside Product Studio and exposes upscaling through the Product Studio API. Any image regenerated with generative tools has to carry IPTC Digital Source Type metadata indicating machine origin, an obligation in place since February 2024 and unchanged by this deadline.
Resolution is also only one of the tests an image has to pass. The main photograph must show the whole product with minimal staging, and must not be a placeholder, a generic illustration or a logo outside a small set of named categories. Promotional overlays are prohibited, including calls to action, price information, free delivery claims, watermarks and borders. Best practice puts the product at no less than 75% and no more than 90% of the image area, on a solid white or transparent background. A bulk regeneration project touches all of those rules at once, which is an argument for starting with a sample rather than the full catalogue.
Frequently asked questions
Is the 500 x 500 pixel minimum blocking my products right now?
No. Enforcement starts on 31 January 2027, and until then an undersized image produces a warning in the Needs attention section rather than a disapproval. The requirement has been in the specification since 14 April 2026, so those warnings may already be sitting in the account.
Does this apply to Merchant Center accounts in Thailand?
Yes, because the requirement is global and the source gives no market-by-market schedule. The documentation describes one date, 31 January 2027, applying across Shopping ads and cost-free listings, and it does not name Thailand or any other country separately.
My images are 800 x 800. Do I have to do anything?
They clear the minimum, so no action is needed for approval. Google separately recommends 1500 x 1500 pixels or above for performance across listing formats, which means an 800 x 800 catalogue is compliant while sitting below the recommendation.
How quickly will a replacement image start serving?
Typically within 24 to 72 hours when the replacement is submitted at a new and unique URL, and up to six weeks when the file is changed at the same URL. The product shows as Under review during the recrawl, and the previous image keeps serving until the new one processes.
What happens to products still disapproved after the deadline?
The source did not say. The documentation states that failing products are disapproved and that the reason appears in Diagnostics, but it describes no grace period, no staged enforcement, and no different treatment for items that were already flagged before 31 January 2027.
A feed audit before the year turns costs less than an emergency re-export in January. Relevant Audience looks at product data and product page visibility together, and the same asset problem usually shows up on both sides, which is where SEO services in Thailand and feed work meet.
