Technical SEO Checklist – 25 Checks for Beginners (2026)

Here’s something we see in almost every batch of new students. Someone builds a nice WordPress site, writes ten blog posts, waits two months and gets zero traffic. When we open their Search Console together, the reason is usually boring. The site is set to “Discourage search engines”. Or half the pages redirect to the homepage. Or the sitemap lists pages that don’t exist.

Good content can’t rank if Google can’t read it properly. That’s what technical SEO is about.

This checklist has 25 checks, grouped into 7 parts. Work through it on your own website or a practice site. If you’re new to the topic, read our technical SEO for beginners guide first, then come back and use this page as your working list.

Before You Start: Tools You Need

You don’t need paid software to learn technical SEO. These free tools cover everything below:

• Google Search Console shows what Google has indexed, what it couldn’t index, and why.
• PageSpeed Insights measures speed and Core Web Vitals for mobile and desktop.
• Your browser. Right-click, “View page source” shows you the title, canonical and robots tags.
• Screaming Frog SEO Spider (free up to 500 URLs) crawls your site like Google does and lists broken links and redirects.

Open Search Console in one tab and your website in another. Now go step by step.

Part 1: Security and Site Basics (Checks 1–3)

1. The whole site loads on HTTPS. Type your domain with http:// in front. It should jump straight to the https:// version. Google treats HTTPS as a ranking signal, and Chrome shows “Not secure” on plain HTTP pages, which scares visitors away.

2. Only one version of your site exists. http://example.com, http://www.example.com, https://example.com and https://www.example.com should all end up at one single address. If two versions load separately, Google sees duplicate websites.

3. Search engines are allowed in. In WordPress, go to Settings → Reading and make sure “Discourage search engines from indexing this site” is not ticked. Developers tick it while building the site and forget to untick it at launch. It happens more often than you’d think.

Checklist for Part 1:

• HTTP redirects to HTTPS on every page
• www and non-www versions redirect to one preferred version
• “Discourage search engines” is switched off

Part 2: Crawling – Can Google Reach Your Pages? (Checks 4–7)

4. robots.txt exists and isn’t blocking important pages. Open yourdomain.com/robots.txt. A line like Disallow: / blocks the whole site. That’s a disaster on a live website. Blocking /wp-admin/ is normal. If you need to write one from scratch, our free robots.txt generator builds a safe file for you.

One thing students often get wrong: robots.txt stops crawling, not indexing. If you want a page kept out of Google, use a noindex tag instead (check 10).

5. CSS and JavaScript files aren’t blocked. Google renders pages like a browser. If robots.txt blocks your theme’s CSS or JS files, Google sees a broken page. Use the URL Inspection tool in Search Console and click “View crawled page” to see what Google sees.

6. Every important page has at least one internal link. A page that no other page links to is called an orphan page. Google may never find it. Your course pages, service pages and best articles should be linked from the menu, footer or related posts.

7. Important pages are within 3 clicks of the homepage. The deeper a page sits, the less often Google crawls it. Flat, simple site structure wins.

Checklist for Part 2:

• robots.txt opens and doesn’t contain Disallow: /
• CSS and JS are not blocked
• No orphan pages among your important pages
• Key pages reachable within 3 clicks

Part 3: Indexing – Is Google Storing Your Pages? (Checks 8–12)

8. An XML sitemap exists and is submitted. Plugins like Rank Math or Yoast create one automatically, usually at /sitemap_index.xml. Submit it under Search Console → Sitemaps. A single sitemap file can hold up to 50,000 URLs.

9. The sitemap only lists pages you want ranked. No redirected URLs, no 404 pages, no noindex pages, no thank-you pages. A clean sitemap tells Google, “These are my real pages.”

10. noindex is used on purpose, not by accident. Thank-you pages, login pages and internal search results should be noindex. Your money pages should not. Check the page source for <meta name="robots" content="noindex"> on any page that isn’t showing in Google.

11. Canonical tags point to the right URL. A canonical tag tells Google which version of a page is the main one. Every page should normally have a canonical pointing to itself. If a blog post’s canonical points to the homepage, Google may ignore the post completely.

12. You’ve read the “Why pages aren’t indexed” list. In Search Console → Indexing → Pages, Google lists reasons like “Crawled – currently not indexed”, “Duplicate without user-selected canonical” and “Page with redirect”. Some of these are normal. Others point straight at a problem. Make it a habit to open this report every month.

Checklist for Part 3:

• XML sitemap submitted in Search Console
• Sitemap contains only live, indexable, 200-status pages
• No accidental noindex on important pages
• Self-referencing canonical on every normal page
• Page indexing report reviewed and real issues fixed

Part 4: URLs, Redirects and Broken Links (Checks 13–16)

13. URLs are short, lowercase and readable. /technical-seo-checklist/ is good. /?p=8432 or /Technical_SEO_Checklist_2026_Final/ is not. Use hyphens, not underscores. Our URL slug generator turns any title into a clean slug.

14. Every changed or deleted URL has a 301 redirect. If you change a page’s URL, redirect the old one to the new one. If you delete a page, redirect it to the closest related page, not blindly to the homepage.

15. No redirect chains. A chain is when URL A redirects to B, and B redirects to C. Each hop wastes crawl time and can lose a little value. Point A straight to C.

16. No broken internal links (404s). Run a crawl with Screaming Frog and filter by “Client Error (4xx)”. Fix the link at its source, or redirect the dead URL. On WordPress, Rank Math’s 404 Monitor shows which missing pages people are actually hitting.

Checklist for Part 4:

• Clean, lowercase, hyphenated URLs
• 301 redirects in place for every changed or removed URL
• Redirects go to the final URL in one hop
• Zero broken internal links

Part 5: Speed and Core Web Vitals (Checks 17–20)

Here are the three numbers and the “good” targets Google publishes:

17. Core Web Vitals pass on mobile. Test your key pages in PageSpeed Insights. Look at the field data section first (“Discover what your real users are experiencing”). That’s real Chrome user data, and it’s what Google actually uses.

18. Images are compressed and sized correctly. A 3 MB photo shown at 400 pixels wide is the most common speed problem on small business sites. Convert to WebP, resize before uploading and set width and height on every image so the layout doesn’t jump.

19. Caching is switched on. On WordPress, a caching plugin such as LiteSpeed Cache or WP Rocket serves ready-made pages instead of building them on every visit.

20. No heavy, unused scripts. Every chat widget, slider, popup and tracking pixel adds weight. Remove plugins you don’t use. Test speed again after each change, so you know what actually helped.

Checklist for Part 5:

• LCP, INP and CLS in the “good” range on mobile
• Images compressed, in WebP, with width and height set
• Page caching enabled
• Unused plugins and scripts removed

Part 6: Mobile Friendliness (Checks 21–22)

21. Same content on mobile and desktop. Some themes hide sections on mobile to “keep it clean”. If your course details or FAQ are hidden on mobile, Google may not count them.

22. No sideways scrolling and readable text. Open your site on a real phone. Can you read the text without zooming? Does the page slide left and right? Are buttons big enough to tap? Wide tables, long URLs and fixed-width images are the usual causes of sideways scroll.

Checklist for Part 6:

• Mobile shows the same main content as desktop
• No horizontal scroll on a 360px-wide phone
• Text readable at 16px or larger, tap targets easy to press

Part 7: Structured Data and Search Appearance (Checks 23–25)

23. The right schema type is on the right page. LocalBusiness or Organization on the homepage, Article on blog posts, Course on course pages, FAQPage where you have real FAQs. Our schema markup generator writes the JSON-LD code for you.

24. Schema has no errors. Paste your URL into Google’s Rich Results Test. Fix anything marked as an error. Warnings are less urgent.

25. Every page has one unique title and meta description. This sits between technical and on-page SEO. Duplicate titles across many pages confuse Google about which page to rank. Our meta tag generator helps you write them within the right length. For the full on-page side, use our on-page SEO checklist.

Checklist for Part 7:

• Correct schema type on each page template
• Rich Results Test shows no errors
• No duplicate titles or meta descriptions

How Often Should You Run This Checklist?

You don’t need all 25 checks every week. Here’s a simple routine that works for most small websites:

Practice Task: Audit One Real Website This Week

Reading a checklist won’t make you job-ready. Doing one will. Pick a small business website, maybe a local shop, a friend’s clinic or your own blog. Run all 25 checks and write down what you find in a simple sheet with three columns: Check, Problem found, How to fix.

That sheet is a real portfolio piece. When an interviewer asks, “Have you done a technical SEO audit?”, you can show them one instead of describing one. Students in our SEO course in Coimbatore do exactly this on live websites, with a trainer reviewing each finding, before they move on to on-page and off-page work.

Frequently Asked Questions About Technical SEO

What is a technical SEO checklist?

It’s a list of checks that confirm search engines can crawl, render and index your website properly. It covers HTTPS, robots.txt, XML sitemaps, canonical tags, redirects, broken links, page speed, Core Web Vitals, mobile friendliness and structured data.

Is technical SEO hard for beginners?

No. Most technical SEO checks only need Google Search Console, PageSpeed Insights and a browser. You don’t need to know coding to find problems. Some fixes, like speed improvements, may need a developer, but spotting the issue is a skill any beginner can learn in a few weeks.

What is the difference between technical SEO and on-page SEO?

Technical SEO makes sure Google can access and understand your website as a whole: crawling, indexing, speed and site structure. On-page SEO improves the content of individual pages: titles, headings, keywords, images and internal links. You need both for a page to rank.

Does robots.txt remove a page from Google?

No. robots.txt only stops Google from crawling a page. A blocked page can still appear in search results if other sites link to it. To keep a page out of Google, allow crawling and add a noindex meta tag.

How long does it take to see results after fixing technical SEO issues?

Small fixes like removing an accidental noindex can show results within days once Google recrawls the page. Bigger changes like site-wide redirects or speed improvements usually take a few weeks. Use the URL Inspection tool in Search Console to request a recrawl of important pages after you fix them.

Sources

• Google Search Central: Crawling and Indexing
• web.dev: Core Web Vitals
• Google Search Central: Build and Submit a Sitemap
• Google Search Central: Introduction to robots.txt