DELIVERED · M4U EVENTS
AI Search Visibility. Getting a real business cited by AI answer engines — without breaking what works.
- Status
- Deliverables shipped; rollout staged
- Client
- M4U Events
- Stack
- Python · live-site audit · Slack alerts · branded PDF deliverables
- Scale
- 4 staged deliverables · 20-prompt engine baseline · hourly crawler watch
- Year
- 2026
First, do no harmthe audit’s biggest win was what it refused to change
The problem
Couples increasingly ask ChatGPT and Perplexity who to book — and answer engines cite whoever they can read and trust. The client’s site had never been looked at through that lens. The naive playbook (“fix robots.txt, spin up city pages”) could have actively destroyed their existing search traffic.
What I shipped
- ◆A full crawler-access audit of the live site — including discovering that the robots file’s ~90 blocking rules were inert due to a formatting quirk, and that “repairing” them would have de-listed 52 live pages. Flagged, documented, left alone.
- ◆A staged rollout plan — cheap and reversible changes first, expensive and permanent ones only after results land. Sequenced as deliverable documents the team can execute.
- ◆A 20-prompt baseline across answer engines, plus a competitive scan — so “are we cited more?” has a before to compare against.
- ◆An hourly crawler watch — a monitor that checks whether AI crawlers (OpenAI, Anthropic, Perplexity) can reach the site and Slack-DMs when access changes in either direction.
- ◆A branded leadership deck — a four-page PDF that explains the whole strategy to non-technical stakeholders.
How it works
- 1Audit the live site as the crawlers see it
- 2Stage changes: reversible before permanent
- 3Baseline citations across engines before touching content
- 4Monitor crawler access hourly; alert on any change
The hard part
Restraint. The audit found a live pricing mismatch, a booby-trapped robots file, and a WAF that blackholes aggressive crawlers — and in each case the right move was documented caution, not a clever fix. The deliverables include an explicit “what we deliberately refused to build” section (no programmatic city pages, no gaming) because scaled-content tricks are exactly what gets sites demoted.
Proof
- ✓Written audit with reproducible findings on crawler access.
- ✓Monitor built, tested, and self-installing on a schedule.
- ✓Leadership PDF delivered; staged plan awaiting the client’s green light on stage one.
robots audit · 90 inert rulesDO NOT ‘FIX’
AI crawlers · access checkHOURLY
Citation baseline · 20 promptsRECORDED
Where it stands
Deliverables in the client’s hands; execution gated on their decisions, by design. The monitoring runs either way — when access changes, the team knows within the hour.
I scoped the audit and acted on the review that argued against ‘fixes.’ Claude Code did the research and the deliverables. How I work →
Run an events business? I built Ajna for you.
AI automation for wedding & event vendors — quotes in minutes instead of days, a human always in the loop.