Homepage: Is public information separated from private data?

What this homepage needs to accomplish

Understand the business and choose a useful first action. The relevant information includes company name, core offer, actual service coverage, direct project discussion and free assessment alternative.

A visitor can mistake an assessment for a required purchase or overlook a direct project inquiry when every option has equal visual prominence.

Run the specific check

Inspect public output and review authorized data mappings where available. Identify customer messages, internal notes, credentials and administrative fields that should not be included in public payloads.

• Begin with direct project discussion. Record the current value or behavior and identify its approved source.
• Compare free assessment alternative with the page's purpose: understand the business and choose a useful first action.
• Start from an unfamiliar visit, choose the offer that fits, and follow its primary action without relying on saved preferences.
• Apply the public-data boundaries check to this route, keeping a direct arrival separate from a visit with saved context.

Choose the repair and its completion condition

Restrict sensitive data at the appropriate system boundary and verify the published result. State private-access checks as unverified when the necessary authorized evidence is unavailable.

Retest direct project discussion and the route described above after publication. Keep any untested private system outside the completion claim. A pass on this task does not automatically verify the other responsibilities of a homepage.

A related Benchmark example or explanation

The link below is a current website example. Use it to explore the relevant feature, scope or evidence. It is not proof that the hypothetical homepage in this guide has passed this check.

• See Benchmark's current homepage