What Is Technical SEO? A Checklist for Non-Developers

Technical SEO is the part of search engine optimisation that makes sure search engines can find, crawl, render and index your website efficiently, and that the site is fast, secure and easy to use on any device. It covers things visitors rarely notice, such as XML sitemaps, robots.txt, redirects, canonical tags, page speed, mobile usability, HTTPS and structured data. When technical SEO is broken, even excellent content struggles to rank, because Google either cannot reach it or cannot trust which version to show.

How search engines process your website

To understand technical SEO, it helps to know the steps a search engine follows.

1. Discovery. Google learns that a URL exists, usually from a link, your sitemap or a submission in Search Console.
2. Crawling. Googlebot requests the page. Your server's response, speed and robots.txt rules decide whether it gets through.
3. Rendering. Google processes the HTML, CSS and JavaScript to see the page as a user would. Content that needs JavaScript is rendered later and less reliably.
4. Indexing. Google decides whether to store the page in its index, and which URL to treat as the canonical version.
5. Ranking. Indexed pages compete for searches based on relevance, quality, authority and experience.

Technical SEO removes friction from steps one to four, so your content can compete at step five.

The technical SEO checklist

Crawlability

• robots.txt allows crawling of everything you want indexed. A single "Disallow: /" line can hide an entire site.
• An XML sitemap exists at a predictable address such as /sitemap.xml, lists every indexable page, includes honest lastmod dates and is declared in robots.txt and submitted in Search Console.
• Internal links connect every important page. Pages with no internal links, called orphan pages, are rarely crawled.
• Links are real links. Navigation built with JavaScript click handlers instead of normal anchor tags with an href can be invisible to crawlers.
• No broken internal links. Every link should lead to a working page.

Indexability

• Important pages return a 200 status code.
• No stray noindex tags in the robots meta tag or the X-Robots-Tag header.
• Canonical tags point each page to its preferred address, usually itself.
• Missing pages return a real 404 or 410. If unknown addresses show your homepage with a 200 code, Google calls it a soft 404.
• Thin or duplicate pages are consolidated, redirected or marked noindex, so they do not dilute the site.

One version of every page

• HTTPS everywhere, with a valid certificate.
• http redirects to https with a permanent 301 redirect.
• One host. Either www or the bare domain, with the other redirecting to it.
• Short redirect paths. Each old URL should reach its destination in one hop.
• Consistent trailing slashes and lowercase URLs, so the same page is not reachable at several addresses.

Speed and Core Web Vitals

The usual fixes are compressed, correctly sized images in WebP or AVIF, image width and height attributes, lazy loading below the fold, fewer and deferred scripts, text compression with Brotli or Gzip, browser caching for static files, and good hosting with a CDN.

Mobile usability

• A responsive layout with a viewport meta tag.
• Readable text without zooming and tap targets large enough for a thumb.
• No intrusive pop-ups that cover content on mobile.
• The same important content on mobile as on desktop, because Google indexes the mobile version first.

Structured data and metadata

• Unique title tags and meta descriptions on every page.
• One H1 per page and a logical heading structure.
• Structured data such as Organization, LocalBusiness, Article, Product, FAQPage and BreadcrumbList, validated with Google's Rich Results Test.
• Open Graph and X card tags so shared links display a proper title, description and image.
• A declared language with the html lang attribute, and hreflang tags for multilingual sites.

JavaScript and rendering

Sites built with JavaScript frameworks can rank well, but they need care. Make sure important content and links are in the HTML the server sends, through server-side rendering or pre-rendering. Content that only appears after scripts run is indexed later by Google and is often invisible to AI crawlers.

Security and trust

• HTTPS with HSTS.
• No mixed content, meaning no images, scripts or styles loaded over plain http on secure pages.
• Basic security headers such as X-Content-Type-Options and Referrer-Policy.
• Keep the CMS, themes and plugins updated. Hacked sites can be flagged or removed from results.

AI search readiness

• AI search crawlers allowed in robots.txt if you want to be cited.
• Key content readable without JavaScript.
• An llms.txt file summarising your site and key pages.
• Organization structured data with sameAs links to your official profiles.

Technical SEO for online stores

E-commerce sites face technical problems that small brochure sites never meet, because they generate many pages automatically.

Faceted navigation lets shoppers filter by size, colour, price and brand. Each combination can create a new URL, and a store with a few hundred products can end up with millions of near-identical filter pages. Decide which filtered pages deserve to rank, such as "black running shoes", and give those clean URLs and unique content. Keep the rest out of the index with canonical tags, noindex or parameter handling, and avoid linking to endless combinations.

Out-of-stock and discontinued products need a policy. Temporarily unavailable products should stay live with a clear message and alternatives. Permanently discontinued products with links and rankings should redirect to the closest replacement or category, while those with no value can return a 404.

Pagination and sorting should not create duplicate versions of category pages. Make sure page two and beyond are crawlable through normal links and that sort orders do not produce new indexable URLs.

Product structured data with price, availability and review information makes products eligible for rich results and shopping features in Google.

Crawl budget and server logs

Google does not crawl every page of a large site every day. The amount of crawling it spends on your site, often called crawl budget, depends on how fast your server responds and how important Google thinks your pages are. For small sites this rarely matters. For sites with tens of thousands of URLs, wasted crawling on duplicate, filtered or low-value pages means important pages are refreshed less often.

Server logs show exactly which URLs Googlebot requests and how often. Reviewing them reveals crawl traps, such as calendars and filters that generate infinite URLs, along with important pages that are rarely visited and errors that only crawlers see. Fixing these focuses Google's attention where it matters.

International technical SEO

If you serve several countries or languages, technical choices decide whether the right version reaches the right searcher. Choose a URL structure, either country domains such as example.ae, subfolders such as example.com/ar/ or subdomains. Subfolders are usually the simplest to manage and keep authority on one domain. Add hreflang tags so every language version lists itself and all its alternatives, with an x-default for everyone else. Translate titles, descriptions and structured data as well as body text, and avoid automatically redirecting visitors by IP address, which can stop Google crawling other versions.

How to run a technical SEO audit

1. Run an automated check. Our free SEO checker tests 56 signals across indexing, speed, technical health and AI readiness in under a minute.
2. Review Google Search Console. The Pages report shows what is indexed and why other pages are excluded. Core Web Vitals and HTTPS reports show site-wide issues.
3. Crawl the site. A crawler tool follows every link like a search engine and reports broken links, redirect chains, duplicate titles, missing tags and orphan pages.
4. Test key templates. Check your homepage, a service or product page, a blog post and a category page in PageSpeed Insights and the Rich Results Test.
5. Prioritise. Fix anything that blocks crawling or indexing first, then duplication and redirects, then speed, then metadata and structured data.

Technical SEO during a redesign or migration

Most catastrophic ranking drops happen during redesigns, platform changes and domain moves. URLs change without redirects, noindex tags from the staging site go live, or canonical tags point to the old domain. Before any migration, map every old URL to its new home, test redirects in staging, keep titles and content that perform, and monitor Search Console daily after launch. Our guide on redesigning a website without losing SEO has the full checklist.

Technical SEO for different platforms

• WordPress. Generally SEO friendly with a good SEO plugin. Watch for bloated themes, too many plugins and duplicate archive pages.
• Shopify. Handles many basics automatically. Watch for duplicate product URLs through collections, app scripts that slow pages and limited control over some URLs.
• Webflow and Wix. Much improved for SEO. Check speed with heavy animations and make sure redirects are set when pages move.
• Custom and JavaScript frameworks. Flexible and fast when built well. Make sure rendering, metadata, sitemaps and redirects are handled deliberately.

How often should you check technical SEO?

Glance at Search Console weekly for new errors, run a full automated check monthly and do a deeper audit at least once a year, plus before and after any significant change to the site. Technical problems often arrive silently with a plugin update, a new tracking script or a security setting, and catching them early prevents ranking losses.

Written by the Proklisi editorial team

Proklisi builds websites and apps, runs SEO, ASO and social media, and creates SI influencers for brands. Everything here comes from work we do for clients every week. About us or talk to the team