winston-geo-tech-audit: GEO Technical Audit packages in minutes, not weeks.

What it does.

Point it at a target domain. The Skill crawls the site, pulls Google Search Console (GSC) data, hits DataForSEO for Search Engine Results Page (SERP) and AI-engine visibility, validates schema, scores against the GEO rubric, and writes the result to two artifacts. An Excel workbook with the full data and a Winston-branded PowerPoint deck for the client meeting.

How we use it.

It's the standard GEO Technical Audit deliverable for new and existing engagements. Strategist scopes the audit, triggers the Skill, reviews the output, edits the prioritization call, ships to the client. Two days from kickoff to deck instead of four weeks. The senior strategist's time goes into the recommendations, not into building the artifact.

Why we built it.

GEO Technical Audits are repetitive: same data sources, same rubric, same workbook structure, same deck shape. Roughly four weeks of senior time per engagement. Most of those four weeks were data-gathering and formatting. The judgment call is what to recommend. Build the Skill for the data-gathering and formatting. Keep the human on the recommendation.

The stack inside it.

• DataForSEO for SERP, AI Overview, and competitor visibility data
• Firecrawl for the site crawl and content sampling
• Google Search Console (GSC) API for impressions, clicks, and indexability data
• Schema.org structured data validator for markup pass/fail
• openpyxl to render the Excel audit workbook
• python-pptx to render the Winston-branded PowerPoint deck
• Claude Skills as the orchestration and rubric-scoring layer

What this proves.

Skills compound. Every job that was a half-day or a multi-day stretch of senior time becomes a Skill the team triggers from chat. The output ships faster. The strategist's calendar opens up for the work that actually needs human judgment: positioning, narrative, the prioritization call on what the data is really saying. That is the Winston operating model in one Skill.