core web vitals indexation crawl schema

Technical SEO & Audits · Canberra & the ACT

Technical SEO in Canberra: find what is quietly blocking your rankings

Great content cannot rank if Google struggles to crawl, render or index your site, or if it fails Core Web Vitals on mobile. A technical SEO audit finds exactly what is holding you back, ranks every issue by real business impact, and gives your team the precise fix. No 300-item tool dump, no jargon, just the blockers that matter and how to clear them.

  • Issues ranked by business impact
  • The exact fix for each, in plain English
  • Fixed-price, scoped before we start
Technical audit · your-site.com.au
Critical
214 pages crawled but not indexedThin or duplicated content, cannot rank
High
Homepage LCP 4.1s on mobileFails Core Web Vitals, target is 2.5s
High
DOM size 3,180 nodesPage-builder bloat, slows interactions
Medium
Sitemap lists 640 dead URLsWastes crawl budget on nothing
Low
Missing breadcrumb schemaForegoes rich-result eligibility
Every finding comes with its impact and the fix
100+Technical checks in a full audit
≤2.5sThe mobile LCP target we build to
4Severity levels, ranked by impact
0Guesswork, every fix explained

What it is

What does a technical SEO audit cover?

A technical SEO audit is a structured review of everything that affects whether search engines can find, understand and trust your site. It checks crawlability, indexation, Core Web Vitals, mobile usability, structured data, sitemaps, canonicalisation, redirects and internal linking. You get back a prioritised list of issues by severity, the business impact of each, and the exact fix, so your team knows what to do first rather than drowning in a tool export.

Crawlability

Whether Googlebot can reach your pages at all: robots.txt, status codes, redirect chains, crawl traps and orphaned pages.

robots.txt · redirects · crawl budget

Indexation

Whether crawled pages actually make it into Google. We diagnose the Search Console statuses that keep pages out of search.

index coverage · canonicals · sitemaps

Speed & Core Web Vitals

Real-user loading, responsiveness and visual stability on mobile, measured against Google's current thresholds.

LCP · INP · CLS

Structured data

Schema markup that makes your pages eligible for rich results and helps search engines, and AI answers, understand them.

JSON-LD · rich results

Architecture & links

Site structure and internal linking, so important pages are easy to reach and your authority flows where it should.

site structure · internal links

Mobile & rendering

Mobile-first readiness and whether key content and links appear without needing JavaScript to run first.

mobile-first · JS rendering

Speed, correctly

Core Web Vitals, and what actually counts as good

Core Web Vitals are three metrics Google uses to measure the real experience of your visitors, taken at the 75th percentile of your actual mobile and desktop users. Here are the current thresholds we build to. Note that INP replaced the older First Input Delay metric in March 2024, so any advice still quoting FID is out of date.

LCP

Largest Contentful Paint

Loading: when the biggest element on screen finishes rendering.

≤ 2.5s good
GoodNeeds workPoor
INP

Interaction to Next Paint

Responsiveness: how quickly the page reacts when someone taps or clicks.

≤ 200ms good
GoodNeeds workPoor
CLS

Cumulative Layout Shift

Stability: how much the layout jumps around unexpectedly as it loads.

≤ 0.1 good
GoodNeeds workPoor

Thresholds per Google's web.dev Core Web Vitals documentation. Measured at the 75th percentile of real users on mobile and desktop.

The one most people Google

Why are my pages not showing up on Google?

It almost always comes down to one of two Search Console statuses, and they mean very different things. Knowing which one you have tells you whether the problem is Google reaching your page, or Google rating it. Every technical SEO Canberra audit we run pins this down page by page.

Discovered · currently not indexed

Google has not looked yet

Google knows the page exists but has not crawled it. This is a crawl-priority or site-quality signal: Google is choosing to spend its crawling elsewhere.

CauseCrawl budget limits, a slow server, thin sitewide quality, or too many low-value URLs from faceted navigation.
FixStronger internal links to the page, a faster server, a cleaner sitemap, and pruning low-value URLs.
Crawled · currently not indexed

Google looked and passed

More serious. Google crawled the page and chose not to index it. It has judged the page and decided it is not worth including, usually on quality grounds.

CauseThin or shallow content, near-duplicate pages without canonicals, or a format that does not match what searchers want.
FixRaise the page's quality and uniqueness, align it to search intent, add canonicals, and strengthen internal links. Earn the index, do not force it.

In short: "Discovered" means Google has not looked yet, a crawl problem. "Crawled, not indexed" means Google looked and passed, a quality problem.

Crawl budget waste and index bloat, the quiet versions

Crawl budget is the amount of attention Google is willing to spend crawling your site in a given period. A ten page site never runs out of it. A site whose filters, tag archives, on-site search results and calendar pages generate thousands of near-identical URLs absolutely does, and Google spends its visit on junk while the pages that earn you money wait their turn. Online stores are the classic case, which is why technical SEO for stores gets its own page.

Index bloat is the same problem one step later: hundreds of thin URLs that made it into Google's index and now drag on how the whole site is judged. Google rates sites as well as pages, so a large tail of low-value indexed URLs dilutes the quality signal of everything else. The fix is deliberate pruning, with noindex, canonicals or removal, so the index holds only pages you actually want to be judged on. Every SEO audit Canberra businesses commission from us maps both problems URL by URL before recommending either.

Page indexing, after clean-up

Illustrative GSC-style coverage trend over 12 weeks

fixes shipped wk 1 wk 12
Indexed pagesNot indexed

What you actually get

A sample from a real audit

Most agencies promise an audit and show you nothing. Here is an anonymised excerpt from a real one, so you can see the format before you commit: each issue with its severity, its business impact and the exact fix. Your report reads like this, prioritised so you tackle the costly problems first. It is the kind of SEO audit Canberra businesses can hand straight to a developer and act on.

Issue foundSeverityWhy it mattersThe fixEffort
214 product pages "crawled, currently not indexed"CriticalThese pages get zero organic traffic; likely thin or duplicated descriptionsRewrite to unique descriptions, add internal links from category pages, consolidate near-duplicates with canonicalsLarge
Homepage LCP 4.1s on mobile (target 2.5s)HighFails Core Web Vitals; a slow first paint hurts both experience and rankingsCompress and lazy-load the hero image, preload the LCP element, serve modern WebP or AVIF formatsMedium
DOM size 3,180 nodes (excessive above 1,400)HighPage-builder bloat inflates INP, so interactions feel slow on mobileTurn on optimised DOM output, remove nested wrapper sections, cut unused widgetsMedium
Sitemap lists 1,900 URLs, 640 are noindex or redirectedMediumWastes crawl budget and sends Google mixed signals about what to indexRegenerate the sitemap to include only canonical, indexable pages returning a 200 statusSmall
Faceted filters create around 8,000 crawlable URLsMediumCrawl budget is drained on filter combinations before important pages are reachedBlock filter parameters in robots.txt, canonical them to the base category, or noindex the combinationsMedium
47 internal links point to redirected URLsLowMinor loss of link equity and an extra hop on every clickUpdate the links to point straight to the final destination URLsSmall
Missing Organization and Breadcrumb schemaLowForegoes eligibility for rich results in the search listingAdd JSON-LD structured data across the siteSmall

Tap Severity or Effort to re-sort, exactly as you can in the real report. Small effort plus high severity is where we start.

Critical: blocking indexing or traffic High: failing a ranking factor Medium: crawl or efficiency waste Low: polish and best practice

A Canberra-common one

Is your page builder quietly slowing you down?

Most small business sites in Canberra run on WordPress with a page builder like Elementor, or on Wix or Squarespace. These are fine, but they wrap every element in extra containers, which inflates the code the browser has to process. Google flags a page as having an excessive number of elements above roughly 1,400, and heavy page weight is the most common reason builder sites fail the INP responsiveness metric on mobile.

A heading, a button and an image, written cleanly, is a handful of elements. Built through a page builder, the same block can produce thirty or forty nested containers. Multiply that across a page and interactions start to lag, especially on the mid-range phones most of your visitors actually use. It is one of the most common issues we find, and one of the most fixable.

The fix is rarely a rebuild. Turning on optimised output, flattening nested sections, removing unused widgets and lazy-loading below-the-fold content usually brings the count down and the responsiveness up. If your whole build needs rethinking, that is a job for SEO web design, and WordPress speed and technical fixes have their own dedicated page.

<section class="wrap">
<div class="col">
<div class="inner">
<div class="widget"> × 40
</div>
</div>
</section>
→ flattened: 3,180 to 1,100 nodes
Fewer nodes, faster interactions, better INP on mobile.

How it works

From audit to fixed, four steps

An audit is only worth something if it gets acted on. We scope the price up front, deliver a prioritised report your team can read, then fix it ourselves or brief your developer, whichever you prefer.

01

Scope & quote

Day 1

We size your site and give a fixed price before starting. Small sites are quick, large sites cost more because there is more to analyse.

02

Audit

1 to 2 weeks

A full crawl plus Search Console and real-user data. We separate the issues that cost you traffic from the ones that do not.

03

Prioritised report

Walked through

Every issue by severity, its impact and the exact fix, explained in plain English in a call, not emailed as a spreadsheet.

04

Fix

Ongoing or handover

We implement the fixes, or brief your developer with clear instructions. Indexing fixes can show within days; speed gains within weeks.

A technical audit pairs naturally with local SEO and ecommerce SEO, and it is the usual first step in any full SEO engagement.

Timing

When should you get a technical audit?

Not on a subscription, and not every month. A technical audit earns its money at specific moments: before you change something big, after something has gone wrong, right at the start of a site's life, or when growth has stalled and nobody can say why. If one of the four situations here sounds like yours, an audit is the cheapest way to find out what is really going on before you spend on anything else.

For an established site that is not changing platforms, a full audit once a year is plenty, with lighter monitoring in between through Search Console. What you should never do is pay for the same full audit every quarter while the first one's findings sit unfixed. The SEO audit Canberra businesses actually need is one thorough diagnosis, acted on properly, then checked. That is also why ours comes with the fix list built in.

Before a migration or redesign

Changing domain, platform or design puts every ranking you own at risk. Audit first, so the new site inherits the old one's equity instead of losing it.

Traffic has dropped

Rankings fell and nobody knows why. An audit separates a technical cause you can fix this week from a content or competition problem that needs a different plan.

A new site just launched

Launch problems are cheapest to fix now, before Google forms a lasting view of the site. A short audit at launch prevents months of quiet underperformance.

Growth has stalled

The content is good, links are building, and rankings still will not move. A hidden technical ceiling is the usual suspect, and an audit either finds it or rules it out.

FAQs

Technical SEO Canberra: your questions answered

The questions businesses ask before booking an audit, answered straight: what it covers, what it costs, why pages go missing, and how quickly fixes show.

An SEO audit is the diagnosis and technical SEO is the treatment. The audit reviews your site and produces a prioritised list of issues, their business impact and the fix for each. Technical SEO is the ongoing work of implementing those fixes and keeping the site healthy: crawlability, indexation, Core Web Vitals, structured data and site architecture. Most engagements start with an audit so we know exactly what to work on first.

A full technical audit checks everything that decides whether Google can find, understand and rank your pages: crawlability and how your crawl budget is spent, indexation and any "crawled, currently not indexed" pages, Core Web Vitals and page speed, site architecture and internal linking, structured data, HTTPS and security, redirects and broken links, and mobile usability. You get each finding with its severity, its business impact and the exact fix, prioritised so the costly problems come first, exactly like the sample excerpt above rather than a raw tool export nobody can act on.

Core Web Vitals are three metrics Google uses to measure real user experience. Largest Contentful Paint (loading) should be 2.5 seconds or less, Interaction to Next Paint (responsiveness) should be 200 milliseconds or less, and Cumulative Layout Shift (visual stability) should be 0.1 or less, all measured at the 75th percentile of your real visitors. INP replaced the older First Input Delay metric in March 2024, so any advice still quoting FID is out of date.

Google Search Console usually gives one of two reasons. "Discovered, currently not indexed" means Google knows the page exists but has not crawled it yet, often a crawl-priority or site-quality signal. "Crawled, currently not indexed" means Google crawled the page and decided not to index it, usually because the content is thin, too similar to another page, or does not match what searchers want. Our audit identifies which pages are affected and the reason for each, then the fix.

It can, mostly through page bloat. Builders wrap every element in extra containers, so a simple block that should be a few lines of code can become thirty or forty. Google flags a page as having an excessive number of elements above roughly 1,400, and heavy page weight is the most common reason builder sites fail the INP responsiveness metric on mobile. It is fixable with settings and clean-up rather than a rebuild, and we handle that as part of the work.

It depends on the size of your site, because more pages means more to analyse. A small business site is usually a few hundred to around a thousand dollars, while large sites with thousands of URLs cost more. We scope your site first and give a fixed quote before any work starts, so you know the price and what you are getting up front, with no open-ended hourly billing. The full picture on cost sits on our pricing page.

Crawl budget is the amount of crawling attention Google gives your site in a given period. For a typical small business site of a few dozen pages it is a non-issue, so ignore anyone selling crawl budget optimisation for a ten page site. It matters when something on your site multiplies URLs: ecommerce filters, tag archives, on-site search pages or calendar plugins can generate thousands of near-duplicate addresses, and Google wastes its visit on those instead of the pages that make you money. The audit checks whether this is happening and, if it is, blocks the waste at the source.

Once a year is enough for most established sites, plus a fresh audit before any migration, redesign or platform change, and after any unexplained traffic drop. Between audits, Google Search Console gives you free ongoing monitoring of indexing and Core Web Vitals, and we set that up as part of the work. What wastes money is repeating a full audit every few months while the first report's fixes are still sitting in a drawer. Fix first, verify, then re-audit when the site or the situation genuinely changes.

Some fixes show quickly. When we clear an indexing block or a crawl issue, pages can start appearing in Google within days of a re-crawl. Core Web Vitals and speed improvements usually reflect within a few weeks, once Google gathers enough real-user data at the 75th percentile. Bigger gains in rankings and traffic build over one to three months, because a healthy technical foundation is what lets your content and links finally do their job.

Get started

Find out what is holding your site back

Tell us about your site and we will scope a technical audit and give you a fixed price. You get a prioritised report you can act on, whether we do the fixes or your own developer does. No open-ended billing, and no jargon.

If a quick look shows only a couple of small issues, we will tell you that too. We would rather point you to a free tool than sell you an audit you do not need.

Your technical auditFixed price
  • Every issue found, ranked by business impact
  • The exact fix for each, in plain English
  • Core Web Vitals and indexation checked properly
  • A walk-through call, not just a document
  • Fixes done by us or handed to your developer