Evidence, explained clearly

How Greg's website audits work.

An SEO and AEO website audit turns website evidence into a prioritized plan. Greg checks how clearly search engines, local listings and selected AI answer tools can understand a business, documents what he finds and explains what to improve next.

  1. 01Describe the problem
  2. 02Confirm the evidence
  3. 03Review the website
  4. 04Prioritize the findings
  5. 05Receive the report

Start with the questions you need answered

We’ll agree on the pages, evidence and areas to review before work begins. The quote will explain the scope, deliverables and timing.

An audit can be a focused first look or a deeper review. You can also bring existing recommendations and discuss help with implementation.

Clear evidence boundaries

Greg checks what can be verified.

Public evidence

No account access required.

A review can use public pages and business information without access to analytics, Google Search Console or the website’s content management system.

Agreed evidence

Useful private data, when available.

Our initial discussion identifies whether private sources would answer an important question. Access, scope and responsibilities are agreed before those sources are used.

What the review covers

Connected checks, not a generic score.

The review follows the evidence available within the agreed scope. Findings are explained individually so an owner can see what was checked, why it matters and how confident the recommendation is.

01

Search foundations

Page titles, descriptions, headings, internal links, crawl signals and other technical basics that help search engines find and interpret useful pages.

02

Content clarity

Whether important pages clearly explain the business, services, location, audience and next action in language customers can understand.

03

Local visibility

Public location, service-area and business information that should remain clear and consistent across the website and relevant profiles.

04

AI-answer observations

Dated prompts in selected AI answer tools, including whether the business, a competitor or neither appears and which public sources are visible.

05

Competitor context

A relevant comparison that shows where another business presents clearer, more complete or easier-to-verify information.

06

Practical next steps

Recommended content, structured data and technical changes, separated into work an owner may handle and work that may need specialist help.

The five-step process

From request to useful report.

The process keeps the scope visible, the evidence traceable and the recommendations tied to a practical decision.

  1. 01

    Share your website and the problem.

    Send an inquiry with your website and what you want to understand or improve. I’ll follow up to discuss the work.

  2. 02

    Confirm the scope and evidence.

    We’ll confirm the pages, available evidence, deliverables and timing. I’ll provide a quote before you decide to go ahead.

  3. 03

    Inspect, compare and document.

    Greg records the relevant page evidence, checks the connected SEO and AEO questions and compares a relevant competitor where included. Observations are kept separate from assumptions.

  4. 04

    Prioritize the work.

    Findings are ordered by their importance to visibility, clarity and the customer journey. The report distinguishes meaningful foundations from optional refinements so the next step is not buried.

  5. 05

    Deliver the report and recommend what comes next.

    You receive the report and guidance set out in the quote. Findings explain the evidence, priorities and recommended next steps; implementation help can be discussed separately.

What an audit can establish

A clearer baseline, not a guaranteed outcome.

An audit can document the current public evidence, identify gaps, establish selected search and AI-answer observations and recommend improvements. It cannot guarantee rankings, traffic, leads, sales, AI mentions or citations because those outcomes also depend on competitors, platforms, customer behaviour and future changes.

After delivery

The report belongs to you.

Use the recommendations yourself, share them with your existing developer or discuss future implementation support with Greg. Ongoing review can be discussed once there is a baseline and a clear reporting scope.