Technical SEO Checklist: 15 Critical Checks for Your Website

What it is: SSL (Secure Sockets Layer) encrypts data transmitted between your server and a visitor's browser. HTTPS is the protocol that uses SSL/TLS certificates to serve pages securely.

Why it matters: Google has used HTTPS as a ranking signal since 2014. Beyond rankings, browsers display "Not Secure" warnings on HTTP pages, which destroys user trust and increases bounce rates. HTTPS also protects form submissions, login credentials, and payment data.

How to check: Visit your site and look for the padlock icon in the browser address bar. Use a tool like SSL Labs to check certificate validity, expiration date, and configuration. Crawl your site to find any mixed-content warnings where HTTP resources load on HTTPS pages.

What it is: Mobile-friendliness means your website displays and functions correctly on smartphones and tablets, with readable text, tappable buttons, and no horizontal scrolling required.

Why it matters: Google uses mobile-first indexing, meaning it primarily crawls and ranks the mobile version of your site. Over 60% of all search traffic comes from mobile devices. A poor mobile experience directly hurts both rankings and conversions.

How to check: Test your pages using Google's Lighthouse (built into Chrome DevTools) or the PageSpeed Insights tool. Check Google Search Console's Mobile Usability report for site-wide issues.

What it is: Page speed measures how quickly your web pages load. It encompasses server response time (TTFB), resource download time, and rendering performance.

Why it matters: Page speed is a confirmed Google ranking factor. Research shows that a 1-second delay in page load time can reduce conversions by 7%. Slow pages also consume more crawl budget, meaning fewer of your pages get crawled per session.

How to check: Use Google PageSpeed Insights to test individual pages. For site-wide performance analysis, use Rank Crown's Site Audit to test speed across all pages at once.

What it is: Core Web Vitals are three real-user metrics that measure loading performance (LCP), interactivity (INP), and visual stability (CLS). They are part of Google's Page Experience ranking signals.

Why it matters: Pages that pass all three Core Web Vitals thresholds receive a ranking boost. More importantly, these metrics directly reflect real user experience. Poor scores correlate with higher bounce rates and lower engagement.

How to check: Google Search Console has a dedicated Core Web Vitals report showing field data across your entire site. For lab testing, use web.dev's Core Web Vitals guide alongside Chrome DevTools Lighthouse.

What it is: An XML sitemap is a file that lists every important URL on your website, helping search engines discover and prioritize pages for crawling.

Why it matters: While Google can discover pages through links alone, an XML sitemap ensures that new, updated, or deeply nested pages are found quickly. It is especially critical for large sites, new sites with few external backlinks, and sites with orphan pages.

How to check: Visit yoursite.com/sitemap.xml. Verify it is referenced in your robots.txt. Submit it through Google Search Console and check for errors in the Sitemaps report.

What it is: The robots.txt file tells search engine crawlers which parts of your site they are allowed or not allowed to access. It lives at the root of your domain (e.g., yoursite.com/robots.txt).

Why it matters: A misconfigured robots.txt can accidentally block important pages or your entire site from being crawled. Conversely, a well-configured robots.txt preserves crawl budget by blocking low-value pages (admin panels, staging areas, search result pages).

How to check: Review your robots.txt file directly. Use Google Search Console's URL Inspection tool to test whether specific pages are blocked. Validate the syntax using Google's robots.txt documentation.

What it is: A canonical tag (rel="canonical") tells search engines which URL is the preferred version of a page when duplicate or near-duplicate versions exist.

Why it matters: Without canonical tags, search engines may index multiple versions of the same content (e.g., with and without trailing slashes, with URL parameters, HTTP vs HTTPS). This splits ranking signals and can cause the wrong version to appear in search results.

How to check: Crawl your site and verify that every page has a canonical tag. Check that canonical URLs are absolute (not relative), point to indexable pages, and are self-referencing on unique pages. Learn more about handling duplicate content in our complete site audit guide.

What it is: Structured data is code (typically JSON-LD) that you add to your pages to help search engines understand the content. It follows the Schema.org vocabulary and enables rich results (star ratings, FAQs, product prices, breadcrumbs) in search results.

Why it matters: Rich results significantly improve click-through rates. Pages with rich snippets stand out visually in the SERP and provide more information to users before they click. While structured data is not a direct ranking factor, the increased CTR and user engagement it drives can indirectly improve rankings.

How to check: Use Google's Rich Results Test or the Schema Markup Validator to check individual pages. For site-wide validation, review the Enhancements reports in Google Search Console. For deeper guidance on SERP features, see our SERP analysis guide.

What it is: Hreflang tags tell search engines which language and regional version of a page to serve to users in different countries. They use the format rel="alternate" hreflang="en".

Why it matters: Without hreflang, Google may show the wrong language version to users or flag your multilingual pages as duplicate content. Correct implementation ensures French users see the French version, Japanese users see the Japanese version, and so on.

How to check: Crawl your site to verify that hreflang tags are present on all multilingual pages. Check that every hreflang annotation is reciprocal (page A references page B, and page B references page A). Confirm the x-default tag is set for your fallback language.

What it is: A 404 error occurs when a page no longer exists at its URL. Broken links are hyperlinks that point to 404 pages, creating dead ends for users and crawlers.

Why it matters: Broken internal links waste crawl budget and prevent link equity from flowing to important pages. They also create a frustrating user experience. External links pointing to your 404 pages (from other sites) represent lost backlink value that could be recaptured. Our guide to finding and fixing broken links covers this topic in depth.

How to check: Use a site crawler (like Rank Crown's Site Audit) to scan every internal link for 404 responses. Check Google Search Console's Pages report for crawl errors. Review your backlink profile for external links pointing to non-existent pages.

What it is: A redirect chain occurs when URL A redirects to URL B, which redirects to URL C (or further). A redirect loop occurs when URL A redirects to B, and B redirects back to A, creating an infinite cycle.

Why it matters: Each redirect hop adds latency, degrades user experience, and can dilute PageRank. Google follows up to 10 redirect hops but may drop some link equity along the way. Redirect loops are worse because they make pages completely inaccessible to both users and crawlers.

How to check: Crawl your site and filter for redirect chains longer than one hop. Use the Network tab in Chrome DevTools to trace individual redirect paths. Check both internal redirects and incoming external links that hit redirects before reaching the final destination.

What it is: Duplicate content means substantially identical content accessible at multiple URLs on your site. Common sources include URL parameters, www vs non-www variants, HTTP vs HTTPS versions, trailing slash inconsistencies, and printer-friendly page versions.

Why it matters: When Google finds duplicate content, it must choose which version to index. This splits ranking signals (backlinks, engagement) across multiple URLs and can result in the wrong version ranking, or none of them ranking well.

How to check: Crawl your site and compare page titles, content hashes, and word counts to identify near-duplicates. Use the site:yoursite.com "exact phrase" operator in Google to find indexed duplicates. Check URL parameter handling in Google Search Console.

What it is: Crawl budget is the number of pages Googlebot will crawl on your site within a given timeframe. It is determined by crawl rate limit (how fast Google can crawl without overloading your server) and crawl demand (how much Google wants to crawl based on popularity and freshness).

Why it matters: For small sites (under 1,000 pages), crawl budget is rarely a concern. But for large sites with tens of thousands of pages, inefficient crawl budget usage means important pages may not be crawled frequently enough, delaying indexing of new content and updates.

How to check: Review the Crawl Stats report in Google Search Console to see how many pages Googlebot crawls daily, your average response time, and which pages are crawled most. For more advanced insight, analyze your server log files (see Check 15).

What it is: JavaScript rendering refers to how search engines process and index content that is generated by JavaScript on the client side. Modern frameworks (React, Vue, Angular) often render content dynamically, which requires Googlebot to execute JavaScript to see the full page.

Why it matters: While Googlebot can render JavaScript, the process is not instant. Google uses a two-pass indexing system: it first indexes the raw HTML, then queues the page for rendering. This delay can mean your JavaScript-rendered content takes days or weeks longer to appear in search results. Some content may never be indexed if JS execution fails.

How to check: Use Google Search Console's URL Inspection tool and compare the "tested URL" (rendered) view with the raw HTML. If content appears in the rendered view but not in the source HTML, it depends on JavaScript. Test with JavaScript disabled in your browser to see what Googlebot sees on the first pass.

What it is: Log file analysis involves examining your server's access logs to see exactly which pages Googlebot (and other crawlers) are requesting, how often, and what response codes they receive. It is the definitive source of truth for understanding how search engines interact with your site.

Why it matters: Unlike crawl tools that simulate bot behavior, log file analysis shows you real crawler activity. You can identify pages that Googlebot visits frequently (or never), discover crawl budget waste on irrelevant URLs, spot server errors that only affect bots, and verify that your robots.txt changes are working as intended.

How to check: Export your server access logs (Apache, Nginx, or CDN logs) and filter for Googlebot user-agent requests. Use a spreadsheet or a dedicated log analysis tool to aggregate the data. Look for patterns: which directories get crawled most, which return errors, and which important pages receive zero bot visits.