Improving a ScamAdviser trust score: audit the signals you control

What does ScamAdviser consider about a website?

Quick test: Open your site as a stranger. Can you find the company name, an address and a contact within 10 seconds?

ScamAdviser assesses websites using public signals connected to the domain and the site. The review can cover domain age and registration data, hosting location, SSL, site content, contact details, business registration, blacklist information and user reviews.

That means a low or uncertain score is not necessarily explained by one visible page or one technical issue. Our first task is to map the signals we can inspect to the information your project publishes, then separate a correctable gap from a factor your team cannot change immediately.

During the review, we look for practical inconsistencies such as:

• A site that uses HTTPS inconsistently, or has certificate or redirect issues.
• Missing or difficult-to-find company identity, contact information, terms or privacy policy.
• Business details on the site that do not match the information you provide.
• Content or links that appear risky, outdated or unrelated to the project.
• A blacklist entry that may describe a different domain or an outdated status.

The useful outcome is a prioritized list, not a promise based on a single score. For the broader context of platform visibility and profile work, see promotion on platforms and listings and verification.

How we audit your domain and visible trust signals

We compare what a visitor can see on your website with the domain and business information you supply. This gives your team a grounded view of which gaps to correct before asking ScamAdviser to review the site again.

To start, share the main domain, any active subdomains relevant to the project, the preferred company name and contact details, and links to current legal or business records. Tell us about recent domain moves, ownership changes, hosting changes or security incidents if they affect the site. Access to a domain registrar or hosting account is not required for an initial review; changes that need account access are completed by your team or an authorized provider.

We check whether the site loads consistently, whether its SSL certificate is present and usable, whether redirects lead to the intended destination, and whether key information is easy to locate. We also compare visible business details across the pages and documents you provide. If something appears inconsistent, we identify the exact page or record and suggest a correction rather than drafting a vague list of general recommendations.

The result is a written, ordered set of findings: urgent technical hygiene, missing or conflicting trust information, and items that need supporting evidence. We also flag any point that should be checked by your legal, security or domain administrator before changes go live.

Trust signals your project can improve

The project can improve the accuracy, accessibility and consistency of the information it controls. We help turn the audit findings into concrete website changes and evidence for issues that need review outside the site.

Depending on the audit, the work may cover:

• SSL and technical hygiene: identify certificate, redirect or mixed-destination issues for your technical owner to correct.
• Company identity: make the project or operating entity clear and consistent across relevant pages.
• Contact details: publish a usable, monitored contact route and check it is not hidden behind broken links.
• Business information: align the site with the registration or company details you can substantiate.
• Legal pages: review whether privacy policy and terms are present, accessible and relevant to the service described.
• Site content: locate outdated, risky or unrelated material and recommend removal or correction.

We provide specific suggested edits and a verification checklist; your team approves changes to legal, corporate and technical claims. When a blacklist entry appears mistaken, we assemble the relevant evidence and prepare a correction request through the appropriate channel. We do not alter records on your behalf without authorization or present unverified claims as fact.

For projects also managing public review profiles, Trustpilot profile and reputation management can complement this work. Keep the same company name, contact route and service description across both destinations.

What follows the fixes and the review request

Common mistake: Hiding company details. Show who runs the site, where and how to reach them.

Once the agreed corrections are live, we check the public-facing pages again, organize the supporting evidence and request a ScamAdviser re-check. The point of the follow-up is to confirm that the submitted information is coherent and to record what is visible after the platform has reviewed it.

A typical engagement moves through a clear sequence: first, the domain and requested materials are reviewed; next, the team receives prioritized corrections; then your authorized owners publish the approved updates; finally, we verify the live pages and prepare the re-check request. The elapsed time is shaped by how quickly the project can confirm company details, implement technical changes and provide any supporting records.

You receive a concise report that records:

• The domain and public pages reviewed.
• The issues identified and the agreed corrective actions.
• Which changes were confirmed on the live site.
• The materials submitted with the re-check request.
• The score or status visible when we complete the follow-up.

This record helps your team distinguish completed work from items still awaiting a decision or further evidence. If you need help coordinating the wider platform work, our platform promotion overview can help you identify complementary channels without mixing unrelated visibility goals into this remediation.

How should a project ask users for reviews?

A review request should invite genuine users to describe their own experience, without scripting a favorable conclusion. Clear, voluntary feedback gives prospective visitors context and helps your project maintain a transparent public profile.

Before asking for reviews, confirm that the product or service is available and that the request reaches people who have actually used it. Keep the message neutral: explain where to leave feedback, what kind of experience is useful to describe, and how the project handles support concerns. Do not ask people to repeat specific phrases, hide negative feedback, or suggest that a positive review is required to receive assistance.

For a Web3 team, it is useful to prepare a small set of materials before making requests:

• A short explanation of the service and the relevant user journey.
• A direct link to the correct review destination, checked on desktop and mobile.
• A support contact for users who want help before or after leaving feedback.
• A simple internal process for responding to questions and correcting factual errors.

We can review the wording and the surrounding site information so the request is consistent with your published business details. Where reviews are involved, Trustpilot profile and reputation management is a separate service; it does not replace corrections to domain, SSL, business or website information.

Your 7-point trust signal checklist

Walk through these 7 points before you ask for a re-check. Each is a public signal that a reviewer or a visitor can verify in seconds.

• Confirm the domain is renewed for at least 1 year.
• Check that SSL is valid and not expiring soon.
• Show company name, address and contact on every page.
• Add privacy and terms pages.
• Check hosting and server location are consistent.
• Remove broken links and old copy.
• Save a dated record of every fix.

Terms in one line

SSL certificate means the file that makes a site load over a secure connection.

Remediation: fixing the issues behind a low score.

What can and cannot change in a review

Our work improves the accuracy and completeness of the public information submitted for review; ScamAdviser makes its own assessment. The score is calculated by ScamAdviser and cannot be bought, and a young domain gains trust with time, so a corrected site does not guarantee an immediate or particular score.

For the project, the practical decision is to proceed when the domain and business facts are clear enough to verify and the website owner can implement the necessary changes. If a record is disputed, gather supporting documents before requesting a correction; if technical ownership is unclear, identify the person who controls the registrar, hosting or certificate before planning implementation. This avoids submitting a request that relies on claims the project cannot substantiate.

Send 3 things: your domain, your company details and the contact for registrar changes.

How it works

1. Share the domain and project detailsSend the main website, project description, current company identity and any relevant ScamAdviser page. Include recent domain or site changes that may help explain inconsistencies.
2. Review public signalsWe inspect the site and compare visible technical, contact, business and content information with the records you provide. You receive findings in priority order.
3. Confirm and implement correctionsYour authorized owners review suggested edits and make approved changes. We identify what needs technical, legal or business-owner input before publication.
4. Verify the live site and prepare evidenceWe check that agreed updates are visible and assemble supporting material for any correction request or ScamAdviser re-check.
5. Submit and reportWe request the re-check and record the visible outcome, completed actions and any remaining items for your team.