Skip to content

Docs: AI Search Specialist — description auto-optimization (DAT-4274) - #610

Open
haleyserrano wants to merge 1 commit into
masterfrom
claude/gifted-hawking-41n53l
Open

Docs: AI Search Specialist — description auto-optimization (DAT-4274)#610
haleyserrano wants to merge 1 commit into
masterfrom
claude/gifted-hawking-41n53l

Conversation

@haleyserrano

Copy link
Copy Markdown
Contributor

JIRA

DAT-4274 — Description Optimization (Search AI Specialist): relevance-gated refresh + revert path


Change classification

Feature behavior change — Business App end-user experience

Repo target: Business App (end-user-facing docs)


Summary of changes

File Action Description
docusaurus/docs/business-app/ai/ai-workforce/ai-search-specialist.md Created New article explaining what the AI Search Specialist does, how it evaluates descriptions, when it triggers, what the notification looks like, and the tracked-keywords scope
docusaurus/docs/business-app/ai/index.md Updated Added AI Search Specialist row to the AI roles table; added link in More resources section
docusaurus/docs/business-app/ai/ai-workforce/ai_workforce_overview.md Updated Added AI Search Specialist to the Guides list

New vs. existing docs

New page created. No existing page covered the AI Search Specialist or autonomous description optimization. The feature is a distinct autonomous AI Employee with its own behavior, trigger, and notification — a new article is warranted.

Placement reasoning: The AI Search Specialist is an AI Employee that lives alongside the AI Reputation Specialist, AI Chat Receptionist, and AI Voice Receptionist in docusaurus/docs/business-app/ai/ai-workforce/. This is the correct home for all AI Employees.


Acceptance criteria coverage

AC Documented? Where
AC#1 — Detection: 90-day age flag + services/specialties "How it works" section; FAQ on 90-day recency
AC#2 — Relevance gate: skip if nothing meaningful changed "How it works" and "When your description is updated"
AC#3 — Generation uses website, tracked keywords, business category "How it works" bullet list; "Tracked keywords" section
AC#3 — Untracked keywords are skipped "Tracked keywords" section; FAQ
AC#5 — Write + sync to Google, Bing, Apple, Facebook "When your description is updated" step 3
AC#6 — Notification: "AI Search Specialist: Profile Description Updated" links to Business Profile "When your description is updated" steps 1–2
AC#4 — Re-optimization guard (post-revert, 90 days) ⏭️ Not documented — revert (DAT-4288) is not yet shipped; guard activates automatically once it is

Figma / images

No Figma links or screenshots were provided in the JIRA story. No images added to this PR.


Skills used

  • Repository search (mcp__github__search_code) — confirmed no existing AI Search Specialist documentation in this repo
  • JIRA issue lookup (mcp__Atlassian__getJiraIssue) — sourced acceptance criteria
  • GitHub PR search (mcp__github__search_pull_requests) — identified code authors and confirmed merged feature PRs (ai-assistants-config#609, automations-config#37)

Assumptions and limitations

  • The revert feature (DAT-4288) is not yet shipped; DAT-4274 explicitly excludes it from scope. The re-optimization guard post-revert is intentionally omitted from these docs and will be covered when DAT-4288 ships.
  • No screenshots available at time of writing — can be added once UI is confirmed stable.
  • "Local SEO Premium" is the subscription tier that activates the AI Search Specialist (sourced from PR descriptions); not stated in JIRA AC but confirmed in code PRs.

@ahnikakuse @haleyserrano @maryam6samadi


Generated by Claude Code

@haleyserrano
haleyserrano marked this pull request as ready for review August 5, 2026 20:24

@nisarg-va nisarg-va left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once the merge conflicts are resolved its good to be merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants