Technical SEO
Technical SEO is the practice of optimizing website infrastructure so that search engines can efficiently crawl, render, index, and rank your content. For SEO programs, technical SEO is the foundation: even the best content will not rank if search engines cannot access, understand, or trust the underlying website. Technical SEO covers site speed, crawlability, indexation, structured data, mobile usability, and security.
This page covers what technical SEO involves, how I approach it, common mistakes, and the tools I use.
What It Is and Why It Matters
Technical SEO is distinct from content SEO and link building. Content SEO focuses on creating pages that match search intent. Link building focuses on earning external signals of authority. Technical SEO focuses on ensuring the website itself does not prevent search engines from accessing and properly evaluating your content.
The core areas of technical SEO include: site speed and Core Web Vitals (Largest Contentful Paint, Cumulative Layout Shift, Interaction to Next Paint), crawl efficiency (how search engines discover and access your pages), indexation management (controlling which pages are indexed and which are not), URL structure and canonicalization (preventing duplicate content issues), structured data markup (helping search engines understand page content), mobile usability (ensuring proper rendering on mobile devices), HTTPS security, and international SEO (hreflang implementation for multilingual sites).
For web development teams, technical SEO is an ongoing requirement, not a one time project. Every code deployment, content management system update, and infrastructure change can introduce technical SEO issues. Regular auditing and monitoring are essential to catch problems before they affect search traffic.
The tools I use for technical SEO include Screaming Frog for deep site crawling, Google Search Console for indexation monitoring and performance data, Ahrefs and Semrush for ongoing site health monitoring, and browser developer tools for performance analysis. Each tool provides different perspectives on technical health.
Common Use Cases
What technical SEO covers in practice.
Core Web Vitals Optimization
Improving page speed metrics (LCP, CLS, INP) that directly affect search rankings and user experience. This includes image optimization, font loading strategy, JavaScript reduction, server response time improvement, and layout stability fixes.
Crawl Budget Optimization
Ensuring search engines spend their crawl budget on your most important pages. This involves managing robots.txt, internal linking structure, XML sitemaps, and removing low value pages from the crawl path. Critical for large sites with thousands of pages.
Indexation Management
Controlling which pages appear in search results through proper use of noindex directives, canonical tags, and XML sitemaps. Preventing duplicate content issues and ensuring important pages are indexed while low value pages are excluded.
Structured Data Implementation
Adding JSON-LD schema markup to help search engines understand page content. Implementing Organization, FAQ, BreadcrumbList, Product, and other schema types that can result in rich search result features.
International and Multilingual SEO
Implementing hreflang tags correctly for multilingual sites, managing country specific URL structures, and ensuring search engines serve the right language version to users in different markets.
Site Migration Support
Planning and executing site migrations (domain changes, CMS migrations, URL restructuring) without losing search traffic. This involves URL mapping, redirect implementation, monitoring, and post migration validation.
Practical Experience
I approach technical SEO as an integral part of web development, not a separate discipline. When building or maintaining a website, technical SEO considerations are built into the architecture from the start rather than applied as fixes after problems appear.
For new sites built with Next.js, I implement the technical SEO foundation during development: server side rendering for complete HTML delivery, automatic sitemap generation from CMS data, programmatic meta tag management, canonical URL logic, structured data generation, and image optimization through the Next.js Image component. This approach prevents most common technical SEO issues from occurring in the first place.
For existing sites, I start with a comprehensive audit using Screaming Frog with JavaScript rendering enabled. This crawl reveals the site as Google sees it: which pages are accessible, how the internal link structure works, where redirect chains exist, which pages have technical issues, and how content is rendered. I cross reference the crawl data with Google Search Console index coverage reports to identify discrepancies between what the crawler finds and what Google has indexed.
Core Web Vitals optimization is a significant part of my technical SEO work. I use Lighthouse, Chrome DevTools, and real user data from Google Search Console to identify performance bottlenecks. Common fixes include: optimizing images (format, size, lazy loading), reducing JavaScript bundle size, improving server response time, fixing layout shift issues, and implementing proper font loading strategies.
For site migrations, I follow a structured process: crawl the old site to create a complete URL inventory, build a redirect map covering every URL, implement redirects on the new platform, crawl the new site to verify redirect coverage, monitor Google Search Console for indexation changes, and track organic traffic for 3 to 6 months after migration to catch any issues early.
Structured data is another area where I add value. I implement JSON-LD schema markup programmatically based on page content. For this site, every page includes WebPage schema, pages with FAQ blocks include FAQPage schema, and the site includes Organization and Person schema. This structured data helps search engines understand page content and can enable rich search result features.
Common Mistakes to Avoid
Common technical SEO mistakes that affect search performance.
Ignoring Core Web Vitals
Not monitoring or optimizing Core Web Vitals (LCP, CLS, INP). These metrics are a confirmed Google ranking factor and directly affect user experience. Sites with poor Core Web Vitals face a ranking disadvantage. Check Google Search Console Core Web Vitals report regularly and address issues proactively.
Misconfigured Canonical Tags
Setting canonical tags incorrectly, which can cause Google to ignore important pages or consolidate traffic to the wrong URL. Canonical tags should point to the preferred version of each page. Self referencing canonicals (each page canonicalizes to itself) are the safest default. Never canonicalize paginated pages to page 1.
Blocking Important Resources in Robots.txt
Using robots.txt to block CSS, JavaScript, or image files that search engines need to render pages properly. If Google cannot load your CSS and JS, it cannot render the page as users see it. Only block truly private areas (admin panels, staging environments) in robots.txt.
Not Monitoring After Changes
Making technical changes (URL structure updates, CMS migration, redesign) without monitoring the SEO impact for weeks afterward. Technical SEO issues often appear gradually as Google recrawls the site. Monitor Google Search Console indexation and organic traffic closely for 4 to 8 weeks after any significant change.
Redirect Chain Accumulation
Allowing redirect chains to build up over time (A redirects to B, B redirects to C, C redirects to D). Each redirect adds latency and dilutes link equity. Regularly audit redirects and update them to point directly to the final destination. Maximum one redirect hop is the target.
Frequently Asked Questions
Core Web Vitals are three metrics that measure user experience: Largest Contentful Paint (LCP) measures loading speed (how quickly the main content appears), Cumulative Layout Shift (CLS) measures visual stability (how much the page layout moves during loading), and Interaction to Next Paint (INP) measures responsiveness (how quickly the page responds to user interaction). Google uses these as ranking signals. Targets: LCP under 2.5 seconds, CLS under 0.1, INP under 200 milliseconds.
Use Google Search Console URL Inspection tool to see how Google views specific pages. Use the Coverage report to see which pages are indexed and which are excluded. Run a Screaming Frog crawl with JavaScript rendering to simulate how Google crawls your site. Check robots.txt to ensure important pages are not blocked. These tools together give a complete picture of crawl accessibility.
Run a comprehensive audit quarterly for most sites. After major changes (migration, redesign, CMS update), run an audit immediately and monitor weekly for 4 to 8 weeks. For large sites with frequent content changes, monthly audits are appropriate. Between audits, monitor Google Search Console for indexation changes and Core Web Vitals regressions.
They serve different functions. Technical SEO ensures search engines can access and understand your content. Content determines whether that content matches what users search for. You need both. The best content will not rank if the site has severe technical issues. The most technically perfect site will not rank without relevant content. For most sites, content quality has a larger impact on rankings, but technical issues can be absolute blockers.
Structured data is code (usually JSON-LD) added to pages that helps search engines understand the content type and attributes. For example, FAQ schema tells Google which questions and answers are on the page. Product schema provides price and availability information. Structured data can enable rich search results (FAQ dropdowns, product cards, breadcrumbs) which increase click through rates. It is not required for ranking but provides a competitive advantage.
Start with the biggest impact items: optimize images (use modern formats, correct sizes, lazy loading), reduce JavaScript (remove unused code, defer non critical scripts), improve server response time (caching, CDN, faster hosting), fix layout shift (set explicit dimensions for images and embeds), and optimize fonts (use font-display: swap, preload critical fonts). Use Lighthouse to identify specific issues and prioritize by impact.
Need Technical SEO Help?
I audit and optimize website infrastructure to ensure search engines can efficiently crawl, index, and rank your content.