Initialising Digital Ignition
Enkindle Group
TECHNICAL SEO PERTH

Technical SEO in Perth, run by the person who builds the sites

Technical SEO decides whether Google can reach your pages, render them and understand them. Publish good content for a year and it goes nowhere if the page returns the wrong status code or the canonical points somewhere else.

Google Rating
5.0
★★★★★
23 reviews
+89%
non-brand organic impressions for Fridgy Australia, read back from Search Console
+161%
sessions in twelve months for Fridgy Australia
+274%
clicks year on year on ETA Training's main course term
$1,000
where our SEO starts, including GST, per 4 week cycle

Technical SEO is not a channel.
It is the condition your site
has to be in first.

It covers the mechanics: how a crawler discovers your URLs, what it gets back when it asks for them,
how quickly the page becomes usable, and how clearly the page describes itself.
Plenty of the Perth sites we look at do not have a content problem at all. What they have is unglamorous and specific, and fixing it is usually the cheapest lift available on a site that already has traffic. If your site is technically sound already, we will tell you that and point you at the thing that is genuinely holding you back instead.
CLIENT RESULTS

Proof this works

Built around discovery, indexation,
and what happens after.

Before anything ranks, it has to be found and kept.
We start by separating three problems that usually get lumped together.
That means looking at:
pages Google has never discovered
pages it discovered and chose not to index
pages it indexed and then dropped
the sitemap and internal linking that decide whether a page is reachable at all
pages reported as crawled and not indexed, and whether they are thin, duplicated by a variant or blocked
robots rules left over from a staging site, or an AI crawler block that also catches Googlebot
server log files, where the hosting gives us access, so crawl behaviour is what actually happened rather than what a tool estimated

What a technical audit actually checks

A technical audit is a list of specific questions with verifiable answers, not a score out of a hundred.

What we check first, in the order it usually pays:

+
status codes and redirect chains on every URL we can reach
+
the canonical on each template, and whether internal links agree with it
+
parameter, filter and variant URLs splitting one page into four
+
what is in the raw HTML response versus what only appears after rendering

Every finding comes with the URL it was found on, so you can check it yourself.

Illustration comparing WordPress, Webflow and Shopify as three browser windows, each labelled with what that platform handles

Why duplicate URLs
matter commercially

Duplication is one of the problems we find most often, and it almost never looks like duplication from the front end.
One page quietly becomes four through:
+
a filter or a sort order
+
a session or tracking parameter
+
a print view
+
a trailing slash
+
an uppercase variant
+
the same product living under two collection paths
Left alone, those split signals across near identical pages and Google picks a canonical for you. Often it picks the wrong one, which is how a filtered listing ends up ranking instead of the category page you optimised. We map the real URL set, decide which version should rank, and make the canonical tag, the internal links, the sitemap entry, the hreflang and the redirect rules all agree.
Agreement matters more than any single tag.

Core Web Vitals, measured on your real site

Speed work goes wrong when it becomes a score chase.

What we measure on
When we use it
Field data
Where there is enough traffic to have it
Lab testing on throttled mobile
Where there is not
A perfect result in a lab test on a fast connection tells you very little about what a customer on mobile data in Perth experiences at 7pm.

The fixes are ordinary engineering:

+
serve images in a modern format at the size they are displayed
+
give them width and height
+
preload the hero
+
stop loading the review widget, the chat widget, the heatmap and three tracking scripts before the page is usable
+
defer what can be deferred and remove what nobody uses

The three metrics worth your attention

What is usually behind each one:
LCP
Largest Contentful Paint, usually a hero image or a web font blocking the first meaningful paint
INP
Interaction to Next Paint, usually too much JavaScript competing on the main thread
CLS
Cumulative Layout Shift, usually images without dimensions, late loading banners or a cookie bar that pushes the page down

How a technical engagement runs

Three stages, in this order. Fixing what is broken comes before adding anything new.
01

Find it

A full crawl of every reachable URL, plus Search Console and server logs where the hosting allows it, so the problem list is evidence rather than opinion.
GET A FREE AUDIT
02

Fix it

We work in the theme or the project ourselves on Shopify, Webflow and WordPress, so the fixes ship instead of sitting in a ticket queue.
SEE HOW WE BUILD
03

Prove it

A before position, the change we made, and the measurement after it, read from Search Console and GA4 rather than a tool's own score.
SEE OUR SEO SERVICE

What structured data can include

Structured data tells a search engine what a page is rather than making it guess. We implement it where there is a real reason to, not as a blanket layer across every template:
Product markup with accurate price and availability on ecommerce
LocalBusiness on a location page, with details that match your Google Business Profile exactly
Article on editorial content
Breadcrumb, so the result shows a readable path
Organization markup, so your brand entity is consistent across the site
markup that describes what is genuinely on the page, never a price, rating or stock status the page does not show
no FAQ markup added purely to win extra space, because FAQ rich results now show only for a narrow set of well known government and health sites
no self serving aggregate ratings, because they are not eligible
Is your problem technical, or is it something else entirely?

Where the platform hides the problem

We work daily in Shopify, Webflow and WordPress, so we know where each one hides things:
01
theme settings that strip a heading
02
an app that injects duplicate schema
03
a page builder where key copy, internal links or a canonical tag only exist after client side rendering
04
a nested sitemap that a crawler will not follow
05
old URLs sent to the homepage instead of a single hop to their closest equivalent
Migrations are where the largest losses happen and where they are most preventable, so we map the old URL set to the new one before launch, keep the redirect table, and monitor status codes and Search Console coverage in the weeks after.

The crawler we built, and the free audit

We built our own crawler because the off the shelf tools kept telling us things we could not verify. It is not a product and we are not pretending it is one.

It fetches every page on a site and records:

+
status codes
+
redirect chains
+
titles
+
meta descriptions
+
headings
+
canonicals
+
indexability
+
internal link structure
+
structured data

It then scores what it finds so we can rank issues by how much they actually matter.

Having our own crawler means we can check a specific claim on a specific site rather than trusting a number in someone else's dashboard.

The audit a person writes

On top of that we run a free audit that a person writes, not an automated PDF with a traffic light chart. We crawl the site, look at what Search Console and Analytics are reporting, and write up what is wrong, what it is costing you and what we would do first. Technical work is usually front loaded into the first cycles. We are a founder-led agency in Perth, Western Australia, and the person who audits your site is the person who fixes it.

Who this is for

The heavier technical work earns its keep on:
01
sites with traffic already
02
stores running to thousands of URLs
03
sites facing a migration
04
pages live for months, still not indexed
05
fixes that have to ship in the theme
06
owners who want fixes made, not listed
Questions

Technical SEO questions Perth businesses ask.

How do I know if my problem is technical SEO or something else?+
The quickest tell is a gap between what is published and what is indexed. If you have pages that have been live for months and Search Console shows them as discovered or crawled but not indexed, that is technical. If your pages are indexed and ranking on page two or three for the right terms, that is usually content, relevance or authority instead. We will tell you which one you are dealing with before you spend anything, because the answer changes what we would recommend.
Do I get the fixes implemented, or just a list of them?+
We make them. Web design and development is our own lane, so on Shopify, Webflow and WordPress we work directly in the theme or the project rather than writing a ticket and waiting. If your site sits on a platform your internal team controls, we will scope the changes precisely enough that a developer can implement them without guessing, and we verify the result afterwards rather than assuming it shipped correctly.
How long before I see anything from technical work?+
It depends on what was broken. Fixing an indexation block or a bad canonical can show up within a couple of weeks once Google recrawls, because the pages already had value that was being suppressed. Speed and structured data work is slower and compounds. We will not give you a date, and you should be careful with anyone who does.
Do I need a full technical audit if my site is only a few pages?+
Usually not a deep one. A small brochure site has a small number of things that can go wrong, and our free audit will surface them. The heavier work, log file analysis, crawl budget, parameter handling, variant duplication, earns its keep on stores and larger content sites where the URL count runs into the thousands. We would rather tell you your site is fine and point you elsewhere than sell you an audit you do not need.
What does technical SEO cost in Perth?+
SEO with us starts from $1,000 including GST per four week cycle, scoped to the site and the work in front of it. Technical remediation is normally weighted into the early cycles because it unblocks everything after it. We bill every four weeks, not monthly, so the cycle and the invoice always line up. If you want a sense of the shape before you talk to us, start with the free audit and we will quote off what we actually find.

Tell us what your site is doing

Send us your URL and what you are seeing, whether that is pages falling out of the index, slow load times or crawl errors. We will check the site and come back with the specific faults. If you would rather talk it through, call us.

Call 0455 089 036
We reply to every enquiry ourselves. No call centre, no automated sequence.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Want someone who will make the fixes, not just list them?

Related
growth areas

Technical work clears the way. What you put through it decides what the traffic is worth.

These are the areas technical SEO is usually paired with.
Enkindle Group logo
Enkindle Group
2026