> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwaio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Issue page template

> The canonical structure for every audit-issue page. Copy this file to create a new issue page.

Replace this opening line with a one-sentence, plain-English statement of the problem. Example: "Your page is missing a meta description, the short summary search engines and AI systems use to understand what the page is about."

## What this means

Two or three sentences a non-technical reader can follow. No jargon without an immediate definition. Explain what the audit actually detected on their site.

## Why it matters

Which of the three audiences does this hurt, and how?

* **People**: what breaks or degrades for a human visitor, if anything
* **Search engines**: what this costs you in crawling, indexing, or ranking
* **AI systems**: what this costs you in citations, retrieval, or agent compatibility

Cut any audience row that isn't relevant. Don't pad.

## How to fix it

Concrete steps, ordered. If the fix differs by platform, use tabs:

<Tabs>
  <Tab title="Webflow">
    Steps for Webflow users, referencing actual Webflow UI locations.
  </Tab>

  <Tab title="Other platforms">
    The generic version, written so a developer on any stack can act on it.
  </Tab>
</Tabs>

<Note>
  If this fix usually needs a developer, say so plainly: "This one is a developer task. Send them this page."
</Note>

## Learn more

Two or three links out to authoritative technical references. Prefer, in order: [MDN](https://developer.mozilla.org), [web.dev](https://web.dev), official platform docs, [W3Schools](https://www.w3schools.com). Label each link with what the reader will find there, not just the site name.

* [MDN: relevant reference page](https://developer.mozilla.org) — the technical specification
* [web.dev: relevant guide](https://web.dev) — Google's practical guidance