Technical SEO Checklist for WordPress Websites

I still remember the night I almost gave up on my WordPress blog.

I’d spent three months writing what I thought were genuinely good posts. Decent word count, proper headings, images, the whole thing. But my traffic graph in Google Search Console looked like a flat line with a pulse problem. Barely any impressions. Almost zero clicks.

I assumed my content just wasn’t good enough. So I rewrote a few posts. Nothing changed.

Turns out the problem wasn’t my writing at all. It was everything happening behind the scenes that Google couldn’t even see properly — broken sitemaps, a robots.txt file quietly blocking my images folder, and a page speed score so bad my site was basically asking visitors to leave before it finished loading.

That’s when I actually sat down and learned technical SEO. Not the theory-heavy stuff, just the practical, “fix this and see what happens” kind. And honestly, once I started ticking things off, my organic traffic doubled in about four months. Not overnight magic, but steady, real growth.

So here’s the checklist I put together from actually going through it — mistakes included.

Why Technical SEO Matters More Than People Think

Most beginners obsess over keywords and forget that Google first has to be able to crawl, understand, and load your site properly. You can have the best article on “best coffee makers 2026,” but if your site takes 8 seconds to load or your pages return the wrong status codes, none of that content matters.

Technical SEO is basically the plumbing of your website. Nobody notices it when it works. Everybody notices when it doesn’t.

1. Start With Google Search Console (Your Reality Check)

Before fixing anything, you need to know what’s actually broken. I skipped this step originally and just guessed at problems, which wasted weeks.

Set up Google Search Console if you haven’t already, then check:

• Coverage report — pages Google can’t index, and why
• Sitemaps — whether your sitemap is even submitted
• Core Web Vitals — how your pages perform on real user data
• Mobile usability — errors specific to mobile visitors

When I finally checked mine, I found 40+ pages marked “Crawled – currently not indexed.” That single discovery explained half my traffic problem.

2. Fix Your Robots.txt File (Mine Was Silently Blocking Content)

This one stung. My robots.txt file, generated by a plugin I installed and forgot about, was blocking /wp-content/uploads/. That meant Google couldn’t properly crawl or index a chunk of my images, which also hurt my image search traffic.

How to check yours:

1. Go to yourdomain.com/robots.txt
2. Look for any Disallow lines
3. Make sure you’re not accidentally blocking CSS, JS, or image folders
4. Confirm your sitemap URL is listed at the bottom

If you’re using Rank Math or Yoast SEO, both let you edit robots.txt directly from the plugin settings, no FTP needed.

3. Submit and Clean Up Your XML Sitemap

Your sitemap is basically a map you hand Google so it doesn’t have to guess how your site is structured.

Rank Math and Yoast both auto-generate one at /sitemap_index.xml or /sitemap.xml. Submit that exact URL in Search Console under the Sitemaps tab.

A mistake I made: my sitemap included tag pages and thin author archive pages that had almost no content. Google was wasting crawl budget on junk pages instead of my actual articles. I went into my SEO plugin settings and excluded tags and archives from the sitemap. Within a few weeks, indexing improved noticeably.

4. Sort Out Your Site Speed (This Is the Big One)

I used to think speed only mattered for user experience. It also directly affects rankings through Core Web Vitals.

Here’s what actually moved the needle for me:

• Installed a caching plugin — I use WP Rocket, though LiteSpeed Cache is a solid free alternative if your host supports it
• Compressed images before uploading using ShortPixel instead of relying on WordPress to do it after the fact
• Switched to a lighter theme — I was using a bloated multipurpose theme with features I never used. Moving to a lightweight theme like GeneratePress cut my load time almost in half
• Removed unused plugins — I had 27 plugins installed at one point. I now run under 12

Test your speed using both Google PageSpeed Insights and GTmetrix, since they measure slightly different things. Don’t chase a perfect 100 score — I’ve never seen a real business site hit that. Aim for “good” Core Web Vitals instead of obsessing over the number.

5. Fix Your URL Structure Before It’s Too Late

If your permalinks still look like yourdomain.com/?p=123, change that immediately under Settings > Permalinks and choose the “Post name” structure.

Just be careful — if your site already has traffic and indexed pages, changing permalink structure later means you’ll need to set up 301 redirects for every old URL. I learned this after switching structures on a client site and losing rankings for two weeks because old URLs started returning 404 errors.

The Redirection plugin makes this manageable if you ever need to do bulk redirects.

6. Handle Duplicate Content and Canonical Tags

WordPress creates a surprising number of duplicate-ish pages automatically — category pages, tag pages, paginated archives. Without canonical tags, Google can get confused about which version to rank.

Rank Math and Yoast handle canonical tags automatically in most cases, but it’s worth spot-checking a few pages using “View Page Source” and searching for rel="canonical" to confirm it’s pointing to the right URL.

7. Make Sure Your Site Is Actually Mobile-Friendly

Not “looks fine on my phone” mobile-friendly — actually tested. Use Google’s Mobile-Friendly Test tool and check a few different page types: homepage, blog post, product page if you have one.

I once had a pricing table that looked perfect on desktop but overflowed horizontally on mobile, forcing users to scroll sideways to read prices. That’s the kind of thing you only catch by actually testing on a real device, not just resizing your browser window.

8. Set Up Proper HTTPS and Fix Mixed Content Warnings

If your site isn’t on HTTPS yet, most hosts now offer free SSL certificates through Let’s Encrypt — Bluehost, SiteGround, and Hostinger all make this a one-click setup.

After switching to HTTPS, check for “mixed content” warnings, which happen when some resources (usually old images) still load over HTTP. The Really Simple SSL plugin catches most of these automatically.

9. Improve Internal Linking (Underrated but Powerful)

This isn’t strictly “technical” but it overlaps heavily. Google uses internal links to understand which pages matter most on your site.

I went through my top 20 posts and made sure each one linked to at least 3-4 relevant related posts. Simple move, but it helped spread authority around and reduced my bounce rate slightly too.

10. Check for Crawl Errors Regularly

Set a reminder to check Search Console’s Pages report monthly. Broken pages happen more often than you’d expect, especially after plugin updates or theme changes.

Screaming Frog’s free version (crawls up to 500 URLs) is genuinely useful here. Run it occasionally to catch broken links, missing meta descriptions, or duplicate title tags before Google finds them first.

Common Mistakes I See (and Made Myself)

• Installing too many SEO plugins at once — they can conflict and generate duplicate schema markup
• Ignoring image alt text — small thing, but it adds up across dozens of posts
• Ignoring the “noindex” tag — I once left a page set to noindex after testing something, and it sat invisible to Google for two months before I noticed
• Chasing perfect scores — obsessing over a 100/100 speed score instead of just making the site reasonably fast and usable

Related post: Internal Linking Strategy That Improves Rankings
Local SEO in 2026: The Complete Guide to Growing Your Business Online

Final Thoughts

None of this fixed my traffic overnight. It was more like slowly removing obstacles that were quietly working against me the entire time. The content I’d already written started performing better simply because Google could finally crawl, understand, and load it properly.

If you’re stuck wondering why decent content isn’t ranking, don’t assume it’s always the writing. Sometimes the real issue is sitting quietly in your robots.txt file or your Core Web Vitals report, waiting for someone to actually look.

Start with Search Console, work through this list one item at a time, and give it a few weeks before judging results. That’s roughly how it played out for me, and it’s been the same story for most site owners I’ve talked to since.