Catch-up after a rescheduled slot. Sarah has been pulled between GBP posts, updating the Loveland parent page, and a self-built SEO plan spreadsheet organised by Protect / Improve / Grow / Maintain columns. Nico reviews the sheet and the kitchen-remodeling page, flags one gap (no Service schema), and proposes a tighter per-page checklist: correct schema, locality mentions, FAQs, unique images. Then the big shift of the session: migrate Sarah off Claude chat + Projects and onto Claude Co-work (the desktop agentic wrapper). They open a fresh desktop folder (SEO work/), drop a pre-built context MD file in, connect the Chrome MCP, and hand Cowork three prompts in sequence: (1) understand the project from the folder + GSC data, (2) analyse the Fort Collins whole-home template as the reference structure, (3) generate the equivalent Timnath contractor page as a fully-differentiated (50%+) Excel sheet with every section (hero, SEO, value prop, testimonials, and the full city-info tabs: weather, economy, cost of living, employment, quality of life, industries) with hyperlinked research citations. The Excel file lands in her folder in a few minutes and reads cleanly. Nico closes with a safety note (Cowork has browser access and WordPress is logged in), schedules Mar 16 + Mar 31, and sets the homework: review the Timnath output, then run the same prompt chain for Loveland, Windsor, Wellington, and Greeley.

• The "Sweetheart City Home Remodeling" hallucination came from a Claude Project with no persistent memory of the naming rules. Fixed by moving context into a dedicated MD file.
• Co-work + a desktop folder with a context MD file beats Claude Projects for this kind of multi-location page work. More tools, persistent context, scheduling, browser access.
• Timnath is a real gap in the GSC data despite being a small town. First target after Fort Collins.
• One Cowork run produced a full Timnath location-page Excel with 50%-differentiated content and hyperlinked research citations in under five minutes.
• Naming files stays constant; contents can evolve. System prompt references files by name.
• Safety: Cowork can drive a logged-in Chrome, which means it can also touch WordPress. Watch it when it scrapes the site.

• Sarah moves all ongoing website work into Co-work, not Claude chat or Projects.
• Next session pushed to Monday Mar 16 (Nico's birthday on the 17th); final session Mar 31.
• Review the Timnath Excel; if it passes QA, run the same flow for Loveland, Windsor, Wellington, and Greeley.
• Build a per-page SEO checklist (schema, locality mentions, FAQs, unique images).
• Start experimenting with Co-work for non-website tasks (invoice review, subscription audit).