Technical SEO audit: a one-off check of what holds a website back in search
A written report with proof for each finding and a list put in order.
Your website may look fine and still be hard for Google to read. A technical SEO audit is a one-off check of the site itself: what Google can reach, what it keeps, and what it struggles with. True North Innovations is a Melbourne-based team that works with businesses across Australia. You get a written report, not a tool printout. If you want the work done each month after the audit, see our SEO service. If your question is why visitors do not enquire, see conversion rate audit.
Six areas checked · Proof for each finding · Put in order · One report
Melbourne based.
Australia-wide delivery.
Melbourne · Sydney · Brisbane · Perth · Adelaide · Canberra
The six areas Google checks first
These are the first things Google runs into when it visits a website. Each one gets its own part of the report.
Site speed
How long pages take to appear and become usable, on a phone and on a desktop.
Mobile experience
Whether the pages work on a small screen: text size, buttons, menus and forms.
Crawling
Whether Google's visiting program can reach your pages, and whether it wastes time on pages that do not matter.
Indexing
Which pages Google keeps in its list, which it leaves out, and the reason it gives for each group.
Structured data
The code that tells Google what a page is, such as a business, a service or a list of questions, checked for errors.
Core Web Vitals
Google's three measures of how a page feels to a real visitor: how fast it loads, how fast it reacts, and how much it moves.
Where the proof comes from
Every finding in the report names the place it came from, so you or your developer can check it.
Google Search Console
Google's own report on your site: pages it knows, pages it left out and errors it found.
A crawl of the whole site
Our program visits every page the way a search engine does and records addresses, answers, titles and links.
The page code
We read the code of key pages to see what a search engine receives, which is not always what a visitor sees.
Speed data from real visits
Where Google has it, the measures from real visitors, next to tests we run ourselves.
How findings are put in order
A long list of faults is not useful if every item looks equal. We sort each finding by two counts: how many pages it touches, and how much of your search traffic those pages bring. A fault on one old page comes after a fault that touches every product page.
Next to each finding the report says how sure we are. Where Google gives a reason, we repeat it. Where we are guessing from the evidence, we say that too.
One table from a report
A made-up table with the figures left out, to show the shape. A real report shows your own figures and the date they were read.
The figures are left out on purpose. A made-up table is not a result of ours.
From the report to the fixes
- 01
We go through the report with you
We explain each finding in plain words and answer what is unclear.
Output: A report you understand
- 02
Your developer makes the fixes
If you have a developer, they get the findings with the evidence, so they can work without guessing.
Output: A list for your developer
- 03
Or we make the fixes, as a separate job
If you want us to do them, we scope that job separately and agree it in writing first.
Output: A separate agreed job
What you give us to start
- The address of your website and a list of any other domains or sub-sites it uses.
- Access to Google Search Console, or help to add us as a user.
- Read access to the website code or admin, if the site is large or custom-built.
- A note of recent changes such as a redesign, a move or a change of hosting.
- The pages and searches that matter most to the business.
What is not included
A website move
Moving a site without losing search visits is its own job. See SEO for a website move.
What affects the scope
An audit is scoped after a first look at the site. What changes the scope: the number of pages, whether the site has several languages or sub-sites, how it is built, and how much Search Console data exists.
You get the scope in writing before work starts. The audit does not change your website. If something is urgent, such as a rule that blocks Google from the whole site, we tell you before the report is finished.
Technical SEO audit: good to know
What is a technical SEO audit?
A one-off check of the website itself: how Google reaches it, what Google keeps, and what errors it meets. The result is a written report with a list put in order.
Is this the same as running an SEO tool?
No. Many tools give a long list that you have to sort yourself. Our report names the evidence, sorts the list by how many pages and how much search traffic each finding touches, and explains it.
Do you change my website during the audit?
No. The audit only reads. Fixes are a separate step, done by your developer or by us as a separate job.
Do I need Search Console?
It is the strongest evidence, so we ask for it. If you do not have it, we help you add it. Some of its data only builds up over time.
Can you promise better rankings after the fixes?
No. Nobody outside Google can. We find what holds the site back and say how sure we are about each finding.
Will the audit cover speed?
It measures speed and Core Web Vitals and says what is slow. The repair is a separate job; see website speed optimisation.
What if the site is built on WordPress, Shopify or custom code?
The checks are the same. How the faults are fixed depends on how the site is built, and the report says so.
Do you also write content or build links?
Not in the audit. The monthly search work is on our SEO page.
Related services
Monthly search work after the audit.
Repair of what the audit finds slow.
When visitors arrive and do not enquire.
Keeping search visits through a move.
Tell us about your website.
Tell us about your website and what worries you
Give us the address of the website and what you have seen. A person from our Melbourne team will reply by email.
Call 03 4158 4444info@truenorthinnovations.com.au
Every job is scoped before work starts.