Don’t skip these critical recurring SEO tasks
As we near the end of the year, it's time to review broken links, plugins, functionality and page speed before there is a crisis.
No matter how perfectly you’ve optimized a website, it will always require constant maintenance. This is because figuratively speaking, much like a vehicle, there are a lot of moving parts and many of those parts have an impact on others.
In other words — SEO will never be done. It’s a constantly moving target.
There are some tasks, like migrating from HTTP to HTTPS, that are done once. Other tasks are performed on a weekly or monthly like content development, and others that might be conducted on a quarterly or yearly basis.
As we near the end of the year, many marketers will begin planning for next year. It’s equally important to review what we’ve done throughout the year to make sure that our work didn’t inadvertently cause issues in other areas. This helps us to get the most from our efforts as well as to begin next year with a head start.
In this article, I’m going to dig into the tasks that we typically handle on a quarterly or yearly basis, because frankly, they often get ignored until there is a crisis. Proactively handling them will give you a powerful advantage over competitors.
Crawl for broken links
Pages get moved or deleted. Images get replaced. External resources move or even disappear.
Over time, these seemingly minor changes can have a significant impact on a website. Often the impact is positive. But when it results in broken links that aren’t resolved, the negative impact can add up quickly.
It’s easy to fix some broken links on the spot by updating the main navigation when core pages are moved or deleted. It can be more complicated when internal links within content come into play.
This is where specialized tools are especially useful.
Rather than manually reviewing each page, which is what we had to do when I first got into SEO, you can simply use automated software to do the heavy lifting. An added benefit is that unlike humans with short attention spans, the software will catch every broken link.
Review content for quality and relevance
You should be producing content regularly.
If you’re doing that, you’ll typically find that over time, some of that content will become irrelevant or may no longer meet your quality standards. Some of this content may need to be pruned or improved.
This isn’t a bad thing. It’s just the nature of content development.
As we approach the end of the year, now is the effect time for this. Most business owners are elbow deep in evaluating their performance for the year and planning for the next year.
I recently reviewed one of our client’s websites for this reason and found a tremendous amount of content, that while useful at one point, no longer served a purpose.
This happens for a variety of reasons.
For this particular client, in some cases, it was news related to their industry that was no longer relevant. In others, it was content about specific internal events. And in some, fortunately, rare cases, it was content created by the client’s staff that never should have been created in the first case.
Once you’ve identified the content on your website that doesn’t meet your quality and/or relevance standards, you’ll need to determine what to do with it.
Some content may no longer be relevant because of changes in your industry or your business. This content can be deleted, and the URLs should then be redirected to the most relevant content that still exists. If there is nothing relevant to a particular page that’s being deleted, then you can delete it without setting up a redirect. However, if that page has any inbound links or has received any organic traffic in the past twelve months, I highly encourage you to find something on your website to redirect it to.
Some content may simply no longer meet your quality guidelines. Perhaps your writing skills have improved dramatically. Or maybe the content is simply too thin.
The solution to lower-quality content is simple — improve it.
This may mean rewriting the content, adding additional information, and even including images, data, and links to other external resources. Just remember — longer isn’t always better. You should aim to answer your visitors’ query clearly and concisely. Skip the fluff. If you can say everything that needs to be said with just 750 words, then there won’t be anything gained by inflating it to 3,000 words.
Test for page speed
We already know, thanks to data from a variety of sources, that page speed has a dramatic impact on user experience. We also know that it is a ranking factor, both because we’ve seen the evidence and because Google has told us.
Just as low-quality content can grow over time, small tweaks to your website can add up to adversely affect page speed over time as well.
I can tell you from first-hand experience that this happens to most websites that are maintained and updated regularly. That’s why it’s so important to regularly test page speed especially on your highest traffic pages.
If you have a small website (under 1,000 pages), then I recommend testing all of your pages. The task isn’t as monumental as it may seem. We’ll talk about the execution shortly.
For websites over 1,000 pages, my recommendation is to first test the pages that drive 30 percent of your traffic. Next, test any pages not included in that dataset that are critical to your business. And finally, identify the pages in the bottom 10 percent in terms of organic traffic, highlight any that are somewhat to moderately important, and test them.
The good news is that you don’t need to manually test each page. You can collect the initial data right inside of Google analytics.
If a page typically loads in under three seconds, you’re good to go. If it typically takes longer than three seconds, it’s time to use a tool like WebPageTest.org or GTmetrics to identify the elements that are causing the issues.
If fixing these type of issues is something you’re not familiar with, you can check out a recent article I published on the topic, titled How to rev up your page speed for better website performance.
Review WordPress plugins
Plugins must be updated by the author regularly to continue functioning properly. This is due to changes in:
- HTML standards
But for a variety of reasons, plugin authors may infrequently update their plugins to keep up with changes in this environment, or in some cases, may simply abandon them entirely.
This can affect functionality, appearance, page speed, and even technical SEO. In some cases, it can even render an entire website inaccessible.
It’s wise to review WordPress plugins regularly—not just in terms of you having the most current version installed, but also in terms of whether the author has kept the plugin up to date with current standards.
While doing this, I also recommend putting serious thought into whether each plugin is really necessary. If you can eliminate a plugin, not only will you typically improve page speed, but you’ll also reduce your maintenance workload and potentially improve security. It’s a win all the way around.
Test layout and functionality in major browsers
I explained how incremental changes to your website could impact page speed, but they can also impact how some pages look and function.
I had this happen to me recently with a client’s website.
We made a change to the CSS file to change the appearance of a particular section but didn’t realize until it has been live for a few days that it also changed the appearance in another section. It was pure coincidence that we stumbled across the other section and spotted the issue.
Imagine how small changes throughout weeks or months could inadvertently add up to drastically affect the layout and functionality of unintended elements.
I recommend taking an approach similar to the one I explained for testing page speed. First, identify the pages that drive 30 percent of your organic traffic for testing. Then identify any pages not part of this group that is critical to your business. You can skip the pages that deliver the bottom 10 percent of your organic traffic.
Unfortunately, to test layout and functionality, you will need to manually check these pages, but in most cases, it shouldn’t take more than a few seconds per page.
Opinions expressed in this article are those of the guest author and not necessarily Search Engine Land. Staff authors are listed here.