Warning: Unknown: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in Unknown on line 0

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 265

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 266

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 267

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 340

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 341

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 359

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 360

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 361

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 362

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 363

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 364

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 365

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 366

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 367

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 368

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 369

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 370

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 371

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 372

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 373

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 374

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 375

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 376

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 377

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 378

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 379

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 380

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 381

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 382

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-includes/script-loader.php on line 26

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-includes/script-loader.php on line 29

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-includes/script-loader.php on line 32

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-includes/script-loader.php on line 35

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-includes/script-loader.php on line 38

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 383

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 384

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 385

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 386

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 387

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 388

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 389

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 572

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-content/plugins/headspace2/headspace.php on line 21

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-content/plugins/headspace2/headspace.php on line 22

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-content/plugins/headspace2/models/headspace.php on line 24

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-content/plugins/headspace2/models/headspace.php on line 25

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-content/plugins/headspace2/models/headspace.php on line 26

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-content/plugins/headspace2/headspace.php on line 23

Warning: require() [function.require]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 601

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-settings.php on line 717

Warning: include() [function.include]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/affiliat/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/affiliat/public_html/wp-includes/template-loader.php on line 52
Reed Floren :Affiliate Spam

The Perfect Traffic Storm? Or just more waves of spam?

Traffic. When driving to work we all wish it would just disappear, but when running a website, we want to be choking on the proverbial fumes. Everyone who has a website no matter how big or how small, wants traffic. Even if you’re just a blog like me who’s intentions are set more on informing your readers than simply emptying their pockets, you want people to actually see what you’re doing.

When I started receiving emails about Perfect Traffic Storm and it’s promises that “I may never need to worry about getting enough traffic to your sites EVER again“, I was intrigued. Even though I don’t have all the sales pages, the review sites and more to promote in attempts to convert as many sales as possible, I’d still like to reach as many people as I can with this blog. Investigating a bit more however, I made some very interesting discoveries!

Take a look at the following two images and tell me what you see…

Perfect Traffic StormTraffic PythonNotice the big red writing? Look similar? No, they look identical and so do the entire sales pages for both! Perfect Traffic Storm’s sales page is a direct replica of Traffic Python’s. So much so you could even call it a… clone! Oh why hadn’t I had this example when writing the Affiliate Clone X blog post lol!

The funny thing is, there’s nothing really wrong with either product – you promote the program to earn credits which you then use to promote your advertisements on other people’s websites. Obviously there’s a little bit more to it than that, but you get the general idea. The problem I have however, is I find it really difficult to sign up to (or stay signed up to) a product that completely rips off someone elses sales page.

I mean, you just have to check out both pages!! Seriously, have to!! Open them up in tabs and flick between then as you read down. While some of the wording, mostly with regards to the testimonials have been changed, the layout, bullet points and information is identical.

Pay particular close attention to the “Banner Statistics” image about three-quarters down the page, the one with the 19.5% click through and 29.17% conversion. It’s the same image! Check out the Impressions count, clicks and sales. The numbers are the same. The only difference is that Perfect Traffic Storm photo-shopped out the dates shown in Traffic Python’s drop down section and under the graph.

From what I can gather so far, Traffic Python was released in July of 2009, whereas Perfect Traffic Storm was released November 10th of 2009. I can confirm the second release as I have 51 emails informing me of such. The thing is, there’s different owners involved. Traffic Python is claimed by Brett Ingram, while Perfect Traffic Storm was released by Mark Lareau and Todd Gross.

As I said, there’s nothing inherently wrong with either program, and supposedly PTS has upwards of 20,000 members now, which has to mean something (perhaps just a more aggressive promotion). Of course, if you are wanting to use it to promote and recruit to your ‘downline’ so you can then promote other products to people, a higher membership count is a negative – less people to recruit. Although for promoting your own sites via the slide-in ad impressions on other network sites, then PTS wins over Traffic Python for starting you with 1000 free ad credits.

I figure I might as well use those up to promote the blog since I have them :)

My question (actually two) to you all is:

  1. Have you used either of these products before and do you have anything you can share about them? And
  2. What is your opinion on the copying of someone elses sales page?

P.S. They say everything comes in three’s right? Well I found the third!! Web Traffic Juggernaut has an almost identical sales page to both Perfect Traffic Storm and Traffic Python. Same layout and information, just some slight variances with images used. That said, Juggernaut is also owned by Brett Ingram, so I would assume that it’s either the first draft of what was then made into Traffic Python, or he just really liked that sales page and reused it lol.

The Impotence of Proofreading…

The Impotence er, Importance of Proofreading… ;-)

TrifiliiatePayday

The above reminds me a lot of a grade school teacher’s corrections on some poor kids assignment. Sadly, that is not the case. Those spelling errors, misplaced words and grammatical errors are taken straight from Jani G’s sales pages. Yup, the same sales pages meant to inspire you to part with your valuable money to learn what ever this guy is teaching.

Trifilliate Pay Day is the product in question that first bought Jani’s use of “&” to begin a sentence to my attention. Chad Michaels sent me an email that was short, sweet and to the point. His friend discovered a technique that allowed him to make over $10,322 in just 24 hours and he did it without a list, any traffic, any products or any JV Partners. Sweet I thought, I should definitely take a look.

Ironically, Chad’s email ends with the line, “Jani will be taking this site down pretty soon, so i suggest you drop everything you are doing and go here rite now.” Oh amusement.

Unfortunately however, while the product may be everything Jani is promising, I find it hard to hand over my credit card when a sales page contains spelling errors, random capitalizations, a new paragraph for every sentence and begins a lot of those sentences with the symbol ‘&’. Maybe I’m old fashioned, but I was taught in school to never begin a sentence with the words ‘and’ or ‘but’.

Nowadays a lot of that has changed and you will often find sentences beginning with ‘but’, in fact some of the well known books such as Lord of the Rings do just that. I too occasionally drop a but in at the beginning, however I will always make sure I never begin with the word and, let alone the symbol &. (One sentence actually begins with …& )

Trifilliate Pay Day is apparently the way to make lots of money without a pre-existing ‘list’, without the use of PPC and other common marketing tactics. In theory this is great, and my issue has absolutely nothing to do with the product itself – I have not purchased it so can not make any claims on that. (If you have, or do and would like to share your thoughts, please post a comment, I’d love to know!) What gets me however, is the fact that this newly discovered technique earned Jani over ten thousand dollars in 24 hours and yet, he didn’t think to outsource his sales page copywriting?

After some researching I discovered Jani G’s blog which contains the same use of the ‘&’ symbol to begin sentences which only confirms that he wrote his sales page as well. I also discovered he has a previous product called Twitter Traffic Exposed that contains the exact same trademarks as well as a few other wonderful spelling mistakes, matched only by the affiliate page for the same product sporting words such as ‘Basiclaly’ and even a double punctuation example of an exclamation mark with a full stop (!.) The $11k In 4 Hours Blueprint sales page does better… not perfect, but better lol. Does that mean he’s getting… worse?

What does all this tell me?

  • For someone who makes tens of thousands of dollars, he won’t outsource his copywriting and prefers to write it himself which is fine but…
  • Jani doesn’t take the time to run a spell checker over any of his sales or affiliate pages
  • He likes to begin sentences with the symbol &, ellipses (the … ), or a combination of both.

Do any of these traits affect his ability to make money? Apparently not. Teaching you to make money? No, not if you can ignore it all. I personally would get too distracted, especially obvious spelling errors or missed words in sentences, but then I have been labeled a grammar nazi on quite a few occassions lol. Yes, I have high standards, but when I am parting with hard earned money, or wanting to learn how to make lots more, I’m not going to give it to just anyone. If I read two sales pages, one of which has been spell checked and proof read, and the other belongs to Jani, I know which one I’m going to spend more time considering.

In this day and age, nearly all software used to write up something like a sales page comes with built-in spell checking facilities. And if it doesn’t (hard to believe but let’s go out on a limb), then copy and paste into one that does.

Sorry Jani, I’m sure you’re a really sweet guy, but please, have someone run a spell checker over your sales pages before you send them live, I’m sure you can afford it. Hell, pay me to proof read them for you!

P.S. Chad Michaels, what is with your 882 dashes (-) used to lengthen the gap between the end of your email and the unsubscribe link? Seriously?!
P.P.S. Or you Steven Johnson for copying them? Arg!