A technical SEO checklist covers the 25 things that decide whether search engines can crawl, render, index and trust your website: crawl access, indexing signals, site structure, Core Web Vitals, security, structured data and JavaScript rendering. Work through the checks below in order, fix anything that blocks crawling or indexing first, and then improve speed and structure.
At Softwix we have run technical audits on WordPress, WooCommerce and custom PHP sites since 2017, for clients in Bangladesh, the UK, the US and Europe. This is the same list our SEO team starts with, written so a business owner or in-house marketer can follow it without a developer for most steps.
Technical SEO checklist at a glance
| Area | Checks | Main tool | Why it matters |
|---|---|---|---|
| Crawling | 1–6 | robots.txt, XML sitemap, site crawler | If Google cannot reach a page, nothing else counts |
| Indexing | 7–12 | Search Console Page indexing report | Makes sure the right version of each page is in the index |
| Redirects and structure | 13–17 | Site crawler, analytics | Passes signals cleanly and helps users and bots find content |
| Performance and mobile | 18–21 | PageSpeed Insights, Core Web Vitals report | Page experience is part of what Google’s ranking systems reward |
| Security, data and rendering | 22–25 | Browser, Rich Results Test, URL Inspection | Trust, rich results and pages that render the same for bots as for people |
What is technical SEO, and does it still matter in 2026?
Technical SEO is the work that makes a website easy for search engines to crawl, render and index. It still matters in 2026 because every ranking, every rich result and every citation in an AI answer starts with a page that a crawler could fetch and understand.
Content and links get most of the attention, but they sit on top of the technical layer. A brilliant guide that is blocked in robots.txt, canonicalised to the wrong URL or hidden behind JavaScript that fails to render will not perform.
AI search has raised the stakes rather than lowered them. Answer engines still depend on crawlable, well-structured HTML, which is one reason technical hygiene features heavily in our SEO trends for 2027.
What tools do you need for a technical SEO audit?
You need four free or low-cost tools: Google Search Console, PageSpeed Insights, a site crawler and Google’s Rich Results Test. Together they cover almost every check on this list.
- Google Search Console – the Page indexing report, Core Web Vitals report, URL Inspection tool and sitemap submission.
- PageSpeed Insights – lab and field data for Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
- A site crawler – Screaming Frog, Sitebulb or a similar tool to find broken links, redirect chains, missing canonicals and orphan pages.
- Rich Results Test – validates structured data and shows how Google renders the page.
Run a full crawl first and export the results. Most of the checks below are a matter of filtering that export and comparing it with Search Console.
Can search engines crawl your site? (Checks 1–6)
Search engines can crawl your site if your robots.txt allows the important sections, your sitemap lists the right URLs, your server returns healthy status codes and your pages link to each other with normal HTML links. These six checks confirm it.
1. robots.txt does not block important pages
Open yoursite.com/robots.txt and read every Disallow line. Staging sites often go live with Disallow: / still in place, which blocks the whole site.
Remember what robots.txt is for. Google’s robots.txt documentation says it is used mainly to manage crawler traffic and “is not a mechanism for keeping a web page out of Google”. A blocked URL can still be indexed if other sites link to it. Use noindex or a password instead.
2. The XML sitemap is clean and submitted
Your sitemap should list only indexable, canonical URLs that return a 200 status. Remove redirected, noindexed and 404 URLs, then submit the sitemap in Search Console.
According to Google’s sitemap guidelines (updated July 2026), one sitemap can hold up to 50,000 URLs or 50MB uncompressed; larger sites need a sitemap index. Google ignores <priority> and <changefreq>, and only uses <lastmod> when it is consistently accurate, so do not update it for trivial changes.
3. Server status codes are healthy
Filter your crawl for 4xx and 5xx responses. Fix or redirect broken internal URLs, and investigate any 5xx errors with your host, because repeated server errors slow down crawling.
4. Internal links are crawlable HTML links
Google discovers pages through <a> elements with an href attribute. Menus, “load more” buttons and filters built only with JavaScript click events may hide pages from crawlers.
5. No important pages are orphaned
An orphan page has no internal links pointing to it. Compare your sitemap URLs with the URLs found in the crawl; anything in the sitemap but not in the crawl needs links from relevant pages.
6. Crawl budget is only a concern if you are large
Most small and medium sites do not need to worry about crawl budget. Google’s crawl budget guide is aimed at sites with over a million unique pages, sites with over 10,000 pages that change daily, or sites with many URLs stuck as “Discovered – currently not indexed”. If new pages are crawled the same day you publish them, move on.
Are the right pages being indexed? (Checks 7–12)
The right pages are indexed when Search Console shows your key pages as indexed, low-value pages are deliberately excluded, and every duplicate points to one canonical URL. These checks find the gaps.
7. Review the Page indexing report
In Search Console, open Indexing > Pages and read every “Why pages aren’t indexed” reason. Focus on reasons that affect pages you want to rank, such as “Crawled – currently not indexed” on service or product pages.
8. noindex is used on purpose, not by accident
Check that thank-you pages, internal search results, cart and account pages carry noindex, and that no money page does. On WordPress, also confirm that Settings > Reading > “Discourage search engines” is unticked on the live site.
9. Canonical tags point to the right URL
Every indexable page should have a self-referencing canonical, and duplicates should point to the main version. Google’s canonicalisation guide ranks redirects and rel="canonical" as strong signals and sitemap inclusion as a weak one. It also warns against using robots.txt or noindex to choose canonicals, and against sending conflicting signals on the same page.
10. One preferred version of the domain
Type the http, https, www and non-www versions of your homepage into a browser. All of them should end on one HTTPS version with a single 301 redirect.
11. Duplicate and thin URLs are under control
Look for URL parameters, tag archives, print versions and filtered category pages that create near-identical copies. Consolidate them with canonicals or noindex, and improve or merge thin pages that add nothing.
12. Missing pages return a real 404
A “page not found” message served with a 200 status is a soft 404. Test a made-up URL on your site and confirm it returns a 404 or 410 status with a helpful page that links back to key sections.
Do your redirects and site structure pass signals cleanly? (Checks 13–17)
Your structure passes signals cleanly when redirects are permanent and direct, important pages sit close to the homepage, and URLs and breadcrumbs describe where each page belongs. These five checks cover it.
13. Moved pages use permanent server-side redirects
Google recommends permanent server-side redirects (301 or 308) whenever content has moved for good. Temporary codes (302, 303, 307) keep the old URL in results, and JavaScript redirects are a last resort because rendering can fail.
14. No redirect chains or loops
Each old URL should jump straight to its final destination. Update internal links so they point to the final URL rather than relying on a redirect at all.
15. Important pages are within three clicks of the homepage
Check click depth in your crawler. Service pages, top categories and best-selling products should be reachable from the main menu or a hub page, not buried five levels deep in pagination.
16. URLs are short, readable and stable
Use lowercase words separated by hyphens, avoid dates and IDs where you can, and do not change URLs without redirects. A URL such as /web-design/ tells users and search engines more than /?page_id=482.
17. Breadcrumbs reflect the hierarchy
Breadcrumbs help users move up a level and give search engines context about how pages relate. Add BreadcrumbList structured data so they can appear in results.
Does your site pass Core Web Vitals and mobile checks? (Checks 18–21)
Your site passes when real-user data shows LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, and the mobile version carries the same content as desktop. Google’s Core Web Vitals documentation sets these thresholds and says good scores align with what its core ranking systems seek to reward.
18. Largest Contentful Paint (LCP) within 2.5 seconds
LCP measures how quickly the main content loads. The usual fixes are a faster host, page caching, a CDN, compressed and correctly sized hero images, and not lazy-loading the image that appears first.
19. Interaction to Next Paint (INP) under 200 milliseconds
INP measures how quickly the page responds when someone taps or clicks. It replaced First Input Delay as a Core Web Vital on 12 March 2024. Heavy JavaScript from page builders, chat widgets and tracking scripts is the most common cause of poor INP.
20. Cumulative Layout Shift (CLS) under 0.1
CLS measures unexpected movement while the page loads. Set width and height on images and embeds, reserve space for ads and banners, and load web fonts so they do not reflow text.
For WordPress sites, our guide on how to speed up a WordPress site and pass Core Web Vitals walks through each fix in detail.
21. Mobile content matches desktop
Google indexes and ranks the mobile version of your pages. Its mobile-first indexing guidance asks for equivalent primary content, matching titles, meta descriptions and structured data on both versions, and warns that Google will not load content that needs a swipe, click or typing to appear.
Is your site secure, structured and renderable? (Checks 22–25)
It is when every page loads over HTTPS without mixed content, structured data validates and matches what users see, JavaScript renders correctly for Googlebot, and multilingual pages declare their language versions. These final four checks close the audit.
22. HTTPS everywhere, with no mixed content
Check that your SSL certificate is valid and renews automatically, and that no images, scripts or fonts load over plain http. Browser developer tools flag mixed content in the console.
23. Structured data is valid and honest
Use JSON-LD for Organization, LocalBusiness, Product, Article, BreadcrumbList and FAQ markup where it fits. Google’s structured data guidelines say not to mark up content that is not visible, and that correct markup does not guarantee a rich result. Test every template in the Rich Results Test.
24. JavaScript content renders for Googlebot
Google crawls, then renders pages in headless Chromium, then indexes the rendered HTML. Use URL Inspection to compare the rendered HTML with what you see in a browser. Google’s JavaScript SEO guide also warns that if a page starts with noindex, Google may skip rendering, so removing noindex with JavaScript may not work.
25. hreflang is correct on multilingual sites
If you serve the same content in several languages or regions, such as English for the UK and Bangla for Bangladesh, each version needs hreflang tags pointing to every other version and to itself. Single-language sites can skip this check.
Which technical SEO fixes should you prioritise first?
Fix anything that stops crawling or indexing first, then redirects and duplication, then performance and enhancements. A slow page that is indexed can still rank; a fast page that is blocked cannot.
| Priority | Issue type | Examples |
|---|---|---|
| 1 – Critical | Blocks crawling or indexing | Sitewide Disallow, accidental noindex, 5xx errors, wrong canonicals on money pages |
| 2 – High | Wastes or splits signals | Redirect chains, duplicate domain versions, soft 404s, orphaned service pages |
| 3 – Medium | Hurts experience | Failing Core Web Vitals, mobile content gaps, mixed content |
| 4 – Enhancement | Improves visibility | Structured data, breadcrumbs, hreflang, cleaner URLs |
Online shops have a few extra checks, such as faceted navigation and out-of-stock product handling. Our WooCommerce SEO guide covers those.
How often should you run a technical SEO audit?
Run a full audit at least twice a year, and a quick check after every redesign, migration, theme change or major plugin update. Between audits, Search Console email alerts tell you when indexing or Core Web Vitals problems appear.
Large or fast-changing sites, such as e-commerce stores adding products every week, benefit from a monthly crawl. Keep each crawl export so you can compare changes over time.
Frequently asked questions
What is included in a technical SEO checklist?
A technical SEO checklist covers crawl access (robots.txt, sitemaps, status codes, internal links), indexing (noindex, canonicals, duplicates), redirects and site structure, Core Web Vitals and mobile parity, HTTPS, structured data and JavaScript rendering. The 25 checks in this guide follow that order so you fix blockers before enhancements.
How long does a technical SEO audit take?
For a small business site of under 100 pages, a thorough audit usually takes one to two working days. Large e-commerce sites with thousands of URLs can take a week or more, mainly because of duplicate and faceted URLs. Fixing the issues takes longer than finding them.
Can I do technical SEO myself on WordPress?
Yes, many checks need only Search Console, an SEO plugin and a crawler. Robots.txt edits, sitemap clean-up, noindex settings and redirects are all manageable from the dashboard. Server errors, Core Web Vitals and JavaScript rendering problems usually need a developer.
Do Core Web Vitals directly affect rankings?
Google says good Core Web Vitals align with what its core ranking systems seek to reward, so they are part of the picture. They do not outweigh relevant, helpful content. Treat them as a way to avoid losing ground and to keep visitors who would otherwise leave a slow page.
What is the difference between technical SEO and on-page SEO?
Technical SEO deals with the site as a whole: how it is crawled, indexed, rendered and served. On-page SEO deals with individual pages: titles, headings, content, images and internal links. Both are needed, and technical problems usually limit how much on-page work can achieve.
Get a technical SEO audit from Softwix
If you would rather have an expert run these 25 checks for you, Softwix can review your site and send you a prioritised list of fixes. Request a free SEO audit and we will show you which technical issues are holding your rankings back and what to fix first.
Part of the Softwix team — helping businesses grow through SEO, marketing and better websites.
