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

Final URL error

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi,

 

I'm setting up an ad and AdWords Editor will not let me enter a final URL that is not the homepage. When I enter the URL of the landing page I want it to point to, it tells me simply that it is "invalid" when I try to post it.

 

Can anyone tell me why this is and how to resolve it?


Thanks

1 Expert replyverified_user

Final URL error

Explorer ✭ ✭ ☆
# 2
Explorer ✭ ✭ ☆

Hi Alan

What's your site and this URL? We can't foretell

Marked as Best Answer.
Solution
Accepted by topic author Alan L
February 2017

Final URL error

Google Employee
# 3
Google Employee

Are you editing a text ad, by any chance? Be aware that, as of Jan 31st, "standard" (as opposed to expanded) text ads can no longer be created or edited: https://support.google.com/adwords/answer/7048854

Re: Final URL error

Visitor ✭ ✭ ✭
# 4
Visitor ✭ ✭ ✭

Hi,

 

I added multiple keywords in the AdWords editor, such as "cheap sofa" or "+sofa +discount" - these keywords have the following final URL: https://www.living24.co.uk/?q=sofa&campid=sea-uk-123

 

When trying to upload these keywords to the Google AdWords UI, AdWords editor shows me a warning with the following status:

"Invalid Final URL. To post the keyword, edit the final URL."

 

All other URLs from the same account have the exact same structure - Does someone have an idea what the issue might be?

 

Thanks in advance for your help!

 

Final URL error

Google Employee
# 5
Google Employee

Do you recall, by any chance, when (on what date) you tried that and got this error? Better still, could you try again today, and respond here if you are still seeing the error? I'm trying to locate your failing requests in the server logs, and so far I'm unsuccessful. Knowing the date would help narrow the search down.

Final URL error

Google Employee
# 6
Google Employee

Never mind, found it.

 

There's an invisible Unicode character (U+FEFF, ZERO WIDTH NO-BREAK SPACE) in the middle of the URL, like this:

 

...?q=<U+FEFF>sofa&...

 

It is the presence of this character that the server complains about.

 

This character often appears as the first character in text files, to indicate the file's encoding (a so-called byte order mark, https://en.wikipedia.org/wiki/Byte_order_mark ). Not clear how it ended up in the middle of your URL - you may want to examine your workflow and figure out how it's creeping in. Meanwhile, you would need to remove it from your URLs before you can post them.