Technical SEO Basics Small Business Owners Can Actually Understand
“Technical SEO” sounds like something that requires a computer science degree. It doesn’t. At its core, technical SEO basics come down to a simple idea: make sure Google can reach your website, understand it, and serve it to visitors without anything breaking. This guide explains every technical concept that actually matters for a small business — in plain English, with no code — plus how to check each one for free and what to fix first.
What Technical SEO Actually Is
Think of your website as a shop. On-page SEO is the signage, the product displays, the helpful staff — everything the customer sees. Technical SEO is the building itself: the foundations, the wiring, the plumbing, the locks on the doors. Customers rarely notice it when it’s right, but everything falls apart when it’s wrong.
More precisely, technical SEO covers three jobs: help Google find and crawl your pages, help Google understand and index them, and give visitors a fast, safe, stable experience. Google’s own documentation describes Search as a pipeline of crawling, indexing, and serving results — technical SEO is simply removing the blockages at each stage of that pipeline.
The good news: most small business sites fail on a handful of basic, cheap-to-fix issues. You don’t need to master everything below — you need to check everything below, then fix what’s actually broken.
1. Can Google Crawl Your Site?
Crawling is Google’s discovery process — its automated programs (Googlebot) following links to find your pages. If Googlebot can’t reach a page, that page doesn’t exist as far as search is concerned.
What can go wrong:
- Robots.txt blocks. This small text file tells crawlers which parts of your site to avoid. It’s meant for admin pages and staging sites — but we’ve seen live business sites accidentally blocking their entire website because a developer left a “disallow everything” rule from the build phase. Check yours at yourdomain.com/robots.txt.
- Broken links and server errors. Pages returning 404 (not found) or 500 (server error) codes waste Google’s crawl attention and frustrate visitors. A handful is normal; dozens signal neglect.
- Orphan pages. Pages with no internal links pointing to them. Google discovers pages by following links — a page nothing links to is nearly invisible.
- JavaScript-heavy sites. If your site’s content only appears after complex JavaScript runs, Google can usually still read it (it renders pages with a real browser), but it takes longer and sometimes fails. Content in plain HTML is always safer.
How to check (free): Google Search Console’s Pages report shows exactly which pages Google can and can’t crawl, and why. If you take one action from this guide, let it be setting up Search Console — it’s the single most useful free tool in SEO.
2. Can Google Index Your Pages?
Crawling finds pages; indexing stores them in Google’s database. Not every crawled page gets indexed — Google evaluates quality and usability first, and some pages are excluded deliberately.
What can go wrong:
- Accidental “noindex” tags. A noindex tag tells Google “don’t store this page.” Useful for thank-you pages and internal search results; catastrophic on your homepage. WordPress sites sometimes get this from a “discourage search engines” checkbox left ticked.
- Duplicate content. When multiple URLs show the same content (www vs non-www, HTTP vs HTTPS, trailing slashes, printer-friendly versions), Google picks one and ignores the rest — sometimes picking wrong. A canonical tag tells Google which version is the real one.
- Thin content. Pages with almost nothing on them — a contact page with just a form, service pages with two sentences — often don’t make Google’s quality bar for indexing.
- Brand-new pages. Indexing isn’t instant. New pages typically take days to weeks to appear; you can speed it up by requesting indexing in Search Console and linking to the page from already-indexed pages.
How to check: Search Google for site:yourdomain.com to see roughly what’s indexed. For precision, Search Console’s URL Inspection tool tells you the exact index status of any page and why.
3. Site Speed: The Technical Factor Visitors Feel
Speed is the technical issue with the most direct business impact. Slow pages lose visitors before Google even enters the picture — and Google measures speed as part of its page experience signals. Google’s three Core Web Vitals define “good” performance in concrete numbers:
- Largest Contentful Paint (LCP) — under 2.5 seconds. How quickly the main content appears. Usually held back by oversized hero images or slow hosting.
- Interaction to Next Paint (INP) — under 200 milliseconds. How fast the page responds when someone taps or clicks. Usually wrecked by heavy JavaScript — chat widgets, popups, and tracking scripts piling up.
- Cumulative Layout Shift (CLS) — under 0.1. How much the layout jumps around while loading. That infuriating moment when text shifts just as you’re about to tap a button.
Google measures these at the 75th percentile of real visitors — meaning three out of four of your actual visitors need a good experience, not just your office fibre connection. Check the Core Web Vitals report in Search Console for your real-world scores, and PageSpeed Insights for specific fixes per page.
The fixes that solve 80% of speed problems on small business sites:
- Compress all images (the number-one culprit — often the entire problem).
- Remove plugins, widgets, and tracking scripts you don’t actively use. Each one is a tax on every page load.
- Enable caching so returning visitors don’t re-download everything.
- Use decent hosting. The cheapest shared plan is often the bottleneck no plugin can fix.
4. Mobile-Friendliness: Non-Negotiable
Around 73% of local searches start on a mobile phone, and Google predominantly uses the mobile version of your site for indexing and ranking. “Mobile-friendly” in 2026 means:
- Text readable without zooming or horizontal scrolling.
- Buttons and links big enough to tap accurately (fingers, not mouse cursors).
- Phone numbers as tap-to-call links — a mobile visitor who has to memorise your number won’t call.
- Forms that work on small screens with appropriate keyboards (number pad for phone fields).
- No content that only works on desktop — if mobile visitors can’t see it, Google largely can’t either.
How to check: Open your site on your own phone and try to complete your main conversion — request a quote, book a call. Every point of friction you feel is costing you customers daily. Google’s mobile-friendly test gives you the technical verdict.
5. HTTPS: Your Site Must Be Secure
HTTPS (the padlock in the browser bar) encrypts data between your visitors and your site. In 2026 this is table stakes, not a bonus:
- Browsers explicitly warn visitors away from non-HTTPS sites.
- Google treats HTTPS as a ranking signal — minor, but free.
- Any form collecting personal details on HTTP is a trust and compliance disaster.
How to check: Visit your site and look for the padlock. Then check for mixed content — an HTTPS page loading images or scripts over HTTP, which browsers may block. Most hosts offer free SSL certificates (Let’s Encrypt); if yours charges extra for basic SSL in 2026, that’s a reason to switch hosts, not a reason to pay.
6. Site Structure: Make Your Site Easy to Navigate (for Humans and Bots)
A logical structure helps visitors find things and helps Google understand what matters most on your site:
- Keep important pages close to the homepage. Your key service pages should be one or two clicks from home — not buried four levels deep.
- Use clear, consistent navigation. If humans can’t find your services page, neither can Google’s crawlers.
- Submit an XML sitemap. It’s a machine-readable list of your pages that you hand to Google via Search Console. Most SEO plugins generate one automatically — you just need to submit it once.
- One page, one topic. Each page should have a clear subject (this is where keyword mapping meets technical SEO). A sprawling page about everything ranks for nothing.
7. Structured Data: Label Your Content for Google
Structured data (schema markup) is code that explicitly tells Google what your content means: “this is a local business”, “these are our opening hours”, “this is a frequently asked question”. It doesn’t directly boost rankings, but it makes your pages eligible for rich results — review stars, FAQ dropdowns, event details — which earn more clicks. It’s also increasingly how content gets selected for AI-generated answers.
For most small businesses, two schema types cover it: LocalBusiness (on your homepage/contact page) and FAQPage (on pages with FAQs). Most SEO plugins generate LocalBusiness schema automatically. Validate anything you add with Google’s Rich Results Test — broken schema is worse than none.
8. International and Multi-Location Basics
If you serve multiple areas, structure matters: one strong page per genuinely distinct service area beats fifty auto-generated suburb pages with swapped names (Google recognises template spam). Each location page needs real local content — the suburbs you actually serve, local landmarks or context, area-specific reviews or case studies, and a local phone number if you have one. Businesses with physical locations in multiple places should also maintain a separate Google Business Profile for each.
Your Technical SEO Action Plan
Don’t try to fix everything at once. Run these checks in order — each takes under an hour, and most small business sites fail at step one or two:
- Set up Google Search Console and check the Pages report. Fix crawl errors and check your robots.txt isn’t blocking anything important. (1 hour)
- Check indexation. site:yourdomain.com on Google, plus URL Inspection for key pages. Remove stray noindex tags. (30 minutes)
- Run PageSpeed Insights on your homepage and top service pages. Compress images and remove unused plugins first — that alone often fixes the scores. (2–3 hours)
- Test your site on your phone. Complete a quote request end to end. Fix whatever annoys you. (1 hour)
- Confirm HTTPS everywhere and submit your XML sitemap in Search Console. (30 minutes)
- Add LocalBusiness and FAQ schema via your SEO plugin, then validate. (1 hour)
That’s roughly a day’s work, and it puts your site’s technical health ahead of most small business websites — because most have never been checked at all. For the content side of the equation, our on-page SEO checklist picks up where this leaves off, and our start-here page puts it all in sequence.
Frequently Asked Questions
Do I need a developer for technical SEO?
For the basics in this guide, no — checking Search Console, compressing images, removing plugins, and testing on your phone are all owner-level tasks. You need a developer (or an agency) when the fixes involve server configuration, theme code changes, migrations, or diagnosing issues Search Console flags that you can’t interpret.
What is the difference between technical SEO and on-page SEO?
On-page SEO is about the content on your pages — words, titles, headings. Technical SEO is about the infrastructure — crawling, indexing, speed, security, structure. They overlap (a slow page is both a technical and a content problem), but the distinction helps you diagnose: if Google can’t reach the page, no amount of content optimisation matters.
How often should I check technical SEO?
Glance at Search Console monthly for new errors — it emails you about critical issues if you let it. Do a proper technical review quarterly, and always after any site change: redesigns, migrations, new plugins, and hosting moves are when technical SEO breaks.
Will fixing technical SEO alone improve my rankings?
Sometimes, dramatically — if the technical problem was the thing holding you back (a blocked page, a hacked site, a brutally slow mobile experience). But technical SEO is usually a foundation, not the whole building: it removes the penalties and barriers so your content and authority can do their work.
What are Core Web Vitals in simple terms?
Google’s three measurements of real-world page experience: how fast your main content loads (under 2.5 seconds), how quickly the page responds to taps (under 200 milliseconds), and how stable the layout is while loading (minimal jumping). Pass all three and you’re in good shape; they’re a tiebreaker between pages of similar quality.