Technical SEO Checklist for 2026 — Prioritised by Impact

Most technical SEO checklists list everything alphabetically or by difficulty. That leaves you doing low-impact work while a crawl error blocks half your pages from indexation. This checklist is ordered by impact on organic traffic. Start at the top and work down. Skip nothing in the first two levels.

Level 1: Crawlability and indexation

If Google cannot reach a page, it cannot rank it. This is the highest-impact category because fixing a crawl problem can unlock hundreds of pages that were invisible.

Check your robots.txt. Run the URL through a robots.txt tester. Ensure you are not accidentally blocking CSS, JavaScript or images — Google needs those to render your page correctly. If you have accidentally blocked an entire section of your site, unblock it immediately.

Review your XML sitemap. Submit it in Google Search Console and check for errors. A good sitemap lists only canonical, indexable pages. Remove URLs that return 3xx, 4xx or 5xx status codes, and keep the sitemap under 50,000 URLs or 50 MB. Our robots.txt generator can help you set up a clean starting point.

Fix crawl errors. In Google Search Console, go to the Pages report. Everything marked "not found", "server error" or "redirect error" needs attention. A 404 that should have been a 301 is lost authority. A pattern of 5xx errors tells Google your server is unreliable.

Audit internal linking. Pages with no internal links pointing to them are orphan pages. They may be indexed, but they receive almost no link equity from the rest of your site. Run a link audit and add contextual links to every important page. Our internal linking guide shows the process.

Check for duplicate content. If the same content lives at multiple URLs, Google has to pick one. Use self-referencing canonicals on every page and redirect or canonicalise duplicate versions. This is especially common with e-commerce sites where filter parameters create hundreds of near-identical URLs.

Level 2: Page speed and Core Web Vitals

Google has confirmed that page speed is a ranking factor, and more importantly, users abandon sites that take more than three seconds to load. The three Core Web Vitals — LCP, INP and CLS — are the metrics that matter.

Measure your current state. Run your site through PageSpeed Insights or look at the Core Web Vitals report in Search Console. Focus on the field data — real user measurements — rather than lab data. If field data shows failing scores, you have a problem that needs fixing regardless of what your local test says.

Optimise images. Images are the most common cause of slow LCP. Convert to WebP, serve responsive sizes with srcset and lazy-load below-the-fold images. A properly optimised hero image can cut LCP by 40 percent. Read our detailed guide on how to improve LCP for cause-by-cause fixes.

Eliminate render-blocking resources. CSS and JavaScript that must load before the page renders delay LCP. Inline critical CSS, defer non-critical JavaScript and remove unused code. Tools like PageSpeed Insights will tell you exactly which resources are blocking.

Reduce server response time. Aim for a Time to First Byte under 800 milliseconds. If your server takes longer, consider upgrading your hosting plan. The jump from shared to private shared hosting at BD 8.5 a month often solves this immediately.

For a full walkthrough of all three metrics, see our Core Web Vitals explained article.

Level 3: Mobile usability

Google uses mobile-first indexing, meaning the mobile version of your site determines rankings. If your desktop site is flawless but the mobile version has problems, your rankings will reflect the mobile version.

Check the Mobile Usability report in Search Console. It lists pages with issues such as text too small to read, tap targets too close together and content wider than the screen. These are usually quick fixes in the CSS.

Test viewport configuration. Ensure your meta viewport tag is present and set correctly. Without it, mobile browsers render the page at a desktop width and force users to zoom and scroll horizontally.

Verify font sizes and tap targets. Body text should be at least 16 px on mobile. Buttons and links should have enough spacing that a thumb tap does not hit the wrong target. Google recommends tap targets of at least 48 by 48 pixels.

Level 4: Structured data and schema

Structured data helps Google understand what your page is about and can qualify it for rich results — star ratings, product prices, FAQ accordions in search, event listings and more. In 2026, structured data also helps AI answer engines extract and cite your content.

Add the right schema for each page type. Every page should carry at minimum BreadcrumbList and the appropriate page-type schema. For articles, use BlogPosting or Article with author and publisher. For services, use Service with Offer. For FAQs, use FAQPage.

Validate your markup. Use Google's Rich Results Test and the Schema.org validator before deploying. Common mistakes include missing required fields, mismatched answer text in FAQ schema and orphaned schema blocks that reference a non-existent @id.

Test in an AI search engine. Paste your page URL into ChatGPT or Perplexity and see what it extracts. If the AI misses key information, your schema may need refinement. We cover this more in our schema markup guide and AI search optimisation guide.

Level 5: Security and HTTPS

A secure connection is non-negotiable. Chrome marks HTTP pages as "Not secure", and Google uses HTTPS as a ranking signal. Security is also a trust signal — visitors are unlikely to enter their details on a page served over HTTP.

Check your SSL certificate status. Ensure it is active, correctly installed and not expired. Use a full SSL check tool to verify the certificate chain and ensure there are no mixed-content warnings where secure pages load insecure resources like images or scripts over HTTP.

Fix mixed content. Any HTTPS page that loads an HTTP resource triggers a mixed-content warning. Most browsers block scripts and iframes loaded over HTTP on an HTTPS page. Use a crawler to find all mixed-content URLs and update them.

Redirect HTTP to HTTPS. Set up a 301 redirect from every HTTP URL to its HTTPS equivalent. Do not use 302 redirects — they do not pass link equity. Our website security checklist covers this and 23 other security actions.

Level 6: International SEO

If your business serves multiple countries or languages, international SEO is the final layer of technical optimisation. Get this wrong and you can accidentally hide the right version of your site from the right audience.

Use hreflang tags. For pages with content in multiple languages or aimed at different regions, add hreflang annotations to tell Google which version to serve to which user. Common mistakes include missing self-referencing hreflang, mismatched language codes and hreflang that points to a non-canonical URL.

Check language-specific canonicals. Each language version should have its own self-referencing canonical. Never canonicalise the Arabic version of a page to the English version, or vice versa — each is a separate page serving a different audience.

Verify country targeting in Search Console. If you have a country-specific site, set the target country in Search Console's International Targeting report. This tells Google which market the site is intended for and can improve local rankings.

Level 7: Crawl budget and log file analysis

Crawl budget determines how many pages Googlebot crawls on your site in a given period. For most small to medium business sites, crawl budget is not a limiting factor. But if your site has thousands of pages, a poor crawl budget can mean important pages are crawled infrequently or not at all.

Prioritise important pages in your sitemap. List your most important pages first and exclude low-value pages like tag archives, pagination or parameter-filtered URLs. Use noindex on pages that do not need to be in search results, which saves crawl budget for the pages that matter.

Monitor crawl stats in Search Console. The Crawl Stats report shows how many requests Googlebot made per day, the response codes it received and the time it spent downloading. A sudden drop in crawl activity may indicate a server issue or a robots.txt block.

Analyse server logs if possible. Log files tell you exactly which pages Googlebot is crawling, how often and whether it is encountering errors. Log file analysis is the most accurate way to identify crawl waste — pages Google is crawling that add no value to your rankings.

International SEO and crawl budget management are the most commonly overlooked areas in a technical SEO checklist. Most sites that complete levels one through five will see a significant improvement. Adding levels six and seven captures the remaining gains and builds a foundation that supports long-term growth.

Running your technical SEO audit

A technical SEO audit does not need to be expensive or complicated. The tools you need are mostly free, and the process can be completed in a day once you know what to check. Here is a practical workflow.

Step 1: Crawl your site. Use a crawler like Screaming Frog or Sitebulb to extract every URL, response code, meta tag and internal link. Export the crawl and look for 4xx and 5xx errors, missing meta descriptions, duplicate title tags and pages with no internal links. A crawl gives you the raw data you need for every subsequent step.

Step 2: Cross-reference with Search Console. Log into Google Search Console and compare the Pages report with your crawl data. Search Console shows you which pages Google has indexed, which it could not crawl and which have manual actions or security issues. Any page that is indexed but has a crawl error in your data needs attention.

Step 3: Test Core Web Vitals. Run your top five pages through PageSpeed Insights. If the field data shows poor LCP, CLS or INP, those pages are the priority. Fix the highest-impact issues first using the guidance in levels two and above of this checklist.

Step 4: Validate structured data. Use Google's Rich Results Test on your most important pages. Fix any errors or warnings in the schema markup before the next crawl cycle.

Step 5: Document and prioritise. List every issue found, estimate the traffic impact of fixing it and the effort required. Fix high-impact, low-effort items immediately. Schedule medium-impact items for the next development sprint. Re-audit quarterly to catch new issues.

For a structured audit approach that covers everything on this technical SEO checklist, see our technical SEO audit service and our detailed audit walkthrough.

Prioritising your technical SEO fixes

When you run your first technical SEO audit, the list of issues can feel overwhelming. The key is to prioritise by impact rather than trying to fix everything at once. Use this three-tier system to decide what to tackle first.

Tier 1 — Critical. Issues that prevent Google from crawling or indexing pages: blocked robots.txt, server errors, pages returning 4xx status codes, missing or broken XML sitemaps, and noindex on important pages. These must be fixed before anything else because no other SEO work matters if the pages are invisible.

Tier 2 — High impact. Issues that directly affect rankings or user experience: poor Core Web Vitals, missing title tags or meta descriptions, thin content on important pages, duplicate content without canonicals, and broken internal links that waste crawl budget. These should be scheduled for the next development cycle.

Tier 3 — Improvement. Issues that improve performance but are not urgent: missing structured data, unoptimised images that are not the LCP element, non-critical redirect chains, and slow pages that are not in the top-traffic tier. These can be fixed over time as part of regular site maintenance.

Revisit your technical SEO checklist quarterly. A site that changes regularly — adding new pages, installing new plugins, updating the design — will accumulate new issues between audits. Catching them early prevents the slow degradation that silently costs traffic over months.