Technical SEO Checklist: What Your Website Needs to Rank

Technical SEO is the foundation that determines whether Google can find, crawl, and properly evaluate your website's content. Without it, even strong content and external links will underperform. This checklist covers the six categories that matter most for small business websites: crawlability, indexation, page speed, mobile optimization, structured data, and Core Web Vitals. Each item includes context explaining why it matters, not just what to check. Work through it by category, not all at once.

Why Does Technical SEO Matter?

Technical SEO encompasses the site-level factors that allow search engines to discover, crawl, interpret, and index your content. It is the prerequisite layer beneath everything else in your SEO program.

A site with an excellent blog post and a strong backlink pointing to it will still underperform if that page is accidentally blocked from crawling, loads in 9 seconds on mobile, or lacks basic schema markup. The content quality and external authority signals are present, but the technical layer prevents Google from efficiently processing them.

For small business websites, the most common high-impact technical issues are: pages blocked from crawling by misconfigured robots.txt, pages not being indexed due to noindex tags, slow page load speeds on mobile, missing or broken canonical tags, and an absence of structured data markup. All of these are fixable, and most are auditable without enterprise tools.

For a full audit of your site's technical SEO health, see our Technical SEO services page.

How Do You Check Your Site's Crawlability?

Crawlability covers whether Google's bots can access and navigate your site's pages. Issues here prevent ranking because Google cannot evaluate content it cannot read.

robots.txt is correctly configured. Your robots.txt file tells search engine crawlers which pages they can and cannot access. A misconfigured robots.txt that blocks Googlebot from crawling your site's key pages is one of the most severe technical SEO issues a site can have. Check yours by appending /robots.txt to your root domain and verify that your key service and content pages are not listed in Disallow directives.

XML sitemap is present, current, and submitted to Google Search Console. Your sitemap tells Google which pages you want indexed and when they were last updated. An outdated sitemap that includes deleted pages or excludes new content slows Google's discovery of your site's current state. Sitemaps should be submitted in Google Search Console under the Sitemaps section and updated automatically by your CMS whenever new content publishes.

Internal linking allows Google to reach all important pages within 3 clicks from the homepage. Pages that are deeply buried in your site architecture or that have no internal links pointing to them receive fewer crawl budget allocations. Every important page on your site should be reachable from the homepage in three clicks or fewer, and should have at least one contextual internal link from a related page.

Crawl errors are resolved or accounted for. In Google Search Console, the Pages report shows which pages could not be crawled and why. Crawl errors on pages you care about (404s, server errors, redirect chains longer than 3 hops) should be resolved. Crawl errors on pages you intentionally removed are expected and do not require action if the original pages are properly redirected.

No redirect chains longer than 3 hops. Each redirect in a chain reduces the amount of link equity passed from the referring page and adds load time. Any URL that redirects more than three times before reaching the final destination should be updated to point directly to the final URL.

How Do You Verify Your Pages Are Properly Indexed?

Indexation covers whether the pages Google can crawl are actually being added to its index. A page that is crawlable but not indexed will not appear in search results.

Key pages are not set to noindex. A noindex tag or header tells Google not to add a page to its index. This directive is appropriate for internal search results pages, thank-you pages, and other utility pages. It is not appropriate for service pages, blog posts, or any page you want to rank. Check your key pages using a browser extension like SEO Meta in 1 Click or the URL Inspection tool in Google Search Console.

Canonical tags are set correctly on all pages. Canonical tags tell Google which version of a page is the authoritative one. Without correct canonicals, Google may split ranking signals between duplicate or near-duplicate URLs (www vs. non-www, HTTP vs. HTTPS, trailing slash vs. no trailing slash). Your canonical should always point to the preferred, canonical version of each URL.

Duplicate content is addressed. Identical or substantially similar content appearing on multiple URLs within the same site confuses Google's ranking algorithm and dilutes the authority of both pages. Common causes: printer-friendly pages, pagination, URL parameters, and session IDs. Address duplicates through canonical tags, 301 redirects, or by consolidating the content onto a single URL.

Google Search Console confirms your key pages are indexed. Use the URL Inspection tool in Google Search Console to verify that your homepage, key service pages, and recent blog content are confirmed as indexed. If a page you care about shows "URL is not on Google," the inspection report will tell you why and what to fix.

The site is not blocking CSS or JavaScript from Googlebot. Modern websites often render content through JavaScript. If Googlebot is blocked from loading your CSS or JavaScript (for example, through robots.txt), it may see a stripped-down version of your pages and miss content or structured data. Test your key pages with Google's Rich Results Test and the URL Inspection tool's "View Tested Page" feature to confirm Google sees the full rendered content.

How Do You Test and Improve Page Speed?

Page speed is a confirmed Google ranking factor and has direct effects on both bounce rate and conversion rate. Google's research has documented that the probability of a user bouncing increases 32% when page load time goes from 1 second to 3 seconds, and 90% when it goes from 1 to 5 seconds.

Test page speed using Google PageSpeed Insights. Run your homepage and 2 to 3 key service pages through PageSpeed Insights (pagespeed.web.dev) and record your mobile and desktop scores. Mobile scores are more important because Google uses mobile-first indexing. A mobile score below 50 indicates significant performance issues worth prioritizing.

Images are properly compressed and in modern formats. Oversized images are the most common page speed issue on small business websites. All images should be compressed to the smallest file size that maintains visual quality, and converted to modern formats (WebP or AVIF) rather than PNG or JPEG where the CMS supports it. A single uncompressed hero image can add 2 to 4 seconds of load time on mobile.

A content delivery network (CDN) is in place. A CDN stores copies of your site's static assets on servers distributed geographically, reducing load times for visitors who are not near your primary server location. Most quality web hosting providers include CDN functionality. If your site does not have one, your hosting provider can advise on the most straightforward option for your CMS.

Render-blocking resources are minimized. JavaScript and CSS files that load before the page content renders delay how quickly users see anything on the screen. Google's PageSpeed Insights report identifies render-blocking resources. Common fixes include loading non-critical JavaScript asynchronously (async or defer attributes) and moving inline CSS to external files.

Server response time is under 200ms. Time to First Byte (TTFB) measures how quickly your server responds to a page request. A TTFB above 500ms indicates a server or hosting issue that degrades performance before the browser has started rendering anything. If your TTFB is high, the first step is evaluating your hosting tier. Shared hosting frequently produces poor TTFB at scale.

How Do You Audit Mobile Optimization?

Google uses mobile-first indexing, which means it primarily uses the mobile version of your site for crawling, indexing, and ranking. A site that performs well on desktop but poorly on mobile will rank based on the mobile experience.

The site passes Google's Mobile-Friendly Test. Run your site through the Mobile-Friendly Test (search.google.com/test/mobile-friendly) to confirm it is identified as mobile-friendly. This test checks for text that is too small to read, interactive elements too close together, and content wider than the screen.

Tap targets are appropriately sized. Buttons, links, and navigation elements need to be large enough and spaced far enough apart for a user to tap accurately on a touchscreen. Google recommends tap targets of at least 48x48 pixels, with at least 8 pixels of spacing between adjacent elements.

Content does not require horizontal scrolling. Pages that require horizontal scrolling on mobile indicate content or elements that are wider than the viewport. This is a negative mobile usability signal and creates a poor user experience that increases bounce rates.

Font sizes are readable without zooming. Body text should be at least 16px on mobile. Text smaller than this requires users to pinch-to-zoom to read comfortably, which is a usability failure that Google's mobile evaluation penalizes.

How Do You Validate Your Structured Data?

Structured data (schema markup) helps Google understand the content, context, and relationships on your pages. It is also a prerequisite for rich results in search (star ratings, event listings, and similar features) and an increasingly important signal for AI search citation. Note that Google retired the FAQ rich result in May 2026, so FAQPage markup is now an AI-extraction signal rather than a Google search feature.

Organization schema is implemented on the homepage. Your Organization schema establishes your business's core identity for Google: name, URL, logo, contact information, and social profiles. This is the entity foundation that makes it possible for Google to accurately attribute your content and your brand across the web.

Article schema with author markup is on all blog posts. Article schema identifies your blog content as journalism or editorial content rather than a product page or service page. The author markup links to your Person schema, which builds E-E-A-T signals for Jaron Mossman as the named author across all 360ROI content.

FAQPage schema is on all pages with FAQ sections. FAQPage schema provides explicit question-and-answer structure that AI search systems use for extraction and citation. Google retired the FAQ rich result on May 7, 2026, so this markup no longer surfaces a Google search feature, but it stays valuable as an AI-extraction signal and is worth keeping. We explain the full call in Google killed FAQ rich results, keep the schema anyway. Every page with a FAQ section should have corresponding FAQPage schema.

LocalBusiness schema is implemented for local businesses. LocalBusiness (or its specific subtypes like MedicalBusiness, Restaurant, ProfessionalService) establishes your location, hours, service area, and contact information in a machine-readable format. This is particularly important for local search visibility and Map Pack ranking.

Schema is validated with the Rich Results Test. After implementing any schema, run the page through Google's Rich Results Test (search.google.com/test/rich-results) to confirm the markup is valid and eligible for rich result display. Schema with errors will not qualify for rich results regardless of how accurately the information is entered.

How Do You Diagnose Core Web Vitals Issues?

Core Web Vitals are a specific set of user experience metrics that Google uses as ranking signals. They measure three dimensions: loading performance, visual stability, and interactivity.

Largest Contentful Paint (LCP) is under 2.5 seconds. LCP measures how long it takes for the largest visible content element (usually a hero image or headline) to load. An LCP above 4 seconds is rated "Poor" by Google. The most common fixes are image compression, CDN implementation, and removing render-blocking resources above the fold.

Cumulative Layout Shift (CLS) is under 0.1. CLS measures how much the page layout shifts unexpectedly during loading (for example, when an image loads and pushes text down). A CLS score above 0.25 is "Poor." The most common causes are images without defined dimensions, ads that load late, and embedded iframes without reserved space.

Interaction to Next Paint (INP) is under 200 milliseconds. INP replaced First Input Delay as a Core Web Vital in March 2024. It measures the time from a user interaction (click, tap, keyboard press) to the next visual response. INP above 500ms is "Poor." JavaScript optimization and reducing long tasks on the main thread are the primary levers.

Core Web Vitals are assessed using field data, not lab data. Google Search Console provides field data for Core Web Vitals based on real user measurements collected over the previous 28 days. This is more representative of actual user experience than lab data from PageSpeed Insights, which simulates a single device and connection speed. Use the Core Web Vitals report in Google Search Console as the authoritative source for whether your pages are passing or failing.