Why was my Google dynamic ad disapproved?
Direct answerGoogle disapproves a dynamic ad when a feed image is the wrong file type, when the image cannot be retrieved, or when an address in the feed is not in an approved format. The dynamic ad requirements, reviewed October 19, 2026, apply to ads that pull products, services, or promotions from a feed you control. A blurry photo is a different policy.
The file type
An unsupported image format is not allowed. The note on the page is that images are only allowed in PNG, JPG, JPEG, or GIF. If you cannot convert the file, Google says to upload a different image that complies.
Best practice, not a disapproval rule: Google says that for best results you should save images in RGB with an ICC profile attached. The page does not say a missing ICC profile is itself a violation.
A photo that is blurry, rotated, or flashing is image quality. This page is whether the feed can fetch an allowed file type.
When Google cannot fetch the image
An unavailable feed image includes:
- Images that are missing, blocked by permissions, or otherwise inaccessible.
- Images that cannot be retrieved because of problems with the website’s SSL certificate.
Google’s troubleshooter then says to:
- Check the hosting server so the images are not blocked and the server is not taking too long to serve them.
- Host the image in an accessible location.
- Open permissions so the feed can use the image.
- Check the SSL certificate with an online tool, or switch to URLs that do not use that website’s SSL certificate.
- If the server cannot respond in a reasonable amount of time, move the content to a server that can handle image requests.
“A reasonable amount of time” is not defined on the page. If you cannot fix the violation, or you choose not to, Google says to remove the ad. The reason it gives is to help prevent the account from becoming suspended later for having too many disapproved ads. That sentence is on the troubleshooter. This requirements page does not print a 7-day warning.
Addresses in the feed
Addresses that are not formatted correctly are not allowed. Google’s approved methods are:
- City, state code, country.
- A full address with a zip code.
- Latitude-longitude in the DDD format.
Use commas to separate the address. The page also says to see the specs for cities, regions, and countries. Those specs are not copied here. A location pin on a Search ad, including owner approval and a permanently closed store, is the location asset rule.
The same page points dynamic ads at sexual content, unclear relevance, and trademarks when the feed item itself breaks those rules. A feed row that advertises a different business from the ad is the kind of mismatch unclear relevance already covers.
Sources
Reviewed October 19, 2026. Policies change. This is not legal advice.
Frequently asked questions
Which image files can a dynamic ad feed use?
Google allows PNG, JPG, JPEG, or GIF. Any other format is not allowed. Saving in RGB with an ICC profile is described as a step for best results, not as a separate disapproval rule.
The image URL works in my browser. Why is the feed image unavailable?
Google’s examples are a missing file, a file blocked by permissions, a file that cannot be retrieved because of the website’s SSL certificate, and a server that takes too long to serve the image. A URL you can open while logged in can still fail those checks.
How should an address be written in the feed?
Google names three approved methods: city, state code, and country; a full address with a zip code; or latitude-longitude in DDD format. Separate the parts with commas. The page points at a city, region, and country spec and does not reprint that list.
Check the feed before the ad
LaunchGuarding can scan the ad and landing page for policy risk while you fix the file type, the image URL, and the address format in the feed.