Why technical SEO matters even if you never touch code
Technical SEO covers the stuff that isn't your words or your photos, it's the plumbing underneath the website that determines whether Google can find, load, and trust your site in the first place. You don't need to be a developer to understand it, and you definitely don't need to be one to spot-check whether your own site is in reasonable shape.
I bring this up because I see businesses spend real money on content and photography for a site that's quietly failing on the basics: slow to load, broken on mobile, or missing files Google expects to find. Good content on a technically broken site still underperforms. Here's what actually matters, without the jargon.
Page speed
Page speed is exactly what it sounds like: how quickly your pages load for a visitor. Google cares because slow pages frustrate people, and people who get frustrated leave before your site even finishes loading, which Google can measure and factor into rankings.
You don't need to guess at this. Run your homepage and a couple of key pages through Google's own PageSpeed Insights tool (search "PageSpeed Insights", paste in your URL). It'll give you a score and, more usefully, a list of specific things slowing the page down, oversized images being the most common culprit by a wide margin on small business sites. A photo straight off a phone camera can be 5-10MB, and a page with three or four of those loads painfully slowly, especially on mobile data. Compressing images before uploading them is one of the highest-impact, lowest-effort fixes available to a non-technical site owner.
Mobile-friendliness
More searches happen on phones than desktops for most small businesses now, and Google evaluates your site primarily on how it performs on mobile, not desktop. This is called mobile-first indexing, and it means the mobile version of your site is effectively the "real" version as far as Google's concerned.
To spot-check this yourself: open your own site on your phone and actually use it the way a customer would. Can you read the text without zooming? Are buttons big enough to tap without missing and hitting the wrong thing? Does the menu work properly? Does a contact form actually let you type into it comfortably? If anything feels fiddly on your own phone, it's costing you customers, and it's very likely affecting your rankings too.
XML sitemaps
An XML sitemap is a file, usually found at yoursite.co.nz/sitemap.xml, that lists every page on your site in a format Google can read. Think of it as a table of contents you hand directly to Google rather than hoping its crawler stumbles across every page on its own by following links.
It won't force pages into search results that Google doesn't want to index for other reasons, but it does make sure Google knows a page exists in the first place, which matters especially for larger sites or pages that aren't linked to from many other places. Most modern website platforms generate this automatically. It's worth checking yours exists by typing that URL directly into your browser, and if you've submitted it inside Google Search Console under the Sitemaps section, which helps Google find it faster.
Robots.txt
Robots.txt is a small text file, found at yoursite.co.nz/robots.txt, that gives instructions to search engine crawlers about which parts of your site they're allowed to look at. It's meant for things like admin login pages or internal search result pages, areas that genuinely shouldn't show up in Google.
The problem is when this file is misconfigured and accidentally blocks pages that should absolutely be visible, sometimes an entire site gets blocked by a leftover setting from when a site was in development and nobody remembered to remove it before launch. It's worth opening that URL directly in your browser occasionally and having a look. If you see a line that says "Disallow: /" with nothing else qualifying it, that's blocking your entire site from being crawled, which is a serious problem worth fixing immediately.
HTTPS and SSL
HTTPS is the secure version of a website connection, shown by the padlock icon in your browser's address bar, and it's powered by something called an SSL certificate. Beyond the obvious security benefit of encrypting data between your site and your visitor, Google has confirmed HTTPS is a ranking factor, and browsers actively warn visitors with a "not secure" message if a site doesn't have it. That warning alone is enough to make plenty of visitors leave immediately.
Checking this one is simple: look at your own site's address bar for the padlock icon. Almost every hosting provider issues SSL certificates for free and automatically these days, so if your site doesn't have one, it's usually a quick fix rather than a costly one, and it should be treated as a priority rather than something to get around to eventually.
Bringing it together
Technical SEO isn't about becoming a developer, it's about knowing enough to spot-check the basics: is the site fast, does it work properly on a phone, does Google have a sitemap to find your pages, is robots.txt accidentally blocking anything it shouldn't, and does the site have a valid SSL certificate. Most small business sites have at least one of these quietly working against them without the owner ever knowing.
If you want someone to run through these checks properly on your site and fix what's not working, this is core to the kind of hosting and maintenance work I do for clients on the Hibiscus Coast and beyond, so the technical side stays sound while you focus on running the business. Get in touch if you'd like a proper look under the bonnet.