How scans and reports work

Enter your website address, read the results and use them to plan your next steps. After making changes, scan again to check the outcome.

How it works

From a URL to your next check

  1. 1

    Enter the website address

    Use the public URL of a website you own or are authorized to check. No admin password or plugin is needed.

  2. 2

    Run the scan

    TrustyRunner performs the checks included in your plan, within the scan’s acquisition limits.

  3. 3

    Read the results

    The report groups the findings, explains their meaning and suggests where to start.

  4. 4

    Make the relevant changes

    Review the findings with whoever maintains the website. The technical guides on DigitalBanzai help you investigate and make changes.

  5. 5

    Check the website again

    Run a new scan after an intervention. Registered lets you keep reports; automatic response-time comparison belongs to Light, which is coming soon.

Facts, suggestions and incomplete checks

An observed result describes a response, configuration or content collected during the scan. A suggestion proposes something to check or change; a possible cause is not a confirmed diagnosis. An incomplete check lacks the information needed for a conclusion.

Addresses excluded from automatic exploration

TrustyRunner does not follow recognized action URLs, such as add-to-cart or logout links. It also skips typical WordPress sign-in and administration paths and recognized editor or preview parameters discovered in links or sitemaps. These exclusions do not mean the site has an error or the plan allowance is exhausted.

The report retains the observed links and their sources within the detail limits. Check those links: ordinary navigation should lead to public content. An explicit starting address can still be examined if it is not an action URL; an address reached through a redirect can also remain in the results. A name such as “thank-you” or “login” alone does not prove a page’s purpose, so it does not trigger a general exclusion.

Why some checks remain incomplete

An incomplete check does not establish a site error. The reason shown beside the result applies to that check or navigation path, not the entire scan.

Limit reached

The scan can stop acquiring pages when it reaches a limit on pages, addresses, navigation depth or the amount of content read. When available, the result identifies the limit.

What to do: To revisit a specific page, start a new scan from its address. The scan starts there, but can also explore other pages on the same site; the same limits apply.

Path not explored

A page found through the sitemap can be examined without following its links. This is an exploration rule, not an exhausted allowance.

What to do: To check a destination that was not visited, start a new scan from that address.

Site response

The site denied access, did not respond in time or returned an error. This does not establish that the whole site is down.

What to do: Try again later. If access is repeatedly denied, ask the site manager to check access rules, a firewall or anti-bot protection. A login requirement is another possible cause: do not remove protection from private pages.

Insufficient data

The information needed to complete the check was unavailable, and this result does not identify the cause.

What to do: Repeat the scan. If the same check remains incomplete, contact support with the check name and scan date. This result alone does not justify changing the site configuration.

Shortened list

The report shows only some of the addresses found. Counts of shown and omitted entries refer to this list, not to pages that were left unchecked.

What to do: Use the listed addresses to investigate the result. An address missing from this list does not tell you whether it was checked.

Not all these cases depend on your plan.

Start with your website

Free works without registration. Use TrustyRunner on a site you own or are authorised to check.

Start a free scan