Can't tweet shortened URLs

[andreaog]

Hi everyone,

Twitter is blocking my tweets with the message

"This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later."

No matter what shortner I use, after a couple of tweets with the same url i get the above message.

If I shorten the same url again with the same url shortener provider it goes trough. But I'd like to use always the same url since i'm automating it. Is anyone else experiencing the same? Any solution?

Thanks a lot i advance

 

[Nonilol]

Even common link shorteners like bitly?

Or do you try to to share adfly (or similar) links with ads on it?

How often did you try to post it and why exactly do you want to share the same link more than once or twice in a short period of time?

 

[andreaog]

Even common link shorteners like bitly?

Or do you try to to share adfly (or similar) links with ads on it?

How often did you try to post it and why exactly do you want to share the same link more than once or twice in a short period of time?

Thanks for your answer - It happens with google, ow.ly, bit.do. I'm promoting Crakrevenue offers using Social Auto Poster plugin in Wordpress. This Wordpress automation system is set to post a tweet every 40 minutes (spinning around 5 tweets with mixed shortned urls)

 

[ChanzGrande]

Don't be silly. Just change the url for every post. There is no legitimate usage in your situation, so since you are spamming - you simply must change the url EVERY time you tweet it. That's all.

There's plenty of examples of best practices to do this. If you think it is too hard for you to do, then you are being ridiculous. Just get something setup. Plenty of us automate this without issue. You're just not being creative at all about this.

It does take SOME effort on your part to succeed you know?

-----------

Alternative posting solutions that easily allow you to rotate your short-urls in more clever ways include IFTTT, TwitterFeed, bots including massplanner and followliker, and custom coded PHP or other feed based solutions.

-----------

Your problem with SNAP may easily be that your primary urls were flagged. When snap posts, the content inside the wordpress post will be posted, however ... snap uses whatever url shortener you tell it to use in the settings, so every time it posts ... your primary posting domain is "invested" in this activity. So if your primary domain or IP was blocked, no amount of url shortener rotation of the "in-post" content will change that it's your domain and/or server IP making the post.

So an easy work around here might be to use some of honeybird's suggestions below using an alternate posting solution such as I suggested above. If your domain is blocked, you will need another domain to redirect and/or to directly url-shorten a direct link to offer.

 

[HoNeYBiRD]

Well, you can redirect a domain to the offer url, if url shorteners don't work.

Oftentimes the "issue" with url shorteners, that they don't generate different short urls for the same long url, no matter what, they will only generate the same shortened url, you can trick them though.
A method to generate different shortened urls for the same long url, if you append a slash, a question mark and some random string at the end of your long url like this and shorten the url after that:
domain.com/?1234
domain.com/?abcd
These long urls go to the same destination, but they're unique, so the url shorteners will generate unique short urls. You'll never run out of unique long/short urls this way.

It doesn't help if a particular url shortener or your domain is blocked by Twitter, but if you need unique short urls, it's a way to do it.

 

[andreaog]

Don't be silly. Just change the url for every post. There is no legitimate usage in your situation, so since you are spamming - you simply must change the url EVERY time you tweet it. That's all.

There's plenty of examples of best practices to do this. If you think it is too hard for you to do, then you are being ridiculous. Just get something setup. Plenty of us automate this without issue. You're just not being creative at all about this.

It does take SOME effort on your part to succeed you know?

-----------

Alternative posting solutions that easily allow you to rotate your short-urls in more clever ways include IFTTT, TwitterFeed, bots including massplanner and followliker, and custom coded PHP or other feed based solutions.

-----------

Your problem with SNAP may easily be that your primary urls were flagged. When snap posts, the content inside the wordpress post will be posted, however ... snap uses whatever url shortener you tell it to use in the settings, so every time it posts ... your primary posting domain is "invested" in this activity. So if your primary domain or IP was blocked, no amount of url shortener rotation of the "in-post" content will change that it's your domain and/or server IP making the post.

So an easy work around here might be to use some of honeybird's suggestions below using an alternate posting solution such as I suggested above. If your domain is blocked, you will need another domain to redirect and/or to directly url-shorten a direct link to offer.

I wouldn't have asked for help if the solution was to change the URL for each tweet.

What I have set up is:

One twitter account with two WP domain connected -

1st wp domain sends pictures taken from tumblr RSS - only pictures and not links to any offer
2nd wp domain is the one which is giving issues. Instead of posting random pics from Rss, I'm uploading pix manually and scheduling them every 40 mins with a URL to the offer.

The problem is not the domain as If I try to tweet manually the shortened offer it doesn't go trough either.

I was trying to automate the 2nd part (handpicked image+link with offer) with Hootsuite but was failing as well

The only one which worked is Buffer, but it's limit are 10 posts a day only.

 

[living2xl]

I didn't get this type of problem ever with twitter.
But I think there is any problem with URL shortner. I don't think there'll be any other problem