The Complete Technical SEO Checklist for 2026

The Complete Technical SEO Checklist for 2026

Last updated: March 2026 | Reading time: 14 minutes

You can publish the most compelling content on the internet, but if search engines cannot crawl, render, and index your pages properly, none of it matters. Technical SEO is the foundation of every successful search strategy. When that foundation cracks — broken canonicals, bloated page loads, misconfigured hreflang tags — your rankings crumble regardless of how strong your content or backlink profile may be.

This technical SEO checklist for 2026 is built from hundreds of audits we have conducted at our technical SEO practice. Every item is specific, actionable, and prioritised so you can work through it systematically — whether you are a business owner diagnosing why traffic has dropped, a marketing manager briefing your developer, or a junior SEO running your first full audit.

Bookmark this page. You will return to it often.

1. Crawling & Indexing

If Google cannot discover and index your pages, they do not exist in search. This section of the technical SEO audit checklist addresses the most fundamental requirement: making sure search engines can actually find your content.

Robots.txt Audit

☐ Verify your robots.txt is accessible at yourdomain.com/robots.txt. A 404 or 5xx response means Google assumes everything is crawlable — which sounds fine until Googlebot wastes your crawl budget on admin pages, staging environments, or filtered URL parameters.

☐ Check for accidental Disallow rules blocking critical pages. We see this constantly: a Disallow: / left over from a staging environment that migrated to production. Open Google Search Console (GSC) > Settings > Crawling > robots.txt to see exactly what Google last fetched.

☐ Ensure CSS and JavaScript files are not blocked. Google needs to render your pages fully. If your robots.txt blocks /wp-includes/ or /assets/js/, Google cannot render the page and may misinterpret its content.

☐ Reference your XML sitemap(s) in robots.txt. Add Sitemap: https://yourdomain.com/sitemap.xml at the bottom of the file. This gives every crawler — not just Google — a direct path to your sitemap.

XML Sitemaps

☐ Confirm your sitemap contains only indexable, canonical, 200-status URLs. Run your sitemap through Screaming Frog’s sitemap analysis mode. Every URL in your sitemap should return a 200 status code, should not have a noindex tag, and should be the canonical version of itself. A sitemap full of redirects and noindexed pages signals poor site hygiene to Google.

☐ Stay within sitemap size limits: 50,000 URLs or 50MB (uncompressed) per file. For larger sites, use a sitemap index file that references multiple child sitemaps. Segment by content type: sitemap-posts.xml, sitemap-products.xml, sitemap-categories.xml.

☐ Include accurate <lastmod> dates. Only update <lastmod> when the page content genuinely changes. Sites that set every <lastmod> to today’s date train Google to ignore the signal entirely.

☐ Submit sitemaps in GSC and monitor the “Discovered — currently not indexed” report. If Google discovers hundreds of URLs from your sitemap but chooses not to index them, you likely have a quality or crawl-budget problem.

Crawl Budget Optimisation

☐ Identify and eliminate crawl traps. Faceted navigation, infinite calendar widgets, and session-based URLs can generate millions of near-duplicate URLs. Use GSC’s Crawl Stats report to spot unusual spikes in crawl requests.

☐ Block low-value parameter URLs via robots.txt or GSC’s URL Parameters tool (if still available for your property). For example, ?sort=price-asc or ?colour=blue variants that do not warrant their own index entry.

☐ Fix or redirect soft 404s. Pages that return a 200 status but display “no results found” or empty content waste crawl budget. Identify these in GSC > Pages > “Soft 404”.

Canonical Tags

☐ Ensure every page has a self-referencing canonical tag. Even if a page has no duplicates today, a self-referencing canonical prevents future issues from URL parameters, tracking codes, or syndication.

☐ Check that canonical tags point to the correct, indexable version. A canonical should never point to a 404, a redirect, or a noindexed page. Screaming Frog’s “Canonicals” report flags these conflicts instantly.

☐ Resolve canonical chain conflicts. If Page A canonicals to Page B, and Page B canonicals to Page C, Google may ignore both signals. Every canonical should resolve in a single hop.

Noindex/Nofollow Usage

☐ Audit all pages with noindex meta tags or X-Robots-Tag headers. Confirm that noindexed pages are genuinely ones you want excluded — thank-you pages, internal search results, admin areas, thin tag pages.

☐ Never noindex a page that is also blocked by robots.txt. If Googlebot cannot crawl the page, it cannot see the noindex directive. The page may remain indexed indefinitely.

Orphan Pages

☐ Cross-reference your sitemap URLs against your crawl data. Any URL in your sitemap that is not reachable through internal links is an orphan page. Google may crawl it via the sitemap, but it receives no internal link equity, which severely limits its ranking potential.

☐ Cross-reference GSC indexed pages against your sitemap. Indexed pages that are not in your sitemap and have no internal links are hidden orphans — often old pages that still rank but could perform far better with proper internal linking.

2. Site Speed & Core Web Vitals

Core Web Vitals remain a confirmed ranking signal in 2026, and their impact compounds with user experience — slow pages drive higher bounce rates, which further erodes performance. This section of the website technical SEO checklist covers every metric that matters.

Largest Contentful Paint (LCP) — Target: Under 2.5 Seconds

☐ Identify your LCP element on key pages. Use Chrome DevTools > Performance panel or PageSpeed Insights. The LCP element is usually a hero image, a heading, or a featured video poster. You cannot optimise what you have not identified.

☐ Preload the LCP image. Add <link rel="preload" as="image" href="/hero.webp"> in the <head>. This tells the browser to fetch the largest element before it would naturally discover it in the HTML.

☐ Serve images in next-gen formats (WebP or AVIF). AVIF delivers 30-50% smaller file sizes than WebP for photographic content. Use the <picture> element with AVIF as the primary source and WebP as a fallback.

☐ Ensure server response time (TTFB) is under 800ms. If TTFB is slow, no amount of front-end optimisation will save your LCP. Investigate server-side caching, database query optimisation, or upgrading your hosting infrastructure. For Singapore-based audiences, ensure your server or CDN edge node is in the Asia-Pacific region.

☐ Eliminate render-blocking resources. Inline critical CSS (the styles needed for above-the-fold content) and defer all non-critical CSS and JavaScript. Use <script defer> or <script async> appropriately.

Interaction to Next Paint (INP) — Target: Under 200 Milliseconds

☐ Audit main-thread blocking time. Open Chrome DevTools > Performance > record a session of typical user interaction. Long tasks (exceeding 50ms) on the main thread are the primary cause of poor INP.

☐ Break up long JavaScript tasks using scheduler.yield() or setTimeout chunking. If a single task takes 300ms, the browser cannot respond to user input during that time. Split it into smaller chunks that yield back to the browser between executions.

☐ Defer or lazy-load third-party scripts. Analytics, chat widgets, social embeds, and ad scripts are notorious for blocking the main thread. Load them after the page becomes interactive, or use a facade pattern (e.g., a static image for a YouTube embed that loads the player only on click).

☐ Minimise DOM size. Pages with more than 1,500 DOM nodes see measurably worse INP. Audit for unnecessary wrapper divs, duplicated elements, and hidden content that could be loaded on demand.

Cumulative Layout Shift (CLS) — Target: Under 0.1

☐ Set explicit width and height attributes on all images and videos. This allows the browser to reserve the correct space before the asset loads, preventing content from jumping.

☐ Reserve space for dynamically injected content. Ad slots, cookie banners, and promotional bars that inject into the DOM without reserved space are the leading cause of CLS failures. Use min-height on container elements.

☐ Audit web font loading for FOUT/FOIT. Use font-display: swap at minimum. For better CLS, use font-display: optional — this prevents layout shifts entirely by falling back to the system font if the custom font does not load within a very short window.

☐ Avoid inserting content above existing content. If a notification bar or lazy-loaded element pushes the page down after initial render, it will trigger a layout shift. Insert above-the-fold dynamic elements before the first paint, or use CSS transforms (which do not trigger layout shifts) for animations.

Additional Speed Optimisations

☐ Configure browser caching with appropriate Cache-Control headers. Static assets (images, CSS, JS) should have max-age=31536000 (one year) with cache-busting filenames. HTML documents should use no-cache (always revalidate) or short max-age values.

☐ Implement a CDN. For sites targeting Singapore and the broader APAC region, a CDN with edge nodes in Singapore (Cloudflare, AWS CloudFront, or Bunny.net) reduces latency significantly for your primary audience.

☐ Implement responsive images with srcset. Serving a 2400px hero image to a 375px mobile screen wastes bandwidth. Use srcset with multiple image sizes and sizes to tell the browser which one to fetch based on the viewport.

☐ Lazy-load below-the-fold images. Use loading="lazy" on all images that are not in the initial viewport. Crucially, do not lazy-load the LCP image — this is one of the most common performance mistakes we encounter in SEO audits.

3. Mobile Optimisation

Google uses mobile-first indexing for all sites. The mobile version of your page is what Google sees, indexes, and ranks. If your mobile experience is degraded, your rankings will reflect it. Our mobile SEO specialists consistently find that these items are the most commonly overlooked.

☐ Test responsive design across real devices, not just browser emulators. Use BrowserStack or physically test on an iPhone SE (small screen), a mid-range Android device (representing the majority of Singapore’s mobile users), and a tablet. Browser DevTools emulation does not catch touch-specific issues or real-world rendering bugs.

☐ Verify the viewport meta tag is correctly configured. Your <head> should contain <meta name="viewport" content="width=device-width, initial-scale=1">. Do not use maximum-scale=1 or user-scalable=no — these prevent pinch-to-zoom, which is an accessibility violation and may negatively affect rankings.

☐ Ensure tap targets are at least 48×48 CSS pixels with 8px spacing between them. Google’s mobile usability report in GSC flags undersized tap targets, but it misses near-miss cases. Manually check navigation menus, footer links, and form elements.

☐ Confirm full content parity between mobile and desktop. Every piece of content that appears on the desktop version must be accessible on mobile. If you are hiding content behind accordions on mobile, that is acceptable — the content is still in the DOM. But if you are removing content entirely via CSS display:none combined with server-side decisions, Google will not see it.

☐ Test mobile page speed independently. Mobile devices typically have less processing power and may be on 4G connections. Run PageSpeed Insights with the “Mobile” tab selected and treat those scores as your primary benchmark.

☐ Eliminate intrusive interstitials. Full-screen pop-ups that cover the main content on mobile trigger Google’s intrusive interstitial penalty. Acceptable alternatives: small banners using less than 30% of the screen, legally required cookie consent dialogs, and age-verification gates.

4. Site Architecture & URL Structure

A well-structured site helps search engines understand content relationships and distributes link equity efficiently. It also helps users find what they need — and both of those outcomes improve rankings. Good architecture is central to effective on-page SEO.

URL Structure

☐ Use flat, descriptive, lowercase URLs. Prefer /technical-seo-checklist over /blog/2026/03/25/the-complete-technical-seo-checklist-for-2026. Shorter URLs tend to perform better and are more shareable. Remove unnecessary date folders unless publishing time-sensitive news content.

☐ Use hyphens, not underscores, to separate words. Google treats hyphens as word separators but treats underscores as word joiners. technical-seo is two words; technical_seo is one token.

☐ Avoid URL parameters for primary content pages. Parameters like ?id=234 or ?ref=homepage create duplicate content risks. Use clean, static URLs and handle tracking via JavaScript or server-side logic.

☐ Enforce a single URL format. Choose between www and non-www, trailing slash and non-trailing slash, and enforce it with 301 redirects. All four variations (www/non-www x slash/non-slash) should resolve to one canonical version.

Internal Linking Strategy

☐ Implement a hub-and-spoke (topic cluster) model. For each core topic, create a comprehensive pillar page (hub) that links to related, more specific pages (spokes), and ensure every spoke links back to the hub. This concentrates topical authority and creates clear semantic relationships for search engines.

☐ Audit for pages with fewer than 3 internal links pointing to them. In Screaming Frog, export the “Inlinks” data and sort by count. Pages with very few internal links are effectively invisible to both search engines and users.

☐ Use descriptive anchor text for internal links. “Click here” and “read more” waste an internal linking opportunity. Use anchor text that describes the target page’s content — this directly helps Google understand what the linked page is about.

Breadcrumbs

☐ Implement breadcrumb navigation on every page except the homepage. Breadcrumbs reinforce site hierarchy for both users and search engines. Use BreadcrumbList schema markup (covered in the Structured Data section below) to make breadcrumbs eligible for display in search results.

Site Depth

☐ Ensure all important pages are reachable within 3 clicks from the homepage. Use Screaming Frog’s crawl depth report to identify pages buried more than 3 levels deep. These pages receive less crawl attention and less internal link equity. Restructure navigation, add contextual internal links, or create hub pages to flatten the architecture.

Pagination

☐ Note that rel="prev" and rel="next" are no longer used by Google. Google confirmed they had not used these signals for years. Instead, implement these alternatives:

☐ For paginated article series: Create a “view all” page if the combined content is not excessively large (under 3MB). Canonical all paginated pages to the “view all” version. If a “view all” page would be too heavy, ensure each paginated page has unique, self-referencing canonicals and strong internal links between pages.

☐ For paginated listings (e-commerce categories, blog indexes): Ensure page 1 is the canonical and most linked-to version. Use noindex, follow on deeper paginated pages (/page/5/, /page/6/) if they add no unique ranking value. Implement infinite scroll with Google’s recommended pattern: real paginated URLs that are accessible without JavaScript, so Googlebot can follow the links.

5. Security

HTTPS has been a ranking signal since 2014, but security extends well beyond installing an SSL certificate. A compromised site can be deindexed entirely, and security headers increasingly influence how browsers treat your site. A robust security posture should be part of every web design and development project from the outset.

☐ Enforce HTTPS on every page. Check that all HTTP URLs 301-redirect to their HTTPS equivalents. Use Screaming Frog to crawl the full site and filter for any resources (images, scripts, iframes) loaded over HTTP — these are mixed content issues.

☐ Detect and fix mixed content. A single image loaded over HTTP on an HTTPS page triggers a “Not Secure” warning in some browsers. Use the browser console (DevTools > Console) to find mixed content warnings, or use a tool like Why No Padlock to scan entire pages.

☐ Implement HSTS (HTTP Strict Transport Security). Add the header Strict-Transport-Security: max-age=31536000; includeSubDomains; preload. This tells browsers to always use HTTPS for your domain, preventing downgrade attacks. Once confident, submit to the HSTS preload list.

☐ Set a Content Security Policy (CSP) header. CSP prevents cross-site scripting (XSS) by specifying which sources are allowed to load scripts, styles, and other resources. Start with Content-Security-Policy-Report-Only to monitor violations without breaking your site, then enforce once you have resolved all issues.

☐ Add X-Frame-Options and X-Content-Type-Options headers. X-Frame-Options: SAMEORIGIN prevents your site from being embedded in malicious iframes (clickjacking). X-Content-Type-Options: nosniff prevents browsers from MIME-type sniffing, reducing the risk of drive-by attacks.

☐ Run regular vulnerability scans. Use tools like Sucuri SiteCheck (free) or Qualys SSL Labs to check for known vulnerabilities, outdated server software, and SSL configuration weaknesses. Schedule monthly scans at minimum.

☐ Monitor GSC for “Security Issues” notifications. If Google detects malware, phishing, or hacked content, it will flag it in GSC and may add a warning to your search results. Check the Security Issues report weekly.

6. Structured Data & Schema Markup

Structured data does not directly boost rankings, but it enables rich results — enhanced search listings that dramatically improve click-through rates. Implementing the correct schema types for your content is a high-leverage technical SEO task.

Schema Types and When to Use Each

☐ Article schema — on every blog post and news article. Include headline, datePublished, dateModified, author (with a valid Person or Organization entity), and publisher. This enables article-specific rich results and supports Google News eligibility.

☐ LocalBusiness schema — on your contact or about page if you have a physical location. Include name, address (with PostalAddress), telephone, openingHours, and geo coordinates. For Singapore businesses, use "addressCountry": "SG" and include your UEN if applicable.

☐ Organization schema — on your homepage. Include name, url, logo, sameAs (linking to your social profiles), and contactPoint. This establishes your brand entity in Google’s Knowledge Graph.

☐ FAQ schema — on pages with genuine frequently asked questions. Each FAQ pair must be visible on the page (not hidden behind JavaScript that prevents rendering). Google has tightened FAQ rich result eligibility — they now primarily appear for authoritative government and health sites, but the schema still aids content understanding.

☐ HowTo schema — on tutorial and step-by-step guide pages. Include step objects with name and text for each step. Note that Google has reduced HowTo rich result visibility, but the structured data still contributes to content comprehension.

☐ Product schema — on every product page. Include name, description, offers (with price, priceCurrency as SGD where applicable, and availability), and aggregateRating if you have genuine reviews. This enables price and availability display in search results.

☐ BreadcrumbList schema — on every page with visible breadcrumb navigation. This gives Google an explicit understanding of your site hierarchy and enables breadcrumb-style URLs in search results instead of the raw URL path.

Validation

☐ Test every schema implementation with Google’s Rich Results Test. Visit search.google.com/test/rich-results and enter your URL. The tool shows which rich result types are detected and flags errors and warnings.

☐ Monitor the Enhancements section in GSC. After deployment, GSC will report valid items, items with warnings, and errors for each schema type. Resolve errors within 7 days and request revalidation.

☐ Use JSON-LD format, not Microdata or RDFa. Google recommends JSON-LD, and it is significantly easier to implement and maintain. Place the <script type="application/ld+json"> block in the <head> section.

7. International SEO

Singapore’s multilingual market makes international SEO particularly relevant even for businesses operating within a single country. With English, Chinese, Malay, and Tamil as official languages, proper language targeting prevents search engines from misidentifying your audience.

Hreflang Implementation

☐ Implement hreflang tags for every language version of each page. If you serve content in English and Chinese, every English page should contain both hreflang="en-sg" (self-referencing) and hreflang="zh-sg" (pointing to the Chinese version), and vice versa.

☐ Include an x-default hreflang. This specifies the fallback page for users whose language or region does not match any of your hreflang declarations. Typically, this is your English-language version: hreflang="x-default".

☐ Ensure hreflang reciprocity. Every hreflang relationship must be bidirectional. If Page A declares Page B as its Chinese equivalent, Page B must declare Page A as its English equivalent. Non-reciprocal hreflang tags are ignored by Google. This is the single most common hreflang error we see.

☐ Validate hreflang implementation at scale. Use Screaming Frog’s hreflang audit (Configuration > Spider > Hreflang) or Ahrefs’ Site Audit hreflang report. For large sites, implement hreflang via XML sitemap rather than HTML <link> tags to avoid bloating the <head>.

Language Targeting

☐ Set the correct lang attribute on the <html> element. For Singapore English, use <html lang="en-SG">. For Simplified Chinese, use <html lang="zh-Hans-SG">. For Malay, use <html lang="ms-SG">. This helps screen readers and browser translation features, and contributes to Google’s language detection.

☐ Use GSC’s International Targeting report to confirm Google is detecting the correct language for each page version.

Content Localisation vs. Translation

☐ Localise, do not merely translate. Singaporean English content should use local terminology (e.g., “HDB flat” not “public housing apartment”, “MRT” not “subway”). Chinese-language content should be in Simplified Chinese (used in Singapore) rather than Traditional Chinese (used in Taiwan and Hong Kong). Malay content should use Malaysian/Singapore Malay conventions.

☐ Localise structured data values. Prices should use SGD as the priceCurrency, addresses should follow Singapore’s postal format, and phone numbers should include the +65 country code.

☐ Adapt keyword strategy per language. Direct keyword translation rarely captures actual search behaviour. Research keywords natively in each language using Google Keyword Planner set to the Singapore market. Search intent often differs across language versions of the same query.

8. Essential Tools for Your Technical SEO Audit

A technical SEO audit checklist is only as effective as the tools you use to execute it. Here is what we use at our agency and what each tool does best.

Google Search Console (GSC)

Best for: Understanding how Google specifically sees your site. GSC is the only tool that provides Google’s actual data — which pages are indexed, which are excluded and why, which queries drive impressions, and what errors Google encountered during crawling. Start every audit here.

Key reports to check: Pages (indexing), Core Web Vitals (field data), Sitemaps, Links, Manual Actions, Security Issues.

Screaming Frog SEO Spider

Best for: Comprehensive site crawling that mimics how search engines discover and process your pages. It is the fastest way to identify broken links, redirect chains, missing meta tags, duplicate content, and orphan pages. The free version crawls up to 500 URLs — sufficient for most small-to-medium Singapore business websites.

Pro tip: Configure Screaming Frog to render JavaScript (Configuration > Spider > Rendering > JavaScript) to catch issues on JavaScript-heavy sites.

Google PageSpeed Insights

Best for: Diagnosing page speed and Core Web Vitals issues on a per-URL basis. It combines lab data (Lighthouse) with field data (Chrome User Experience Report) to give you both diagnostic recommendations and real-world performance metrics. Always prioritise field data — lab data is a simulation, field data is reality.

Ahrefs Site Audit

Best for: Ongoing monitoring and large-scale audits. Ahrefs crawls your site on a schedule, tracks issues over time, and groups problems by severity. Its internal linking analysis and content gap reporting make it particularly useful for identifying structural improvements. It also provides the best visualisation of site architecture and crawl depth.

Additional tools worth noting: Cloudflare Observatory for security header testing, Schema.org Validator for structured data debugging, and web.dev Measure for a holistic performance audit.

9. Frequently Asked Questions

How often should I run a technical SEO audit?

Run a full technical SEO audit quarterly, with monthly checks on critical metrics: Core Web Vitals field data in GSC, indexing errors, crawl stats, and security issues. If you deploy a major site update — redesign, CMS migration, URL restructure — run a full audit immediately before and after the change. Many of the issues in this technical SEO checklist can be caught early through automated monitoring tools like Ahrefs Site Audit, which runs on a configurable schedule.

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

Technical SEO focuses on the infrastructure that enables search engines to crawl, render, and index your site — server configuration, site speed, security, structured data, and architecture. On-page SEO focuses on the content and HTML elements visible on individual pages — title tags, headings, keyword usage, and content quality. Both are essential. Technical SEO creates the foundation; on-page SEO builds the structure on top. A page with perfect on-page optimisation will not rank if Google cannot crawl it, and a perfectly crawlable page will not rank if its content does not match search intent.

Do I need to hire a specialist for technical SEO, or can I handle it in-house?

Many items on this technical SEO checklist can be handled by a competent developer or marketing manager with some training — particularly crawl audits, sitemap management, and basic schema implementation. However, complex issues like JavaScript rendering problems, crawl budget optimisation for large sites, international SEO configuration, and Core Web Vitals debugging often require specialist expertise. If your site has more than 10,000 pages, operates in multiple languages, or relies heavily on JavaScript frameworks, working with a dedicated technical SEO team will almost always deliver a faster and more reliable outcome.

How long does it take to see results from technical SEO improvements?

Some changes produce visible results within days — fixing a sitewide noindex tag, resolving a major crawl error, or implementing redirects for broken high-traffic URLs. Core Web Vitals improvements typically take 28 days to reflect in GSC’s field data, as Google uses a rolling 28-day window from the Chrome User Experience Report. Structural changes like improving internal linking architecture or restructuring URLs may take 2-4 months to fully impact rankings, as Google needs to recrawl, reprocess, and re-evaluate the affected pages.

Is technical SEO more important than content or backlinks?

Technical SEO is not more important than content or backlinks — it is a prerequisite for them. Think of it this way: if your technical foundation prevents Google from indexing 40% of your pages (which we have seen more than once during audits for Singapore businesses), then 40% of your content investment is generating zero organic return. If slow page speed causes a 53% bounce rate on mobile (Google’s own benchmark), your content never gets read. Fix technical issues first, then invest in content and links. That said, a technically perfect site with thin content and no backlinks will not rank either. All three pillars — technical, content, and authority — must work together as part of a comprehensive search engine optimisation strategy.

Start Your Technical SEO Audit Today

This technical SEO checklist for 2026 covers every critical element that affects how search engines discover, understand, and rank your website. Work through it section by section, prioritising quick wins (security issues, indexing errors, broken canonicals) before tackling larger structural improvements.

If you would rather have specialists handle the audit — and the implementation — our technical SEO team has the tools, experience, and Singapore-market expertise to identify and resolve every issue on this checklist, typically within 4-6 weeks. Get in touch for a no-obligation technical audit consultation.