Docs: Add AEO Audit documentation (LIS-2643)

[haleyserrano]

JIRA

LIS-2643 — Run AEO audit report once a month

---

Change Classification

Feature behavior change — New automated AEO Audit scheduling for Local SEO Premium users (SMB-facing)

Repo: Business App (end-user documentation)

---

Summary

Added a new AEO Audit section under Local SEO (docusaurus/docs/local-seo/aeo-audit/) documenting:

• How the initial audit triggers automatically upon activating Local SEO Premium (deep-crawl up to 50 pages, AI analysis)
• What the AEO Dashboard shows on first visit: Readiness Score + Top 5 Fixes (Schema, Robots.txt, JSON-LD, Metadata, Content, Speed)
• Automatic monthly re-audit cadence and mid-month activation behavior
• Credit-based manual re-runs with purchase prompt when credits are insufficient
• Historical audit result storage for trend tracking

---

New vs. Updated Documentation

New documentation created. No existing AEO or AI search readiness content was found in this repository. A new section was required.

Placement: docusaurus/docs/local-seo/aeo-audit/ at sidebar position 10 (after Analytics at position 9), as this is a Local SEO Premium feature.

---

Acceptance Criteria Coverage

AC	Documented
AC1: Initial audit triggers automatically on Premium activation (deep-crawl up to 50 pages)	✅
AC2: AEO Dashboard shows completed Readiness Score + Top 5 Fixes on first visit	✅
AC3: Monthly automatic re-audit cadence	✅
AC4: Manual re-runs require credits; prompt to purchase if insufficient	✅
AC5: Historical results stored for comparisons over time	✅
AC6: Mid-month activation — audit runs on activation day, then next on scheduled date	✅
AC7: Website changes after audit starts → reflected in next scheduled run only	✅

---

Figma / Images

No Figma links or screenshots were provided in the JIRA ticket. No images included.

---

Partner Center

No Partner Center update required. This feature is entirely SMB-facing (Business App). The Partner Center has no existing Local SEO product documentation home for this type of content.

---

Skills Used

• pre-push-validation — validated frontmatter, tags, links, and _category_.json before push

---

Assumptions & Limitations

• The exact monthly schedule date (1st of month per implementation; last Wednesday per PM comment) was intentionally described as "monthly" in user-facing docs to avoid documenting an implementation detail that may change.
• No screenshots available; article is text-only.

---

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code