How a $45K/Month SEO Agency Runs on Claude: Skills, Chrome Extension, Design, and Code

TL;DR: Kasra Dash, operator of a $45K/month SEO agency, has rebuilt his production workflow around four Claude capabilities: Skills for brand-specific content templates, the Chrome Extension for autonomous publishing, Claude Design for rapid website prototyping, and Claude Code for converting those designs into deployable WordPress themes. The result is a near-fully automated content and web-build pipeline that requires minimal human intervention.

The Pulse:

• Kasra Dash runs a $45K/month SEO agency using Claude as the primary production engine across content, publishing, design, and front-end development.
• The Claude Chrome Extension can upload a batch of 15 articles autonomously to a WordPress CMS, completing each upload in approximately 30 seconds per article while the operator works elsewhere.
• Claude Code converts a standalone HTML file exported from Claude Design into a deployable WordPress theme: complete with 5 core theme files: in roughly 4 minutes, with no developer required.

The core friction in modern SEO agency operations is not talent: it is throughput. Producing citation-worthy, brand-consistent expert articles at scale while simultaneously managing web builds, client reporting, and link acquisition is operationally impossible without automation. Kasra Dash’s agency workflow resolves this by treating Claude not as a chat assistant but as an orchestration layer across four distinct production surfaces: each one eliminating a category of manual labor.

Claude Skills: Encoding Brand Intelligence into Reusable Templates

Claude Skills are persistent, brand-specific instruction sets stored in Claude’s briefcase interface. They function as the operational equivalent of a senior editor’s style guide: every article generated under a Skill inherits the brand’s URL structure, target keywords, tone of voice, audience definition, and formatting rules without the operator re-entering that context on every session. For any agency running content across multiple client websites, Skills are the mechanism that makes AI content generation consistent rather than generic.

The setup process Dash describes is deliberately low-friction. A Google Sheet houses all SOPs, and the content-writing Skill prompt uses red-highlighted fields as variables: brand name, website URL, industry vertical, service area (single location, nationwide, or worldwide), target audience, primary keywords, tone of voice, and any compliance rules. For a dental practice in Manchester, those fields populate with NHS approval signals and local area pages. For a worldwide e-commerce store, the location field simply reads “worldwide shipping.” The same template architecture handles both without modification to the underlying prompt logic.

Once the prompt is pasted into Claude’s Skill Creator with the creator toggle enabled, Claude interrogates the operator: what article types will this Skill generate (blog posts, service pages, or both), what output format is required (Dash specified HTML-ready), and are there trust signals to include by default? The resulting Skill artifact contains the practice area, address, target keywords, LSI terms, page types, and meta-title and meta-description formatting rules: all extractable and editable via the three-dot menu if the business changes address or rebrands.

A critical operational advantage is portability. Dash notes that a completed Skill can be downloaded and distributed to every Claude account within a team, ensuring that a junior content writer and a senior strategist produce structurally identical output. This is the equivalent of fine-tuning behavior at the prompt layer rather than at the model layer: achieving consistent inference outputs without the cost or latency overhead of a custom fine-tuned model on OpenAI’s API or Anthropic’s fine-tuning endpoints.

The Real Takeaway: A single Claude Skill: built once from a structured Google Sheet prompt: replicates senior editorial judgment across every team member’s account, eliminating the per-article context-loading overhead that makes AI content generation slow at scale.

The Conventional Approach vs. the Kasra Dash Workflow

Claude Chrome Extension: Autonomous CMS Publishing at Batch Scale

The Claude Chrome Extension transforms the browser into an autonomous agent that executes multi-step CMS workflows without human input. Dash uses it specifically for the upload bottleneck: generating 15 articles in Claude and then delegating the copy-paste-publish sequence entirely to the extension while he works on other tasks. Each article upload: including title, body content, internal links, FAQs, and summary: completes in approximately 30 seconds.

The operational instruction is straightforward: tell the extension which articles to upload, which Claude Skill to use for generation, which website to target, and to set every page as a draft rather than publishing live. The extension navigates to the CMS, logs in if needed, creates a new page, and pastes the structured HTML content. Dash observed it completing internal linking and FAQ formatting automatically during a live demonstration on his own site.

The extension’s capability extends beyond publishing. Dash also used it to autonomously reply to LinkedIn messages: illustrating that any browser-based, repetitive interaction is within its operational scope. The constraint he flags is accuracy with Google Sheets: copying data into or out of spreadsheets is a known weak point, so Sheets-based workflows are better handled through Claude’s API or direct prompt input rather than the extension’s browser automation.

Compared to alternatives like OpenAI’s Operator (which performs similar browser automation via GPT-4o) or Microsoft Copilot’s browser actions in Edge, the Claude Chrome Extension’s advantage is tight integration with Claude’s existing Skill and project context. An operator does not need to re-specify brand rules: the extension inherits the active Skill. The tradeoff is that it currently carries a low user rating in the Chrome Web Store, which Dash attributes to user expectations rather than functional limitations: the extension performs well for the specific automation tasks it is designed for.

What This Means in Practice: Batching 15 articles through the Chrome Extension rather than uploading manually reclaims several hours of production time per client per month: hours that can be reallocated to authority building, link acquisition, or AEO strategy.

Claude Design: From Competitor Screenshot to High-Fidelity Website Mockup

Claude Design, accessible at claude.ai/design, converts a reference image and a structured text prompt into two high-fidelity website design variants simultaneously. The workflow requires zero design software proficiency. An operator finds a competitor’s website, saves a screenshot, uploads it to Claude Design, and describes the required sections, brand colors, and conversion objectives. Claude interrogates the operator on specifics: firm name, practice areas, visual tone, CRO aggressiveness, number of case studies, team member count, years in business: and then generates both variants on a shared canvas.

In Dash’s live demonstration, he specified gold and navy as brand colors for a law firm called KD Law, requested a full-bleed hero banner, an about-the-team section, a company history section, a case study section, a client roster, and a contact form. He set CRO aggressiveness to “super aggressive” and requested 6 case studies and 12 team members. The output included an instant-quote CRO widget with fields for matter type, dispute origin, approximate value, and company name: a conversion mechanism Claude inferred from the brief rather than one explicitly specified.

The design output supports three export paths: raw HTML, a design file for handoff to a human developer, or direct handoff to Claude Code for automated theme generation. For operators without a development budget, the Claude Code path is the fastest route from concept to a working WordPress installation. For agencies with existing developer relationships, the design file export provides a structured brief that eliminates the ambiguity typical of verbal design briefs.

The Strategic Implication: Claude Design collapses the design brief-to-mockup cycle from days to minutes, removing the primary scheduling bottleneck that delays new client website launches and SEO optimization work.

Claude Code: WordPress Theme Generation Without a Developer

Claude Code, available in the Claude desktop application, converts a standalone HTML file into a complete, upload-ready WordPress theme in approximately 4 minutes. The operator selects a working folder, drags the HTML file exported from Claude Design into that folder, and instructs Claude Code to convert the preferred design variant into a WordPress theme. No knowledge of PHP, CSS architecture, or WordPress template hierarchy is required.

The generated theme includes all five core WordPress template files: footer.php, header.php, functions.php, front-page template, and style.css. Claude Code constructs these files progressively, and the operator can monitor the folder as files appear. Once complete, the operator right-clicks the theme folder, compresses it to a .zip archive, and uploads it via WordPress’s Appearance panel using the standard “Add Theme / Upload Theme” interface. Activation is a single click.

Dash’s live output for KD Law included a meet-the-team section with placeholder images, the instant-quote CRO widget from the design phase, a contact form, practice area listings, and a firm resources section: all rendered from the design mockup with structural fidelity. The operator’s only remaining task is replacing placeholder images with real photography and populating the CMS with actual content. Inner pages: service pages, blog templates, contact pages: follow the identical workflow: generate in Claude Design, export, convert in Claude Code, upload.

Comparing this to alternatives: Vercel’s v0 (built on GPT-4o) generates React and Next.js components from prompts but does not natively output WordPress themes. GitHub Copilot can assist with PHP and CSS editing but requires the operator to already understand WordPress’s template architecture. Claude Code’s advantage here is the end-to-end pipeline from design artifact to deployable theme, with no intermediate expertise required.

Why This Matters Now: Eliminating the developer dependency for new client website builds reduces agency delivery time and removes a fixed cost that erodes margin on smaller SEO retainers: directly improving the unit economics of a $45K/month operation.

The Human Review Imperative: Why Draft Mode Is Non-Negotiable

Despite the throughput gains, Dash is explicit that current AI content generation does not eliminate the need for human editorial review. Hallucinations remain a live risk. Publishing AI-generated content directly to a live URL without inspection is, in his framing, a workflow failure rather than a time-saving measure. The correct protocol is to set every AI-generated page as a draft and review it before activation.

The quality ceiling is also prompt-dependent. Dash’s direct observation: “It is literally garbage in, garbage out.” Feeding Claude a minimal prompt produces minimal output. Feeding it a sitemap, a full keyword list, audience definition, tone rules, and compliance requirements produces content that is structurally sound and brand-consistent. The Skill architecture exists precisely to encode this context permanently, so operators do not need to reconstruct it on every generation run.

The Bottom Line: Automation at the scale Dash describes: 15 articles per batch, uploaded autonomously: is only operationally safe when paired with a draft-first review protocol that keeps human judgment in the publication decision.

Frequently Asked Questions

Can Claude Skills be shared across a team without each member rebuilding them?

Yes. A completed Skill can be downloaded from the Claude briefcase interface as a file and distributed via email to any team member’s Claude account. Each recipient imports it and gains access to the identical brand context, keyword targets, and formatting rules. Dash specifically describes this as the mechanism for maintaining output consistency across multiple operators within the same agency.

What is the practical difference between Claude’s Skill system and simply saving a long system prompt?

A saved system prompt requires the operator to paste it into each new conversation manually. A Claude Skill is stored in the briefcase interface and activates via “Try in Chat”: it persists across sessions and is accessible to the Chrome Extension during automated workflows. The Skill also supports structured interrogation during creation, where Claude asks clarifying questions (article types, formatting, trust signals) to refine the instruction set before saving.

How should an agency handle industries with compliance requirements, such as healthcare or legal?

The Skill prompt architecture includes a field for “specific rules,” which is where compliance constraints belong. For a UK dental practice, this would include NHS approval status. For a law firm, it might include jurisdiction-specific disclaimers. Dash also notes that trust signals can be set to appear only when explicitly requested rather than by default: giving the operator control over when compliance language surfaces in generated content.

Is the Claude Chrome Extension suitable for non-WordPress CMS platforms?

Dash demonstrates the extension against a WordPress CMS, but the mechanism is browser-based automation rather than a WordPress-specific integration. Any CMS with a browser-accessible editor: including Webflow, Squarespace, or custom admin panels: is theoretically within scope. The known limitation is Google Sheets interaction, where the extension’s reliability degrades. For Sheets-dependent workflows, direct API calls or manual prompt input are more reliable than the extension.

What is the recommended sequence for a new client website build using this four-tool workflow?

The sequence Dash demonstrates is: (1) build the content Skill in Claude’s briefcase using the client’s brand brief; (2) use Claude Design at claude.ai/design with a competitor reference image to generate two high-fidelity mockups; (3) export the preferred variant as standalone HTML; (4) drag the HTML into a folder and use Claude Code in the desktop app to generate the WordPress theme files; (5) compress to .zip and upload via WordPress’s theme installer; (6) use the Chrome Extension with the active Skill to generate and upload inner pages as drafts; (7) human review before any page is activated. The full cycle from blank brief to a locally hosted WordPress site takes under an hour in Dash’s demonstration.