Skip to content

SEO Audit & Action Plan

SEO audit services for service businesses

Know what to fix first.

I review your website and turn the findings into a prioritised SEO action plan, with evidence, affected pages and clear steps for implementation.

If you have a crawler report full of warnings, service pages that are hard to find, or traffic that rarely becomes an enquiry, I’ll help you understand what needs attention and why.

Discuss your website audit ↗

Ali Pourgholi · For English-speaking service businesses worldwide

Branded illustration of a website inspection with a magnifier and action checklist.
A closer look at the pages, technical signals and customer journey.
Watch the reasoning · Ahrefs

See how a technical finding is investigated.

In this Ahrefs tutorial, Sam Oh checks real websites for technical problems, including how different domain versions redirect. It is a useful introduction to following the evidence instead of treating a tool’s output as the final answer.

The recording is older, so it is background on the reasoning, not a current interface guide or the full scope of this service. My audit also reviews your service-page purpose, internal links and enquiry journey.

Ahrefs · Sam Oh · 8:12 · Tutorial and transcript · Watch on YouTube

Start with your business

Which website problems are getting in the way?

An electrician trying to grow charger installations needs to know whether the relevant service page can be found, explains the work clearly and makes requesting an estimate straightforward. A growing crawl score answers only part of that question.

I start with your priority services, the customers you want and the changes your team can realistically make. That gives the audit a useful direction before I open a crawler.

A useful brief starts here

  • Which services and markets matter most?
  • What feels wrong with the current website?
  • Who will implement the recommendations?
What I review

Six areas, one practical action plan

We agree the depth and coverage before work begins. The review connects technical checks with the content customers use to choose your business.

Can the right pages be found?

I check crawl paths, indexability, status codes, redirects and canonical signals on the agreed URLs and templates. I compare crawler findings with Search Console evidence where access is available.

What you receive
Affected URLs, the evidence and the intended indexable destination.

Does each service page earn its place?

I review page purpose, search intent, titles, headings and overlap. A service page should explain the work, answer buying questions and give customers a clear next step.

What you receive
Page-specific recommendations: improve, clarify, combine or investigate.

Do the important pages connect?

I follow navigation and contextual links to see how people reach your services. I look for broken destinations, isolated pages and links that send visitors to an unsuitable page.

What you receive
A focused internal-link and redirect task list with valid destinations.

Can someone enquire on a phone?

I review the mobile journey, readable content, image behaviour and contact route. Performance findings are tied to affected templates and available field or lab evidence.

What you receive
Reproducible usability findings and checks for the proposed fixes.

What does the available data support?

With access, I review search queries, landing pages and enquiry tracking. I distinguish visibility from relevant visits and recorded enquiries, and flag gaps in measurement.

What you receive
A dated baseline, data limitations and the questions we can answer.

Can the next person act on it?

I turn confirmed findings into scoped tasks. Each task explains the issue, why it matters, what needs changing and how the finished work should be checked.

What you receive
A prioritised action plan your developer, writer or team can use.

Evidence before edits

A warning needs a decision behind it.

I check whether a finding is current, reproducible and relevant to the pages that matter. Related symptoms are grouped so your team can see the underlying work instead of receiving the same problem several times.

Canonical signals, for example, need to be reviewed alongside redirects, internal links and the intended page. Google’s canonicalisation guidance explains the signals involved.

Act first
Confirmed obstacles affecting important pages or enquiries.

Plan next
Supported improvements to content, structure or usability.

Investigate or monitor
Findings that need more evidence before a change is justified.

Branded illustration of audit evidence organised into a prioritised action board.
Evidence → a decision → a task your team can act on.
From my own work

Sometimes the page’s role is the problem.

When rebuilding Mason Electric’s service pages, I worked on thin service content that had been sitting in the blog. I rewrote it as service pages, moved the URLs with 301 redirects and reworked the homepage structure to connect the services.

That experience informs how I review a site: I look at where a page belongs, what job it does and how people reach it. I do not assume that adjusting its title or adding more words will solve a structural problem. I explain the service-area page decisions in my service-area SEO notes.

I apply the same judgement to crawler reports on my own site. A short utility page or several useful H2 headings should be assessed in context. The recommendation needs to improve the page, not simply remove a label from an export.

Branded illustration of website findings moving through fixes to a checked action plan.
A clear handoff includes the fix and the check that follows it.
Your deliverables

Leave with work your team can start.

I prepare a findings register and a sequenced action plan in the format agreed for the project. You can see the decisions, dependencies and open questions without having to interpret a raw export.

  • Evidence: affected URLs or templates, what I observed and when.
  • Recommendation: the proposed change and the reason for it.
  • Priority and dependencies: what should happen first and what needs input.
  • Handoff: the role needed to carry out the task and a clear acceptance check.
  • Limits: sampled areas, missing data and issues needing deeper investigation.

Where several pages share a template problem, I identify that relationship so your developer can address the source of the issue.

Performance in context

Make the website easier to use.

I review slow or unstable pages alongside the actual mobile journey: reading the service, opening navigation and reaching the contact form. Available field data and repeatable lab checks help explain where the problem occurs.

Google recommends looking at the overall page experience. Strong Core Web Vitals scores do not guarantee rankings, so I use performance evidence to guide useful improvements rather than promise a result from a perfect score. Google’s page-experience guidance sets out that distinction.

A clear scope

Agree the work before the audit starts.

Send your website, priority services and the questions you need answered. Tell me about a recent redesign, migration or drop in enquiries, and whether your team already has a crawl or analytics report.

I confirm the pages and templates to review, the available data, deliverables, fee and delivery date. Read-only access is usually the right starting point for search and analytics accounts. You keep ownership and grant access through account invitations.

This is a diagnostic and planning service. Development, full content rewrites, server-log analysis, link outreach and ongoing SEO management need their own agreed scope. If a finding depends on that work, I explain the dependency in the plan.

If your priority is local service pages and coverage, see Local SEO & Service Pages. You can also review the full service list before sending your brief.

Before we begin

Questions about your SEO audit

Which issues need action now?

I prioritise confirmed problems affecting important service pages or the enquiry journey: for example, an unintended indexing block, a broken destination or a contact route that fails. I weigh the evidence, business importance, dependencies and effort. A crawler’s warning colour alone does not decide the order.

What access do you need for the audit?

I can start with your public website and business goals. Read-only access to Search Console and analytics makes the review more useful. Some checks may need additional information from your developer or host. Use account invitations with the necessary permissions; do not send passwords in the contact form.

Is implementation included?

This service covers the audit and action plan. Development, page rewrites and other implementation work are included only if they are explicitly listed in the proposal. I can scope that work separately or prepare a handoff for your existing team.

Can you use my existing Screaming Frog report?

Yes. Send the export and the crawl date, configuration and scope if you have them. I verify important findings against the current site, combine related issues and explain which warnings need action. An old crawl or an incomplete export may need a fresh check.

Will you review every page on my website?

We agree coverage before work starts. A small site may allow a complete URL review; a larger site usually needs template checks, selected page reviews and a crawl of the agreed scope. The report states what was checked, what was sampled and what could not be verified.

What if Search Console or conversion tracking is not set up?

I can review the public site, but I will identify the limits of that evidence. Historical search performance cannot be recreated by installing tracking today. I can recommend the setup needed to establish a useful baseline, with implementation scoped separately.

How is this different from a technical SEO audit?

This review connects technical findings with service-page purpose, internal links and the route to an enquiry. If the problem is already clearly technical and needs deeper specialist investigation, I will explain the scope required before quoting. The deliverables will identify any work that needs further investigation.

How much does an SEO audit cost, and how long does it take?

I quote after seeing the website, its size, the relevant templates and the questions you need answered. Access, migrations, multiple markets and the depth of investigation affect the work. Your proposal specifies the fee, coverage, delivery date and review arrangements before the audit begins.

What will my developer receive?

A findings register and sequenced task list with affected URLs or templates, supporting evidence, the recommended change, dependencies and a verification step. Where a decision needs your input, I label it clearly so implementation does not begin on an assumption.

Does every short page or repeated heading need changing?

No. A contact page, archive and detailed tutorial serve different purposes. Multiple H2 headings can form a useful page structure. I check whether content answers the page’s purpose and whether repeated headings cause confusion or duplicated page intent. I do not add filler to reach a word-count threshold.

Can you guarantee better rankings after the audit?

No. An audit identifies problems and opportunities; it does not control search results or competitors. I define checks for implementation and agree how to monitor the available search and enquiry data. A completed fix and a later performance change are separate observations.

How do we verify the fixes afterwards?

Each actionable finding includes a check, such as revisiting the affected URL, testing its redirect, inspecting the indexability signals or repeating the mobile contact journey. A follow-up implementation review can be included in the scope. Search Console’s indexed information and live test answer different questions, so I record which evidence is being used.

Tell me what feels wrong with your website.

Share your website, the services you want to grow and any reports you already have. Tell me who will handle the fixes. I’ll review the request and suggest a practical next step.

Send your project details ↗

Prefer email? me@alipourgholi.com

Discuss this service ↗

Tell me about your project

Share a few details so I can understand your business and suggest the right next step.

What would you like help with?
Not sure yet — help me choose

Your details are used to review and respond to your project request.

Prefer email? me@alipourgholi.com