What if an <iframe> had within it another <iframe> of the exact same source? Inception, as they say. Baptise Crespy does this all-important research in the name of art and science.
Turns out browsers are smart enough to not allow this infinite looping to occur (and likely crash your browser/computer). They strip the content after the 2nd nest. But! If you change the URL of the src to be unique (but still essentially serve the same document), it works. Adding some random colors and animations and things get weird really fast.
If there’s one thing that most marketers have in common, it’s that we want more leads.
Sure, not all leads are good. Some are even downright unqualified. But leads are what drive business, and as a result, many of us are held accountable for generating more of them.
Out of all of the lead generation strategies out there, there’s one that I find particularly effective: search engine optimization (SEO) and conversion rate optimization (CRO) working together.
While this may seem obvious, you’d be surprised how many marketing teams are really good at one or the other, but fail to find the balance between both.
Below, I’ll share why it’s critical to find alignment between SEO and CRO, and how to do it so that both of these functions work together to drive qualified leads for your business.
SEO and CRO: Why you can’t have one without the other
Being discoverable is more important than it’s ever been. If a prospective buyer can’t find your business online, there’s a good chance that you’re leading them right into the arms of your competitors.
By now, most businesses understand the importance of having a presence in organic search results. SEO is more than just a buzzword, it’s a given. And it’s critical to growing brand awareness and driving traffic to your website.
But there’s a catch.
Traffic doesn’t magically turn into paying customers and revenue. Ask yourself, when someone clicks on an organic result and lands on your website, what kind of browsing experience are they having? Is your site easy to navigate? Are your web pages optimized to guide the user towards an action?
Traffic without conversions is essentially just a vanity metric. CRO is the piece that ties it all together.
Put simply, conversion rate optimization is the process of optimizing a web page to lead a user toward a desired action. Typically, this action comes in the form of a conversion. This can be a demo request, email newsletter sign up, webinar registration — you get the gist.
The idea here is to entice the user to move further down the marketing funnel in some way.
SEO is what brings people to your website and CRO is what gets them to convert.
It sounds like a match made in marketing heaven, but achieving alignment is often easier said than done.
Start with a strong SEO foundation
I could write thousands of words on what it takes to build a strong SEO foundation for your website, but that’s not what this article is about. With that being said, a discussion about the relationship between SEO and CRO wouldn’t be complete without a mention of it.
Earlier, I said you can’t have SEO without CRO. But this goes both ways.
While it’s true that conversions are a meaningful standalone metric, you can’t have conversions without web visitors. Plus, experimentation and testing is a big part of what makes CRO so effective. It can be difficult to run tests if your website doesn’t get a healthy amount of traffic. More on this later.
A successful SEO strategy fuels the inbound marketing engine to bring new prospective buyers to your site on a regular basis. With SEO, your entire marketing team could be on PTO for a week and your website will still be generating traffic on its own.
If you’re still working to build a powerful SEO strategy, there are countless SEO resources that are available to you.
Be intentional about your content
Content and SEO go hand-in-hand.
When a buyer goes to a search engine, they want to find content that brings them an answer to their question.
As marketers, we want to create that content and match it to a buyer’s specific search query. We do this through extensive keyword research and on-page optimization to ensure that every piece of content that’s published has a likelihood to rank on page one.
Although this approach to content creation is effective at generating organic traffic, sometimes we forget to think about how a piece can drive impact beyond just ranking number one for a keyword.
CRO doesn’t just apply to landing pages or core solutions pages. There are elements of CRO that apply to your long-from content as well.
When strategizing topic ideas and doing keyword research, assign a goal to every piece of content that you publish. Ask yourself, “what action do I want the reader to take when they land on this page?”
Build this goal into your content calendar and incorporate it as a call-to-action (CTA) on each page that you publish.
As always, be mindful of the reader and their position in the funnel. Someone that lands on “The Beginner’s Guide to Marketing Automation” probably isn’t ready for a live demo just yet.
Instead, guide that reader toward a less intimidating action, such as signing up for your email newsletter. A good CTA shouldn’t feel spammy or overly promotional, it should provide additional value to the reader overall.
Following this process forces you to think beyond just traffic — you’re focusing on conversions before you even hit the “publish” button.
Test, optimize, and repeat
User experience (UX) is at the heart of both SEO and CRO.
If your website is slow, glitchy, and hard to navigate, it’s going to negatively affect both traffic and conversions. The goal is to continuously refine your website to ensure that anyone who lands on it has a frictionless browsing experience — thereby increasing their likelihood to convert.
Split testing, sometimes referred to as A/B testing, is the process of testing multiple variants of a web page to determine which one converts at a higher rate. This is a core practice among marketers who specialize in CRO. You can test different types of lead forms, CTA buttons, copy variants, and even page layouts.
Here’s an example of a split test between a single and multi-step lead form:
Some SEOs may be hesitant to run split tests because they worry it will negatively affect organic rankings. The truth is that Google not only encourages testing, but it even has its own tool that helps marketers to run split tests.
As long as you’re abiding by Google’s webmaster guidelines, you should see no major negative impact on organic traffic due to testing.
It’s also worth noting that you can’t reach statistical significance in your split tests without a big enough sample size. In other words, you need traffic to have accurate test results.
There’s no hard and fast rule for what counts as “enough traffic” but the general consensus is that your web visitors should be in the thousands, at least. I recommend using this sample size calculator tool to get a better idea of a number that’s unique to your website.
This is yet another example of how closely intertwined SEO and CRO truly are. Earlier we discussed how important it is to start with a solid foundation in SEO, now you know how it fits into the bigger picture.
The common thread here?
CRO and SEO have a symbiotic relationship. What’s good for one is good for the other. And both are working toward the same common goal of generating revenue.
Identify marketing funnel gaps
When looking at the big picture of your inbound marketing efforts, SEO and CRO can help you identify and fix any gaps in your funnel.
Let’s say you have a product page that ranks #1 for its primary keyword and generates lots of traffic. But, when you dig into the conversion data, you notice that only a small percentage of users that land on that page actually convert.
This is a red flag that something is off with the page.
It could be the messaging, the offer, or the lead form. Just because it works for Google doesn’t mean it’s working for your audience. And their opinion is the only one that matters.
This goes the other way around too.
Say you have a product page that’s converting at a high rate, but you notice that it’s one of the lowest-trafficked pages on your site. This should alert you to revisit the content on that page and identify opportunities to re-optimize it. If you don’t, there are likely hundreds of potential conversions that you’re missing out on.
Final thoughts
SEO and CRO is kind of like the digital marketing version of the chicken and the egg. You can’t be really good at one without the other.
Realistically, it doesn’t matter what came first. What does matter is achieving alignment between these two key marketing tactics. By doing so, your website has the potential to become a major driver of leads and revenue for your business.
If there’s one thing you take away from this article, it’s to integrate your SEO and CRO efforts and view them as one cohesive part of your lead generation strategy.
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!
from The Moz Blog https://ift.tt/3q6z96e
via IFTTT
Removing media support from HTML video was a mistake. It means that for every video we embed in HTML, we’re stuck with the choice of serving source files that are potentially too large or small for many users’ devices (resulting in poor performance, wasteful data consumption, and even sub-optimal quality on larger screens), or resorting to more complicated server-side or scripted or third-party solutions to deliver a correct size.
I remember when responsive images were just starting to come out. One way to explain it was to say it’s like <video> in that you can have multiple <source> elements inside which (in supporting browsers) allowed you to specify attributes like type (e.g. video format) and media (e.g. screen size). But then…
Despite being implemented in multiple browsers, the feature was removed from browsers and the HTML specification, without any proposed replacement for the functionality it once provided. One exception is the feature was never removed from Webkit, so it still works in Safari browsers, which is great.
I don’t remember that. That feels like a big WTF moment (some background). I think of the web as being tremendous at backwards compatibility. It’s a rare day when we just yank stuff, and even more rare is a yanking with no alternative whatsoever.
So now with responsive images being a success (it’s a success, right? I can’t imagine how incredibly much bandwidth it has saved the world)… can’t we… put it back?
When I have an immediate need for this, I always think of Cloudinary, because I can alter the size and format of video by changing the URL. Like here’s a video URL where the video codec is automatically determined and the size is forced down to 400px:
What’s so cool about :focus-visible? It’s all about the blue focus ring that displays around elements that are in focus. It’s sort of a happy medium between loving the outline for accessibility purposes (gotta know what element is selected when tabbing on a keyboard) but not-really-loving how it looks (gotta have everything follow brand).
The strategy has largely been an all-or-nothing choice between using a custom outline when any element is in :focus (great, but that means for both keyboard tabbing and mouse clicks) or ditching the outline altogether (not great, like ever). :focus-visible accomplishes the same thing as :focus, but uses a browser’s knowledge of user inputs (or heuristics) to determine whether the focus is coming from a keyboard or a mouse.
(Are a browser’s heuristics perfect at determining the input? That depends. Things get murky once we start factoring in things like touch interactions.)
That means, we get to remove the default focus ring (yay!) for the right types of interactions (double yay!) and display our own custom styles while we’re at it (triple yay!). Allow me to pluck Andy Adams’ fine example straight from our almanac. Note that :focus-visible cannot remove the focus ring like :focus can, so the two are used together:
Chrome implemented :focus-visibleback in 2018. Firefox had it’s own prefixed version, :-moz-focusring, prior to this implementation. Safari? Go vote for the feature!
I always appreciate someone looking into and re-evaluating the best practices of something that literally every website needs and has a complex set of requirements. Andrey Sitnik has done that here with favicons.
It was good timing to do this here on CSS-Tricks, so I tried following the advice to the letter, and it’s working great so far. I think I got fed up at how complex it was at some point that I went ultra-minimalist and only had favicon.ico file. Now I’ve got all of the above in place.
Where I differed…
I don’t have GIMP or Inkscape installed, which can export .ico format, so I used this favicon generator (I fed it my “main” SVG”) just for that one icon.
I found Figma helpful for resizing frames and exporting the right sizes.
I used ImageOptim for optimizing all the images.
I was nervous about adding a “manifest” because I don’t have any other PWA-like steps in place and it feels like an extra web request for little value. But I did it anyway.
I have a theme color (<meta name="theme-color" content="rgb(255, 122, 24)">) because I was told it was a nice touch. Feels related.
What’s the difference between hosting providers? For example, what is the difference between GoDaddy and Hostgator, which seems like “traditional” web hosting providers, to others like Heroku, Digital Ocean, AWS, and Firebase?
When would I use one over the other?
They were hoping for detailed thoughts, so I’m going to oblige!
To be honest, I’m already confused. (Sorry, I promise I’ll try to be more helpful as we go on.) Why is WordPress hosting one dollar more expensive than the Web Hosting plan? If you buy the $5.99 Web Hosting plan are you prevented from installing WordPress on it? Or is it just convenient in that if you pick the WordPress hosting it comes pre-installed and configured? WooCommerce is just a plugin for WordPress, so are you prevented from installing that on the WordPress hosting plan until you upgrade to the WordPress Ecommerce Hosting plan? (To be fair, WordPress.com unlocks WooCommerce at the highest plan as well, so it’s trod territory.) Why is the VPS Hosting plan the cheapest? I don’t blame you if you also find this as confusing as I do, especially as this is just one of many different charts of hosting options they offer.
GoDaddy makes a billion zillion dollars a year, so I’m sure they’ve got this stuff figured out, but I’ll tell ya, after a couple of decades of web development experience, I’d be totally guessing at choosing a plan from options like this. Cynically, it feels like confusion might be a sales tactic.
Technology
I do know this: these plans are for PHP / MySQL sites. That means WordPress, Craft, Perch, Ghost, Drupal, Joomla, etc. This is the LAMP stack which has all the big CMSs covered. Just the way it is. This is going to be the case at Media Temple, Hostgator, Bluehost, and lots of hosts like that. I think a “traditional” web host, as you put it, isn’t a bad way to think about it.
Do you wanna run PostgreSQL or MariaDB instead of MySQL? Or you wanna run ASP instead of PHP? I’ll bet you all these hosts have some kind of answer for those things. The answer is going to be something like “Don’t use our shared hosting product, use our raw VPS (‘Virtual Private Server’) product which has direct root access, and you can install it yourself.” I guess that’s fine, but just know those things aren’t first-class citizens of their hosting. If you have trouble, I’d worry you’ll have a hard time getting good support.
Which leads me to my point: you should go with the happy path offerings from hosting providers.
Say I want to write a Python app. I’m not going to buy a Hostgator server. I’m sure you can get it to work, but it’s not something they really promote. It doesn’t feel like it’s on a happy path. Whereas if I look around at Heroku, they make it a first-class citizen of what they offer:
I can’t vouch for it directly as I’ve never used Heroku, but I’ve heard lots of good things and they’ve been doing this for a good 15 years.
Happy paths are about friendly pairings
Heroku reminds me of another divide in hosting providers that I think is significant. Those “traditional” web hosts don’t lift a finger to help you get your websites over to them. It’s more like: here’s your FTP credentials, good luck. With a host like Heroku, they are giving you a CLI to like heroku container:push to deploy your local code to production. Better, it will deploy right from your GitHub repository. Why every single web host in the world doesn’t help with that is a mystery to me. A web host that helps you with deployment is a valuable thing.
We were talking about happy paths, right? Heroku calls themselves a “Cloud Application Platform.” The happy path there is those server-y languages. Node, Ruby, Python, Go. What if you don’t need any of that? Say you’re building a static site, using a static site generator (like Eleventy) at the core (Jamstack, as it were). Do you pick Heroku? Probably not. While surely you could pull it off on Heroku, static site hosting isn’t core to Heroku, and so not a happy path.
Where should you host a static site? That’s Netlify’s whole ball game. Netlify is a super happy path for static sites.
In fact, Netlify nailed the Jamstack-style hosting thing so strongly that lots of companies have been trying to provide similar offerings. I think of Azure’s Static Web Apps as an example. So why use Azure over Netlify? If it feels like a happy path, and it might if you’re using other Azure products, assuming their products play well together. Azure is a massive cloud platform with loads of other offerings. Or you might just have more experience and developer muscle memory for Microsoft products. We’ll get to that later.
Jamstack (essentially meaning static hosting + services) is available in lots of places now. Cloudflare has Cloudflare Pages, which you might take advantage of because of the unlimited promises (unlimited sites, unlimited requests, unlimited bandwidth, and even unlimited team seats).
You might choose Cloudflare Pages because your Cloudflare products like access or workers that are important to you and it feels like the happy path to keep it all together.
Vercel has Jamstack hosting, but they’ll run servers for you if you need them. Their popular framework, Next.js, prebuilds pages, but can also deliver server-side rendered pages with a Node back end. Vercel gives you that back end.
Next.js on Vercel is a very happy path. “Deploy on the platform made for Next.js,” they say. Hard to beat that.
AWS Amplify is ultimately Jamstack hosting, and the happy path there is using Amplify to stitch together other AWS services. That’s literally the point of AWS Amplify.
Need auth? It’s Amazon Cognito under the hood, but Amplify helps you stitch it into what you are doing. Need storage? S3 is an industry standard, and Amplify helps you integrate it. Need a database? Amplify helps you model it and build APIs.
Firebase has Jamstack-style hosting, and the happy path is leaning into the Firebase framework.
Firebase has lots of very useful features, like real-time data storage, authentication, and RUM analytics. If I wasn’t using any of those things, I’m not sure I’d pick Firebase hosting. Like for a basic Jekyll blog, can it be done? Absolutely. Would I personally do it? Probably not. It’s not really leaning into the Firebase offerings, making it way less of a happy path.
It’s worth talking about 💪 developer “muscle memory” for a moment. You build muscle memory for the things you do a lot. If you’ve got five sites on Netlify already, and you’ve gone through those motions over and over, it makes sense that your sixth site is on Netlify as well — even if some other host might be a slightly better fit. Knowing your tools well and feeling comfortable is a big deal. You can compare pricing and features and all the bits and bobs, but muscle memory is one of the most powerful choice influences, and I think that’s perfectly fine.
Your host should take care of your core needs
Remember how I mentioned a web host that helps you with deployment is a valuable thing? All of these hosts do that: Netlify, Vercel, AWS Amplify, Google Firebase, Cloudflare Pages, Azure Static Sites. That’s become table-stakes for hosting providers. There are more table-stakes as well.
The table stakes of modern web hosts.
Beyond, ya know, hosting the website.
HTTPS. The host should give my site an SSL certificate. Probably automatically, and probably for free (since Let’s Encrypt is free).
CDN. The host should help serve as much as my site as is practical from a CDN, even if it’s a paid feature or requires configuration.
Deployment. The host should connect to Git repositories and move files from the main branch to the production site.
Staging. The host should provide staging environment(s).
I should circle back to the WordPress (and other PHP/MySQL CMS) thing. That’s what this site is. Traditional hosts serve this market. WordPress is 35.2% of all websites, which is bananas, and means there are wheelbarrows full of money in that hosting market. But in my experience, the traditional hosts do almost none of what I just called table stakes in hosting. A lot of times, you’re on your own for HTTPS. You’re on your own for integrating a CDN. You’re on your own for deployment. Staging just means buy another server. It’s just a weird time for hosting right now, with such a wide gap in modern web hosts doing so much and traditional web hosts doing so little.
That’s not true of all WordPress-specific hosts though. Using a WordPress-specific host for hosting WordPress is about as happy path as you can get. I’m on Flywheel now and appreciate all they do. They cover that entire list of table stakes, and go further still, helping with local development.
You asked about Digital Ocean specifically…
I feel the least qualified to explain Digital Ocean, but I think it’s fair to say that Digital Ocean has a lot of happy paths. They have this concept of a “Droplet” (it’s a server) which is spun up from “containers.” I wouldn’t worry terribly much about the idea of containers at this point, but suffice it to say, they are pre-configured servers that can run any sort of combination of technologies. If you want to fire up a LAMP stack thing in a Droplet, that’s a first-class citizen. But so are lots of other technologies. Consider Strapi, a CMS that is Node, Nginx, and PostgreSQL. Digital Ocean has a Droplet for that’s ready for it out of the box.
Droplets also start at $5/month, so they are just as economical as other hosts, if not more so. You might find hosting products that are actually Digital Ocean under the hood! For example, the WordPress hosting tool SpinupWP allows you to quickly create configured WordPress hosting environments, but it doesn’t do the hosting itself, you “bring your own” host, which is likely Digital Ocean or AWS (Amazon Web Services).
It only gets more complicated from here
If Digital Ocean seems complex, wait until you hear about AWS. We talked about AWS Amplify earlier, but that’s like AWS designed for individual developers like you and me to scaffold apps quickly. It’s very cool, but it’s a small wedge of what all that is AWS.
AWS is this massive cloud services provider, meaning that, sure, you can spin up web servers, but there are also hundreds of other services for things, like databases, storage, serverless stuff, APIs, logs, heck — you can rent a damn quantum computer there, which is like sci-fi stuff. It’s not that a normal developer can’t use AWS for a web host, it’s just like, not really designed with that kind of DX in mind. This guide on installing WordPress makes me sweat. AWS is super powerful, has solutions for everything, and is priced as low as it gets. Perhaps it’s useful to think of AWS as like down-to-the-metal web infrastructure, designed for large-scale operations. Web hosts might even be built on top of AWS, for example.
Matching your needs to what’s available
Let’s do some quick hits of needs matched to options. This is in no way comprehensive. I just slapped it together with things that popped to mind that feel happy path aligned.
It’s worth re-iterating that there is a lot of commonality in hosting. Say you’ve got an index.html file you want to host and that’s your entire website; literally any web host will do that. These are all web hosts, after all. They serve files and run code. They aren’t that different. We’re largely talking about DX here: do they run what I need to run? Is it straightforward? Do they help make it easy? Do they clearly offer support for it?
Is it the happy path?
Then there’s pricing
We haven’t really talked much about price. I know that’s a major consideration for a lot of people and I don’t want to downplay it. But it’s hard to talk about without knowing your needs. I also don’t want people to make major web hosting decisions based on something like a few dollars difference in monthly cost. If you spend half an hour troubleshooting you otherwise wouldn’t have had to, those savings are blown.
I find that web hosting is somewhat of a commodity market. The prices are fairly stable. If a host seems expensive, it’s probably because they offer a lot. If a host seems cheap, it’s probably because they cut costs in a way you’ll eventually feel. If you’ve got a little baby site, chances are, you’re going to be hosting it for free. And if and when the site grows up, the hosting costs will feel minimal and fair.
🛠Does all this seem kinda fun and exciting to you? If it does, you might think about a career in DevOps dealing with servers, deployment, infrastructure, and supporting developers doesn’t have to be a side-job to other development work, it can be a whole job.
As an SEO Manager, you’re responsible for growing your company’s organic search traffic. You’re working with your dev team on some technical improvements, but you notice a big slice of the opportunity lies with content. Your company has a content team, but you notice they’re not using keyword research to inform their articles. You’ve tried to send them keyword ideas, but so far, they haven’t been receptive to your suggestions.
Or how about this scenario?
You’re a marketing director at a startup. You know that you need content, but don’t have the expertise or time to do it yourself, so you ask your network for recommendations and find yourself a freelance writer. The only problem is, you’re not always sure what to assign them. With little instruction to work off of, they produce content that misses the mark.
The solution in both of these scenarios is a content brief. However, not all content briefs are created equal.
As someone who lives with one foot in content and the other in SEO, I can shed some light on how to make your content briefs both comprehensive and beloved by your content team.
Let’s start by agreeing on some terminology.
What’s a content brief?
A content brief is a set of instructions to guide a writer on how to draft a piece of content. That piece of content can be a blog post, a landing page, a white paper, or any number of other initiatives that require content.
Without a content brief, you risk getting back content that doesn’t meet your expectations. This will not only frustrate your writer, but it’ll also require more revisions, taking more of your time and money.
Typically, content briefs are written by someone in an adjacent field — like demand generation, product marketing, or SEO — when they need something specific. However, content teams usually don’t just work off of briefs. They’ll likely have their own calendar and initiatives they're driving (content is one of those weird roles that needs to support just about every other department while also creating and executing on their own work).
What makes a content brief “SEO-focused”?
An SEO-focused content brief is one among many types of content briefs. It’s unique in that the goal is to instruct the writer on creating content to target a specific search query for the purpose of earning traffic from the organic search channel.
What to include in your content brief
Now that we understand SEO-focused content briefs in theory, let’s get into the nitty gritty. What information should we include in them?
1. Primary query target and intent
It isn’t an SEO-focused content brief without a query target!
Using a keyword research tool like Moz Keyword Explorer, you can get thousands of keyword ideas that could be relevant to your business.
For example, in my current job, I’m focused on creating content for retail store owners and others in the brick and mortar retail industry. After listening to some sales and support calls on Gong (many teams use this to record customer and prospect calls), I might find out that “merchandising” is a big topic of focus.
So I type “merchandising” into Keyword Explorer, add a couple more helpful filters, and boom! Tons of keyword suggestions.
Pick a keyword (check your existing content to make sure your team hasn’t already written on the topic yet) and use that as the “north star” query for your content brief.
I think it’s also helpful to include some intent information here. In other words, what might the searcher who’s typing this query into Google want? It’s a good idea to search the query in Google yourself to see how Google is interpreting the intent.
For example, if my keyword is “types of visual merchandising,” I can see from the SERP that Google assumes an informational intent, based on the fact that the URLs ranking are largely informational articles.
2. Format
Dovetailing nicely off of intent is format. In other words, how should we structure the content to give it the best chance of ranking for our target query?
To use the same keyword example, if I Google “types of visual merchandising,” the top-ranking articles contain lists.
You might notice that your target query returns results with a lot of images (common with queries including “inspiration” or “examples”).
This better helps the writer understand what content format is likely to work best.
3. Topics to cover and related questions to answer
Picking the target query helps the writer understand the “big idea” of the piece, but stopping there means you risk writing something that doesn’t comprehensively answer the query intent.
That’s why I like to include a “topics to cover / related questions to answer” section in my briefs. This is where I list out all the subtopics I’ve found that someone searching that query would probably want to know.
To find these, I like to use methods like:
Using a keyword research tool to show you queries related to your main keyword that are questions.
Looking at the People Also Ask box, if one exists, on the SERP your target query triggers
Finding sites that rank in the top spots for your target query, running them through a keyword research tool, and seeing what other keywords they also rank for
And while this isn’t specifically search-related, sometimes I like to use a tool called FAQ Fox to scour forums for threads that mention my target query
You can also create the outline yourself using your research with all the H2s/H3s already written. While this can work well with freelance writers, I’ve found some writers (particularly in-house content marketers) feel this is too prescriptive. Every writer and content team is different, so all I can say is just use your best judgment.
4. Funnel stage
This is fairly similar to intent, but I think it’s helpful to include as a separate line item. To fill out this portion of the content brief, ask yourself: “Is someone searching this term just looking for information? Inspiration? Looking to evaluate their options? Or looking to buy something?”
And here’s how you can label your answer:
Top-of-funnel (TOFU or “problem aware”) is an appropriate label if the query intent is informational/educational/inspirational.
Middle-of-funnel (MOFU or “solution aware”) is an appropriate label if the query intent is to compare, evaluate options, or otherwise indicates that the searcher is already aware of your solution.
Bottom-of-funnel (BOFU or “solution ready”) is an appropriate label if the query intent is to make a purchase or otherwise convert.
5. Audience segment
Who are you writing this for?
It seems like such a basic question to answer, but in my experience, it’s easy to forget!
When it comes to SEO-focused content briefs, it’s easy to assume the answer to this question is “for whoever is searching this keyword!” but what that fails to answer is who those searchers are and how they fit into your company’s personas / ideal customer profile (ICP).
If you don’t know what those personas are, ask your marketing team! They should have target audience segments readily available to send you.
This will not only help your writers better understand what they should be writing, but it also helps align you with the rest of the marketing department and help them understand SEO’s connection to their goals (this is also a critical component of getting buy-in, which we’ll talk about a little later).
6. The goal action you want your readers to take
SEO is a means to an end. It’s not only enough to get your content ranking or even to get it earning clicks/traffic. For it to make an impact for your company, you’ll want it to contribute to your bottom line.
That’s why, when creating your content brief, you not only need to think about how readers will get to it, but what you want them to do after.
This is a great opportunity to work with your content marketing and larger marketing team to understand what actions they’re trying to drive visitors to take.
Here are some examples of call-to-actions (CTAs) you can include in your briefs:
Newsletter sign-ups
Gated asset downloads (e.g. free templates, whitepapers, and ebooks)
Case studies
Free trials
Request demo
Product listings
In general, it’s best to use a CTA that’s a natural next step based on the intent of the article. For example, if the piece is top-of-funnel, try a CTA that’ll move them to the mid-funnel, like a case study.
7. Ballpark length
I’m a firm believer that the length of any article should be dictated by the topic, not arbitrary word counts. However, it can be helpful to offer a ballpark to avoid bringing a 500-word blog post to a 2,000-word fight.
One tool that can make coming up with a ballpark word count easier is Frase, which among other things, will show you the average word count of pages ranking for your target query.
8. Internal and external link opportunities
Since you’re reading the Moz blog, you’re probably already intimately familiar with the importance of links. However, this information is commonly left out of content briefs.
It’s as simple as including these two line items:
Relevant content we should link out to. List out any URLs, especially on your own site, that could be natural fits to link out to in this article.
Existing content that could link to this new piece. List out any URLs on your site that mention your topic so that, after your new piece is live, you can go back and include links in them to your new piece.
The second item is especially important, since adding links to your new post can help it get indexed and start ranking quicker. A quick way to find internal link opportunities is to use the “site:” operator in Google.
For example, the following search would show me all posts on the Moz blog that mention “content brief.” These could be great sources of links to this blog post.
9. Competitor content
Search your target query and pull the top three-or-so ranking URLs for this section of your content brief. These are the pages you need to beat.
At risk of creating copycat content (content that’s essentially a re-spun version of the top-ranking articles), it’s a good idea to instruct your writer on how best to use these.
I like to include questions like:
What’s our unique point-of-view on this topic?
Do we have any unique data we can pull on this topic?
What experts (internal or external) can we ask for quotes to include on this topic?
What graphics would make this more visually compelling than what our competitors have?
You get the idea!
10. On-page SEO cheat sheet
One thing I always like to include in my briefs is some form of an “SEO cheat sheet” — tips and resources for helping your writers with important on-page SEO elements.
Here’s an example of one I’ve used in the past:
Important caveat: Writers have varying levels of SEO expertise. Some content teams are very bullish on SEO (companies like G2 and HubSpot come to mind), so the writers may not need much help in this area. For others, SEO is fairly new to them. Determine what’s necessary for your unique situation so that you can avoid over or under-prescribing in this area.
What to avoid when writing content briefs
Sadly, “SEO” has become a dirty word to many writers. Understanding why will help us avoid the major pitfalls that can lead to ignored briefs and interdepartmental tensions.
Don’t provide suggestions after that asset has been written
When writing for search, we’re creating the output. The keyword is the input. In other words, target queries are questions to be answered, not something to be stuffed into copy that’s already been written.
Google wants to rank content that answers the query, not just repeats it on the page.
For this reason, I would avoid having an optimization step after your writing step. If you don’t, you risk the content not matching the intent of the query, which means it has little-to-no likelihood of ranking, and you’ll also likely upset your writers, who don’t want to cheapen their editorially excellent content by stuffing keywords into it.
Don’t favor keywords with high volume over high intent match
I once saw a brief where the SEO Manager requested that the writer use a certain phrase instead of another phrase because it had search volume while the other didn’t.
The problem? While seemingly similar, the keywords actually had totally different intents.
Don’t do this.
At best, targeting keywords purely for volume’s sake can result in vanity traffic that never converts. At worst, you’ll be trying to fit a square peg in a round hole and likely missing intent-match completely.
Don’t blindly follow keyword tools
Keyword tools are helpful, but they’re not perfect reflections of search demand. For example, because they’re not always updated incredibly often, you may mistakenly think a query has no demand when in fact it has a ton.
A good example of this is COVID-19 related keywords. As a newly trending topic earlier this year, many keyword research tools didn’t register that they had any search volume, when in fact they did. If you would have blindly followed the tool, you may have missed out on the opportunity.
To solve for this, you can use tools like Google Trends or even Google Search Console (if you have content on a trending topic or similar topic on your site already, you should be able to see impressions/interest spiking within a few days).
Don’t instruct writers to “include these keywords” (especially a certain number of times)
When listing out the target query (or queries) in your content brief, it’s important that we instruct our writers that this is the main question to answer rather than this the word I need you to sprinkle throughout the content.
There’s no magic number of times you can stick a keyword in your copy so that it ranks for that term. Instead, instruct your writers to focus on answering the intent of the searcher’s question comprehensively.
Don’t try to jam keywords into articles that weren’t intended for search discovery
Organic search is not the only channel for content discovery. As someone coming from an SEO background, this took me a while to learn.
That means adding search content to your content calendar, not trying to cram keywords into everything on the calendar.
While it’s important to get the on-page SEO basics right (title tag, heading tags, links, etc.) for every piece, not every piece lends itself well to organic search discovery.
For example, if we only created content based on keywords that a tool told us gets searched a certain number of times per month, we’d never write about new concepts. It takes a lot of thought leadership off the table, as well as things like case studies and interview/feature story pieces.
Organic search is powerful, but it’s not everything.
Tips for getting your content team bought in
Even the best content briefs won’t make an impact if your content team refuses to use them — and I’ve heard of plenty of situations where that happens.
As an SEO, it can be mind-boggling that your content team doesn’t want to use this: “Don’t you want traffic?!” But as someone who leads a content team, I understand why they’re often rejected.
Thankfully, in many cases, this can be avoided by taking the following actions.
Involve them in the planning process
No one likes to be micromanaged, and thorough content briefs can sometimes feel like micromanaging. One great way to avoid this is by bringing them along for the process. Make content briefs a joint effort between SEO and Content.
For example, connect with the Content Lead and see if they’d be willing to sit down with you to create the content brief template together. By each of you bringing your unique expertise to the table, it can feel less like dictating and more like collaboration (plus, you’ll probably end up with a better brief template that way).
Make it clear that not all content has to be search content
SEO Managers live and breathe the organic search channel, but content teams have a more varied diet. They take a multi-channel approach to content, and sometimes are even writing content to support post-conversion teams like customer success.
When working with your content team on this, make sure you emphasize that this is a new content type that can be added to editorial planning. Not something that’ll replace or need to change the types of content they’re already writing.
Respect their expertise
Writing is hard. Doing it well requires immense skill and practice, but sadly, I’ve heard many SEOs talk about writers as if they didn’t know anything, just because they don’t know SEO.
As an SEO, you’ll get far with your content department simply by respecting their expertise. Just as many SEO Managers aren’t writers, it’s unfair of us to expect writers to have the SEO knowledge of a full-time SEO professional.
Before you implement a content brief process, sit down with the Content Lead and members of the content team to gauge their search maturity. What do they actually need your help with? Then trust them with the rest.
Show results
One of the best ways to get and maintain buy-in is by showing results. Show your content team how much of their traffic is coming from organic search and how, unlike many other content discovery channels, that traffic is staying consistent over time. Give the writer a shout-out when you notice their article ranking on page one.
Remember, we’re on the same team, and stronger together than we are apart.
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!
from The Moz Blog https://ift.tt/2NhF5Lm
via IFTTT