Say you run an auto repair shop in Winchester, Indiana. You have a website, a few good reviews, and a page that lists your services. Yet when someone searches for brake repair near them, your shop never shows up.
The words on your pages might be fine. The problem could be underneath, in the parts of the site nobody sees.
This technical SEO checklist walks you through those parts one at a time, in plain words, with a way to check each one yourself.
Why Technical SEO Matters More Than Ever in 2026
If you run a small business, you probably hear "SEO" tossed around a lot. Most of the time, people mean the words on your page. That matters, but it's only half the story.
The other half is technical SEO, the foundation of your whole online presence.
Think of technical SEO as the mechanics of your website. If your foundation is cracked, the beautiful content you build on top will not matter. Google's bots might get stuck, miss pages, or simply leave because your site is too slow or insecure.
An auto shop owner already understands this better than most. A car can have a fresh coat of paint and clean seats, but if the timing belt is shot, it is not going anywhere. Your content is the paint.
Technical SEO is the engine, the belts, and the wiring.
Google keeps its own list of the bare minimum a page needs before it can even be considered for search results. In its Search Essentials, Google says a page is eligible to be indexed when three things are true:
- Googlebot isn't blocked from the page.
- The page works, meaning Google gets an HTTP 200 (success) status code.
- The page has indexable content.
Google also says plainly that meeting these requirements "doesn't mean that a page will be indexed; indexing isn't guaranteed." So the basics will not earn you a top spot on their own.
They clear away the problems that would keep you out of the results entirely.
Why does this matter more in 2026? Because Google is no longer the only thing reading your site.
AI tools like ChatGPT send their own crawlers to read web pages, and they can only use what they can reach and read.
A site with blocked pages, broken links, or content that only shows up after a lot of JavaScript runs gives every one of these systems less to work with.
What this SEO checklist 2026 covers
This guide follows the same order as the fixes you should make:
- Security and the files that talk to search engines (HTTPS, robots.txt, and your XML sitemap).
- Site speed and Core Web Vitals.
- How your pages are organized and linked.
- Schema markup, so Google knows exactly what kind of business you are.
You do not need to be a programmer to check most of this. You need a phone, a free Google Search Console account, and about an afternoon.
Section 1: The Non-Negotiable Foundations
These are the technical SEO items that can quietly keep your site out of search results altogether. Fix them first, before you spend a dollar on new content or ads.
1.1 Security First: Universal HTTPS
In 2026, a secure website is a must. Google uses HTTPS as a baseline for trust. If you don't have a valid SSL certificate, users see a "Not Secure" warning. Most will leave right away.
This has been true for a long time. Google announced back in 2014 that it was starting to use HTTPS as a ranking signal.
At the time, Google called it "a very lightweight signal," so HTTPS alone will not push you to page one. The bigger effect is on people.
Starting with Chrome 68 in July 2018, Chrome began marking every HTTP site as "Not secure" right in the address bar.
Picture a customer about to type their name and phone number into your "Schedule Service" form and seeing that warning. Would you finish the form?
The good news is that the certificate itself does not have to cost anything. Let's Encrypt is a nonprofit that gives out free TLS certificates (the thing that makes HTTPS work), so ask your web host whether they can set it up for you.
Here is how to check your own site in two minutes:
- Open your homepage and look for the padlock icon in the address bar. No padlock, or a "Not secure" label, means you have a problem.
- Type your address with "http://" at the front instead of "https://". It should jump to the https version on its own. If it loads the http version, your site has two copies and needs a redirect.
- Click through your contact page and any form pages. A page can show a warning if it loads even one image or script over plain http (this is called "mixed content").
- If you use Google Search Console, open the HTTPS report. It shows which of your pages are served securely and what to fix if they are not.
One more thing to watch: certificates expire. If a renewal fails, your visitors see a warning before you do. Put a reminder on your calendar to check the padlock once a month. It takes ten seconds.
1.2 Communicating with Search Engines
You need a direct line to Google. This is done via your robots.txt file and a dynamically generated XML Sitemap. These tell bots which parts of your site to ignore and which represent your "VIP guest list" for indexing.
Your robots.txt file
A robots.txt file is a small text file that lives at the root of your site. For a shop at example.com, it would be at example.com/robots.txt. You can type that into your browser right now and see yours.
Google's own rules say the file must be named robots.txt, you can have only one, and it has to sit at the root of the site.
Here is the part most people get wrong.
Google says robots.txt "is used mainly to avoid overloading your site with requests; it is not a mechanism for keeping a web page out of Google." If you want a page kept out of search results (a thank-you page after a form, for example), Google says to use a noindex tag or password-protect the page.
And those two do not mix.
Google warns that for noindex to work, the page "must not be blocked by a robots.txt file." If robots.txt blocks the page, Google never sees the noindex tag, and the page can still show up in results if other pages link to it.
Common robots.txt mistakes to look for:
- A line that says "Disallow: /" under "User-agent: *". That blocks every crawler from your whole site. It sometimes gets left behind when a site is moved from a test version to the live one.
- Blocking your CSS or JavaScript folders, which can stop Google from seeing your pages the way a customer sees them.
- Trying to "hide" a page with robots.txt when you really want it out of search results.
- Blocking AI search crawlers by accident. OpenAI, for example, says sites that opt out of its OAI-SearchBot "will not be shown in ChatGPT search answers." If you want to show up there, do not block it.
If you use a site builder like Wix, Google notes you might not be able to edit robots.txt directly. That is fine. Your builder's settings for "hide from search engines" do the same job.
Your XML sitemap
An XML sitemap is a list of the pages you want search engines to find. For a Winchester auto shop, that might be the homepage, a page for each service (brakes, oil changes, alignments, check engine light diagnostics), an about page, and a contact page.
A few facts from Google's own sitemap documentation help keep this simple:
- One sitemap can hold up to 50,000 URLs or 50MB. A small business site will never come close.
- Google ignores the "priority" and "changefreq" values in a sitemap, so do not waste time tweaking them.
- Google does use the "lastmod" date, but only when it is "consistently and verifiably" accurate. If your sitemap says every page changed today when nothing did, Google learns to ignore it.
That is why the original advice says "dynamically generated." A sitemap that your website builds on its own stays correct when you add or remove a page.
A sitemap someone made by hand three years ago still lists the service you stopped offering and leaves out the new one.
What belongs in your sitemap: only the real, working pages you want people to find. Leave out redirected pages, error pages, thank-you pages, and anything marked noindex. When your sitemap is ready, submit it in Google Search Console under "Sitemaps."
Check that Google can actually index your pages
Once HTTPS, robots.txt, and your XML sitemap are in order, check what Google actually sees. Google Search Console is free, and two parts of it matter most here:
- The Page indexing report shows which of your pages are indexed and which are not, with a reason for each.
- The URL Inspection tool lets you check a single page. Google says it shows "information about Google's indexed version of a specific page," tests whether a live page can be indexed, and lets you request indexing after you fix something.
Start with your most important pages: the homepage, your top service page, and your contact page. If any of them is not indexed, read the reason Google gives. It is often something on this checklist.
You may read about "crawl budget" online. For most small businesses, you can skip it.
Google's own crawl budget guide says that if your site doesn't have a large number of pages that change rapidly, "you don't need to read this guide." Keeping your sitemap up to date and checking the Page indexing report is enough.
Duplicate pages and canonical tags
Your website can accidentally live at several addresses at once: with and without "www", with http and https, with and without a slash at the end. To you, it is one site. To Google, those can look like copies of the same page.
The fix has two parts:
- Pick one version of your address and redirect all the others to it with a permanent (301) redirect. Google says permanent redirects are a strong signal about which page should be the main one, and that "301 and other permanent redirects don't cause a loss in PageRank."
- Add a canonical tag to each page that points to its own preferred address. Google says this helps it consolidate signals, like links from other sites, into a single preferred URL.
The same goes for pages you rename. If your shop changes "/brakes" to "/brake-repair", set up a 301 redirect from the old address. Otherwise anyone who saved or shared the old link lands on an error page.
Section 2: Performance and Core Web Vitals
In 2026, Google has made it clear: User Experience (UX) is SEO. You need to meet the three Core Web Vitals benchmarks:
- LCP (Largest Contentful Paint): Main content must load under 2.5 seconds.
- INP (Interaction to Next Paint): Your site must feel responsive under 200ms.
- CLS (Cumulative Layout Shift): Visual stability score must be under 0.1.
In Google's own words, Core Web Vitals measure "real-world user experience for loading performance, interactivity, and visual stability of the page." Google recommends that site owners reach good scores and says this "aligns with what our core ranking systems seek to reward."
Speed is the part of technical SEO your customers feel first. If you read older guides, you may see a metric called First Input Delay (FID).
INP replaced it as a Core Web Vital in March 2024, so any checklist still talking about FID is out of date.
How the scores are measured
These numbers are based on real visits. Google's web.dev guide says a good threshold is the 75th percentile of page loads, measured on mobile and desktop separately.
In plain words, at least three out of four visits need to hit the target. A single fast load on your own office WiFi proves very little.
Think about a customer on their phone, parked outside a gas station, with two bars of signal. That is the visit Google is measuring.
Mobile matters twice over. Google says it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." If your site is slow or broken on a phone, that is the version Google judges.
Our guide on mobile-first web design explains what that means for how a site should be built.
How to check your site speed for free
- Go to Google's PageSpeed Insights and paste in your homepage address.
- Look at the mobile results first. If Google has enough real visitor data, it will show your Core Web Vitals at the top.
- Repeat for your main service page and your contact page.
- In Search Console, open the Core Web Vitals report. It groups your pages into good, needs improvement, and poor.
What usually hurts Core Web Vitals on a small business site
Each score has its own usual suspects:
- Slow LCP: a huge photo at the top of the page. A picture of your shop straight from a phone camera can be several megabytes when the page needs a small fraction of that. Resize and compress it, and make sure the main image is not set to load late.
- Poor INP: too much JavaScript. Chat widgets, pop-ups, tracking scripts, and page builder plugins all run code every time someone taps a button. Remove anything you do not really use.
- High CLS: images without a set width and height, ads, or banners that push the page down as they load. If a customer goes to tap "Call Now" and hits something else because the page jumped, that is layout shift.
Cheap, crowded hosting can slow everything down too, no matter how well the pages are built.
Our article on what makes a website fast goes deeper into each fix, and our page speed optimization service handles it for you if you would rather not do it yourself.
Section 3: Site Structure and Architecture
A strong hierarchy helps spread authority. Keep every page reachable within three clicks from the homepage. Use Breadcrumb Navigation to help users and bots understand your depth.
Site structure is the part of technical SEO that decides how easily people and search engines move around your site. For our Winchester auto shop, a clean structure could look like this:
- Home
- Services (a page that lists everything you do)
- One page for each service: Brake Repair, Oil Change, Wheel Alignment, Check Engine Light Diagnostics, Tire Service
- About (who you are, how long you have been in business, certifications your mechanics hold)
- Contact (address, phone, hours, a map, and a short form)
Every service page is two clicks from the homepage.
A customer who lands on the Brake Repair page from Google can see where they are, and a breadcrumb trail like "Home > Services > Brake Repair" lets them go back up one step at a time.
Google describes breadcrumbs the same way: a breadcrumb trail "indicates the page's position in the site hierarchy" and may help users understand and explore a site.
Links that Google can follow
Google finds most of your pages by following links from other pages. That only works if the links are real links.
Google says it can generally only crawl a link if it is an HTML "a" element with an "href" attribute.
A menu built so that pages open only through a script, with no real link underneath, can leave whole sections of your site invisible to Google.
Two simple checks:
- Look for orphan pages. These are pages that exist but that no other page links to. If your "Fleet Service" page is only in the sitemap and nowhere in your menu or text, add a link to it from the Services page and from a related service.
- Use clear link text. "Learn about our brake repair" tells Google and your visitor what is on the other side. "Click here" tells them nothing.
Our guide to internal linking covers how to link your pages together so the important ones get the most attention.
Clean, readable URLs
Google recommends simple, descriptive URLs that use "readable words rather than long ID numbers." Compare "yourshop.com/services/brake-repair/" with "yourshop.com/index.php?page=42". The first tells a customer and Google what the page is about before they ever click it.
If you change your URLs to fix this, remember the 301 redirects from Section 1.
Need a professional health check? Request a professional technical SEO audit from BuzFind so you can focus on running your business.
Schema markup: telling Google exactly who you are
Schema markup (also called structured data) is a small block of code that describes your business in a format search engines read easily. Your page might say "Open Monday to Friday, 8 to 5" in normal text.
Schema markup puts that same information in labeled fields, so Google does not have to guess.
Google's local business documentation says that with this markup, you can tell Google about business hours, departments, and more. Schema.org, the shared vocabulary that search engines use, even has a specific type for your trade: AutoRepair, described as a "car repair business."
For a small business site, the most useful schema markup usually includes:
- Your business type (like AutoRepair), name, address, and phone number.
- Your hours.
- Your website address and logo.
- Breadcrumbs on inner pages.
Google recommends the JSON-LD format for most sites because it is the easiest to set up and maintain.
It also sets a clear rule: don't add structured data about information that is not visible to the user, even if the information is accurate. If your markup says you are open Saturdays, your page should say so too.
And never mark up reviews or ratings you do not actually show on the page.
To check your work, paste a page address into Google's Rich Results Test. It shows what markup Google found and flags errors. Our schema markup optimization page explains how we set this up.
Common technical SEO mistakes to watch for
Beyond the robots.txt, redirect, and sitemap problems above, these are easy to miss:
- Service pages that only exist as tabs or pop-ups, with no page of their own for Google to index.
- Important text placed inside images, like hours or prices baked into a banner graphic. Google and screen readers read text much more reliably than pictures of text.
- Photos with no alt text. Google's image guidelines ask for descriptive filenames, titles, and alt text, and Google says it learns what an image shows from the page content around it, including captions and image titles.
- A contact page that is slow or broken on phones, which is exactly the page that brings in calls.
Your technical SEO checklist 2026, on one page
Print this out, or keep it open in a tab, and work through it in order:
- Your site loads on https, with a padlock, and the http version redirects to it.
- Only one version of your address works. The others redirect with a 301.
- Your robots.txt file exists at the root, does not block your whole site, and does not block CSS, JavaScript, or search crawlers you want.
- Pages you want out of search results use noindex, and those pages are not blocked in robots.txt.
- Your XML sitemap is built automatically, lists only real working pages, and is submitted in Search Console.
- Your homepage, top service pages, and contact page show as indexed in the URL Inspection tool.
- PageSpeed Insights shows good Core Web Vitals on mobile: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less.
- Every page is reachable within three clicks from the homepage, through real links.
- No orphan pages. Every page in your sitemap is linked from somewhere on the site.
- URLs are short and readable.
- Each page has a canonical tag pointing to its own preferred address.
- Schema markup for your business type, hours, and contact details passes the Rich Results Test and matches what the page shows.
- Every image has alt text, and important words are real text, not part of a picture.
Run through this technical SEO list once, fix what fails, then check it again every few months or any time you change your site.
What you can do yourself, and when to get help
Much of this list is free to check and often free to fix. HTTPS, a sitemap, and a Search Console account cost nothing but a little time. If your site runs on a common builder, many of these settings are a checkbox away.
Some items are harder. Poor INP scores often come from how the site was built, and fixing them can mean removing plugins or rewriting parts of the page.
Broken redirects after a redesign, or a site that relies heavily on JavaScript, usually need someone who can read the code. That is when a professional is worth the money.
A cheap fix that breaks your contact form, or a redesign that drops all your old addresses without redirects, can cost you far more than the fix itself.
Our article on the high cost of cheap SEO explains how that trap works.
When you talk to anyone about technical SEO, ask them these questions:
- What will you check, and will a real person test the site on a phone, or only run a tool?
- Will you show me the problems you find in plain words, with the pages they affect?
- Which fixes will you make, and which ones are up to me or my web host?
- How will we know the fixes worked? (Search Console and PageSpeed Insights are good, free answers.)
Be wary of anyone who promises a number one ranking, because nobody can honestly promise that. A good technical SEO job aims to make sure nothing on your site is holding you back, and the work should always be ethical and done right.
A technical fix only opens the door. After that, your pages still need to answer what customers are searching for.
Related reading on our blog: Mastering Keyword Research shows you how to find the words your customers actually type, and On-Page SEO Mistakes to Avoid covers the problems on the page itself.
Stop Fighting Against Your Own Website
If you have been posting, updating, and waiting for calls that never come, that is frustrating. You may have done everything you were told, while a problem in the foundation nobody mentioned kept holding you back.
The good part is that technical problems can be found and fixed, and many of them only need to be fixed once.
Is your technical foundation crumbling under the weight of AI search?
At BuzFind, we look at your site the way both a customer and a search engine see it: the code, the speed, the structure, and whether Google and AI search tools can read what you have built.
Get a free SEO audit today and find the issues that are holding back your rankings. For a deeper look, our technical SEO audit goes through every item on this checklist and more, with a real person reviewing the results.
