What Is Technical SEO? A Plain English Guide for Business Owners
Technical SEO explained without the jargon: what it covers, the mistakes that quietly delete sites from Google, and how much of it a 20 page Australian business site genuinely needs.
Technical SEO is the work that lets a search engine find, read, understand and trust your pages: crawling and indexing, robots.txt, redirects, sitemaps, canonicals, structured data, HTTPS, mobile and speed. On a 20 page Australian business site it is usually a day or two of work, done once. It removes obstacles. It does not create demand.
What does technical SEO actually cover?
It is everything that affects whether a search engine can reach your pages, read them properly, work out which version is the real one, and render them the way a visitor sees them. It is plumbing: nobody buys a house for it, but a blocked drain will stop the sale.
The list runs to about a dozen items: crawling and indexing, robots.txt, XML sitemaps, canonical tags, redirects, internal linking depth, structured data, HTTPS, mobile usability, Core Web Vitals, hreflang, and JavaScript rendering. Most Australian small business sites need roughly five of them handled properly.
How much of this matters for a 20 page site versus a 50,000 page store?
Wildly different amounts, and this is where a lot of money gets wasted. A 20 page site for a Sydney electrician or a family law firm has no crawl budget problem. Google will happily crawl 20 pages every few days, forever.
What does apply is the handful of things that can silently switch your site off. A stray noindex tag. A rebuild that dropped every old URL. A staging site left crawlable and competing with the real one. Any one of those costs more traffic than a year of content work would have gained.
A 50,000 page WooCommerce or Shopify catalogue is a different animal. There it is a permanent discipline: keeping crawlers out of infinite filter combinations, handling out of stock products, managing canonicals across variants. Budget for it as an ongoing line item.
What is the difference between blocking a crawl and blocking indexing?
This is the most expensive misunderstanding in technical SEO, and it costs Australian businesses real money every year.
robots.txt blocks crawling. It tells Google not to fetch a URL. It does not keep that URL out of search results. If other pages link to it, Google can still list it, usually with a grim No information is available for this page snippet.
A noindex meta tag blocks indexing. It tells Google to drop the page from results. But Google has to crawl the page to see that tag.
Combine them and you get the classic own goal: someone adds noindex, then blocks the same URL in robots.txt to be extra safe. Google can no longer crawl it, never sees the noindex, and the page drifts back in. The reverse is more common and far worse. A developer ticks the WordPress option that discourages search engines while building on staging, then pushes live with the box still ticked. The site quietly disappears over the following weeks and nobody links it to the launch.
Thirty second check after any launch or rebuild: open yourdomain.com.au/robots.txt in a browser and make sure it does not say Disallow: /, then view source on your homepage and search for the word noindex. In WordPress, confirm Settings then Reading has the search engine discouragement box unticked. We have been called in to fix the SEO on sites where that was the entire problem.
Do I need an XML sitemap and canonical tags?
A sitemap yes, but treat it as a courtesy to Google rather than a magic trick. It is a list of the URLs you want indexed, submitted through Search Console. Yoast, Rank Math and Shopify generate one for you. Its real value on a small site is diagnostic: Search Console tells you how many submitted URLs actually got indexed, and the gap is where your problems hide.
Canonical tags deal with duplicates. A canonical says this page and that page are the same thing, count that one. WordPress generates duplicates constantly: trailing slashes, http and https, URLs carrying tracking parameters from a Google Ads campaign, product variants. A self referencing canonical on every page sorts out most of it.
Duplicate content is not a penalty, whatever you have read. Google picks one version to rank and ignores the rest, and occasionally picks the wrong one. That is the actual cost, and it is smaller than the industry pretends.
Why do rebuilds lose rankings, and how do redirects stop that?
Because URLs change and nobody maps them. This is where most sites lose their rankings, and it is completely avoidable.
Say the old site had /services/bathroom-renovations-sydney and the new one has /bathroom-renovations. If nothing connects the two, every link pointing at the old address hits a 404 and the ranking history attached to it is gone. Do that across 40 pages and you can lose half your organic traffic inside a fortnight.
The process is boring and it works:
- Before launch, export every indexed URL: crawl the old site with Screaming Frog, then cross check the Pages report in Search Console.
- Map each old URL to its closest new equivalent, one to one wherever possible.
- Use 301 permanent redirects. Not 302s, not a meta refresh, not a JavaScript bounce.
- Never dump everything onto the homepage. Google treats a mass redirect to an irrelevant page as a soft 404, so you inherit nothing.
- Avoid chains. Old A to old B to new C should be rewritten as old A straight to new C.
- Check the 404 report weekly for a month afterwards and patch what you missed.
Expect a wobble of two to six weeks even when the redirects are perfect. A drop that never recovers usually means the mapping was skipped.
How much does site structure and internal linking depth matter?
More than most owners think, and it costs nothing but attention. Structure is how many clicks it takes to reach a page from the homepage. Our rule of thumb: any commercially important page should sit within three clicks, ideally two. Pages buried five or six levels down get crawled less often and inherit less authority.
Internal links are the underrated half. Link from an article to a service page with descriptive anchor text and you tell Google what that page is about while passing it authority. Our own SEO services for Australian businesses page is linked from a dozen articles here for exactly that reason. Pick the three or four pages that actually make you money and point every relevant article at them.
Does structured data matter more now that AI answers cite sources?
Yes, and this is the part that has genuinely shifted in the last couple of years. Structured data is code, usually JSON-LD, that labels what a page is: a LocalBusiness, a Product with a price, a set of FAQs, a review score. It does not lift your ranking directly and Google has been clear about that.
What it does is make your content machine readable, which matters far more now that AI Overviews, ChatGPT and Perplexity answer questions by summarising pages and citing the source. A page stating in structured form that a business is a plumber in Parramatta, open until 5pm, with a 4.8 average across 90 reviews, is much easier for a machine to lift and attribute than one where that sits inside a hero image.
The useful types are few: LocalBusiness or Organization, Service or Product, FAQPage, Article, BreadcrumbList. Rank Math and Yoast handle most of it. Do not mark up things that are not visible on the page; Google issues manual actions for that.
What about HTTPS, mobile usability and Core Web Vitals?
HTTPS is settled. It is a confirmed, if small, ranking signal, and browsers flag non-secure pages in a way that frightens people off your enquiry form. Certificates are free through Let’s Encrypt and included with any decent Australian host, so if you are still on http that is the first fix and it is an hour of work.
Mobile usability is not optional either, because Google indexes the mobile version of your site. If your mobile layout hides content the desktop version shows, the hidden version is what counts, or rather what does not. Test on a real phone.
Core Web Vitals attract the most attention and deserve the least. They measure loading (LCP), responsiveness (INP) and visual stability (CLS). Real ranking factor, genuinely minor one. Get largest contentful paint under roughly 2.5 seconds on mobile, then stop. Going from 2.4 seconds to 1.9 will not move you up the results, though it might lift conversions.
Most of the checks in the table below take under five minutes each and need nothing more than a browser and a free Google Search Console account. Work through them yourself before you pay anyone for an audit. For the non-technical half of the picture, keywords, content and links, there are more plain English guides in the SEO section of our Knowledge Centre.
Do I need hreflang if I sell overseas?
Almost certainly not. Hreflang tags tell Google which language and country version of a page to show. They only apply if you run separate versions of the same content per market, say a .com.au site and a .co.nz one with different pricing.
Selling to Australians from an Australian site? Skip it. Shipping to New Zealand from one set of pages? Still no. Hreflang is for duplicated pages per market, and it must be reciprocal: every version points at every other, including itself. Half implemented, it causes more trouble than none.
Can JavaScript stop Google seeing my content?
It can, and more often on modern builds than people expect. Google renders JavaScript, but in a second pass that lags behind the initial crawl, and anything that fails to execute does not exist as far as search is concerned.
The pattern that bites hardest is a React or Vue front end where product descriptions or the entire body copy load after the page is fetched. Same story with infinite scroll that has no crawlable link to page two.
The test takes a minute. Open URL Inspection in Search Console, run a live test, read the rendered HTML. If your headings and body text are not there, Google cannot see them. Standard WordPress with Elementor is fine, because the HTML is rendered on the server. Headless builds need checking before launch.
Which technical problems actually cost you, and how do you check them?
Ranked roughly by how much damage they do. The first four are what we find most often on sites that suddenly lost traffic.
| Technical issue | How it hurts you | How to check it |
|---|---|---|
| noindex tag left on after launch | Key pages or the whole site drop out of Google within weeks | View page source and search for “noindex”. In WordPress, check Settings then Reading |
| robots.txt disallowing the site | Google stops crawling, rankings decay, new pages never appear | Visit yourdomain.com.au/robots.txt and look for “Disallow: /” |
| Missing redirects after a rebuild | Old links hit 404s, ranking history is lost, traffic falls hard | Search Console Pages report, filter to Not found (404), plus a crawl of the old URL list |
| Staging site left public | A duplicate of your site competes with the real one | Google “site:staging.yourdomain.com.au” and see what comes up |
| Wrong or missing canonical tags | Google ranks the wrong version or splits signals across duplicates | View source and look for rel=”canonical”. Check parameter URLs resolve to one version |
| Site still on http | Browser warnings, abandoned forms, small ranking loss | Look for the padlock. Confirm http:// redirects to https:// |
| Mobile layout hiding content | The hidden version is what gets indexed | Test on a real phone, then compare with the rendered HTML in URL Inspection |
| Important pages four or more clicks deep | Crawled less often, inherit less authority, rank lower | Crawl the site with Screaming Frog and sort by crawl depth |
| Body content rendered by JavaScript | Content may never be indexed at all | URL Inspection live test, compare rendered HTML against view source |
| Slow LCP on mobile, over about four seconds | Lower conversions and a mild ranking drag | PageSpeed Insights and the Core Web Vitals report in Search Console |
| No sitemap, or a stale one full of dead URLs | Slower discovery of new pages, misleading index reports | Check /sitemap_index.xml and the Sitemaps section of Search Console |
| Thin or missing structured data | Fewer rich results, less likely to be quoted by AI answer engines | Google’s Rich Results Test and the Enhancements reports in Search Console |
Will fixing all of this make me rank?
No, and this is the part nobody selling technical audits says out loud. Technical SEO removes obstacles. It does not create demand. A technically flawless site with nothing worth ranking will rank for nothing, and we have audited plenty of those: perfect scores, immaculate markup, no content anyone was searching for.
Clearing the road is not the same as building the car. When a site is technically broken nothing else works, so fixing it has real value. Once it is not broken, further polish has sharply diminishing returns and your budget belongs in service pages, useful content and links.
For most Australian businesses that means a proper technical pass at build time or after a rebuild, a review once or twice a year, then leaving it alone. Monthly technical work suits large catalogues and publishers. On a 20 page site it is padding on an invoice. If you want a straight answer on whether your site has a real technical problem or an ordinary content problem, that is the first thing our search engine optimisation team looks at.
Common questions
How often should I run a technical SEO audit?
For a small business site, once a year is plenty, plus a full check immediately after any rebuild, migration, theme change or host move. Those four events cause almost every technical problem we are called in to fix. Large ecommerce catalogues are different and warrant a monthly look at index coverage. Between audits, having Search Console emails arrive in an inbox someone actually reads catches most issues early.
Is Yoast or Rank Math enough, or do I need a specialist?
For a 20 page WordPress site, a properly configured SEO plugin covers sitemaps, canonicals, meta robots and most structured data. That is the bulk of it. Where you need a person is redirect mapping during a rebuild, diagnosing why pages are not indexed, and anything involving JavaScript rendering. Plugins handle the routine work; they do not tell you when something is quietly broken.
What does a technical SEO audit cost in Australia?
For a small business site, expect roughly $500 to $1,500 excluding GST for a genuine audit with prioritised fixes, and a similar amount again to implement them. Anything advertised at $99 is an automated tool report with a logo on it. Be wary of anyone promising ranking improvements from a technical audit alone, since nobody can guarantee rankings and the ACCC takes a dim view of claims that cannot be backed up.
Will moving to a faster host improve my rankings?
Usually only if your current hosting is genuinely bad. Going from a slow, oversold shared server to decent Australian hosting can cut load times substantially and that is worth doing, mostly for the conversion gain. Going from good hosting to marginally better hosting will not change your position. Server response time matters most; a slow site is more often caused by bloated page builders, unoptimised images and too many plugins.
Should I worry about crawl budget?
Not unless you have tens of thousands of URLs. Google allocates crawl resources based on site size and demand, and a 20 or 200 page site never comes close to the limit. Crawl budget becomes a real constraint on large ecommerce sites where filter and sort parameters generate millions of near identical URLs. If someone is selling you crawl budget optimisation for a brochure site, they are selling you nothing.
My developer says the site scores 100 in PageSpeed Insights. Is that good?
It is nice, but it is a lab score on a simulated device, not what your customers experience. The number that counts is field data, the real user measurements Google shows underneath the score and reports in Search Console. Plenty of sites score in the nineties in the lab and fail on real mobile connections. And a perfect score on a page nobody searches for is worth exactly nothing.
Not sure whether your site has a technical problem?
We will crawl your site, look at your Search Console, and tell you straight whether something technical is holding you back or whether your budget is better spent elsewhere. Australian based team, no lock-in contracts, honest pricing.