This article was published in the December 2015 issue of Maximum PC. For more trusted reviews and feature stories, subscribe here.
Don’t overheat—get your feet wet with these water-cooling tips
For much of recent history, water cooling has been shunned. Only a select few could afford to merrily dance with computing death, taking their chances with water-cooling hardware and components that weren’t even designed to work in the silicon environment. They’d graft plumbing fittings onto hardware and hand-mill various water blocks, all in the hope of creating a leakproof, watertight system that could efficiently and effectively transfer heat away from their component parts, to a far greater degree than traditional air coolers ever could.
That was back in the times when the average PC enthusiast was less concerned about how a PC looked. More important was how many frames per second they could squeeze from their beige box of dominance in Unreal Tournament. It was a terrifying time. But over the last five years, the situation has changed dramatically.
Water-cooling manufacturers and modding companies—such as EKWB, XSPC, Primochill, Bitspower, and E22—have come to the forefront in far greater numbers. This is when water cooling really began to take center stage. Indeed, today you’d be hard-pressed to find a high-end system that’s not running some form of all-in-one CPU cooler or a custom loop. Hell, all of us here at the Maximum PC office would run hard-piped builds if we could, and there isn’t one of us still stuck on the retail cooler, or even an air cooler for that matter.
So, what is it that attracts people to water cooling? Why is it so much better than traditional air cooling? Essentially, all forms of cooling work on the same basic principles. You might have heard of them, they’re part of the laws of thermal and fl uid dynamics. No matter whether you have an air cooler or a full custom-loop setup, you’re transferring heat from one point to the other. It then cools and circulates back around again to transfer that heat out of the system to the outside environment again and again.
All very fancy, right? Air cooling technically isn’t an accurate description of that cooling method, and neither is water cooling—they both essentially require a fan and a radiator to expel that heat. So, is water cooling for you? Should you dive into the murky depths of H2O nirvana? Maybe you’ll discover something about yourself along the way. Read on to find out.
Why Water Cool?
Let’s cut straight to it. Primarily, water cooling is done to enhance the aesthetic beauty of a build. Don’t get us wrong, the heat-reducing properties of multiple radiators and fans cooling your internal components is fantastic and highly effi cient. But if you’re looking for the most effective price-to-performance ratios, a good AIO cooler for your CPU and a triple-fan GPU cooler would be more than enough to ensure you never hit any of the thermal limits dictated to us by our silicon-inducing overlords. And in today’s technological climate, you’re far more likely to encounter hardware-based limits, rather than temperature-based ones, in your overclock attempts.
One of the biggest benefits of water cooling, besides looking better than Gabe Newell’s monthly bank statements, is the noise reduction. Simply put, noise control is all about effective fan control. It’s not necessarily how many fans you have, but how fast they’re spinning. Ultimately, the lower the RPM, the lower the noise output. For instance, if you take five 120mm fans and run them at 1,200rpm, and then take two separate 120mm fans and run them at 3,000rpm, we can guarantee the two fans will be creating more audible noise than the five.
Water cooling is primarily about enhancing the look of your build, ensuring your silicon shrapnel stands out from the crowd and looks as good as it possibly can. There are multiple ways of doing this with water cooling. By all means, we’re not saying that air-cooled builds can’t look good—there are some seriously stunning rigs out there that run on simple old air coolers. But water cooling sits at the centre of the modding community. It’s responsible for most of the innovations we’ve seen in this area of the market. Whether that’s braided cables, windowed-side panels, or LED lighting, you can assume that the vast majority of these ideas originated from some modder out there grafting an idea onto one of their builds, and then showing it off to the masses.
One of 8 Pack’s stunning hard-piped copper tubing builds. An excellent example of what you can do aesthetically to make your build shine.
So, you have four options in total when it comes to liquefying your machine. First, you could simply just use an all-in-one cooler. This way, you avoid the hassle of setting up any kind of crazy system, you’re covered by a warranty, and still gain the benefits of having a water-cooled CPU. Your second option is to go with a soft tubing loop, utilizing flexible colored or clear tubing. This is one of the most adaptable water-cooling methods as the tubing is flexible and easy to use.
The third and currently most popular option is to use acrylic tubing, most notably PETG tubing. This non-fragile, highly robust hard piping creates an entirely different look for a build, utilizing straight lines and angles to really make your rig pop. And then, finally, there’s copper tubing. It’s identical in almost every way to acrylic tubing, except it’s far easier to bend and a lot cheaper. Copper provides a good base to either nickel or chrome plate or even powder coat as well, though it’s opaque. Whichever way you choose, you’ll still benefit from the reduced noise and the far-superior cooling capacity that water cooling provides.
If you thought that building a custom PC was tricky enough, then we’ve got some bad news for you. Here’s a quick rundown of what you’ll have to consider purchasing on top of your standard build. You’ll need: a case, tubing, radiator(s), a CPU block, GPU block(s), GPU backplate(s), memory block(s), reservoir(s), pump(s), compression fittings, angled fittings, bulkhead fittings, stop valves, coolant, and fans. Once you’ve decided how you want to cool your rig and what chassis you want to cool your build in, then it’s a simple matter of pricing your choices, throwing it all in the basket, and breaking your wallet in two as you fork out for an expensive exercise in modding.
By far the most obvious component to cool your rig. You’ll need to make sure you buy a CPU block that’s compatible with the chip you’re trying to cool. More often than not, this is just a simple choice between Intel and AMD, as processor sizes don’t tend to vary greatly.
EK’s Supremacy Evo CPU block provides incredible cooling with a simple mounting mechanism. We went transparent to show off our snazzy white pastel coolant.
Predictably, GPUs experience the greatest deal of variance. Both in the design of the PCB and in which graphics processor you choose as well. You’ll need to make sure you buy a compatible block for your card. Some manufacturers, such as EKWB, will often include specific water blocks designed to work with aftermarket cards such as Gigabyte’s Windforce, MSI’s Lightning, or the Asus STRIX series of cards. This may extend as far as the backplate as well, so always double check.
Whether or not you decide to cool the RAM with your custom loop is entirely up to you. The modules certainly do output heat. But really, it just looks more awesome than anything else. Besides, nobody will penalize you if all you’re looking for is to cool your CPU and GPU. You’ll also need compatible RAM modules that match up with your water blocks.
Some of the most important parts of your build are the fittings you choose to use. Depending on what tubing you decide to use, you’ll need either compression fittings or acrylic fittings. Although acrylic fittings are still technically compression fittings, they’re designed to work around hard tubing by not crushing the acrylic as much, unlike traditional compression fittings, which tend to have a greater pinch to them. If you’re looking for a basic build, you can usually get away with just the standard fittings.
However, if you’re looking at designing a build with cleaner lines and a little more flare, you may want to invest in some angled fittings as well, usually stipulated at 45 or 90 degrees. Additionally, a stop valve might come in handy for loop maintenance.
Technically, you don’t need to buy a reservoir to successfully run a water-cooled loop. However, they do look rather impressive, and make it a lot easier to fill a water-cooled system than using other methods. You will, however, always need a pump to ensure that the fluid within your system is flowing, and pulling heat away from your core components and out to the radiators. Additionally, you should always have your pump gravity fed (meaning fluid should always be flowing down into it).
Radiators and Static Pressure
At this point, you need to look at how you’re going to output that heat. The only option you have is to use radiators. You can do this however you like, either by using separate loops for your GPUs and CPUs or by combining the two together into one single loop. But you’ll still need radiators to get rid of all of that heat, and accompanying fans to reduce this per loop.
Once you’ve decided what space your case has for radiators and how many you’re going to use, you need to take a closer look at the FPI and thickness of the radiators you’ll be using. FPI stands for fins per inch. Essentially, the higher the FPI, the higher the static pressure you’re going to need to effectively move cool air through that radiator. For instance, if you have a radiator with an FPI of 38, you’ll probably want static pressure optimised fans. However, if you have deeper radiators with a lower FPI of 16, you won’t see any comparable difference between static pressure fans or airflow fans. In fact, in these cases, you’re often better off equipping them with airflow fans instead.
Where to Buy?
There isn’t a fantastic array of places where you can buy a lot of these components in the United States. But one of the largest water-cooling specialists in the country is Frozen CPU (www.frozencpu.com), which has a vast selection. Additionally, if you’re a little more patient and want to ensure you’re getting EKWB directly from the source, you can buy straight from EKWB’s site (www.ekwb.com). Also, here’s a special shout out for EKWB, without whom there simply wouldn’t have been any way to provide this first look into water-cooling for y’all.
Planning Your Loop
So, at this point, you should be well aware of all the hardware you’ll need to consider. Next, you want to research which case is best. There’s a huge variety out there. In fact, you’ll find there are watercooling cases from Mini-ITX chassis all the way up to full E-ATX super towers. Once you’ve found your case, check what radiators it can support for water cooling. Then you need to think about your tubing and how you’re going to cool it—a single loop or dual loops. Once you have all these decisions nailed down, your best bet is to sketch out how you want to run your loop, and how many fittings you’ll need for all your hardware. Usually, you’ll need two fittings per water cooling item—one in and one out.
Even if it’s just a shoddy Photoshop design, planning your build visually will save you time when it comes to figuring out how many fittings you’re going to need and how best to run your cooling loops.
For us, the choice was pretty simple. We’d use the Fractal Define S, a case designed from the ground up for easy water-cooling installation. A dual radiator at the top and a triple rad at the front. On top of this, we’d be using a single closed loop to cool both of the EVGA Superclocked GTX 980 Ti cards and the Intel Core i7-5820K. Then it was a matter of tallying up how many fittings we needed, taking into account we’d be using soft tubing and a pump/res combo, as well as planning how our build would look. We’d be using an Asus X99 Sabertooth TUF mobo—stunningly gorgeous and covered in blackand-grey-plated armor. On top of this, we managed to get hold of a mixture of black water blocks and fittings. We’d use white coolant to add a little contrast.
Choosing the Chassis
Picking the right case can be a tricky business, especially when you’re looking to do a water-cooled mod such as this. The best way to do this is to look out for cases designed particularly for water cooling, or by companies who revolve around it. Parvum, Phanteks, Corsair, Caselabs, and Fractal are all fantastic case firms that provide some excellent chassis to work and build in, making it easy to create a stunning work of art.
Selecting the right case is undoubtedly the biggest consideration you have to make. It will dictate where your reservoir goes, how many radiators fit and what thickness they are, plus how your tubing runs will work. For instance, we tried to build this particular setup inside the Phanteks Enthoo Evolv, but we’d already pre-ordered the water-cooling components for a different chassis and they ended up being incompatible with the Phanteks, even though that’s a huge case to work in.
Fittings and Loops
And so begins the building process. Of course, like with our regular builds, we advise that you build all your PCs outside of the case first, just to see if they work. We individually tested both our GPUs, the memory, and the CPU with traditional coolers, before throwing water blocks on any of it.
Once you’ve installed your base components, you’ll have a better idea as to how to run your cooling loops.
Then we began the internal build process, stripping the chassis of any unwanted components, such as hard drive bays and cages, and continued to install the motherboard, the memory, and the GPUs, securing them firmly to ensure that nothing would fall out or become damaged over the course of our build. We also took this opportunity to install the radiators and plug in the fans where they were necessary. It’s also time to attach the reservoir, and install all of the fittings.
In a build like this, cable management needs to be flawless. The last thing you want is excess, untidy cables cluttering up your rig. Not only will they get in the way of the tubing, they’ll also restrict airflow and generally make your tubing routes that little bit more difficult. Cablemod (www.cablemod.com) provides custom-sleeved cables for Be Quiet!, Cooler Master, Corsair, EVGA, and Seasonic power supplies. These should spruce up your build quite nicely. Alternatively, it’s not impossible to sleeve the cables yourself. This takes a lot more time and patience, but you can include cable combs to keep the cables tidy, plus vary your color schemes.
We’ll admit this isn’t the tidiest cabling, but doing a good job at the start will save you time in the long run.
Additionally, we used the Phanteks PWM Fan Hub. Threading all five Noiseblocker fans through one fan controller means we can control how much power they receive directly from the CPU fan header, meaning the system will ramp up or down dependent on CPU temperature (which, admittedly, will be quite low for this build).
Building and Priming the Loop
At this point, it’s time to start your tubing runs. Line up a stretch of tubing between the two points you wish to connect, then cut a little more off than you think you’ll need. It’s better to have too much than too little—you can always shorten the runs later. Next, unscrew one of the fi ttings, wiggle your tubing onto the fitting, and thread the other end of the compression fitting onto the unattached end. Then screw it down, compressing the tubing in place.
If you’re struggling to fit the tubing on, use a pair of needle-nosed pliers. Gently insert them into the end of the tubing and carefully stretch the tubing slightly, so it’s easier to work. Then you’ll need to take the sleeve off the other fitting, pre-attach that to your new tube and do the same with the other end. It’s then simply a case of running all of the tubes to their correct lines. It doesn’t matter which tube goes where, as long as it creates a loop. Once the system is sealed off and pressurised, the temperature of the water will be consistent around the entirety of the loop, regardless of which component goes to which first. Thanks, physics!
You’re now at the scary part—priming your loop. Ensuring that the reservoir is gravity feeding the pump (in other words, it’s above), attach one last fitting with a length of tubing onto the top of the reservoir (depending on how you have your reservoir set up, it might be advisable to get a multi-port top adapter). Then use a funnel to carefully pour your coolant into the loop. In our case, we like to use a plastic ketchup bottle to fill our loop.
It will take time to get your loops right (it took us three attempts to master the bridge between our GPUs). But once it feels snug and secure, you can start filling your loop. Throw paper towels underneath everything—they’re a good indicator of a leak.
Before doing any of this, you want to make sure that everything on your motherboard is unpowered. Ensure that your CPU power, your motherboard ATX power, and any power cables heading to your graphics card are all unplugged, either at the power supply end or the hardware’s end. Then you’ll want to either bridge the two power points on the ATX power with a paper clip, or use a specially designed bridge connector. Then it’s simply a case of switching the power on every time you fill the reservoir, until the entire loop is filled. Just remember not to do this until after your reservoir/pump has fluid inside of it.
As you’ve probably already spotted, the build looks great. Matching the black EK water blocks with the Asus X99 TUF Sabertooth worked out really well, and the white provides a brilliant contrast to the overall style and look.
The temperatures are where we expected them to be. We clocked the Core i7-5820K up to 4.4GHz and recorded temperatures at 55 degrees Celsius under load. The GPUs remained at around 60 degrees under full load and we maintained the fans at a constant 20 percent speed throughout the system.
As for performance, we couldn’t really get much more out of either the GPUs or the CPU, as they were already at their hardware limits. But either way, the performance was still outstanding, and the fact that it remained so quiet even while under high load is really something else.
A worthy mention here is definitely the coolant. We used EK White Pastel coolant to fill our loop and it looks fantastic, even with a soft tubing loop. Our leak test went without a hitch. Although we could only test it for around 45 minutes during the shoot, there was absolutely no spillage. The EK compression fittings ensured an incredibly tight seal around all of the components. That is, as long as you haven’t damaged the tubing in the process (especially if you’re lazy like us and use scissors). Generally speaking, you should always run a leak test for 24 hours minimum before powering any of the components on, but in our case, we simply didn’t have time.
In hindsight, we’d have loved to have gone with hard tubing. It’s all the rage at the moment, and rightly so—it’s some of the nicest looking water-cooled work you can do. A larger case would have also been good. One of Caselabs’s Magnum SM8s or Parvum’s ATX chassis would’ve been excellent—going up to two 360mm radiators instead of just the one and a dual radiator would have been great for additional cooling.
A different chip would have also been nice, just to see if we could push beyond the silicon limits on ours. Thermally, there’s no issue with our 5820K, it just won’t clock beyond 4.4GHz, but that could have been a different story if we’d gone beyond the 4.7GHz boundary. Additionally, running two loops would’ve looked stunning. One in black and one in white, separating the GPU and the CPU.
Should you be water cooling, though? That was the original question. It depends on your budget. As with any build, hard cash is ultimately what it always comes down to. If you’re looking for the best bang for your buck, water cooling with a custom loop just isn’t for you. Even if you do it on the relative cheap, you’ll still be looking at somewhere around the region of $600, minimum, on top of everything else.
Water cooling is for those looking to build a beautiful and quiet workstation capable of destroying benchmarks and running any task you can throw at it with absolute silent ease. It’s not for the faint hearted, and although water cooling has come a long way since the first attempts way back yonder, it’s still filled with danger and possible hardware failure. But then, we don’t know of any aspect of the PC enthusiast’s arsenal that isn’t.
|CPU||Intel Core i7-5820K @ 4.4GHz|
|Motherboard||Asus Sabertooth X99|
|Memory||64GB Corsair Dominator Platinum (8x 8GB) @ 2,666MHz|
|Graphics||2x EVGA GeForce GTX 980 Ti Superclocked ACX 2.0+|
|Storage||2x Samsung 850 EVO 500GB SSD|
|Case||Fractal Define S|
|Power Supply||Be Quiet Dark Power Pro 11 1,200W – Platinum|
|Fans||5x Noise Blocker NB-eloop B12-2 120mm fans|
Dispelling the Myths
Many fictions cloud the world of water cooling, so we’ve sifted the reality from the rumor
If I use deionized water in my loop, then leaks won’t matter or cause any damage.
Answer: Unfortunately, no. As soon as the water is introduced to the system, it will begin making contact with the various metals inside of the water blocks. It will soon be picking up positive ions, meaning it’ll be conductive within a couple of hours, at the very least.
What If I blow it up when I switch it on? What if there’s an instant leak?
Answer: Honestly, you’re not going to damage anything. The best way to fill and test a loop is to make sure everything’s unpowered by using a PSU bridge. By using this bridge, you can switch on just the pump and that’s it. Leave this on for 24–48 hours to see if you have any leaks.
If I water cool my PC and add more fans, it’s going to cool down my room, right?
Answer: Definitely not. In fact, it’s more than likely that the opposite will occur. Your hardware may run cooler, but you’ll still be outputting the same amount of heat (or maybe even more if you’re ramping up that overclock), out of the same radiators. If anything, your room will become warmer as you’ll have more fans pushing more heat out of those radiators.
- No BS Podcast #224: Surface Pro III, Alienware’s Steam Machines, Xbox One & Kinect, FCC on ISPs, and Self Driving Cars
- No BS Podcast #189: Nathan’s Farewell
- No BS Podcast #184: Kepler, Cameras, Kashyyyk
- Microsoft Reportedly Prepping a Smaller, Cheaper Surface Tablet
- No more AdSense Referrals program
Posted by randfish
One thing we can all agree on: there’s a lot to think about when it comes to your SEO tasks. Even for the most organized among us, it can be really difficult to prioritize our to-dos and make sure we’re getting the highest return on them. In this week’s Whiteboard Friday, Rand tackles the question that’s a constant subtext in every SEO’s mind.
Click on the whiteboard image above to open a high resolution version in a new tab!
Howdy, Moz fans, and welcome to another edition of Whiteboard Friday. This week we’re chatting about how to prioritize SEO tasks and specifically get the biggest bang for the buck that we possibly can.
I know that all of you have to deal with this, whether you are a consultant or at an agency and you’re working with a client and you’re trying to prioritize their SEO tasks in an audit or a set of recommendations that you’ve got, or you’re working on an ongoing basis in-house or as a consultant and you’re trying to tell a team or a boss or manager, “Hey these are all the SEO things that we could potentially do. Which ones should we do first? Which ones are going to get in this sprint, this quarter, or this cycle?” — whatever the cadence is that you’re using.
I wanted to give you some great ways that we here at Moz have done this and some of the things that I’ve seen from both very small companies, startups, all the way up to large enterprises.
Look, the list of SEO tasks can be fairly enormous. It could be all sorts of things: rewrite our titles and descriptions, add rich snippets categories, create new user profile pages, rewrite the remaining dynamic URLs that we haven’t taken care of yet, or add some of the recommended internal inks to the blog posts, or do outreach to some influencers that we know in this new space we’re getting into. You might have a huge list of these things that are potential SEO items. I actually urge you to make this list internally for yourself, either as a consulting team or an in-house team, as big as you possibly can.
I think it’s great to involve decision makers in this process. You reach out to a manager or the rest of your team or your client, whoever it is, and get all of their ideas as well, because you don’t want to walk into these prioritization meetings and then have them go, “Great, those are your priorities. But what about all these things that are my ideas?” You want to capture as many of these as you can. Then you go through a validation process. That’s really the focus of today.
Prioritization questions to ask yourself
The prioritization questions that I think all of us need to be asking ourselves before we decide which order tasks will go in and which ones we’re going to focus on are:
What company goals does this task serve or map to?
Look, if your company or the organization you’re working with doesn’t actually have big initiatives for the year or the quarter, that’s a whole other matter. I recommend that you make sure your organization gets on top of that or that you as a consultant, if you are a consultant, get a list of what those big goals are.
Those big things might be, hey, we’re trying to increase revenue from this particular product line, or we’re trying to drive more qualified users to sign up for this feature, or we’re trying to grow traffic to this specific section. Big company goals. It might even be weird things or non-marketing things, like we’re trying to recruit this quarter. It’s really important for us to focus on recruitment. So you might have an SEO task that maps to how do we get more people who are job seekers to our jobs pages, or how do we get our jobs listings more prominent in search results for relevant keywords — that kind of thing. They can map to all sorts of goals across a company.
What’s an estimated 30, 60, 90, and 1 year value?
Then, once we have those, we want to ask for an estimated range — this is very important — of value that the task will provide over the next X period of time. I like doing this in terms of several time periods. I don’t like to say we’re only going to estimate what the six month value is. I like to say, “What’s an estimated 30, 60, 90, and 1 year value?”
You don’t have to be that specific. You could say we’re only going to do this for a month and then for the next year. For each of those time periods here, you’d go here’s our low estimate, our mid estimate, and our high estimate of how this is going to impact traffic or conversion rate or whatever the goal is that you’re mapping to up here.
Which teams/people are needed to accomplish this work, and what is their estimate of time needed?
Next, we want to ask which teams or people are needed to accomplish this work and what is their estimate of time needed. Important: what is their estimate, not what’s your estimate. I, as an SEO, think that it’s very, very simple to make small changes to a CMS to allow me to edit a rel=canonical tag. My web dev team tells me differently. I want their opinion. That’s what I want to represent in any sort of planning process.
If you’re working outside a company as a consultant or at an agency, you need to go validate with their web dev team, with their engineering team, what it’s going to take to make these changes. If you are a contractor and they work with a web dev contractor, you need to talk to that contractor about what it’s going to take.
You never want to present estimates that haven’t been validated by the right team. I might, for example, say there’s a big SEO change that we want to make here at Moz. I might need some help from UX folks, some help from content, some help from the SEOs themselves, and one dev for two weeks. All of these different things I want to represent those completely in the planning process.
How will we capture metrics, measure if it’s working, and ID potential problems early?
Finally, last question I’ll ask in this prioritization is: How are we going to capture the right metrics around this, measure it, see that it’s working, and identify potential problems early on? One of the things that happens with SEO is sometimes something goes wrong — either in the planning phase or the implementation or the launch itself — or something unexpected happens. We update the user profiles to be way more SEO friendly and realize that in the new profile pages we no longer link to this very important piece of internal content that users had uploaded or had created, and so now we’ve lost a bunch of internal links to that and our indexation is dropping out. The user profile pages may be doing great, but that user-generated content is shrinking fast, and so we need to correct that immediately.
We have to be on the watch for those. That requires validation of design, some form of test if you can (sometimes it’s not needed but many times it is), some launch metrics so you can watch and see how it’s doing, and then ongoing metrics to tell you was that a good change and did it map well to what we predicted it was going to do.
General wisdom regarding prioritization
Just a few rules now that we’ve been through this process, some general wisdom around here. I think this is true in all aspects of professional life. Under-promise and over-deliver, especially on speed to execute. When you estimate all these things, make sure to leave yourself a nice healthy buffer and potential value. I like to be very conservative around how I think these types of things can move the needle on the metrics.
Leave teams and people room in their sprints or whatever the cadence is to do their daily and ongoing and maintenance types of work. You can’t go, “Well, there are four weeks in this time period for this sprint, so we’re going to have the dev do this thing that takes two weeks and that thing that takes two weeks.” Guess what? They have to do other work as well. You’re not the only team asking for things from them. They have their daily work that they’ve got to do. They have maintenance work. They have regular things that crop up that go wrong. They have email that needs to be answered. You’ve got to make sure that those are accounted for.
I mentioned this before. Never, ever, ever estimate on behalf of other people. It’s not just that you might be wrong about it. That’s actually only a small portion of the problem. The big part of the problem with estimating on behalf of others is then when they see it or when they’re asked to confirm it by a team, a manager, a client or whomever, they will inevitably get upset that you’ve estimated on their behalf and assumed that work will take a certain amount of time. You might’ve been way overestimating, so you feel like, “Hey, man, I left you tons of time. What are you worried about?”
The frustrating part is not being looped in early. I think, just as a general rule, human beings like to know that they are part of a process for the work that they have to do and not being told, “Okay, this is the work we’re assigning you. You had no input into it.” I promise you, too, if you have these conversations early, the work will get done faster and better than if you left those people out of those conversations.
Don’t present every option in planning. I know there’s a huge list of things here. What I don’t want you to do is go into a planning process or a client meeting or something like that, sit down and have that full list, and go, “All right. Here’s everything we evaluated. We evaluated 50 different things you could do for SEO.” No, bring them the top five, maybe even just the top three or so. You want to have just the best ones.
You should have the full list available somewhere so if they call up like, “Hey, did you think about doing this, did you think about doing that,” you can say, “Yeah, we did. We’ve done the diligence on it. This is the list of the best things that we’ve got, and here’s our recommended prioritization.” Then that might change around, as people have different opinions about value and which goals are more important that time period, etc.
If possible, two of the earliest investments I recommend are A.) automated, easy-to-access metrics, building up a culture of metrics and a way to get those metrics easily so that every time you launch something new it doesn’t take you an inordinate amount of time to go get the metrics. Every week or month or quarter, however your reporting cycle goes, it doesn’t take you tons and tons of time to collect and report on those metrics. Automated metrics, especially for SEO, but all kinds of metrics are hugely valuable.
Second, CMS upgrades — things that make it such that your content team and your SEO team can make changes on the fly without having to involve developers, engineers, UX folks, all that kind of stuff. If you make it very easy for a content management system to enable editable titles and descriptions, make URLs easily rewritable, make things redirectable simply, allow for rel=canonical or other types of header changes, enable you to put schema markup into stuff, all those kinds of things — if that is right in the CMS and you can get that done early, then a ton of the things over here go from needing lots and lots of people involved to just the SEO or the SEO and the content person involved. That’s really, really nice.
All right, everyone, I look forward to hearing your thoughts and comments on prioritization methods. We’ll see you again next week for another edition of Whiteboard Friday. Take care.
Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!
- What’s Really Included in An SEO’s Job – Whiteboard Friday
- Be Intentional about Your Content & SEO Goals or Face Certain Failure – Whiteboard Friday
- Calculating Estimated ROI for a Specific Site & Body of Keywords
- Overcoming Client Objections – Whiteboard Friday
- What if Your Ugly Website is Holding Back Your Marketing Efforts? – Whiteboard Friday