Crawlability and indexing
Inspect status codes, robots instructions, canonical signals and sitemap coverage. Verify the issue before deciding how urgently to act.
Deliverable: evidence + recommended actionA CLEAR STARTING POINT
SEO audit &
website action plan.
Understand what may be holding your website back before investing in changes. I review technical SEO, service-page content, local relevance and the path to enquiry, then turn the findings into a prioritised action plan.
Discuss your projectDIAGNOSE BEFORE YOU INVEST
Technical SEO audit.
From evidence to priorities.
Explore a sample review structure. These examples illustrate the method; they are not findings about your website.
ILLUSTRATIVE AUDIT EXTRACTREVIEW → PRIORITISE
Useful service-page content
Compare the offer, headings, direct answers and internal links against the real questions a prospective customer needs answered.
Deliverable: page-level content prioritiesA clear path to enquiry
Review mobile usability, contact routes and friction. A page needs to work for visitors as well as be understandable to search engines.
Deliverable: practical checks and next stepsWhat does a technical and content SEO audit cover?
The depth is agreed around the size of the website and the decisions you need to make.
Discovery & indexing
Crawl access, status codes, canonical signals, sitemaps and important pages.
Structure & content
Page purpose, overlapping topics, internal links and missing customer answers.
Trust & enquiry
Clear services, real evidence, location information and the next step.
Available measurement
Search and analytics evidence where access exists; missing data is recorded, not invented.
SEO audit deliverables: findings, priorities and next steps.
An audit should make the next decision easier, not create another dashboard to interpret.
Executive summary
The main problems and opportunities in plain language.
Page-level findings
Affected URLs, evidence and recommended changes.
Prioritised roadmap
Actions ordered by value, effort and dependencies.
Implementation route
What can be handled now, what needs content or development, and how to verify the result.
What access is needed for an SEO audit?
Your website, the services you want to prioritise and the customers or locations you want to reach. Search Console and analytics access can improve the evidence; where they are unavailable, the limits are made explicit.
After the audit: implementation and follow-up.
You can use the roadmap to guide your own work, or include agreed implementation with me. A website rebuild is not an automatic conclusion.
GOOD QUESTIONS
Website and SEO questions, answered.
What do I receive after the SEO audit?
A clear set of findings with supporting evidence, priorities and recommended next steps. The exact page coverage and deliverable format are agreed before the review.
Does the audit include AI-search visibility?
The review can cover accessible content, explicit service information, direct answers and appropriate structured data. These support a useful website but do not guarantee AI citations.
Do you need Search Console access?
Access helps assess indexing and search data. A public website review can still identify issues without it, but the report will state the limits of the evidence.
Will you implement the recommendations?
Implementation can be agreed separately, or you can use the action plan with your existing developer. The audit does not silently include an unlimited rebuild.
How long does an SEO audit take?
Timing depends on the website’s size, complexity and available access. I confirm the scope and expected delivery schedule before starting.
Technical audit checks: from access to page experience
The review distinguishes confirmed problems from observations and missing evidence. Each finding identifies the affected URL or template, its impact and a way to verify the fix.
Crawling and indexing
Inspect HTTP responses, redirect chains, robots directives, canonical signals and sitemap coverage. Check whether important pages are discoverable through normal internal links. An excluded URL is not automatically an error: its intended role matters.
Rendering and international pages
Compare delivered HTML with rendered content where needed. Review language routes and alternate-language relationships when translations are in scope. Flag conflicting signals rather than changing working URLs without a plan.
Performance and mobile use
Identify heavy resources, layout instability and interaction bottlenecks on representative templates. Distinguish laboratory measurements from real-user Core Web Vitals data; a single score does not describe every visitor.
How a finding becomes a useful action
Illustrative example: a key service page has a noindex instruction. First confirm that the page should appear in search, check the delivered and rendered instructions, and identify where the directive is set. The recommendation includes the affected URL, an implementation owner and a post-change check—not simply “improve SEO”.
A standard SEO review is not a penetration test, legal compliance certification or a guarantee of indexing. Server logs, private analytics and full-site coverage require the access and scope agreed before the audit.
Connect the audit to the next step
Technical access is one part of visibility. Use semantic analysis when content roles or customer questions remain unclear, and website architecture planning when navigation or a redesign needs a stronger structure.
Semantic analysis ↗
Map customer questions and search intent to distinct pages and content briefs.
SEO website architecture ↗
Plan the page hierarchy, navigation and internal links before a build or redesign.
YOUR NEXT STEP
Tell me what
you want to improve.
A new website, clearer service pages or better search visibility. Start with the goal; the right scope follows. We can discuss your project in Dutch, French or English.
Send a project enquiryContinue to the contact page to share your project.