We audit your website, fix it, or build it correctly from the ground up.

WebTrustEngine examines your live website, your site archive or your local files. It brings the technical findings, the measurement gaps and the work to be done together in one place. The result is reporting leadership can decide on and an improvement plan your technical team can actually carry out.?Measurement status is a separate indicator from the score: it states how many checks could be measured. Detail

Explore the audit service · Read the product guide

Live URL, ZIP and local-folder input · Executive report with technical annexes · Optional controlled improvement

Choose the starting point that fits your need

I want to know the condition of my website

See which problems come first, where further measurement is needed and which jobs your technical team can pick up straight away. Assess your current site, its state before a redesign, or the files your agency delivered.

Website audit and reporting

I want the problems on my existing site fixed

Turn findings into work that can be carried out. The applicable fixes are prepared on a separate working copy; you review the changed files, the re-measurement results and the rollback records together.

Improving an existing site

I want to develop a new website

Start from static site candidates built on your brand and content material. Review the page structure, the design and the technical readiness together, and settle the content migration, the integrations and the launch work up front.

New website design and development

What you have at the end of the audit

A decision brief for leadership. We gather the site's current condition, the priority findings, the measurement gaps and the recommended order of work into one narrative, so you can see the basis for allocating resources.

Actionable work for the technical team. Each finding reads as one unit: the affected pages or files, the observation behind it, the suggested action and the condition for retesting. We keep problems that spread through a shared template separate from one-off fixes.

Evidence you can inspect. We record which input, method, environment and date produced each result. Where the reporting flow allows it, we bind the Word and PDF documents, the technical records and the delivery-verification data to the same piece of work.

A way to judge what changed. We place the next audit alongside the earlier state with a comparable scope. Closed findings, new problems and the areas that could not be measured all stay visible.

Audit your website across domains that complete each other

In the report we collect the topics in this table under the 10 domain headings further down this page. Which measurements actually run depends on the selected scope, the input, the tools and the data provided. The full feature index, the methods and the prerequisites live in the product guide.

Read the capabilities and their operating conditions

How the work proceeds

1. We set the goal and the scope. Together we define the site address or the files, the purpose of the assessment, the page limit and the required measurements.
2. We run the audit. The engine executes the applicable checks and records both the findings and the measurement gaps.
3. We translate the results into decision language. We report the site assessment, the priorities, the need for further review and the technical work.
4. We prepare the selected improvements. Where they are in scope, we apply the applicable SafeFix operations on the working copy; the remaining work goes into the relevant team's implementation plan.
5. We measure the change again. We examine the effect of the fix and any regressions. Applying it to the live site and the decision to publish remain the responsibility of the authorised team.

If the fix scope is agreed at the outset, the engine can apply the applicable operations within the same run after the first analysis and re-check them before the final report.

From one finding to finished work

Suppose a form field is missing its accessible name. The audit points to the affected page and to the element itself. The technical team sets the right label; the re-check then assesses whether that same element meets the expected condition. Where more is needed to show that the form can be completed, the keyboard and assistive-technology tasks are examined separately as well.

Every technical sub-check is assessed together with the scope of the user task it belongs to.

Control over your data and your changes

WebTrustEngine works local-first. An offline ZIP or folder audit works only from the files you supply. Active security testing requires written authorisation and a separate scope document. The data requirements of any external services and additional measurements you choose are settled along with the scope.

A standard audit changes no source file. When you select SafeFix, we prepare the edits on a separate working copy. Decisions about content, design, integrations and going live stay with the people responsible for them.

What you may want to know before starting

Can a site that is not live yet be audited?

Yes. A file-level audit can run from a ZIP or a local folder. Live server, redirect and link behaviour is measured separately, once a suitable production or preview environment is available.

Does the audit fix every problem automatically?

Analysis and fixing are separate scopes. SafeFix can prepare the supported edits on a working copy once the information it needs is supplied. Content, infrastructure and application-development work is planned separately.

How should a high score be read?

Read a score together with the model used, the scope actually measured and the open findings. We show the areas that could not be measured, and the human judgements the remaining risk requires, separately.

How long does it take, and how is it priced?

Site size, the number of languages, the measurement scope, data preparation and the implementation needed determine the work plan. Duration, fees, support and delivery terms are settled on that scope.

Choose your first step

To learn where you stand, start with the audit scope. If you already hold a list of findings, look at the improvement process; if you are building something new, look at the design and development scope.

See the audit scope · See the improvement process · See the new-site scope

A website is now a human storefront plus a machine surface.

The page a visitor sees is simultaneously the input of dozens of automated readers. A page flawless for humans can carry missing headers, broken schemas and unclear identity signals for machines.

Even with great design, machine readability can be weak. Visual redesign projects rarely touch the meta layer, security headers or structured data; the site looks new while its audit surface stays old.