EatCookJoy SF — SEO / GEO / AEO Progress & Process Review

A · May → June · the build phase closed

From a missing foundation to a complete build.

The May audit found the basics absent — no robots, no sitemap, schema gaps, thin content. Those are now shipped. We have ~165 indexable pages (SF + all 77 neighborhoods, plus East Bay, Peninsula & South Bay cities), the full JSON-LD suite, and AI-engine fact sheets. The work now is operational and measurement, not construction.

Technical SEO

Built ✓

robots.txt · sitemap.xml (~165 URLs) · canonical · index,follow · CWV tuning

Structured data

Built ✓

Organization · LocalBusiness · Service · FAQPage · HowTo · BlogPosting · Speakable + more

AEO (snippets, voice)

Built ✓

FAQ + Speakable + HowTo schema · answer-first block on every area page

GEO (LLM answer)

Built ✓

llms.txt + llms-full.txt · robots welcomes AI crawlers · citable compare/blog content

Dimension	May 2026 (audit)	June 2026 (this review)	Phase
Foundation — robots / sitemap / canonical	Missing	Shipped	Done
Structured data coverage	Org only	Full suite	Done
Content depth — area / service pages	8 pages	~165 pages	Done
Indexing — GSC / Bing live	Not submitted	In progress	Active
Local pack — Google Business Profile	None	Claiming	Active
Rankings / traffic / citations	Baseline	Measuring	Tracking

Live results (rankings, organic traffic, LLM citations) are still early by design — indexing only just began, so those numbers start at baseline and are tracked weekly (§E, §F).

B · Question 1 · initiatives in progress

What's active right now.

Each item follows the same loop — Audit → Fix → Verify — and is tracked in the repo so status is auditable, not tribal knowledge.

Indexing push — submitting the sitemap to Google Search Console & Bing, then force-indexing priority URLs (SF neighborhoods → Bay Area cities) at ~10/day via URL Inspection.
Google Business Profile — claiming + verifying the service-area listing. The local "map pack" ranks from GBP signals, not website signals, so this is a separate track.
Review collection — emailing recent clients for Google reviews; hitting 5+ unlocks Review / AggregateRating schema.
Query-driven tuning — once the first week of GSC data lands, rewrite titles/descriptions on pages earning impressions but no clicks, and deepen the pages actually ranking.
Triggered content backlog — chef profile pages (/chefs/[slug]), sameAs social links, and tel:/WhatsApp CTAs — each ships the moment its input (bios, social URLs, a phone number) is available.

C · Question 2 · the metrics we track

Tracked against 30 / 60 / 90-day targets.

Progress is measured, not estimated. The glide path below is the scorecard the founder reviews; live values are pulled from GSC + GBP each cycle and logged (§E).

KPI	30-day	60-day	90-day
Pages indexed	80+	130+	150+
GSC impressions / mo	2,500	8,000	20,000
GSC clicks / mo	80	300	900
Top-10 ranking neighborhoods	5+	15+	30+
Google Business Profile reviews	8+	25+	60+
Organic-attributed bookings / mo	3+	12+	40+
Authority backlinks	3+	10+	25+

Plus, monthly

AEO — featured-snippet and Google AI-Overview appearances for target queries.
GEO — whether ChatGPT, Perplexity & Gemini name EatCookJoy for prompts like "private chef in San Francisco" / "how much does a private chef cost in SF", and whether the facts they cite (pricing, areas) are correct.

D · Question 3 · tools & platforms

What we use to track, optimize & report.

Tool	Role	Access
Google Search Console	Impressions, clicks, position, CTR, indexing/coverage, Core Web Vitals	Confirm
Bing Webmaster Tools	Bing indexing + sitemap submission	Confirm
Google Business Profile	Local pack, reviews, calls/direction requests	Claiming
Rich Results Test / Schema validator	Validate JSON-LD (FAQ, LocalBusiness, Service…)	Public
PageSpeed Insights	Core Web Vitals & performance	Public
Brevo	Neighborhood lead-form capture & tagging	Attrs
Manual LLM checks	GEO — prompt ChatGPT / Perplexity / Gemini monthly	Manual
Git repo (source of truth)	Site, schema, llms*.txt, robots, and all SEO docs — every change a reviewable commit	Live

E · Question 4 · documentation, reports & dashboards

Where everything lives — version-controlled.

Because docs and reports sit in the repo, the full history is a git log — every process change and every weekly report is timestamped and attributable.

Artifact	Location	Purpose
SEO Playbook	docs/SEO-PLAYBOOK.md	Operational playbook — what's built, the day-by-day checklist, the edit-here map, follow-up triggers, templates
Executive Overview	docs/SEO-OVERVIEW.md	One-page stakeholder summary mapping to these five questions
Metrics Log	docs/SEO-METRICS-LOG.md	The running weekly log — a dated block appended every Monday for trend history
This review	/seo/audit-2026-06-12/	June progress & process snapshot (companion to the May audit)
Live dashboards	GSC + GBP Insights	Real-time raw numbers behind the weekly log

The May audit and this June review are both committed companions to the SF Launch Playbook — so the search program's whole story, from 30/100 to a complete build, is one auditable trail. Repo docs · GSC + GBP dashboards · /eatcookjoy-playbook-US-SF/seo/

F · Question 5 · how progress is communicated

The cadence — daily, weekly, monthly.

Frequency	What happens	Output
Daily (Mon–Fri, ~5 min)	Glance at GSC Performance/Coverage + GBP Insights/Reviews; reply to every review within 24h	Health check
Weekly (Monday)	Pull last-7-days GSC + GBP numbers, compare to prior week, flag top climbing/falling queries	Block appended to the Metrics Log
Monthly	Trend roll-up vs. the 30/60/90 targets + LLM citation check	Stakeholder summary
Per change	Each fix is a commit	Reviewable diff

Each weekly report answers four questions

What changed — fixes applied this cycle (with commit links).
What moved — metric deltas vs. last cycle.
What's next — queued initiatives.
Blockers — items needing a human (credentials, real reviews, a phone number, budget) — flagged explicitly, never fabricated.

Channel: committed to the repo and shared with stakeholders. Optional upgrade: a single live Looker Studio dashboard wired to GSC + GBP can replace the written weekly pull if an always-on view is preferred — it needs the analytics access in §G.

G · Open items · needs input

Five things that unblock the live numbers.

These are flagged rather than guessed. The reporting structure is in place; a few fields wait on access and assets.

Verify deploy + submit sitemap to Google Search Console and Bing.
Claim + verify the Google Business Profile (service-area business; SF + East Bay + Peninsula + South Bay).
Configure Brevo contact attributes so the lead-form tags are usable.
Provide social URLs, a phone / WhatsApp number, and chef bios + photos to unblock the triggered backlog.
Collect 5+ reviews to unlock Review / AggregateRating schema.