Website SEO Audit
Find what is stopping important pages from doing their job
An SEO audit looks for concrete problems, explains the evidence, and separates issues that affect important pages from items that can wait. It is a diagnosis, not the same scope as fixing everything it finds.
An audit should answer a business question
Start with the pages you expected to perform a job, such as showing up for a product or helping someone discover a specific service. Explain when the trouble started and what you already checked. That gives the investigation a baseline. Looking at a small set of consequential pages first often gives you a better decision than a report of every automated warning the scanner can produce.
From finding to a decision you can approve
A practical scope identifies the problem, the evidence, and the test that would confirm a change.
- Identify a priority
Connect the affected page or template to what you need it to do. Explain why that problem matters to the business.
- Verify the cause
Report what was checked, what evidence supports the conclusion, and where owner access or additional testing is still needed.
- Choose the repair
Set out the next action, the person or system that owns it, and what will count as passing the verification.
Ask how each finding was verified
Useful evidence might be a tested URL, a reproducible redirect or index instruction, or an owner report that confirms which version of a page was selected. Distinguish a confirmed issue from a plausible explanation. If only the public site was available, note which questions still need owner access. A useful audit should tell you what you can know now and what you should test next.
Put findings in the order you can act on them
Identify which problems block a critical page, which confuse people or systems, and which can wait. State the affected URLs or page patterns, where a change would happen, and how to recheck it. If a problem is repeated across a template, document the pattern so you do not have to pay for separate page-level fixes when one shared change can address the issue.
Use the audit to choose whether to repair, rewrite, or wait
A crawl restriction, a missing explanation, and an outdated listing require different kinds of work. Decide who can make each change, whether a staged test is needed, and what evidence would be enough to mark the item resolved. If the site has already moved, bring redirects and old URLs into the review before assuming a whole new site is necessary.
Ask about the pages you cannot find
Bring one important URL, what you expected to see, and when the problem appeared. You can run the free MJM page scan first to capture a starting point.
Start with the pages that matter
Identify pages customers need to find. Review their discoverability through links and sitemaps, their index settings, canonical choices, and what happens when the URL is loaded.
Separate a symptom from its cause
A missing search result does not by itself prove a technical problem. Compare signals across public pages, site settings, and Search Console data where available, then explain what was verified and what is uncertain.
Turn findings into a decision list
Identify where each issue occurs, why it matters, what a fix would involve, and how to check whether it worked. A list of hundreds of warnings is less useful without that context.
What to bring
Bring the site address, examples of pages you expected to see in search, and any relevant migration history or access to owner reports.
Common questions
Is the audit the repair?
No. The assessment identifies and prioritizes problems. Fixing them and verifying the changes can be scoped separately.
Can anything be checked without a login?
Public pages and links can be reviewed without access. Some questions about search visibility, indexing, and traffic need owner data.
Tell us what you want to do
Bring a goal, a website address, or the problem you are trying to solve.
