What a proper SEO audit should fix first

A proper SEO audit should fix the things that stop the right pages being found, understood and used. That usually means indexing mistakes, weak page targeting, broken internal journeys, poor local signals, and missing measurement before it means polishing every low score in a report.

The practical test is simple. If we fix this issue, are we more likely to receive better enquiries, from the right people, through the right pages? Good SEO audit services help answer that question in order, so a business can act on what matters now and leave the rest for later.

What an SEO audit is actually for

An SEO audit is not a trophy document, a spreadsheet of warnings, or a list of everything a crawler can complain about. Its job is to help us decide what is blocking useful enquiries and what can wait.

That matters because many businesses come to us after receiving a report full of technical labels but very little commercial direction. They know something is wrong, but not whether the issue is serious, who should fix it, or whether it affects the pages that actually win work.

A proper audit should answer questions like these:

• Can search engines reach and index the pages we want to rank?
• Do those pages clearly match what potential customers are searching for?
• Is the site structure helping people move from first visit to enquiry?
• Are local signals strong enough for searches in Ipswich, Suffolk and the wider service area?
• Are we measuring the right actions, so we can tell whether changes improve real enquiries?

That is why we treat an audit as a decision tool, not just a diagnosis. The output should help a business choose between a focused repair, ongoing search work, a content rewrite, or a wider website improvement project.

It should also stop wasted effort. Not every issue in Google Search Console is a problem. Not every page needs to rank. Not every low performance score is holding back sales. Google’s own guidance is clear that excluded pages need investigation by reason, not blanket inclusion, because some exclusions are expected and correct (Google Page indexing report).

What a good audit should check

A good audit checks the whole path from discovery to enquiry. That does not mean producing hundreds of pages of notes. It means covering the main areas properly and linking them back to business goals.

Indexing and crawl control

First, we check whether search engines can access the right pages and whether the wrong pages are being indexed instead. This includes:

• robots.txt rules
• noindex directives
• canonicals
• XML sitemaps
• redirect chains and loops
• duplicate URL versions
• soft 404s and broken pages
• parameter and filter pages
• staging or development pages exposed by mistake

We compare what should be indexable with what actually appears in Google Search Console and search results. The aim is not “more indexed pages”. The aim is the right indexed pages.

Site structure and internal linking

Next, we look at how the site is organised. A business may have good services and useful experience, but if the structure is muddled, search engines and users both struggle to understand priority.

We check:

• whether each main service has a clear landing page
• whether pages compete with each other for the same search intent
• whether important pages are too deep in the site
• whether internal links use clear, descriptive language
• whether navigation helps a visitor move naturally from information to contact

Google’s starter guidance still points back to useful content and descriptive links, rather than tricks or guarantees (Google SEO Starter Guide).

Content quality and intent match

An audit should review whether the wording on key pages actually answers what a buyer needs to know. This is where many sites underperform.

We look for:

• service pages that are too vague
• pages targeting the wrong search intent
• missing location context
• duplicated or near-duplicated copy
• weak titles and meta descriptions
• missing proof, process detail or next steps
• blog content that attracts visits but no relevant enquiries

This is not only about keywords. It is about whether the page is useful, specific, and commercially aligned.

Local visibility

For businesses serving a defined area, local search often matters more than broad national traffic. A proper audit should therefore check:

• Google Business Profile completeness
• service categories
• consistency of business name, address and phone details where used
• local landing page quality
• review profile and how reviews support relevance
• map pack visibility for core searches
• local competitors with stronger signals

Google states that local ranking depends on relevance, distance and prominence, and that businesses cannot buy a better local position from Google (Google local ranking).

Where a business serves multiple counties, as many of our clients do across Suffolk, Essex, Cambridgeshire and Norfolk, the audit should distinguish between genuine local presence, wider service reach, and pages created only to chase location terms.

Usability and accessibility

Search performance and usability are closely linked. If a page is hard to use, slow to respond, or confusing on mobile, the problem is not only technical. It affects trust and conversion.

A sensible audit reviews:

• mobile layout and readability
• form friction
• call to action placement
• intrusive pop-ups
• contrast and legibility
• navigation clarity
• obvious trust gaps
• Core Web Vitals issues where they affect real use

Core Web Vitals are useful diagnostics for loading, responsiveness and layout stability, but a score alone does not prove commercial harm (web.dev on Core Web Vitals). Accessibility basics such as readable contrast, clear controls and understandable navigation also matter for real users (W3C accessibility tips).

Measurement and attribution

Finally, a good audit checks whether we can measure what matters. Many businesses have analytics installed, but not set up in a way that supports decisions.

We check:

• whether form submissions are tracked
• whether phone clicks and email clicks are tracked where relevant
• whether conversions are separated by type
• whether branded and non-branded search performance can be reviewed
• whether key landing pages are visible in reports
• whether consent settings or tag setup are obscuring useful data

Without this, even a strong audit can turn into guesswork.

Which problems matter first

The first priority is not the most technical issue. It is the issue most likely to block relevant traffic or stop it turning into enquiries.

We usually sort findings into four groups.

1. Critical blockers

These are issues that prevent the site or key pages from being discovered, indexed or used properly. Examples include:

• important service pages set to noindex
• incorrect canonical tags pointing elsewhere
• broken enquiry forms
• a site migration with major redirect failures
• duplicate versions of the site confusing indexing
• key pages removed without replacement

If these exist, they come first.

2. High value commercial fixes

These are not always dramatic, but they often have the clearest business effect. Examples include:

• rewriting a service page that ranks for the wrong intent
• separating merged services into clearer pages
• improving internal links to priority pages
• fixing a weak local landing page
• aligning titles and headings with actual buyer searches
• reducing steps between landing page and quotation request

These are often where useful enquiries improve fastest.

3. Important, but not urgent

This group includes worthwhile improvements that should be planned, not panicked over. Examples:

• tidying archive pages
• consolidating older blog posts
• refining schema markup
• improving image handling
• reducing minor duplication in support pages

Helpful, yes. First on the list, not usually.

4. Cosmetic or low impact defects

This is where many bad audits waste attention. Examples include:

• every excluded URL being treated as a fault
• every page needing a green score in every tool
• minor metadata length issues on low value pages
• isolated crawl warnings on pages that do not matter commercially

Google’s indexing documentation is especially relevant here. Excluded does not automatically mean broken. Some pages should be excluded, such as duplicates or pages intentionally blocked from indexing (Google Page indexing report).

The same principle applies to AI visibility. Existing search fundamentals still apply, and there is no special AI schema or text file required just to appear in Google’s AI features (Google AI features). So if an audit makes “AI readiness” sound like a separate mystery discipline, we would ask for specifics.

When a smaller change is enough

Not every business needs a full audit. Sometimes a smaller change is the right call.

A focused fix may be enough when:

• rankings dropped after a specific website change
• one service page is underperforming while the rest of the site is sound
• Google Business Profile visibility is the main issue
• tracking is missing, so performance cannot be judged
• a site has only a small number of core pages
• the business already knows the likely problem and needs confirmation plus implementation

For example, if a business has a five page brochure site and only one real service page, a full technical review may be excessive. A better first step could be rewriting that page, improving local relevance, and fixing the enquiry path.

Likewise, if the website is serviceable but the admin around leads is poor, the real bottleneck may be internal handling rather than search visibility. In those cases, a workflow improvement or workflow automation for repetitive admin may deliver more value than a large SEO project.

The same applies when the site itself is outdated in structure or messaging. If the findings all point to weak page architecture and unclear service communication, it may be better to plan website design and improvement for lead generation rather than repeatedly patching an unsuitable build.

A smaller change is not a compromise if it addresses the actual constraint.

How to brief and assess SEO audit services

If we are comparing SEO audit services, the brief matters. A vague request often produces a vague report.

A useful brief should include:

• what the business sells
• which services matter most
• target locations
• whether the aim is more leads, better quality leads, stronger local visibility, or diagnosis after a drop
• any recent site changes or migrations
• access available, such as Search Console, analytics and CMS
• known constraints, such as internal developers or platform limits

Then ask practical questions.

Questions worth asking a supplier

• What business goal will this audit help us decide on?
• Which pages or service areas will you prioritise?
• Will you review Search Console and analytics, or only run crawler tools?
• How will you separate urgent fixes from nice-to-haves?
• Will the recommendations include implementation detail?
• Who is the audit for, a developer, a marketer, or a business owner?
• Will you identify what does not need fixing?
• Can you explain how local visibility will be assessed?
• If content is weak, will you say whether the problem is structure, copy, intent, or all three?

Good answers are specific. Weak answers rely on jargon, proprietary scores, or promises.

Deliverables we would expect

A useful audit should normally include:

• an executive summary in plain English
• prioritised findings
• the reason each issue matters
• the likely effect if fixed
• affected pages or templates
• recommended action
• who should own it, such as developer, content editor, marketing lead or business owner
• notes on what can wait

Where relevant, it should also include example rewrites, page mapping, internal linking suggestions, or local visibility actions.

What we would avoid is a report that says things like “improve E-E-A-T”, “fix all technical errors”, or “create more content” without naming the pages, the problem, or the next action.

If AI search visibility is part of the discussion, the same standard applies. We should hear what content or structure changes are needed, not vague claims about being “optimised for AI”. For businesses exploring that area, our AI search visibility support sits alongside standard search fundamentals, not instead of them.

What to do after the audit

An audit only becomes useful when it turns into a realistic action plan.

We recommend taking the findings and turning them into a working list with five columns:

• issue
• priority
• owner
• dependency
• target date

That immediately shows whether the work belongs with a developer, content lead, office manager, marketing support, or leadership team.

For example:

• noindex on a key service page, developer, urgent
• rewrite main service page around buyer questions, content owner, high priority
• improve internal links from homepage and related pages, content or web owner, high priority
• fix form tracking in analytics, developer or analytics lead, medium priority
• review low value archive pages, lower priority

This step matters because many audits fail after delivery. The business agrees with the findings, then nobody owns the work.

We also recommend checking for dependencies early. A content rewrite may need service input from the owner. A technical fix may require hosting or CMS access. A local visibility task may need someone to verify or update the Google Business Profile. If those dependencies are ignored, the plan stalls.

Not every recommendation should be implemented at once. We would usually start with:

1. critical indexing or conversion blockers
2. highest value service pages
3. local visibility improvements
4. measurement fixes
5. wider content and structural improvements

If, after the audit, the main issue is a handful of corrections, we can quote for those specific changes. If the findings point to a broader rebuild, a clearer service structure, or ongoing search support, we can quote for that instead.

That is often the right point to ask us for a quotation through the Suffolk Web website. By then, the scope is clearer. We can see whether the job is a focused repair, ongoing search visibility and SEO support, a website improvement project, or a wider business process issue that affects lead handling after the enquiry arrives.

Suffolk Web is Fleeta Limited’s service site, based in Ipswich and working with businesses across Suffolk and the wider UK. Our approach is practical. We look at what is blocking useful enquiries, what can be fixed cleanly, and what should wait. Where a simple change is enough, we say so. Where the findings point to a broader job, we set that out in plain English.

That same practical approach runs through the wider work around Vytautas Pipiras, Logivo.AI, Jagelo Haulage, Fleetalyse and Seonis. The point is not to produce more diagnostics than a business can use. It is to identify what matters, assign it properly, and move from report to action. If you want us to review the problem and quote for the next step, send the brief through our website contact or project form.