Blog
SEO audit: turning findings into priorities
An SEO audit examines how a site can participate in search and turns observations into improvement decisions. A useful result identifies confirmed problems, affected pages and ways to verify a fix. An automated score without that context offers little help in choosing what to do first.
Set the scope
For an initial small-business review, identify page types such as the homepage, services, individual offers and articles. Select examples from each template and add URLs important to bookings or enquiries. This sample may reveal shared problems, but it does not establish that the whole site has been reviewed.
Record the date, tool and scope. When comparing Search Console performance, preserve the periods, search type, country, device and filters. Google recommends breaking down traffic drops before assigning a cause. A seasonal decline needs a different response from accidental exclusion from the index.
Prioritize by observed consequences
Imagine a pottery studio. Its public booking page carries noindex; two articles have unclear titles; an older informative image lacks alternative text. These are hypothetical findings, not the results of an actual site audit.
| Confirmed finding | Initial decision and verification |
|---|---|
| Accidental noindex on a public booking page | Review the exclusion first; then confirm that the published response permits indexing |
| Two titles that do not describe their articles | Rewrite them to match the content; check the published titles |
| Informative image without alternative text | Describe its information; review the reading experience and final attribute |
That proposed priority depends on the booking page actually being intended for search. If it is a private confirmation page, exclusion may be correct. Confirm the purpose and scope with the site owner before changing any rules.
Order work by the observed consequence, the importance of the affected pages and the ability to verify the repair. This editorial method organizes tasks; it is not an official Google formula or a forecast of the traffic a fix will generate.
Separate symptoms, hypotheses and evidence
“Clicks fell” describes a symptom. “There is an indexing error” is a hypothesis requiring evidence. Check whether impressions, queries or pages changed, then inspect the relevant URLs. The Search Console performance report supports those filters, subject to aggregation limits and omitted queries.
For a technical finding, save the relevant response or screenshot alongside the expected behavior. “The course listing links to a URL returning 404” gives someone a reproducible issue. “Improve technical SEO” does not specify a verifiable fix. The follow-up should open that link, confirm the correct destination and check whether the same problem affects its template.
Keep a register someone can act on
Use one row per finding: URL, evidence, consequence, proposed action, owner and validation. Distinguish findings awaiting confirmation from confirmed or fixed ones. Assigning a task does not resolve it.
Adapt this SEO audit register CSV. Its four hypothetical rows reproduce the cases above, with a separate row for each title. They await confirmation so you can use them as investigation records without mistaking the example for an executed audit. The validation field asks for an observable check rather than a promised date for ranking recovery.
After a repair, record the date and repeat the check. Assess search outcomes with comparable data while considering other factors. A server delivering the page again establishes a technical repair. Attributing more bookings to it requires evidence of that outcome. The final report should make clear what was verified, what remains a hypothesis and what decision comes next.
Plan your next post in HeyMark.
Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.