Free Website Marketing Audit Checklist for a Clear Baseline

Use this free website marketing audit checklist to build a bounded public-evidence baseline, not to score the entire business. Review identity, audience, offer, proof, user paths, search foundations, performance, content, and competitive context. Label every item as observed, calculated, inferred, unavailable, or not measured. Then convert only supported findings into research questions and priorities.

A public website cannot reveal private analytics, CRM records, revenue, budgets, customer sentiment, operational capacity, or every competitor. Add those sources before making material strategy decisions. First clarify the scope with website audit versus marketing audit, then use the complete AI marketing audit framework for the broader method.

Prepare the audit record

Create one row for every observation:

Field	What to record
Check	The specific question asked
URL or scope	Exact page, template, domain, device, or path
Evidence	Page text, element, response, screenshot, or provider result
State	Observed, calculated, inferred, unavailable, or not measured
Date	When the evidence was retrieved
Interpretation	Why it might matter, clearly separated from fact
Confidence	High, medium, or low with a short reason
Next step	Verify, research, change, test, defer, or accept
Owner	Person responsible for the next decision

Do not begin with one health score. A score can hide missing evidence and imply that unrelated checks are interchangeable.

1. Identity and public profile

• Confirm the public business name and primary domain.
• Record the one-sentence description visible on the homepage.
• Identify the stated audience, market, and geography, if any.
• List the primary product, service, or offer presented.
• Note whether contact, legal, privacy, and company information are findable.
• Flag conflicts between the homepage, product pages, metadata, and footer.
• Mark ambiguous identity or offer language as inferred, not fact.

The output is a public identity draft. Ask an authorized stakeholder to correct it before using it in strategy or generated content. The domain-first intelligence guide explains why the site is useful but incomplete evidence.

2. Audience, problem, and offer

• Name the specific audience described on the page.
• Capture the problem or job the offer claims to address.
• Record the mechanism or approach, without adding unstated capabilities.
• Identify the primary call to action and expected commitment.
• Note prerequisites, qualification language, exclusions, or conditions.
• Check whether adjacent pages describe the same offer consistently.
• Write down important customer questions the page does not answer.

Do not infer demand or willingness to pay from clear copy. Validate the audience and job with customers, prospects, sales evidence, and market research.

3. Claims and proof

• List objective product, performance, comparative, and outcome claims.
• Link each claim to visible substantiation, if present.
• Check that qualifiers are near the claim and do not contradict it.
• Separate testimonial attribution from company-wide evidence.
• Record dates and scopes for statistics or benchmark claims.
• Flag vague superiority language for legal and editorial review.
• Identify claims repeated in metadata, headings, and calls to action.

FTC guidance expects a reasonable basis for objective advertising claims before they are made. A disclaimer cannot reliably repair a headline that creates a contradictory impression.

4. Journey and conversion paths

• Identify primary entry pages and visible next actions.
• Follow navigation from question to evidence to action.
• Test forms, buttons, contact paths, and confirmation states manually.
• Check whether the commitment matches the information provided.
• Review mobile layouts and keyboard navigation for obvious barriers.
• Note trust, privacy, error, and expectation-setting language.
• Record hypotheses about friction without inventing conversion impact.

A public walkthrough can reveal broken or confusing paths. It cannot establish conversion rate, lead quality, or revenue impact without valid first-party measurement.

5. Search and technical foundation

• Confirm important pages return an intended status.
• Verify that primary navigation uses crawlable links.
• Review titles, descriptions, headings, and visible main content.
• Check canonical and indexing signals for consistency.
• Locate sitemap and robots controls where relevant.
• Look for duplicate intents and unclear internal anchors.
• Record rendering differences that affect content or navigation.
• Disclose crawl depth, page limits, blocked pages, and failures.

This is a first-pass checklist, not a complete technical audit. Use the technical SEO audit guide when search discovery, indexing, rendering, or site architecture owns the decision.

6. Performance and experience evidence

• Test representative pages on mobile and desktop.
• Record lab environment, URL, time, and tool.
• Check for CrUX field data at the relevant URL or origin scope.
• Keep lab diagnostics and field experience in separate fields.
• Record Core Web Vitals scope, period, and percentile when available.
• Treat missing field evidence as unavailable, not zero or perfect.
• Use diagnostic opportunities as hypotheses for testing.

PageSpeed Insights documentation explains that Lighthouse lab data and CrUX field data answer different questions. A passing or failing lab run does not by itself establish the experience of all users.

7. Content usefulness and internal paths

• Assign one audience and search or journey job to each important page.
• Check whether the page answers the question promised by its title.
• Identify unsupported repetition, filler, or conflicting statements.
• Verify that useful next pages are linked with descriptive anchors.
• Check authorship, responsibility, dates, and update needs where relevant.
• Note pages that collide in intent and need clearer boundaries.
• Avoid judging usefulness from word count alone.

Google recommends creating helpful, reliable, people-first content. AI assistance is not itself the issue; content created primarily to manipulate rankings can violate spam policies.

8. Competitor and alternative context

• Write the priority buyer, job, and trigger.
• List direct rivals, adjacent solutions, substitutes, and status quo separately.
• Capture current public audience, offer, mechanism, and proof from dated sources.
• Distinguish search rivals from commercial alternatives.
• Ask sales or customers which options actually entered decisions.
• Remove candidates supported only by surface similarity.
• Keep aspirational peers in a separate learning set.

Use the competitor validation process before accepting positioning conclusions. Public pages are evidence of visible claims, not verified customer choice.

9. Evidence gaps and private follow-up

Create a gap list instead of filling blanks with assumptions:

• Search Console queries, pages, countries, devices, and indexing evidence.
• Analytics events, journeys, segments, and measurement quality.
• CRM stages, lead quality, cycle time, and sales evidence.
• Customer interviews, support themes, win-loss notes, and objections.
• Product usage, retention, commerce, or service-delivery evidence.
• Budgets, margins, capacity, approvals, and legal constraints.
• Server logs or specialist technical evidence where required.
• Paid media, lifecycle, partner, or other channel evidence in scope.

“Not measured” is a valid status. It tells the team what would need a separate workflow and prevents false completeness.

10. Prioritization and handoff

• Group duplicate observations into one finding.
• State affected audience, page, journey, or decision.
• Rate impact, confidence, reach, effort, dependency, and reversibility.
• Separate quick verification from implementation work.
• Assign one accountable owner.
• Write an acceptance test for completion.
• Define an outcome measure without promising causation.
• Record what is deferred and why.

The audit-to-actions workflow helps teams move from findings to an owned backlog. The planned website marketing audit template can later provide a reusable worksheet, but its mapped route should not be assumed published until editorial release.

Optional Alesta starting point

Alesta can seed several public-evidence modules in this checklist: editable identity and offer context, rendered homepage observations, a bounded technical and same-origin page sample, mobile and desktop PageSpeed diagnostics, CrUX where available, and likely competitor candidates for review. Its Product Information and Marketing Strategy documents give reviewers a place to correct inferences and carry supported findings forward.

The team must still perform or supply private and human work. Customer interviews, Search Console, analytics, CRM, revenue, budgets, operational constraints, manual journey testing, claim approval, and implementation ownership are not established by the public baseline. Alesta also does not turn this one-time checklist seed into recurring monitoring or automatic execution. The Alesta home route provides current product context.

Completion test

The audit is ready for review when every material finding has a source, scope, state, interpretation, confidence, next decision, and owner. It is not complete merely because every box is checked. A skipped, unavailable, or inapplicable check should remain visible so the team understands the boundary of the baseline.