Workflow Path & Form Proof

Your scan generates two proof scores. Together they show whether a visitor can easily find the next step and whether a form is likely to be completed.

Each failing check deducts points from the 100-point Path Proof score.

• −30
  Navigation not detectedThe scan could not find a <nav> element in the page HTML. Without visible navigation, visitors have no map of where they are.

  Fix: Add a static <nav> element. Sites using JavaScript-injected menus should verify the script loads correctly.
• −30
  No call-to-action foundThe page has no visible button or link with action text (Book, Call, Get Started, Audit, Scan, etc.).

  Fix: Add a clear button with a specific action verb near the top of the page.
• −10
  No early call-to-actionA CTA exists but does not appear in the first visible section.

  Fix: Move your most important CTA button above the fold, into the hero section.
• −15
  Too many CTAs (more than 6)When every button feels equally important, visitors hesitate.

  Fix: Choose ONE primary action per page. Make it a filled button. Convert secondary links to ghost buttons or plain text.
• −5
  No breadcrumbsBreadcrumbs tell visitors and search engines where a page sits in the site structure.

  Fix: Add a BreadcrumbList schema block and a visible trail on inner pages.
• −3 ea
  Dead # linksLinks set to href="#" with no destination scroll the page to top and confuse assistive tools.

  Fix: Replace every href="#" with a real destination or remove the link.

Only applies when the page has a form. Each item below deducts points.

• −30
  Form inputs missing labelsInput fields without <label> elements are harder for screen readers and browser autofill.

  Fix: Add <label for="fieldId"> before each input. Use sr-only pattern to hide labels visually if needed.
• −10
  No required field markersVisitors do not know which fields they must fill before submitting.

  Fix: Add required attributes and show a visual marker next to each label.
• −15
  Too many fields (more than 8)Long forms have higher abandonment rates.

  Fix: Cut every non-essential field. Name, email, and one message field is enough for most contact forms.
• −10
  No inline help textFields with no hint text force visitors to guess the expected format.

  Fix: Add a brief placeholder or helper note under complex fields.
• −10
  No success message detectedAfter submitting, visitors see nothing and do not know if it worked.

  Fix: Show a confirmation message after successful submission or redirect to a thank-you page.
• −10
  No error guidanceWhen the form fails, visitors see nothing helpful.

  Fix: Add field-level error messages and a general error banner at the top of the form.

The coloured pills give a quick yes/no view of individual signals. Green = passing, red = failing.

Path and Form scores are separate from the main AI Visibility Score but directly affect conversions.