Sample report

Example audit report

This is a complete sample report for a fictional local plumbing business, brightleafplumbing.com. It shows exactly what AuditScout returns for any URL — scores, the fixes that matter most, full sections, a 30-day plan, and a prompt you can paste into Claude or Cursor.

This is a sample report. Real reports vary based on the website scanned.

Run your own audit
78

Overall score

82
64
74
71
69
80
85
77
73
66

Executive summary

brightleafplumbing.com is a solid, credible local plumbing site with a strong SEO and mobile foundation — it loads reasonably fast and reads well on a phone, which is where most of its visitors are. The biggest opportunities are in security headers, conversion, and proof. A few common HTTP headers are missing, the homepage doesn't give mobile visitors a clear primary action, and customer reviews live only on third-party sites. None of these are emergencies, but together they cap how many of today's visitors turn into booked jobs. The fixes below are ordered so the cheapest, highest-impact changes ship first.

Who this website helps

This site serves homeowners and small property managers in the Boca Raton service area who need fast, trustworthy plumbing help — often during an emergency. The visitor is usually on a phone, comparing two or three local options, and deciding in seconds whom to call. Everything in this report is judged against that single goal: turning an anxious, ready-to-act local visitor into a booked job.

Top 3 recommended fixes

  • high

    Add a Content-Security-Policy header

    No CSP was detected. A baseline policy reduces exposure to script injection and clickjacking.

  • medium

    Add FAQ schema markup

    Your FAQ content isn't marked up as structured data, so search and AI engines can't surface it as direct answers.

  • medium

    Strengthen the above-the-fold CTA

    The phone number is the only action on first paint. A clear primary button (e.g. 'Book a visit') would lift conversion.

Full audit sections

Every dimension gets its own breakdown: what's working, what isn't, why it matters, and exactly how to fix it.

SEO

Growth82/100

Strengths

  • Unique, descriptive title tags on every key page.
  • Clean URL structure and a valid XML sitemap were found.
  • Service pages target clear local intent (e.g. 'emergency plumber Boca Raton').

Problems

  • Several service-page meta descriptions are missing or duplicated.
  • Six images on the homepage have empty alt attributes.
  • No internal links from blog posts back to core service pages.

Strong on-page SEO is how local customers find you on Google before they ever see a competitor. Small gaps here quietly cap how much traffic the site can earn.

Recommended fixes

  • Write a unique 150–160 character meta description for each service page.
  • Add descriptive alt text to all content images.
  • Link blog posts to the matching service page using keyword-rich anchor text.

AEO — Answer Engine Optimization

Growth66/100

Strengths

  • An FAQ section exists on the homepage with real customer questions.
  • Headings are phrased as questions visitors actually ask.

Problems

  • FAQ content is not marked up with FAQPage structured data.
  • Key answers are buried mid-paragraph instead of stated up front.
  • No concise, quotable summary near the top of service pages.

Answer engines like ChatGPT and Perplexity lift short, clearly-structured answers into their responses. Pages that answer the question directly — and mark it up — are far more likely to be pulled into an AI answer.

Recommended fixes

  • Add FAQPage schema to the existing FAQ block.
  • Lead each service page with a one- or two-sentence direct answer.
  • Phrase headings as the questions customers search for.

GEO — Generative Engine Optimization

Growth66/100

Strengths

  • A real business name, address, and license number appear site-wide.
  • Organization details are consistent across pages.

Problems

  • No Organization or LocalBusiness schema to define the entity for LLMs.
  • Thin About page gives generative engines little to cite.
  • No outbound citations or case studies to signal authority.

Generative engines decide which sources to name. Clear entity data and credible, well-referenced content make it far more likely an LLM understands your brand and cites it as a source.

Recommended fixes

  • Add LocalBusiness/Organization schema with NAP and service area.
  • Expand the About page with the team, history, and credentials.
  • Publish 2–3 detailed case studies with real outcomes.

Security (passive)

Important64/100

Strengths

  • HTTPS is enforced and the TLS certificate is valid.
  • HSTS header is present with a reasonable max-age.

Problems

  • No Content-Security-Policy header was returned.
  • X-Frame-Options / frame-ancestors not set, leaving the site open to clickjacking.
  • Server version is exposed in response headers.

These are public, passive observations — the kind any visitor's browser can see. Closing common header gaps is cheap insurance against routine automated attacks and builds visitor trust.

Recommended fixes

  • Add a starter Content-Security-Policy header and tighten it over time.
  • Set X-Frame-Options: DENY (or a frame-ancestors CSP directive).
  • Suppress detailed Server / X-Powered-By version headers.

AuditScout performs passive public checks only. It does not replace a professional penetration test, security audit, legal review, or compliance assessment. No exploits, login attempts, brute force, or intrusive testing are performed.

Performance

Important74/100

Strengths

  • HTML response is fast and gzip/brotli compression is enabled.
  • Fonts load with font-display: swap, avoiding invisible text.

Problems

  • Two hero images are served uncompressed at full resolution (~1.4 MB combined).
  • A large render-blocking stylesheet delays first paint on mobile.
  • No lazy-loading on below-the-fold gallery images.

Most local visitors arrive on a phone, often on cellular. Every extra second of load time measurably increases the share of people who leave before the page is usable.

Recommended fixes

  • Compress and serve hero images as WebP at the displayed size.
  • Inline critical CSS and defer the rest.
  • Add loading="lazy" to below-the-fold images.

Mobile UX

Growth85/100

Strengths

  • Layout is responsive with no horizontal scroll on common phone widths.
  • Body text stays readable at 16px and up without zooming.

Problems

  • The header phone number isn't a tap-to-call link on mobile.
  • Two footer links sit closer than the 44px recommended tap target.
  • The hero CTA falls below the fold on shorter phones.

The majority of local visitors are on a phone. Small tap targets and a buried call action cost easy conversions from people who are ready to act.

Recommended fixes

  • Make the phone number a tel: link and keep it visible in the header.
  • Increase spacing so all tap targets are at least 44px.
  • Pull the primary CTA into the first mobile screen.

Accessibility

Growth77/100

Strengths

  • Semantic landmarks (header, nav, main, footer) are used correctly.
  • Most interactive elements are keyboard reachable.

Problems

  • Six images are missing alt text.
  • Two form fields rely on placeholder text instead of a real label.
  • A couple of light-grey text blocks fall below the WCAG contrast minimum.

Accessible sites reach more people, reduce legal risk, and tend to rank better — accessibility and SEO overlap heavily. These fixes are quick and widely beneficial.

Recommended fixes

  • Add descriptive alt text to every content image.
  • Pair each input with a visible, associated <label>.
  • Darken low-contrast text to meet at least 4.5:1.

Conversion

Important69/100

Strengths

  • Phone number is visible in the header on every page.
  • Service area and hours are stated clearly.

Problems

  • No primary call-to-action button above the fold on mobile.
  • The contact form asks for nine fields, including ones most visitors will skip.
  • No reassurance near the form (response time, no-obligation quote).

Traffic only pays off when visitors take the next step. A clear, low-friction action turns the same number of visits into measurably more booked jobs.

Recommended fixes

  • Add a prominent 'Book a visit' button in the hero on every device.
  • Cut the contact form to name, phone, and a short message.
  • Add a one-line trust note next to the form ('We reply within 1 business hour').

Trust

Growth71/100

Strengths

  • Physical address, license number, and phone are present in the footer.
  • An SSL padlock and clear business name reinforce legitimacy.

Problems

  • Customer reviews live only on third-party sites, not on the page itself.
  • No team or 'about the owner' content to humanize the business.
  • No recent activity (blog, updated dates) to signal the business is active.

For a local service business, trust is the deciding factor. Visible proof — real reviews, a real face, clear credentials — is what tips a hesitant visitor into a customer.

Recommended fixes

  • Embed 3–5 recent customer reviews directly on the homepage.
  • Add a short 'Meet the team' section with a photo.
  • Show recently completed jobs or updated content to signal activity.

Business strategy

Growth73/100

Strengths

  • Clear, focused service offering with defined geographic coverage.
  • Seasonal/emergency services create repeat-demand opportunities.

Problems

  • No email capture or lead magnet to nurture visitors who aren't ready to call.
  • Pricing guidance is absent, so price-sensitive visitors bounce.
  • No content targeting high-intent 'near me' and question searches.

The site is a marketing asset, not just a brochure. Capturing leads, setting price expectations, and answering real questions compounds into steady inbound demand over time.

Recommended fixes

  • Offer a simple 'Get a free estimate' email capture.
  • Publish a transparent 'What things cost' guide for common jobs.
  • Write 4–6 FAQ-style articles around the questions customers actually ask.

Investor / pitch angle

Beyond the fix list, AuditScout frames how the site reads to a partner, lender, or acquirer. For brightleafplumbing.com, the strongest angle is a focused, license-backed local operator with repeat emergency demand and an obvious, under-exploited path to recurring revenue (maintenance plans and email nurture). The site already signals legitimacy; the growth story is converting more of its existing local traffic and capturing leads it currently lets slip — a low-cost, high-leverage improvement that a buyer or investor can underwrite with confidence.

Priority fixes

The whole report distilled into three buckets — fix the critical items first, then work down.

Critical

  • Add a baseline Content-Security-Policy header.
  • Set X-Frame-Options / frame-ancestors to prevent clickjacking.

Important

  • Add an above-the-fold 'Book a visit' CTA on every device.
  • Compress hero images to WebP and lazy-load below-the-fold images.
  • Make the header phone number a tap-to-call link.

Growth

  • Add FAQ schema and lead pages with a direct, quotable answer.
  • Add LocalBusiness/Organization schema and expand the About page.
  • Embed real customer reviews and add a comparison/case-study page.

30-day upgrade plan

A realistic, sequenced plan — cheapest, highest-impact changes first.

Week 1

  • Ship a starter Content-Security-Policy and X-Frame-Options header.
  • Suppress server version headers.

Week 2

  • Compress hero images to WebP and add lazy-loading below the fold.
  • Inline critical CSS and defer the rest.

Week 3

  • Add an above-the-fold 'Book a visit' CTA and trim the contact form.
  • Embed 3–5 customer reviews on the homepage.

Week 4

  • Add FAQ + LocalBusiness schema and write the first two FAQ articles.
  • Set up a free-estimate email capture, then re-run the audit.

Copy/paste upgrade prompt

Paste this straight into Claude or Cursor to start shipping the fixes.

Copy/paste upgrade prompt

Upgrade this website based on the audit below. Work through the high-severity items first, keep the existing design language, and explain each change as you make it.

SITE: brightleafplumbing.com
OVERALL SCORE: 78/100
SUB-SCORES: SEO 82, Security 64, Performance 74, Trust 71, Conversion 69, Content 80, Mobile 85, Accessibility 77, Business 73, AEO/GEO 66

TOP FIXES:
1. [HIGH] Add a Content-Security-Policy header — none detected; start permissive, then tighten.
2. [MED] Add FAQ schema markup — mark up existing FAQ content as structured data.
3. [MED] Strengthen the above-the-fold CTA — add a clear "Book a visit" button on every device.

SECONDARY:
- Compress hero images to WebP and lazy-load below-the-fold images.
- Trim the contact form to name, phone, and message.
- Embed real customer reviews directly on the homepage.

Apply these changes file by file and show me the diffs.

Want this for your own site?

Run a real audit on any URL in seconds — no login required for your first one.