Frame the question
Collect and compare evidence
Prioritize decisions
Assign and verify the work

Give the audit a question it can answer

Start with an observable concern. Important service pages may not appear in search. Nonbrand inquiries may have declined after a redesign. People may reach the site but misunderstand the offer. These are different questions, and they require different evidence.

Write down when the concern began and what else changed around that time. A new website, a revised service, seasonal demand and a change in measurement can all affect the picture. The audit should investigate competing explanations rather than automatically blaming the most recent design decision.

Define the expected output before the work begins. A focused investigation may be more useful than a comprehensive review when the problem is narrow. Conversely, a business planning a major site change may need an inventory and risk assessment that goes beyond the immediate symptom.

Use the right evidence for each part of the question

Search Console can show search impressions and clicks, while website analytics describes a different part of the visit. Sales records and staff feedback may be needed to understand inquiry quality. None of these sources alone supplies a complete account of how marketing affects the business.

Google's documentation explains that search metrics have specific counting and aggregation rules. A reported average position is not a permanent rank that every person sees. Compare relevant groups and periods rather than treating a single number as a diagnosis.

Ask for access that is necessary to the agreed question and make missing evidence visible. A public review can inspect pages and observable technical behavior, but it cannot see private account history or determine whether the business responded to a lead. The deliverable should explain those limits.

Review the site in meaningful groups

Group pages by their job and how they are built. Main service pages, product categories, individual products and editorial resources may each have different patterns. A template problem can affect many URLs; a weak explanation may affect one commercially important page.

Check whether the site gives each group a useful place in navigation and internal links. Then review whether its content matches the question the visitor needs answered. An indexable page can still be unhelpful, and a persuasive page can still be difficult to discover.

Technical checks should support the audit question. Crawl access, indexing preferences, redirects and metadata can be relevant, but the presence of a warning does not establish its business priority. Record the affected examples and explain the consequence before recommending a change.

Investigate a traffic decline without guessing its cause

Google's traffic-drop guidance identifies several possible causes, including technical issues, changes in demand, ranking changes and measurement anomalies. It recommends examining the pattern and the affected pages or queries. The practical lesson is to narrow the problem before proposing a broad rewrite.

Consider an illustrative situation where a site's clicks fall after a seasonal peak. If the relevant demand also changed, rebuilding the page may not address the reason. In another hypothetical case, a decline limited to one template after a release may justify investigating that template first. Neither pattern proves its cause by itself.

Keep the timeline and comparison consistent. Changing filters, periods or page groups between screenshots can make an apparent explanation unreliable. If the data is too limited for a confident conclusion, state the uncertainty and identify what further evidence would help.

Assess page usefulness and unnecessary overlap

Read important pages as a potential customer. Can the reader tell what the business offers, who it serves and what happens next? Are material claims supported? Does the page provide an answer beyond what another page on the same site already explains?

An audit should consider consolidation as well as creation. Several location or keyword variants may compete for the same editorial purpose without helping different audiences. Compare their actual content and observed intent before deciding whether to retain, combine or retire them.

Do not turn a keyword list into a mandatory publication list. A new page needs a defensible job, a source of useful information and a place in the site. Sometimes the better recommendation is to improve an existing explanation rather than create another thin destination.

Ask for a finding that can be acted on

A useful finding has a clear structure: the observed issue, an example, its likely impact, the proposed action, the responsible person and a completion check. Mark the confidence level in plain language. A confirmed broken destination and an untested content hypothesis should not look identical in the report.

For example, an illustrative finding could document that a service link leads to a retired page and identify the intended replacement. The repair can then be verified by following the link and checking its destination. 'Improve internal linking' alone leaves too much of the decision to the implementer.

Prioritize by impact, confidence and dependencies. A sitewide exclusion affecting important pages may need attention before minor metadata edits. A content change may depend on the business approving a new service description. The order should help the team complete useful work, not just close the easiest items.

Separate the assessment from implementation

The agreement should say whether the audit ends with recommendations or includes implementation. If another developer or content team will make changes, give them enough detail to work without reconstructing the investigation. Clarify who can approve code, copy and page removals.

Request a follow-up against the original evidence when work is included. A new overall score is less informative than confirmation that the specific problem was corrected. Keep unresolved items and deferred recommendations visible so the business knows what remains.

An audit also has a useful lifespan. Major platform changes, a new product structure or a substantial content rollout may require new checks. Repeating the same broad review on a fixed schedule is not automatically valuable when no relevant change or unresolved concern justifies it.

Prepare for a Dappr audit discussion

Bring the website, the business concern, recent change history and any earlier reports. Identify the pages and customer actions that matter most. If the concern relates to inquiry quality, include a non-sensitive description of the patterns staff are seeing.

Scope and cost depend on the site's complexity, the available data, the depth of investigation and whether repairs are included. Dappr's plans can provide context, but an audit quote should still explain the actual deliverable. No ranking increase, recovery date or fixed commercial outcome is promised.

The result should leave the business with fewer unresolved decisions: what is known, what should be investigated next and which work is worth doing. That is a stronger basis for an SEO engagement than a report designed primarily to make the site look alarming.

Questions before you begin

What is the difference between an SEO audit and technical SEO?

An audit assesses evidence and prioritizes decisions across an agreed scope, which may include content, intent, measurement and technical behavior. Technical SEO focuses more specifically on how the site supports discovery, indexing and reliable page delivery. Either engagement may or may not include implementation.

Can an audit explain a traffic drop with certainty?

Not always. Several factors can change at the same time, and available data may be incomplete. A useful audit separates confirmed findings from plausible explanations and recommends the next evidence check instead of assigning a confident cause without support.

Do we need to give access to every account?

No. Access should match the audit question. Search Console, analytics and business outcome data answer different questions. A public-only review can still be useful, but its conclusions should state what could not be verified without private history.

Will every audit recommendation require a new page?

No. Some findings call for a repair, clearer content, consolidation or no change. A new page should be justified by a distinct customer need and useful information, not merely by a keyword variation.

What should we receive at the end?

Ask for prioritized findings with examples, evidence, recommended actions, owners and completion checks. Confirm whether implementation and follow-up are included. The report should make the next decisions easier rather than leave the business with an unexplained list of warnings.

SEO audit services