New format
Technical SEO audit: goals, tasks, and a DIY start
If the site stalls despite content and ad spend, it’s often not “SERP magic” but tech: indexing, speed, duplicates, status codes, mobile layout.
We’ll cover how a technical audit differs from other checks, what you can inspect yourself, and when it’s smarter to hand the work to specialists.
What a technical audit is for
An audit is a systematic review of the site: tech, structure, content, usability, and search visibility. The goal — see if the resource is ready for promotion or needs fixes first.
The technical loop answers: can a crawler stably crawl and index the right URLs, and can a user get the page quickly without failures.
SEO audit goals
The main job is to gather facts about the site’s state and weak spots — not to “find someone to blame.”
Afterwards you prioritize fixes: what blocks indexing and conversion now, what can wait. Demand, competition, and UX are assessed too — but those are related loops next to pure tech.
An audit usually delivers:
- a list of critical errors with priority;
- a map of what blocks traffic and lead growth;
- a clear work plan for the next iterations.
Audit types
In practice there are several types. Usability and marketing are narrow slices. Technical looks at hosting, code, crawl, and page delivery. Search (on-page / SEO) — meta, headings, internal links, content duplicates — more often after tech isn’t in the way.
An express check before promotion covers only critical issues. A full review needs a crawler and webmaster panels. Tools include Screaming Frog, Netpeak Spider, Titlo, plus Google Search Console and other webmaster tools.
Basic classification:
- technical;
- search (on-page / SEO);
- usability;
- marketing / competitive.
Technical (platform)
A technical audit checks how the site works “under the hood.” Server errors, a broken robots file, duplicates, and a slow mobile version hurt visibility more than one missing paragraph of copy.
What is usually checked:
- 2xx / 3xx / 4xx / 5xx status codes and redirect chains;
- robots.txt and XML sitemap;
- indexing of key URLs (webmaster / Search Console);
- canonicals and duplicates (WWW, HTTP/HTTPS, parameters);
- speed and Core Web Vitals (LCP, INP, CLS);
- mobile layout and viewport;
- HTTPS and mixed content;
- availability of important resources (JS/CSS), critical layout errors.
Express-audit mini-checklist
| Check | Where to look | Severity |
|---|---|---|
| Homepage and services indexed | Webmaster / GSC | high |
| 404 on important URLs | Crawler | high |
| robots blocks needed URLs | robots.txt | high |
| Slow mobile LCP | PageSpeed / CWV | medium/high |
| Duplicates without canonical | Crawler | high |
Search audit (on-page)
After tech, check how ready pages are to rank: meta, headings, internal linking, content duplicates, image optimization.
Typical scope:
- indexing settings and duplicate hunt;
- Title / Description meta tags;
- H1–H3 hierarchy;
- internal linking;
- alt on meaningful images;
- filters and sharp drops — separately, by evidence;
- positions and traffic vs competitors — as context, not as “tech.”
Usability
Usability is convenience for people: speed, mobile readiness, clear navigation, no empty sections. Some metrics overlap with tech (speed, SSL), some with the product (lead flow).
What to look at:
- load speed and UI stability;
- display on phone and tablet;
- HTTPS;
- logical hierarchy and no “placeholders”;
- bounces, depth, devices, and browsers — in analytics.
Content and site fill
A separate slice: uniqueness and freshness of copy, information gaps, keyword effectiveness on landings, outdated pages to delete or update.
Strong content doesn’t cancel tech: if a page isn’t indexed or returns 500, the text won’t save it.
Basic vs full audit
A basic (express) pass covers critical issues: server errors, 404/redirects, meta on key URLs, indexing. It doesn’t claim a full competition or design review.
A full audit — tech + on-page + semantics/structure + usability and competitive context. That’s a turnkey work plan, not one checklist.
When an audit is especially useful:
- site launch or relaunch;
- the site hasn’t been maintained for a long time;
- promotion stopped and metrics dropped;
- you need vendor oversight;
- low traffic, high bounce, rising 404s.
When an SEO audit can wait:
- no budget for fixes afterward;
- the resource is obsolete and better replaced;
- priority is a short paid cycle without organic.
DIY or with a vendor
Your own loop helps: learn to read webmaster tools, crawl the site, fix robots and meta. It takes time and someone who will finish the fixes.
A vendor spots systemic errors faster, separates critical issues from noise, and ties tech to semantics and structure. It makes sense when downtime costs more than the audit.
Arguments for an external audit:
- an independent view without “habit blindness”;
- work priorities, not an endless list of tiny issues;
- practical alignment with search-engine requirements.
What to do after the audit
An audit without implementation is just a PDF. Next: fix critical issues, then structure and landing semantics, then content and growth work.
Takeaways
A technical audit is a fast way to see if the site is breaking its own promotion. Start with indexing, status codes, and speed; go deeper as resources allow. If you need a second pair of eyes — review the report with a specialist and budget for fixes right away.
FAQ
What is a technical SEO audit?
A check of how the site is served to crawlers and users: crawl, indexing, status codes, speed, mobile readiness, utility files, and critical layout/server errors.
How is it different from an “SEO audit” overall?
Tech is the foundation. Separately you review semantics, copy, links, and usability. Without tech, even a strong keyword core rarely converts into stable rankings.
Can I audit yourself?
A basic loop — yes: webmaster panels, a crawler, PageSpeed/CWV, robots and sitemap checks. Deep niche and priority work is usually faster with an experienced specialist.
Where should I start if time is short?
Indexing and duplicates, 4xx/5xx, redirects, mobile version, LCP/INP speed, HTTPS, and access to key landings.
When is it better to postpone an audit?
If there’s no budget for fixes, the site is obsolete and easier to rebuild, or the priority is a short paid cycle without relying on organic.
Site won’t move and you suspect tech, not “SERP luck”?
We’ll run a technical audit: indexing, status codes, speed, duplicates — with a prioritized fix plan.
Discuss the task
