Everything your website needs to be found, indexed, and ranked by Google in 2026. A complete technical SEO checklist covering Core Web Vitals, structured data, sitemaps, HTTPS, and more — with actionable fixes for each item.
Check your technical SEO score free — results in ~30 seconds:
If Google can't find or index your pages, nothing else matters. This is the foundation of technical SEO.
Create a sitemap.xml listing all important pages and submit it to Google Search Console (Settings → Sitemaps). Only include pages you want indexed — exclude login pages, admin areas, and duplicate content.
Check: Visit yoursite.com/sitemap.xml — it should return a valid XML file listing your pages.
Your robots.txt file tells crawlers which pages to skip. Common mistake: accidentally blocking important pages or CSS/JavaScript files Google needs to render your site.
Check: Visit yoursite.com/robots.txt and verify you're not Disallow-ing pages you want indexed. Never Disallow your sitemap file.
In Google Search Console, use the URL Inspection Tool to test any page. Google will show whether the page is indexed, any crawl errors, and how Googlebot renders the page (important for JavaScript-heavy sites).
Red flags: "Crawled — currently not indexed" or "Discovered — currently not indexed" means Google found but isn't indexing the page. Check for thin content, duplicate content, or noindex tags.
Check Coverage → Error pages regularly. 404 errors on pages with backlinks waste link equity — redirect them with 301 redirects. Server errors (5xx) prevent any indexing of affected pages and signal reliability issues to Google.
Search for <meta name="robots" content="noindex"> in your page HTML. This tag prevents Google from indexing the page. Development sites often have noindex enabled by default — double-check it's removed on production pages you want ranked.
HTTPS has been a Google ranking signal since 2014. Without it, Chrome shows "Not Secure" warnings that deter users and hurt conversions.
Get a free SSL/TLS certificate via Let's Encrypt (available through most hosting providers) or Cloudflare. Verify your certificate is valid and not expired. A expired SSL cert breaks your site for all visitors.
Every HTTP URL must redirect to its HTTPS equivalent with a 301 (permanent) redirect. Without this, you have two versions of every page competing for rankings and splitting link equity. Test by visiting http://yoursite.com — it should auto-redirect to https://yoursite.com.
Mixed content occurs when an HTTPS page loads resources (images, scripts, CSS) over HTTP. Chrome blocks mixed content and shows a broken padlock icon. Check DevTools → Console for "Mixed Content" errors and update resource URLs to HTTPS.
Security headers improve your Best Practices score and protect users. Key headers: X-Frame-Options: SAMEORIGIN (prevents clickjacking), X-Content-Type-Options: nosniff (prevents MIME sniffing), and Referrer-Policy: strict-origin-when-cross-origin.
Core Web Vitals are Google's direct page experience ranking signal since 2021. Passing all three thresholds gives you a competitive advantage.
| Metric | Good | Needs Work | Poor | What It Measures |
|---|---|---|---|---|
| LCP | ≤ 2.5s | 2.5–4s | > 4s | Loading — how fast the main content element appears |
| INP | ≤ 200ms | 200–500ms | > 500ms | Interactivity — response time to user clicks/keystrokes |
| CLS | ≤ 0.1 | 0.1–0.25 | > 0.25 | Visual stability — how much content shifts during load |
Images are the #1 cause of slow LCP. Convert to WebP or AVIF format (40–60% smaller than JPEG). Compress to under 200KB for above-the-fold images. Add loading="lazy" to below-the-fold images. Always specify width and height attributes to prevent layout shift (CLS).
Render-blocking scripts and stylesheets delay the first paint. Add defer or async to non-critical scripts. Move non-critical CSS to be loaded asynchronously, or inline critical CSS in the <head>.
A CDN serves your static assets (images, CSS, JavaScript) from servers close to your visitors, dramatically reducing latency. Cloudflare's free plan is a great starting point. Aim for Time to First Byte (TTFB) under 0.8 seconds.
Layout shift happens when elements move unexpectedly during page load — often caused by images without dimensions, ads, embeds, or fonts loading late. Always specify width and height on images. Use font-display: optional or font-display: swap with fallback fonts matched to your web font's metrics.
Heavy JavaScript blocks the main thread and causes poor INP scores. Break up long tasks (over 50ms) using scheduler.yield() or setTimeout. Remove unused JavaScript (use Chrome Coverage tab). Consider code-splitting for large single-page apps.
Google uses Mobile-First Indexing — it primarily crawls and indexes the mobile version of your site. If your mobile site is broken, your rankings will suffer regardless of how good your desktop site is.
Every page must include <meta name="viewport" content="width=device-width, initial-scale=1"> in the <head>. Without it, mobile browsers render your page at desktop width and users see tiny, unreadable text. This is one of the most basic and commonly missed technical SEO requirements.
Search Console's Mobile Usability report flags pages with clickable elements too close together, content wider than the screen, text too small to read, and viewport not set. Fix all reported issues — they directly affect your mobile ranking.
Tap targets (buttons, links) should be at least 44×44 CSS pixels (WCAG 2.5.5) or 24×24 with adequate spacing (WCAG 2.5.8 in WCAG 2.2). Small tap targets frustrate mobile users and are flagged by both SEO tools and accessibility auditors.
Google penalizes pages with intrusive interstitials (popups that cover the main content immediately after landing from search). Cookie consent banners are generally fine if they don't cover the entire screen; full-page popups that can't be dismissed are not.
Duplicate content and inconsistent URLs confuse Google and split ranking power across multiple versions of the same page.
Add a <link rel="canonical" href="https://yoursite.com/page/"> tag to every page to tell Google which version is the "master." This prevents duplicate content issues when pages are accessible via multiple URLs (with/without trailing slash, with UTM parameters, etc.).
Pick either www.yoursite.com or yoursite.com as your canonical domain and redirect the other version to it with a 301. Set your preferred domain in Google Search Console. Mixing the two creates duplicate content issues.
URLs should describe the page content: /guides/technical-seo-checklist is better than /p?id=1234. Use lowercase letters, hyphens (not underscores) between words, and avoid unnecessary parameters, session IDs, or dates that will become outdated.
A → B → C redirect chains waste crawl budget and slow page loads. Each hop in the chain adds latency and risks losing some link equity. Redirect directly from A to the final destination C. Check for chains with Screaming Frog or Google Search Console's Coverage report.
Structured data helps Google understand your page content and can unlock rich results in search (FAQs, reviews, breadcrumbs, sitelinks) that dramatically improve click-through rates.
Add WebSite schema with a SearchAction to your homepage to enable Sitelinks Search Box in Google results (users can search your site directly from the SERP). Also add Organization schema with your logo, contact info, and social profiles.
If you have FAQ sections on your pages, add FAQPage schema. This can expand your search result to show 2–4 expandable Q&As directly in the SERP, significantly increasing visible real estate without any change in ranking position.
Breadcrumb schema tells Google your site hierarchy, and Google displays breadcrumb paths in search results instead of raw URLs. This improves click-through rates and helps users understand where in your site they'd land.
Use Google's Rich Results Test (search.google.com/test/rich-results) to validate your structured data and preview how your page would appear as a rich result. Fix any errors — invalid JSON-LD will silently prevent rich results from appearing.
Internal links distribute "link equity" (PageRank) across your site and help Google discover and understand the relationships between your pages.
Pages that aren't linked to from anywhere else (orphan pages) are hard for Google to find and rank. Every page that matters should have at least one internal link pointing to it. Use your sitemap as a checklist — if a page is in the sitemap but has no internal links, fix it.
Anchor text tells Google what the linked page is about. "Click here" is worthless. "Website accessibility audit guide" is informative. Use keywords naturally — not stuffed — in your anchor text. Avoid linking the same keyword phrase to different pages (anchor text dilution).
Every extra click from the homepage reduces the crawl priority of a page. Important pages should be reachable in 1–3 clicks. If your blog posts are buried 6 levels deep, Google will crawl them less frequently and rank them lower than shallower pages on the same topic.
Broken internal links (linking to pages that return 404) waste crawl budget, hurt user experience, and can misdirect link equity. Audit monthly with a site crawler or Google Search Console's Coverage report. Either fix the broken link target or update the link to point to the right page.
Properly optimized images improve both SEO (via Google Images traffic and faster page loads) and accessibility (via descriptive alt text).
Alt text serves double duty: it helps Google understand image content for image search rankings, and it provides text descriptions for screen reader users. Write descriptive alt text that explains what the image shows and why it's on the page. Decorative images should use alt="" to be skipped by screen readers.
WebP images are 26% smaller than PNGs and 25–34% smaller than JPEGs at equivalent quality. AVIF is even smaller. Convert images during your build process. Use the HTML <picture> element with WebP as the primary source and JPEG as a fallback for older browsers.
Rename IMG_1234.jpg to website-accessibility-audit-checklist.webp. Google's image crawler uses filenames as signals for image content. Use hyphens between words, not underscores or spaces.
Use the srcset attribute to serve different image sizes to different screen sizes. A mobile user shouldn't download a 2000px wide image. This reduces page weight on mobile and improves Core Web Vitals scores.
Technical SEO isn't a one-time project. CMS updates, new templates, developer mistakes, and third-party scripts can introduce issues at any time. Set up ongoing monitoring to catch regressions before Google does.
| Monitoring Tool | What It Monitors | Frequency |
|---|---|---|
| Google Search Console | Crawl errors, indexing issues, Core Web Vitals (field data), manual actions | Weekly review |
| PageGuard | SEO score, meta tags, canonical, page speed, accessibility, best practices | Automated weekly/daily |
| Google PageSpeed Insights | Core Web Vitals (lab data), performance opportunities | After deployments |
| Bing Webmaster Tools | Bing crawl errors, keyword data, site scanner | Monthly review |
Add your site to PageGuard and get weekly automated SEO, performance, accessibility, and best practices scans with email alerts when scores drop. Catch technical issues within hours of deployment.
Start monitoring free ›Free. No signup required. SEO score, meta tag audit, Core Web Vitals, and more — in ~30 seconds.
Technical SEO is the process of optimizing a website's infrastructure so search engines can efficiently find, crawl, index, and rank your pages. It covers HTTPS, site speed (Core Web Vitals), sitemaps, robots.txt, canonical URLs, structured data, mobile optimization, and crawl error resolution — independent of content quality.
Run a free scan with PageGuard to check your SEO score, meta tags, and performance in 30 seconds. Also use Google Search Console (free) for crawl errors and indexing status, and Google PageSpeed Insights for Core Web Vitals measurements.
In 2026, the top technical SEO priorities are: (1) Core Web Vitals — especially LCP under 2.5s and INP under 200ms, (2) Mobile-First Indexing readiness, (3) HTTPS and security, (4) structured data for rich results, (5) crawlability and proper sitemap/robots.txt configuration, and (6) canonical URL implementation.
Run a comprehensive audit quarterly and after any major site change. Set up automated weekly monitoring with PageGuard to catch regressions as they happen — new pages missing meta descriptions, accidentally blocked URLs, or broken structured data.
Yes. Technical SEO covers infrastructure: crawlability, site speed, HTTPS, sitemaps, and structured data. On-page SEO covers content: keyword usage, headings, body text, and meta descriptions. Both are required for strong rankings — technical SEO ensures Google can access your content, on-page SEO ensures that content is relevant.