Does this sound familiar?
Sort of like How To Grow Website Traffic to Over 100,000 Visits Per Month, but with an extra zero…
Well it is, sort of – same author, different case study.
This time I’m going to break down the changes I made to YourListen.com that increased organic traffic to the site by more than 300% in 18 months, to over 1 million visits.
My 100,000 visit case study was about building and launching a new website in Japan that my team and I grew to over 100k visits per month, in just 9 months.
This time was a bit different;
- The website wasn’t new.
- It already had a decent base of traffic (~230k/mo).
- We created 0 content (yes, ZERO) – this site is 100% UGC.
- I had no team outside of myself, the owner, and his developer.
Although there were a few elements that remained the same;
- This website’s content is all UGC, or user-generated content, vs. the last time where 95% of the content was UGC but my team picked topics to write seed descriptions for.
- We did not spend $1 on paid advertising of any kind; all traffic is 100% organic.
- Pumpkin hacking was key.
The reason I’m writing this post is to walk-through the nuances between traffic growth for a new site versus attacking growth for an existing site.
Many of these principles (if not all) can and should be applied to new sites.. but in this case, these changes were used to unlock growth potential.
Table of Contents
Key Drivers To Growth
The following 3 areas were the strategic elements that had the biggest impact on organic growth.
To re-visit a still hugely important piece of SEO; pumpkin hacking. We paid attention to which pages were not only picking up the most steam in terms of traffic, we took some extra steps to make sure these pages got as much of boost as we could give them.
To give these pages the little extra boost we could, we used one of the most powerful tools we had for search; our website.
Sounds super obvious and a bit stupid doesn’t it? But seriously, perhaps the most commonly overlooked factor for driving organic growth brings me to my next point;
We added links with target anchors to the homepage, created new sections on top-level pages to display links for “featured content” around the site, and baked new views into site-wide navigation.
In addition there were some very specific things wrong with the way the code was built and being rendered on the pages, which I’ll come back to in a bit.
Leveraging a mix of Google’s Webmaster Tools, a lot of blood and sweat in development hours to get things right, and amazing tools like URL Profiler; cleaning up the site’s foundation has proven invaluable.
Special thanks to Patrick and Gareth at URL Profiler for all your help with the massive crawl logs for YourListen.
One interesting tool that only some of the smartest digital marketers on the internet know about, and even more so, know how to use – is traffic leaks.
This strategy involves engineering large amounts of short-term traffic to your site, by acquiring (or leaking) that traffic from another site that already has all the traffic you want. Perhaps the most popular site for running these kinds of campaigns is Reddit.
We didn’t use Reddit, but we did put a lot of time into building relationships with people who held similar keys to kingdoms of huge traffic.
As a music and audio hosting site, and after taking a hard look at analytics, we found that our big traffic events happened when new music was released; and more specifically, when it was released on our site.
So how do we make sure we become the source for music leaks? Build relationships and mindshare with the people who have access to this content.
To do this we leverage the relationships with the lowest barrier of rejection; existing power users on the platform.
You’d be amazed at how many people who use your tools are genuinely willing to help, just because you ask.
A Look At Traffic Growth
When I first joined the YourListen team:
18 months later:
When I first came on the site was averaging between 7 and 8,000 visits per day, and while we’re now averaging closer to 25,000 visits per day, we’re not yet at the 1 million visit per month run-rate.
We did finally hit that milestone (as you can see above) but we’re not all the way there; our current sustainable run-rate is closer to 800,000 visits per month.
Here’s how that traffic breaks down in terms of acquisition channels:
Let’s Talk About One Time Events
Coming back to this idea, cause it’s critical to hitting these kinds of traffic levels – when you are able to have these big traffic events a couple times per year, it has an amazing effect on your overall residual traffic.
What we’ve noticed is that even after the URL’s that drive these traffic spikes stop receiving huge temporal increases in traffic, the overall site traffic lifts up, and stays there.
Notice in the screenshot above that 3 days after the spike, as traffic is starting to level back off; it begins to grow again, all on its own.
What’s Causing This?
Those large spurts of traffic generate awareness, which leads to an increase in traffic from all channels; direct, social, and of course organic.
They directly lead to increases in branded search, type-in traffic, and social referrals. All sending a lot of positive trust signals throughout the interwebs.
All of these contribute to what I’ll call the trust graph of your website from a search engine perspective, not to mention the links 🙂
One of the leaks on YL gained so much attention it resulted in links from some big websites like Billboard, USA Today, and other major media news outlets.. not to mention, a phone call from Prince.
Back To On-Site SEO
There were some really specific things that needed to be fixed, as well as some enhancements that started to really make a difference.
Let’s start with the things that we needed to clean up.
Taking a closer look at the track pages (the individual URL’s that comprise more than 95% of the site’s content), I realized that the track titles that were being displayed lived within the custom Flash player, not in the pages HTML.
What’s worse? The page not only had no H1, but the track title was being rendered in the HTML, but then hidden with a display:none tag in the CSS.
Bad, bad, bad.
Google parses all of this HTML and this looks shady as hell.
The fix was simple; pull the track title out of the flash player, turn on the HTML version, and wrap it in an <h1> tag.
Looking at the way the URL’s were built, not only were they not using the most ideal naming conventions to create optimized topical relevancy (woohoo keyword research!) but they were all flat.
Flat URL’s work when you have extremely horizontal content sets, like Wikipedia, but they fall short when you have big top-level content groups that all of your other content fits into.
So we organized all the content types into 2 master parent directories;
- Audio, and
Optimizing Crawl Budget
This is far from a new concept, however, I still constantly meet and speak to “SEO’s” who give this no consideration.
Which is real stupid.
While Google doesn’t exactly have limited resources, it does start to pay less attention to your site’s pages and the importance it assigns them based on what it finds when it crawls your site.
Using a combination of your site’s robots.txt file and the URL Parameter management console within Webmaster Tools, you need to help Google help you.
What I’m talking about is filtering out URL parameters that are not priorities.
For YourListen this meant taking the URL’s that hosted the embed-able player, the source .swf files, a handful of code assets and moving these to their own directories so they could be blocked from being crawled, like so:
and then going into the URL Parameter manager in WMT and blocking all the parameters that don’t merit having every variation crawled;
Building Optimized Sitemaps
For all the veteran SEO’s reading this you already know how important these files are, but let me share some learning with you.
I’ve worked on large sites, but I can honestly say that YourListen was probably the largest – with millions of individual content pages.
In case you didn’t know, Google limits it’s individual sitemap crawls to 10MB and 50,000 URL’s.
But, based on my first hand experience, we found that limiting individual XML sitemaps to 35,000 URL’s yielded a far more effective crawl.
Furthermore, we found that not only nesting sitemap files into indexes improved the efficacy of the crawl rate but that actually linking (like with <a> tags) helped us maximize the number of URL’s that were parsed during the crawls.
and finally, I found that when I uploaded the sitemaps it helped to not only test them for errors (confirming to Google that they’re properly formatted and clear of errors) but then also re-submitting them everyday for a few days; essentially brute-forcing the re-crawl.
Unfortunately you can’t set a date range in Webmaster Tools so I can’t show how big of a difference the above changes made to the index rate, but I can show the effect this has had for at least the past 10 months:
The biggest learning I hope you take away from this post is just how incredibly important it is to be meticulous when it comes to the cleanliness of your site’s mark-up and structure.
In addition, here are your TL;DR points:
- Leverage your site’s internal link equity and your strongest page’s citation flow. Use this to your full advantage to send link equity to the pages that need it most.
- Optimize your site’s crawl budget and make sure you’re not wasting Googlebot’s time crawling pages with thin or near-duplicate content.
- Don’t underestimate the power of properly built and optimized sitemaps, and make sure you’re submitting the shit out them through Webmaster Tools.
- Put in the work to engineer a few big traffic pops, while they may only be a flash in the pan in terms of growth; the sum of these parts will create a larger whole.
I am a Partner and Investor in YourListen.com, and we are looking to sell the site and all related assets. If you are interested, you can check out our sales deck here ›