TECHNICAL SEO AUDIT
Technical SEO audit: find what blocks your site before you invest in content.
Know exactly which technical issues deserve attention first.
I crawl your site the way search engines do, review indexing, Core Web Vitals, and template-level issues, then deliver a prioritized fix list — so content efforts build on solid ground.
Is this the right support?
Is your site technically ready to rank?
Your pages exist and your content is reasonable, but search performance is flat and nobody can say whether the problem is technical.
Important pages are not indexed and nobody knows the true coverage.
Content investment is wasted on pages search engines never see.
I compare crawl results with Search Console coverage to find excluded, orphaned, or conflicting pages.
Key pages load slowly and fail Core Web Vitals.
Visitors bounce and search systems see a poor experience signal.
I measure field and lab data per template to separate site-wide issues from page-specific ones.
The same template flaw repeats across dozens or hundreds of pages.
Fixing pages one by one never ends; the root cause survives every content update.
I review templates, canonicals, and structured data at the source so one fix repairs every affected page.
WHAT WE'LL WORK ON
Four work areas, each connected to your situation
Crawl and indexation review
Pages that cannot be crawled or indexed cannot rank.
Crawl the site, review robots directives, sitemaps, and internal linking.
Output: A coverage map showing what is indexed, excluded, or orphaned.
Decision: Which exclusions are intentional and which are leaks.
Core Web Vitals and page experience
Slow templates hurt visitors on every page they touch.
Measure vitals per template and identify render-blocking and media issues.
Output: Template-level findings with estimated effort per fix.
Decision: What to fix at the template level before page-level polish.
Templates, canonicals, and structured data
Duplicated signals confuse search engines about which page to show.
Review canonical tags, hreflang where used, and schema markup validity.
Output: A markup and duplication report with corrections.
Decision: Which template changes remove the most confusion.
Prioritized roadmap and handover
A long issue list without priorities never gets implemented.
Rank every finding by business impact and implementation effort with your team.
Output: A sequenced fix list with owner, effort, and validation signal.
Decision: What your developer fixes first, and what can wait.
THE TOOLKIT
Tools I work with
A practical stack for research, execution, measurement, and better decisions.
Explore the wider toolkit
Illustrative example
Three typical audit findings, ordered by priority. Each row shows the issue, the corrective action, who does it, and how you verify the fix.
| Issue | Action | Owner | Dependency | Review |
|---|---|---|---|---|
| Service pages blocked by outdated robots directives | Update directives and validate coverage in Search Console | Consultant + developer | None — blocking crawl issues come first | Coverage report shows pages indexed within the agreed window |
| Slow largest-contentful-paint on service templates | Optimize media delivery and remove render-blocking requests | Developer | Depends on crawl access so fixes can be verified | Field data improves on the affected templates |
| Missing canonical tags on filtered listing pages | Add self-referencing canonicals at the template level | Consultant + developer | Comes after blocking issues so verification is clean | Crawl confirms canonicals present on all listed pages |
Blocking crawl and indexation issues precede performance polish: a fast page that is not indexed still brings no search traffic.
PROJECT EVIDENCE
Go Fluent Academy
Related workStarting situation: A website with strong programs but inconsistent positioning and a digital journey that did not reflect the offer.
Documented work: Restructured the website around buyer questions and unified analytics to see which pages attracted qualified visitors.
Relevance: This project involved website and analytics work that supports technical SEO decisions. It does not demonstrate proven ranking results.
Explore the project ↗PARTNERSHIP PROCESS
How we work together
1. Collect access
We arrange website, CMS, and Search Console access and confirm the pages that matter most.
An agreed crawl scope and priority pages.
2. Diagnose
I crawl the site, review coverage and vitals, and inspect templates manually.
A complete findings list with evidence per issue.
3. Prioritize together
We rank findings by business impact and effort with your developer in the room.
A sequenced roadmap with owners.
4. Hand over
You receive the report, the raw crawl data, and a walkthrough of the top findings.
Everything your team needs to implement or to scope the next step.
SCOPE AND INVESTMENT
What shapes the quote
What shapes the quote
- Number of pages and templates
- CMS and hosting complexity
- Depth of manual template review
Your part
- Website and CMS access
- Search Console access where available
- A developer contact for feasibility questions
Scope boundaries
The audit stands alone. If you want implementation or monitoring afterwards, we scope it as a focused project or ongoing partnership.
The audit is itself a diagnostic: it answers what is broken and what to fix first.
Implementing the fixes is a natural focused project once the roadmap is agreed.
Advertising spend, specialist production, and third-party tools are scoped separately.
FAQ
How is an audit different from ongoing SEO support?+
The audit produces findings and a prioritized roadmap. Ongoing support implements the fixes, monitors changes, and adjusts priorities.
Do you need developer access for the audit?+
Read access is enough to diagnose. Implementation needs someone who can deploy changes, which we agree in the follow-up scope.
How long does an audit take?+
Timing depends on site size, templates, and access. We agree the delivery date before starting.
Will you fix the issues you find?+
Fixes are scoped separately — as a focused project or as part of an ongoing partnership — after you see the findings.
What do you check that automated tools miss?+
Tools flag symptoms. I verify templates manually, compare crawl data with Search Console coverage, and judge business impact before prioritizing.
How do we know the fixes worked?+
We re-crawl, check Search Console coverage, and review the agreed signals at a set review point.
Let's explore whether I'm the right fit.
Discuss your site, what you suspect is broken, and whether an audit makes sense.