Blog

Technical SEO Checklist for U.S. Business Websites

By Purav Mukhia11 min read
Technical SEO Checklist for U.S. Business Websites

Technical SEO is the set of site settings that let Google find, render, and index your pages, and that keep them fast and safe to use. For a U.S. business site, the essentials are: pages that are crawlable and indexable, one canonical URL per page, HTTPS, a mobile-friendly layout with the same content as desktop, passing Core Web Vitals, clean redirects, and accurate structured data.

AreaCheckTool
Crawlingrobots.txt does not block important pages or resourcesSearch Console, robots.txt
IndexingImportant pages are indexed; private pages use noindexURL Inspection
CanonicalsEach page has one preferred URLPage source, Search Console
SecurityHTTPS everywhere, no mixed contentBrowser, Search Console
MobileSame content, metadata, and structured data as desktopMobile test, URL Inspection
SpeedLCP within 2.5 s, INP 200 ms or less, CLS 0.1 or lessPageSpeed Insights, CrUX
Redirects301s for moved pages, no chainsCrawler such as Screaming Frog
Structured dataValid JSON-LD that matches visible contentRich Results Test

What does technical SEO cover, and why does it matter?

Technical SEO covers everything that determines whether search engines can reach your content and understand it, apart from the words on the page. If Google cannot crawl a page, it cannot index it, and a page that is not indexed cannot rank for anything.

Google's SEO Starter Guide says that most sites in its results are found and added automatically as Google crawls the web, and that publishing a site is often enough to get started. The problem for business owners is that things go wrong quietly: a developer leaves a "noindex" tag on after launch, a plugin blocks CSS, a redesign breaks old URLs. Traffic drops and nobody knows why.

A checklist gives you a repeatable way to catch those problems. Run it after any redesign or migration, and once a quarter otherwise. Our full 2026 SEO checklist for American small businesses covers the content and local pieces that sit on top of this technical base.

How do you set up Google Search Console first?

Add your site as a property in Google Search Console and verify ownership. Use a Domain property if you can, since it covers all subdomains and both HTTP and HTTPS versions. Then open the Pages report (indexing), the Performance report, and the Core Web Vitals report.

Search Console is where Google tells you what it sees. The URL Inspection tool shows whether a specific page is indexed and lets you request a recrawl after a fix. Google's documentation on noindex recommends URL Inspection to confirm Googlebot can see a tag and to request recrawling.

Also connect Google Analytics 4 if you do not already have it. It is not a Google Search Console requirement, but it lets you connect organic visits to leads.

People planning together at a whiteboard in a bright office

Is your site crawlable? Checking robots.txt

Open yourdomain.com/robots.txt in a browser and read it. It should not contain a line like "Disallow: /" unless you truly want the whole site blocked, which sometimes happens when a staging site setting is copied to production.

Google's documentation states that a robots.txt file tells crawlers which URLs they can access, and it is mainly for managing crawler traffic. It also says that robots.txt is not a mechanism for keeping a page out of Google, because a blocked URL can still be indexed if other sites link to it.

To keep a page out of search results, use a noindex meta tag or an X-Robots-Tag HTTP header. There is a trap here: Google's documentation notes that if a page is blocked by robots.txt, the crawler never sees the noindex rule, and the page can still appear in results. Do not do both. Also confirm you are not blocking the CSS and JavaScript files Google needs to render your pages.

Are the right pages indexed?

Use the Pages report in Search Console to see which URLs are indexed and which are excluded, with reasons. Compare it to the pages you actually want to rank: your home page, service pages, location pages, and blog posts.

Common reasons a page is excluded and what to do:

Crawled, currently not indexed: the page may be thin or duplicate; improve the content or consolidate it.

Discovered, currently not indexed: Google knows the URL but has not crawled it; add internal links from strong pages.

Blocked by robots.txt or marked noindex: confirm this is intentional.

Duplicate without user-selected canonical: set a canonical tag.

Page with redirect: fine if intentional; list only final URLs in your sitemap.

Soft 404: the page returns a 200 code but looks empty or like an error; return a real 404 or improve the page.

Use the site: search operator for a quick check. Google's starter guide recommends it to see if your content is indexed. A search for site:yourdomain.com that returns very few pages when you have dozens signals a problem worth investigating.

Do you need an XML sitemap?

A sitemap helps but is optional for small sites. Google's sitemap documentation says sites of about 500 pages or fewer with good internal linking may not need one, while large sites, new sites with few external links, and sites with rich media are more likely to benefit. It also notes that a sitemap helps discovery but does not guarantee that URLs are crawled or indexed.

Most business sites should still have one, because it costs almost nothing. Most CMS platforms such as WordPress, Shopify, and Wix generate one automatically, often through an SEO plugin. Submit it in the Sitemaps report in Search Console.

Keep the sitemap clean. List only canonical, indexable, 200-status URLs. Do not include noindex pages, redirected URLs, or pages blocked by robots.txt. A sitemap full of junk trains you to ignore its errors.

How should you handle duplicate URLs and canonical tags?

Pick one preferred URL for each page and tell Google. The same page often exists at several addresses: with and without "www," with HTTP and HTTPS, with a trailing slash or without, and with tracking parameters. Google uses a canonical URL to identify the preferred version, consolidate signals such as links, and spend crawl effort on new content.

Google's documentation ranks the methods. A permanent redirect is a strong signal, a rel="canonical" link element in the page head is next, and a sitemap entry is the weakest. Recommendations from the same page include using absolute URLs, adding self-referencing canonicals, preferring HTTPS, and avoiding conflicting signals from different methods.

For a typical business site the practical steps are:

Choose one version of your domain (for example https://www.example.com) and 301-redirect all others to it.

Add a self-referencing canonical tag on every page.

Make sure filter, sort, and tracking-parameter URLs point their canonical at the clean page.

Confirm the URL Google picked matches yours, using URL Inspection.

Is HTTPS set up correctly?

Every page should load over HTTPS, and HTTP addresses should redirect to HTTPS with a permanent redirect. Google's page experience documentation lists security through HTTPS as one of the elements it considers part of a good experience.

Check for mixed content, where an HTTPS page loads images, scripts, or fonts over HTTP. Browsers may block or warn on those resources. Also confirm the certificate is valid and renews automatically, since an expired certificate shows visitors a full-page warning.

Is your site mobile-ready under mobile-first indexing?

Google uses the mobile version of your site for indexing and ranking, and it announced in October 2023 that its move to mobile-first indexing was complete. That makes your mobile site your site, as far as Google's index is concerned.

Google's best practices for mobile-first indexing say to make sure the mobile site contains the same content as desktop, uses equivalent titles and meta descriptions, has the same structured data, does not block resources with robots.txt or noindex, and does not lazy-load primary content that requires user interaction. Google recommends responsive web design as the easiest pattern to implement and maintain. See our guide to mobile optimization for U.S. businesses for the customer-experience side.

A common mistake is hiding content on mobile behind tabs or removing sections to "simplify." Content that exists on desktop but not on mobile may not be indexed at all.

What are the Core Web Vitals targets, and how does a typical site perform?

The Core Web Vitals targets, per web.dev, are: Largest Contentful Paint (LCP) within 2.5 seconds, Interaction to Next Paint (INP) of 200 milliseconds or less, and Cumulative Layout Shift (CLS) of 0.1 or less, measured at the 75th percentile of page loads. A page needs to meet all three to be considered good.

Most websites still miss at least one. The HTTP Archive's 2025 Web Almanac reports that 48% of mobile sites had good Core Web Vitals, up from 44% in 2024, and 56% of desktop sites, up from 55%. On mobile, 62% of pages had a good LCP, 77% had a good INP, and 81% had a good CLS. The Almanac also found unsized images on 62% of mobile pages, which is a direct cause of layout shift.

Google says Core Web Vitals are used by its ranking systems, but good scores do not guarantee top rankings, and relevant content can outrank a page with a better experience. So do not sacrifice content for a perfect score. Fix real problems first:

Slow LCP: compress images, use modern formats, serve them at the right size, and consider a content delivery network.

Slow INP: remove or delay heavy JavaScript, chat widgets, and tag manager bloat.

High CLS: set width and height on images and embeds, reserve space for ads and banners, and avoid inserting content above what is already visible.

Check field data in the Core Web Vitals report in Search Console and in PageSpeed Insights. Lab scores are a guide, but field data from real users is what counts.

How do you handle redirects, broken links, and 404 errors?

Use a 301 redirect when a page has moved permanently. Google's redirect documentation says the indexing pipeline treats a 301 as a signal that the target should be canonical, while a 302 does not carry that signal. For site moves, it recommends permanent server-side redirects.

Steps to follow when you change URLs:

Make a list of every old URL and the closest new equivalent.

Redirect each old URL directly to the final destination, avoiding chains of redirects.

Update internal links so they point to the new URLs and not through the redirect.

Update the sitemap and canonical tags.

Watch the Pages report for new errors for a few weeks.

Do not redirect every old URL to the home page. That confuses users and Google treats it as a soft 404 in many cases. Return a real 404 (or 410) for pages that are gone with no replacement, and create a helpful 404 page with search and links to main services.

Run a crawler such as Screaming Frog or the site audit tools in Ahrefs or Semrush to find broken internal links, redirect chains, and missing titles. Fix internal links first because you control them.

Does JavaScript get in the way of indexing?

It can. Google processes JavaScript sites in three phases: crawling, rendering, and indexing. Its JavaScript SEO basics page says Google can only discover links that are <a> elements with an href attribute, that you should avoid URL fragments for navigation, that you should return correct HTTP status codes, and that server-side rendering remains a sound choice since not all bots can run JavaScript.

If your site is built on a framework like React or on a page builder that loads content after the page opens, test with the URL Inspection tool and look at the rendered HTML. Confirm your main text, headings, and links appear. Also make sure your title, meta description, and canonical tag are present in the HTML, ideally not set only by scripts.

For most small business sites built on WordPress, Shopify, Squarespace, or Wix, this is rarely an issue. It becomes one with custom builds or heavy use of client-side rendering.

Is your structured data valid and honest?

Add structured data where it matches visible content, and validate it. Google recommends JSON-LD in most cases and says structured data should describe content users can see. It also warns that markup does not guarantee rich results, and that it is better to give fewer but complete and accurate properties than many poorly formed ones.

For a local business, LocalBusiness markup (with a more specific subtype where one exists) requires name and address per Google's documentation. Recommended properties include telephone, url, opening hours, geo coordinates, and price range. Make sure the data matches your Google Business Profile exactly, including name, address, and phone number.

Test pages with the Rich Results Test and watch the structured data reports in Search Console. Do not mark up reviews you wrote yourself as if they were independent customer reviews, and do not add markup for content that is not on the page.

What else belongs on a technical SEO checklist?

A few items are easy to miss:

Unique title tags and meta descriptions. Google's documentation says every page should have a title, that titles should be concise and descriptive, and that Google may rewrite them.

Descriptive URLs with real words, not random IDs.

A logical internal link structure so important pages are within a few clicks of the home page, with descriptive anchor text.

Image alt text on meaningful images.

Consistent name, address, and phone across the site, footer, contact page, and schema.

A custom 404 page, and no soft 404s.

Log or server access so you can see crawl errors and slow responses.

A staging environment that is blocked from crawling and never shipped with those blocks to production.

Set a calendar reminder to rerun the checklist every quarter, and after any migration, redesign, or plugin change. Technical fixes usually take effect once Google recrawls, but rankings respond over weeks or months, and results depend on competition. See how long SEO takes for realistic timelines.

The bottom line

Technical SEO is mostly maintenance. Make sure Google can crawl and index the right pages, pick one URL for each, serve everything over HTTPS, keep mobile and desktop content the same, and fix the speed problems that real users hit. Then recheck on a schedule. None of it guarantees rankings, but a site with technical problems gives every other effort a lower ceiling.

Keep reading

Sources

Frequently asked questions

How often should I run a technical SEO audit?

Once per quarter is a reasonable rhythm for a small business site, plus after any redesign, migration, or major plugin update. Between audits, watch the Search Console Pages and Core Web Vitals reports for new errors, since Google will show issues there as it finds them.

Can I do technical SEO myself without a developer?

Many checks can be done yourself with Search Console, PageSpeed Insights, and a crawler. Fixes such as image compression, redirects, and canonical settings are often available through your CMS or a plugin. Server-level changes and JavaScript rendering problems usually need a developer.

Does page speed directly affect rankings?

Google says Core Web Vitals are used by its ranking systems, but that good scores do not guarantee top rankings and that relevance can outweigh page experience. Speed also affects whether visitors stay and act, so it is worth fixing on those grounds alone.

Do I need schema markup to rank?

No. Structured data can make pages eligible for rich results and helps machines interpret your content, but Google does not promise that any markup will change your rankings or display. Add it where it is accurate and useful, and validate it.

← All posts

See what AI says about your business.

Start with a free audit. We'll show you where you stand today, and exactly how to fix it.

More from the blog