Service detail

An SEO audit you can actually use.

Find the evidence, separate the priorities and leave with a next action someone can carry out.

01 / Service detail

Check the starting condition

Choose by the actual obstacle and readiness. A different or smaller intervention can be the appropriate result.

Fit, reason to wait and a useful alternative
Decision	Condition
Explore this scope when	A decline, inherited site, redesign or competing priority needs evidence before a decision.
Pause or choose another scope when	The issue and bounded fix are already known, or the necessary coverage/data cannot answer the question.
Before commissioning work	Agree the named output, supported platform, responsible role and a testable finish line. No purchase, account access or live action is authorized by reading this page.

Work through the earlier decision

02 / Service detail

Agree the diagnostic boundary

Define the pages, priority offers, markets, systems and questions before starting. A public-site review sees different evidence from one with approved search and analytics access. Missing access should be a stated limitation, not filled with guesses.

03 / Service detail

Follow the discovery path

Review the relevant crawl and indexing behavior, intended canonicals, redirects, page structure and internal links. A technical observation needs its URL, evidence and impact explained; a tool warning is not automatically a business priority.

04 / Service detail

Judge a complete finding

Hypothetical planning specimen. It explains the decisions and checks to agree; it is not a completed customer deliverable or a fixed offer.

Hypothetical audit specimen; no live fix is claimed
Field	Finding
URL / intended state	/service/ is an example public service page intended for discovery.
Observed evidence	A dated fetch shows a noindex directive; retain the reproducible source and environment.
Interpretation / confidence	High confidence in the directive, but confirm the page intent. Lost sales are not established.
Priority / consequence	Resolve if it conflicts with approved intent; assess dependencies and business usefulness before ordering work.
Recommended action / owner	Release owner reviews and removes only the unintended directive under an approved scope.
Verification	Re-fetch live source/rendered metadata and observe search processing separately; no index/rank guarantee.
False positive	Noindex may be correct on private, staging or confirmation pages.

What a useful SEO audit should include

05 / Service detail

Set the coverage and access limits

Use this local worksheet to record the scope and unresolved decisions. Use roles and fictional examples, without credentials or private records.

Use roles and hypothetical examples. These fields stay in this page; no information is submitted or saved.

Domains, URL/template sample and markets

A sample audit is not a review of every URL.

Public-only versus approved first-party read-only evidence

List unavailable systems as blocked/Unknown.

Business decision the audit should support

Decline, inheritance, redesign or competing priorities.

Walkthrough, recommendation owner and implementation boundary

Findings are not automatic live fixes.

SEO strategy and roadmaps

06 / Service detail

Map pages to customer questions

Compare the purpose of each important page with the actual offer and buyer question. Look for missing answers, confusing overlap and weak links between guides, services and the next action.

Clear words that help customers decide

07 / Service detail

Prioritize findings so work can begin

Evidence: The page or system checked, observation, method and limitation.
Priority: Why this matters to a customer or search discovery, with risk and dependency.
Action: A concrete change, an implementation owner and a way to verify it.

08 / Service detail

A report is different from implementation

Agree whether delivery includes a walkthrough, developer handoff, implementation or later verification. A useful diagnostic should not hide a dependency on an unquoted ongoing service.

How it works

09 / Service detail

Agree the inputs, effort and boundary

Use these work variables to compare a written scope. They are not a price list, payment policy or authorization to purchase tools, media or services.

Scope preparation and cost drivers
Buyer question	Scope answer to agree
What will I receive?	A dated coverage record, reproducible priorities and walkthrough
What do I need to supply?	Website, business decision, priority offers/markets, changes, available read-only data and implementer
What changes the effort and cost?	URL/template sample, stack/rendering, first-party evidence, markets/languages and manual depth
What needs separate scope or is excluded?	Automatic production fixes, a keyword-volume forecast, guaranteed recovery and a mandatory ongoing contract
How will completion and support be defined?	Identify the reviewer, actual test evidence, known limits and handover. Any recurring allowance, fees, cancellation and response arrangement need their own written terms.

To keep the deliverable and finish line reviewable: Review the acceptance and handover checkpoints

Scope and pricing

10 / Service detail

Start with the search question

Name the site, priority offers, actual markets and concern. If an internal team will implement changes, include that handoff in the scope. Prepare a local brief, then choose whether to email the details.

Tell us what you need