AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
2.5K members online now
2.5K members online now
Understand Google's advertising policies, including ad approval status and account suspension
Guide Me
star_border
Reply

Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are fine.

[ Edited ]
Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

I have four ads that keep getting "disapproved". The reason given is Invalid HTTP Response Code.

 

If I copy the URL from my Destination URL field and go to that URL, I get a valid page, and using Firebug, with the Net monitoring turned on, everything comes back with Status codes of 200.

 

I reactivated the ads, so they went back to "Eligible" status, but within 10 minutes or so, I they returned to the disapproved status. But the site was up and I was still able to get to those pages just fine. 

 

Any ideas?  I contacted customer support to see if they can give me any additional details on what status code was being returned, but I won't hear from them 'til tomorrow.  Anybody else see this one before?

3 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by Zee (Community Manager)
September 2015

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are fine.

Google Employee
# 8
Google Employee

Hi sicignano,

 

> I understand how they might have originally been disapproved for invalid HTTP status codes...

> My site was temporarly screwed up for a few days last month.

 

That's probably it.  And sometimes if we get a bad result from a URL we'll remember that for a day or so, which means even an intermittent problem could cause multiple ads to get disapproved.  Right now, re-submitting them is the only way to get them re-reviewed.

 

> If an ad is disapproved because of an error on the URL, AdWords should give you an

> option to simply reactive it when you know things are back to being good again.

 

We're actually working on that exact feature.  I can't say anything about when (or if) it will launch externally or exactly what it will look like, but it's a common request and we're trying to get it done.

 

Laura

AdWords review engineer

View solution in original post

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are find.

Collaborator ✭ ☆ ☆
# 2
Collaborator ✭ ☆ ☆

Hi sicignano,

 

It's worth checking to see if you are using any keyword destination URL's as this can sometimes be overlooked and can cause this issue.

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are find.

[ Edited ]
Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭

That is a good suggestion, and I did see that mentioned in the help online. I checked and my keyword URLs are all blank.

 

So that doesn't seem to be an issue.

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are find.

Explorer ✭ ✭ ☆
# 4
Explorer ✭ ✭ ☆

Hi Sicignano,

 

Have you taged your URLs manually? If so, I would suggest you check the tagging.

 

Hope this helps.

- Neeti Ghildiyal
@NeetiGhildiyal | SMG Convonix | Join Us - Facebook | Twitter | LinkedIn

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are find.

Top Contributor
# 5
Top Contributor

Hello.

 

In case you have auto-tagging turned on, your URLs, when your ads get clicked, get transformed into something like somepage.html?gclid=1234, or somepage.html?parameter=value&gclid=1234.

 

If your website does not support them, it will return a 404. When checking your destination URLs, you did not include gclid and therefore the URLs (if this is the case) worked just fine.

 

Take one of the destination URLs and see if it still works after appending ?gclid=1234 or ?gclid=test to it. If it doesn't, either disable auto-tagging or make sure the website can deal with the gclid parameter.

Calin Sandici, AdWords Top Contributor | Find me on: Google+ | Twitter | LinkedIn | myBlog
Was my response helpful? If yes, please mark it as the ‘Best Answer.’ Learn how here.

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are fine.

Visitor ✭ ✭ ✭
# 6
Visitor ✭ ✭ ✭

I tested out that idea by adding some parameters to the end. Seems to work fine.

 

More progress though.  I was using the Google AdWords Editor.  When I saw these disapproved, and after checking out the ads to make sure they were good, and the URLs were good, I did the following in this order.

 

Changed the status of those ads to Paused

Uploaded changes

Changed the status of those ads to Activated.

Uploaded changes

 

They then showed up as eligible, but quickly went to disapproved (minutes)

 

This I tried multiple times.

 

On a whim, I tried the following.  I changed the ad text in some meaningless way, like adding a period, or swapping the two description lines, even though the ads were disapproved for invalid HTTP status codes.

 

And now they seem to be approved and staying that way.

 

I understand how they might have originally been disapproved for invalid HTTP status codes... My site was temporarly screwed up for a few days last month.

 

But it seems that getting those ads rolling again requires more than pausing and unpausing them. It seems like you need to make a change to one of the other fields, even though the URL and message text doesn't require a change.

 

If an ad is disapproved because of an error on the URL, AdWords should give you an option to simply reactive it when you know things are back to being good again.

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are fine.

Community Manager
# 7
Community Manager

Hi sicignano,

 

I'm escalting this to our technical specialists for further help.

 

Thanks, 

Mini

Marked as Best Answer.
Solution
Accepted by Zee (Community Manager)
September 2015

Re: Ads being disapproved for Invalid HTTP Response Codes - Destination URLs are fine.

Google Employee
# 8
Google Employee

Hi sicignano,

 

> I understand how they might have originally been disapproved for invalid HTTP status codes...

> My site was temporarly screwed up for a few days last month.

 

That's probably it.  And sometimes if we get a bad result from a URL we'll remember that for a day or so, which means even an intermittent problem could cause multiple ads to get disapproved.  Right now, re-submitting them is the only way to get them re-reviewed.

 

> If an ad is disapproved because of an error on the URL, AdWords should give you an

> option to simply reactive it when you know things are back to being good again.

 

We're actually working on that exact feature.  I can't say anything about when (or if) it will launch externally or exactly what it will look like, but it's a common request and we're trying to get it done.

 

Laura

AdWords review engineer

Re: Ads being disapproved for Invalid HTTP Response Codes - Destinatio

[ Edited ]
Visitor ✭ ✭ ✭
# 9
Visitor ✭ ✭ ✭

Check that you support HEAD only requests. The bot Google uses makes the lighter HEAD request and not the full GET request. There is an Apache tool that allows you to check the response code based on the request method.

 

http://www.askapache.com/online-tools/http-headers-tool/

Re: Ads being disapproved for Invalid HTTP Response Codes - Destinatio

Visitor ✭ ✭ ✭
# 10
Visitor ✭ ✭ ✭
I am having the same issue as sicignano. I just wanted to get clarity on one point. You mentioned the following...

>... sometimes if we get a bad result from a URL we'll remember that for a day or so, which means even an intermittent problem could cause multiple ads to get disapproved. Right now, re-submitting them is the only way to get them re-reviewed.

Is it the case that resubmitting will blow away the cached 'memory', or that one should wait a 'day or so' and then resubmit? I have gone through the same steps, and am still getting disapproved for http response, e.g. checking urls for errors, changing ads slightly and resubmitting, changing urls and resubmitting, checking with apache tool listed in the thread below, turning off auto-tagging.