
Technical SEO Checklist for Blogs: 12 Checks We Ran on Our Own Site
A 12-point technical SEO checklist for bloggers, in the order problems cost you traffic, with the results from running it on our own 73-URL site.
November 4, 2026 · 9 min read
A technical SEO checklist for a blog comes down to one question: can Google reach each post, read it, and understand which URL to show? Twelve checks answer that, and the order matters. A robots.txt mistake can hide your whole site, while a missing bit of schema costs you almost nothing.
Google's technical requirements are short: Googlebot isn't blocked, the page returns a 200, and the page has indexable content. Google also says that meeting them doesn't guarantee indexing. So this list won't make a weak post rank. It removes the reasons a good post can't.
Most checklists never show what happens when you use them, so we ran this one on our own site on November 4, 2026. It found a real problem we hadn't noticed, which is covered below.
What We Found on Our Own Blog
We crawled all 73 URLs in the trafficmonitor.app sitemap, then requested every internal link those pages contain. The crawl was a short script, and a desktop crawler would get you the same list. Here's the full scorecard from November 4, 2026.
- 1. robots.txt allows posts: Pass. Only the dashboard, API, and login paths are blocked
- 2. No accidental noindex: Pass. 0 of 73 URLs
- 3. Pages return the right status: Pass. 73 of 73 return 200, and a made-up URL returns a real 404
- 4. One version of each URL: Pass. HTTP and trailing-slash versions both 308 to the clean URL
- 5. Canonical tags point to themselves: 2 misses. Both refund policy pages have no canonical
- 6. Sitemap lists only live pages: Pass. 73 of 73 return 200
- 7. Mobile version matches desktop: Viewport tag on 73 of 73. Content parity not tested
- 8. Internal links work: Fail. 64 links return 404
- 9. No orphan pages: Pass. Every sitemap URL has at least one internal link
- 10. Unique titles and descriptions: 3 duplicate groups, all on legal pages
- 11. Core Web Vitals: Not tested in this crawl
- 12. Structured data: Present on 8 of 73 URLs. Blog posts have none
The failure is the useful part. Each post and category page has a language switcher pointing to a Korean version of that page, but we only publish the blog in English, so all 64 of those links lead to a 404. Search Console's performance data wouldn't have flagged this, because nobody searches for those URLs. We only saw it because the crawl followed every link. Your site's version of this will be something equally boring, like a theme feature nobody clicks.
Can Google Reach and Index Your Posts?
These first three checks come first because a failure here can erase a post, or every post, from search.
1. Check robots.txt. Open yourblog.com/robots.txt and read it. You want your posts allowed and only private areas blocked. Google's documentation is explicit that robots.txt "is not a mechanism for keeping a web page out of Google", so don't use it to hide pages. If you've edited the file recently, test it before Google trips on it.
2. Look for accidental noindex. A leftover staging setting or an SEO plugin toggle can add noindex to a whole section. Check both the meta tag and the HTTP header, because the X-Robots-Tag header won't show up when you view the page source. One trap is that Google has to crawl a page to see its noindex, so a page blocked in robots.txt can still appear in results. If Search Console already lists pages as excluded by noindex, start there.
3. Confirm status codes. Live posts should return 200 and missing pages should return 404. The failure to look for is a "not found" page that returns 200, which Google reports as a soft 404. You can check any URL in a few seconds:
curl -sI https://yourblog.com/some-post | head -1
curl -sI https://yourblog.com/this-should-not-exist | head -1
If the second line says 200, your missing pages are soft 404s.
Does Every Post Have One Clear URL?
Once Google can reach a page, it has to decide which address to index. This is where small blogs quietly split their signals.
4. Redirect every variant to one version. Test http://, https://, www, and a trailing slash. Each should land on a single URL in one hop. Multiple hops are worth fixing with a redirect chain check. Seeing some Page With Redirect entries in Search Console is usually normal for these variants.
5. Use self-referencing canonicals. Every post should have a canonical tag pointing at its own URL. Google treats redirects and rel="canonical" as strong signals and sitemap inclusion as a weak one, so a sitemap alone won't settle it. Google can still choose differently, which is what the Alternate Page With Proper Canonical Tag status tells you.
6. Keep the sitemap clean. List only live, canonical URLs that you want indexed. The limits are 50MB or 50,000 URLs per sitemap, which no ordinary blog will reach. Google ignores priority and changefreq and only uses lastmod when it's consistently accurate, as our sitemap best practices guide explains. If the Sitemaps report shows an error, see what to do when a sitemap could not be read.
7. Match mobile to desktop. Google uses the mobile version of your content for indexing and ranking. If your theme hides sections or internal links on small screens, Google may not be counting them. Open a post on your phone and compare it with the desktop version, paying attention to anything collapsed or removed.
Can Crawlers and Readers Move Through Your Site?
Internal links are how Google finds new posts and how it judges which ones matter. They're also the part of a blog that decays fastest, since every deleted or renamed post leaves links behind.
8. Fix broken and redirecting internal links. Run a crawl with a tool from our free technical SEO stack. Screaming Frog's free tier covers 500 URLs. Check the template links too, not just the ones in your post body. All 64 of our broken links came from a template, which meant a single fix would clear them.
Also check that links are real anchors. Google says it can generally only crawl a link that's an <a> element with an href, so a JavaScript click handler on a button isn't a dependable path to a post.
9. Find orphan pages. A post that nothing links to depends on the sitemap alone. Compare your sitemap against the crawl's list of linked URLs to find orphan pages. Then do a wider internal linking audit, because one link from an old footer is technically not an orphan but isn't much support either. One of our posts had a link from only one other page we crawled, which passes this check and still needs work.
10. Clear duplicate titles and descriptions. A crawl export lists them in one sheet. Prioritize posts first, and fix duplicates by rewriting the page's actual purpose, not by adding a word. Our three groups were all legal pages, so they're low on our list.
Which Checks Can Wait?
The last two matter, but they rarely explain why a post is missing from Google entirely. Do them after the first ten.
11. Core Web Vitals. Google's "good" thresholds are LCP within 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Test a few post templates in PageSpeed Insights, not just your home page. Slow scores usually trace back to a theme, plugin, or oversized image shared across every post, so you can fix them once.
12. Structured data. It's optional for ranking, and Google has cut back what earns a rich result, so check what's still eligible with the Rich Results Test before spending time on it. Our posts have no article markup, and that's now on our list as an improvement, not an emergency.
One thing you can leave off entirely is crawl budget. Google's guide is aimed at sites with roughly 1 million or more pages, or 10,000 or more that change daily. If you run a normal blog, this isn't your problem.
How Often Should You Run This?
You don't need all twelve checks every week. Tie them to the events that break things.
- After a theme, plugin, or hosting change: checks 1 to 5, plus 11
- After a site migration or redesign: all twelve, right away
- Monthly: a crawl for checks 8 to 10, and a look at the Page indexing report
- After you publish a post: make sure something links to it, then give it time before you worry that it's not showing up in Search Console
A checklist only tells you what's true on the day you run it. Between runs, the first sign of a technical problem is often a post losing clicks. Traffic Monitor connects to Search Console with read-only access and tracks clicks, impressions, and CTR for each post daily, so a drop stands out as a change instead of something you find a month later. It won't replace the crawl, but it can tell you when to run one. You can connect your blog here.
The Short Version
Start at the top and stop to fix anything that fails. Reachability and indexing come first, then URL consistency, then internal links, and only then speed and schema. Run the crawl even if everything looks fine, because the problems it catches are the ones nobody reports. Ours was sitting in the navigation of every post, and we only found it by following the links.
Related posts
How to Add a User to Google Search Console (And Which Permission to Give)
How to add a user to Google Search Console, which level to pick (Owner, Full, or Restricted), the per-property limits, and how to remove access safely.
SEO Chrome Extensions for Bloggers: 6 Free Ones Worth Installing (And What Each Can't See)
The free SEO Chrome extensions a blogger actually needs, matched to one job each, plus the one Google retired and what no extension can tell you.
Track your blog rankings automatically
Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.
Start free →