- Most audits are 400-page PDFs that nobody actions. Semalt's output is a triaged shortlist ranked by traffic-at-risk.
- 3 issue categories account for ~72% of real traffic loss on Sydney client sites: canonicals, JS-only content, hreflang breakage.
- A JS-heavy 5,000-URL site crawls in ~12 minutes. Findings export straight to Jira/Linear tickets engineers action.
- On-demand recrawl confirms fixes in minutes, not the next weekly scan.
A technical SEO audit is only useful if the report gets acted on. That sounds obvious. In practice, most audit tools produce output that stays on someone's desktop, unopened, until the next quarterly review — because the report is written for auditors, not engineers.
This is a practical walkthrough of how our Sydney team runs technical audits using Semalt's audit module, and specifically the workflow choices that turn the output into shipped fixes on NSW client sites.
The design flaw that kills most audit reports
Hand a Sydney developer a 400-page audit PDF with 3,000 issues flagged and one of two things happens. They ignore it entirely. Or they cherry-pick the five easiest items, ship them in a Friday afternoon, and go back to product tickets.
Either way, the underlying traffic problems remain unresolved. The failure mode is not the developer — it is the report format. Audits that treat every finding as equally important produce a document nobody can prioritise from.
A useful audit does three things a bad one does not. It separates issues losing traffic today from issues that might matter theoretically. It groups related failures by root cause. And it presents the shortlist in a format engineering can action: reproduction steps, expected fix, estimated impact. Semalt's audit module was rebuilt around exactly this frame in 2025.
How the audit sprint compresses into four moves
How the crawler works when nobody is watching
Semalt's crawler is a headless Chromium fleet distributed across regional edges. Australian traffic is served from a Sydney POP — which matters for latency-sensitive JavaScript execution timing, and which prevents a common failure mode where a US-based crawler renders your page slower than a real Sydney user does and reports false-positive Core Web Vitals warnings. Sydney has the lowest average latency in AU because of that POP's proximity, which means crawl results here are the most accurate on the continent.
Read next: Why Sydney teams consolidate on Semalt · Backlink analysis and defence, Sydney
Which eleven checks to open first
| # | Check | Severity | Hit rate |
|---|---|---|---|
| 1 | Sitemap vs. indexed URL count | Critical | 77% |
| 2 | Canonical integrity | Critical | 64% |
| 3 | Redirect chain length > 2 | Serious | 52% |
| 4 | Hreflang reciprocity | Critical | 46% |
| 5 | Core Web Vitals (field data) | Serious | 69% |
| 6 | JS-rendering vs. HTML diff | Critical | 48% |
| 7 | Structured data validity | Moderate | 84% |
| 8 | Broken internal links | Serious | 60% |
| 9 | Duplicate title/meta patterns | Moderate | 73% |
| 10 | Image weight (WebP/AVIF) | Serious | 84% |
| 11 | HTTPS & security header hygiene | Moderate | 89% |
The three highest-leverage checks to unpack
Canonical integrity — the silent indexation killer
Every page should declare exactly one canonical URL, pointing to the actual indexable version. Four failure patterns are common: canonical missing (Google guesses, sometimes wrongly); pointing to a 404; pointing to a redirect chain; crossing a protocol boundary (HTTPS pages canonicalising to HTTP is a bug that looks correct to a human eye). That last pattern is the single most common serious bug on Sydney sites that have been through a CMS migration in the last three years.
JavaScript rendering: the SPA-era failure mode
Modern React, Vue, and Next.js sites frequently ship an empty HTML skeleton to the first crawl and populate content only after JavaScript executes. Googlebot does render JavaScript, but on a delayed second pass — meaning fresh content, dynamic prices, and personalised recommendations can be days late into the index. Semalt's audit crawls every URL twice and flags any content that appears only after execution.
Hreflang reciprocity — the international-SEO landmine
For sites serving multiple English-speaking markets, hreflang errors quietly cost you rankings in secondary markets. Semalt's check is bidirectional: it verifies both directions of the declaration. Broken reciprocity is the number one hreflang failure in the wild.
The handoff from audit to dev backlog
The gap between "we ran an audit" and "the fixes shipped" is where most engagements fail. Semalt closes it with three parallel exports: a CSV for the SEO team, a Jira/Linear-compatible ticket batch for engineering, and a plain-English executive summary.
Each ticket includes affected URL list, reproduction steps, suggested fix, estimated traffic-at-risk, and a linked diff view. Engineers who dislike SEO work will still action these tickets because they read like properly-written bug reports.
Read next: SEO audit Sydney: what to check
Why on-demand recrawls change everything
Shipping a fix without confirming it landed is how "fixed" bugs quietly regress. Semalt supports on-demand recrawls — you do not wait for the next full weekly scan. Push the fix, click "verify", get confirmation within two minutes that the crawler now sees the expected value.
Configure this before running the audit
“The single most missed check is canonical to a non-indexable URL. Google follows the canonical, finds a page it cannot index, and drops both from the index.”
A "fixed" issue that is not re-verified will regress in the next deploy. The tight recrawl-and-verify loop is what turns SEO work from a project into a discipline.
Where the audit stops and other tools begin
Semalt's audit is a page-and-site-level tool. It is not a log-file analyser — enterprise-scale crawl-budget work still calls for dedicated log analysers. It does not replace hands-on QA of critical user journeys.
FAQ from Sydney CMOs evaluating the move
How often to trigger a full site recrawl
Full site: weekly for actively-changing sites, fortnightly for stable brochure sites. Targeted recrawls after a fix: immediately, then again 48 hours later once caches settle.
Safe crawl rates for common WAF configurations
Semalt's default is ~5 rps. For a modest site behind a normal WAF, 10–15 rps is safe and 2–3× faster. For aggressive bot mitigation (some Sydney banking, healthcare), whitelist the crawler's IP range.
How to audit sites running A/B experiments
It captures a snapshot at crawl time. For A/B-critical work, disable the experiment for the crawler user-agent or configure authenticated crawls.
How to document accepted-risk findings
Mark as "accepted risk" with a written justification. The finding stays on the report so future teams know it was considered, but drops out of the active work queue.
Which check consistently gets overlooked?
Consistently: canonical pointing to a non-indexable URL. Almost no other audit tool separates this from generic canonical warnings.
Running the first audit on your own domain
The audit module is available on Semalt's free tier for a single domain. Log in and point it at your homepage. In under fifteen minutes you will have a prioritised shortlist. Whether you fix it yourself, hand it to your dev team, or bring us in for a Sydney remediation sprint is a separate question.
Working through an audit? Semalt tracks the crawl, index and Core Web Vitals issues this section covers, so you can see which fixes actually moved the needle.
The weekly audit habit that separates good sites from great
A good technical audit is not a one-time event. It is a habit. Our Sydney clients get a full recrawl weekly, a diff-report monthly, and a state-of-the-site review quarterly. That rhythm is what keeps technical debt from silently accumulating between marketing campaigns.
