Illustrative example — not a scanned customer website

What a report explains

This shortened example shows the style and limits of the £29 report. The findings below are invented for illustration. No website was assessed to create this example, and these findings are not claims about your site.

Example finding: no meta description detected

Observation: The homepage HTML did not contain a meta description recognised by the scanner.

Why it may matter: A clear description can help communicate what a page offers. Search engines may choose different text for their results; adding one does not guarantee a ranking or traffic improvement.

Practical steps

  1. Open your homepage’s SEO or page settings.
  2. Write a concise description of the page’s actual purpose.
  3. Publish it and check the public HTML contains a description meta tag.

Verify: Re-run the check after publication. If the site renders metadata dynamically, ask your developer to inspect what search engines receive.

Example finding: image alt attributes need review

Observation: Some image elements in the returned HTML did not have an alt attribute.

Why it may matter: Useful alternative text can convey informative images to people who cannot see them. A missing attribute needs review, but attribute presence alone does not prove good accessibility.

Practical steps

  1. Identify which images convey information.
  2. Add meaningful alternatives for informative images.
  3. Use an empty alt attribute for genuinely decorative images.
  4. Review the page with appropriate accessibility tools and human checks where needed.

Verify: Inspect the published markup and review the content in context. This scanner cannot judge whether the text is suitable.

Example finding: HSTS header not detected

Observation: The homepage response did not include a Strict-Transport-Security header.

Why it may matter: HSTS can instruct compatible browsers to prefer HTTPS for a hostname. Absence is not proof of an exploitable vulnerability.

Practical steps

  1. Ask your developer or host whether HSTS is appropriate.
  2. Check certificates, renewal and HTTPS redirects first.
  3. If appropriate, start cautiously and validate the behaviour before extending the policy.

Caution: Avoid enabling long durations, all subdomains or preload without assessing the consequences.

Illustrative AI Security & Exposure Review

Example observation: A homepage references a possible AI assistant widget in a public script URL. This is an invented example, not a finding about a real website.

Suggested review: Ask the website operator to confirm the widget provider, its data-handling settings and access controls.

Not assessed: Prompt injection, private endpoints, model permissions, API keys, data retention and exploitability.

Limitation: A public indicator does not establish a vulnerability. No AI system is accessed or tested.

What the paid report contains

The emailed report includes an indicative score, summary, recommended next steps for detected issues, verification advice and scope limitations. Guidance depends on the checks that found issues. A page that passes every assessed check may have few or no recommended actions; it has not been certified secure, accessible or fully optimised.

The paid report adds explanations and practical guidance to the same homepage checks offered free, plus a passive AI-related indicator review. It is not a whole-site crawl, AI penetration test or human consultancy review.

Run a free homepage check · Read the 14-day money-back guarantee