What should an SEO audit actually tell you?

Agree what is being examined

Record the website, important services, target audience and languages. Distinguish a small public-page review from an audit with authorized access to Search Console, analytics and the content system.

• Can important pages load and be crawled?
• Are redirects, canonicals, robots rules and sitemaps consistent?
• Does each page answer a distinct user need?
• Can visitors read, navigate and understand the next step on a phone?

Ask for evidence and priorities

Each finding should include the affected URL, the observation, likely impact and a proposed correction. Prioritize availability and access problems before cosmetic scores. Keep assumptions separate from measured data.

• A finding is specific enough for a developer or editor to reproduce.
• The recommended change has an owner and a way to verify it.
• High effort is not automatically high value.
• A failed data connection is recorded as unavailable data, not zero traffic.

Verify changes after implementation

Keep the starting observations and compare the same pages after the work. Technical checks can confirm a repair quickly; changes in search performance need time and context. An audit cannot guarantee rankings.