Website Rating Template

In plain language: Identifies the evaluator and the website owner by their full legal names, states the purpose of the rating, and records the date the evaluation was commissioned.

Common mistake: Identifying the evaluator by trade name rather than registered legal entity — if a dispute arises over findings, the contracting party must match the entity that provided the service.

In plain language: Defines exactly which pages, subsections, and functions of the website were included in the rating and lists any areas that were explicitly excluded.

Common mistake: Leaving scope undefined so the client later claims the audit should have covered the entire site — including sections the evaluator never accessed or agreed to assess.

In plain language: Sets out the specific criteria being scored, the rating scale used (e.g., 1–5 or 0–100), the weight assigned to each criterion, and the source standards referenced.

Common mistake: Using a rating scale without defining what each score level means — a score of 3 out of 5 is meaningless without a rubric describing what distinguishes a 3 from a 2 or a 4.

In plain language: Documents scores for load speed, mobile responsiveness, uptime, security (HTTPS, SSL), and Core Web Vitals measurements taken at the time of evaluation.

Common mistake: Recording a single snapshot measurement for load speed without noting the testing tool, geographic location, and device type — results vary significantly across these variables.

In plain language: Records the evaluator's assessment of navigation clarity, content accuracy, readability, call-to-action effectiveness, and user experience against the agreed criteria.

Common mistake: Combining objective findings (broken links count) with subjective opinions (design is outdated) in the same scored criterion without distinguishing them — conflating the two undermines the document's credibility in a dispute.

In plain language: Documents whether the website meets applicable legal requirements including cookie consent, privacy policy, accessibility standards, and jurisdiction-specific disclosures.

Common mistake: Checking for the presence of a privacy policy without verifying its content covers the data types the website actually collects — a policy that doesn't match real data practices is a compliance deficiency.

In plain language: Calculates the composite score across all criteria using the agreed weights and assigns an overall rating category — for example, Excellent, Satisfactory, Needs Improvement, or Non-Compliant.

Common mistake: Presenting a final score without showing the calculation — if a client disputes the result, an undocumented score has no audit trail to defend.

In plain language: Lists each deficiency found, the criterion it failed, the recommended corrective action, and a suggested priority level (critical, high, medium, or low).

Common mistake: Including remediation items in the findings without assigning priority — a client who sees 30 issues with no urgency signal will likely deprioritize all of them.

In plain language: Confirms the evaluator has no financial interest in the outcome, that findings represent conditions at the time of evaluation only, and limits the evaluator's liability to the fee paid for the rating.

Common mistake: Omitting a liability cap entirely — without one, a client could argue that a missed compliance finding caused regulatory fines and seek damages far exceeding the evaluation fee.

In plain language: Records that both parties have reviewed and accepted the findings, identifies the governing jurisdiction, and provides signature blocks for both evaluator and client.

Common mistake: Having only the evaluator sign and treating the document as a unilateral report — without the client's signature, disputes about whether findings were communicated and accepted are much harder to resolve.

A website rating document is a formal written evaluation that scores a website against defined criteria — covering technical performance, usability, content quality, and legal compliance — using a structured methodology and weighted scoring system. It is used by agencies, auditors, and consultants to deliver defensible, signed findings to clients or internal stakeholders, and serves as a record of the website's condition at a specific point in time.

A formal, signed website rating is appropriate when findings will be used to support a contractual obligation — such as a web development agreement milestone sign-off — when compliance findings must be documented for regulatory purposes, when a third-party evaluator is being paid to deliver an objective assessment, or when procurement decisions will be based on the evaluation scores. Informal internal reviews are sufficient for routine monitoring, but any evaluation with legal or financial consequences should use a signed document.

For the rating to function as a legally accepted document — confirming the client received and acknowledged the findings — signatures from both the evaluator and the client are generally recommended. Without a client signature, there is no documented evidence of acceptance, which complicates payment disputes, scope disagreements, and any subsequent liability claims. The evaluator's signature alone is sufficient only when the document is intended as a unilateral internal report with no contractual consequence.

A complete website rating typically covers four categories: technical performance (load speed, uptime, mobile responsiveness, SSL), content and usability (navigation, readability, accessibility, CTA effectiveness), legal and regulatory compliance (GDPR cookie consent, privacy policy, WCAG accessibility level, required disclosures), and SEO fundamentals (meta tags, structured data, crawlability). The relative weight of each category should be agreed with the client before evaluation begins.

Each criterion is assigned a weight reflecting its relative importance, expressed as a percentage of the total score. The evaluator scores each criterion on an agreed scale (typically 1–5 or 0–100), multiplies each score by its weight, and sums the results to produce a composite score. The composite score is then mapped to a rating category — such as Excellent, Satisfactory, Needs Improvement, or Non-Compliant — as defined in the rating schedule. Showing this calculation in full is important for auditability.

Yes, in many contexts a signed website rating can serve as contemporaneous documentary evidence — for example, to show that a web developer delivered a non-compliant site, that a vendor's website failed to meet contracted performance standards, or that a company was aware of an accessibility deficiency at a specific date. The document's value as evidence depends on how clearly scope, methodology, findings, and signatures are documented. Consider engaging a lawyer when the rating is intended for litigation or regulatory proceedings.

A website audit is a broad investigative process — it identifies issues, analyses root causes, and may be informal or internal. A website rating is a formal scored evaluation that produces a documented, defensible assessment with a composite score, signed acceptance, and remediation recommendations. Audits inform ratings: you conduct the audit work, then formalise the findings in a rating document when the output needs to be legally or contractually significant.

The rating document itself is not regulated, but the compliance criteria it assesses are governed by law. WCAG accessibility requirements are mandated for public sector websites in the US (Section 508), UK, and EU, and are increasingly required for private sector sites under disability discrimination law. GDPR and ePrivacy rules apply to cookie consent and data handling assessments for any site accessible to EU users. Evaluators should clearly reference the applicable legal standard for each compliance criterion and note the jurisdiction in the governing law clause.

For websites with active legal compliance obligations — such as healthcare, financial services, or e-commerce sites handling personal data — an annual formal rating is a reasonable baseline, with an additional review any time the site undergoes a material redesign or change in data collection practices. For websites subject to ongoing service-level agreements, a quarterly or semi-annual rating aligned to contract milestones is common. A rating more than 12 months old should not be relied upon as evidence of current compliance.