Product SEO: Claude + Make

A handmade-soap shop adds new scents constantly, and every one goes up with the default SEO Shopify generates, which is to say none worth having. The products are lovely and invisible: no search title, no meta, no tags, so they never surface when someone searches for exactly what they make.

This build optimizes each one as it lands. When a new product is created, Claude writes an SEO title, a meta description, and tags from the product’s own details, and Make saves them back to the product. The catalog optimizes itself, scent by scent.

We wire it in Make, part of our e-commerce set. It is the companion to writing descriptions: that build creates listings, this one makes the listings findable. Claude handles the wording; Make writes it back to Shopify.

What does this workflow actually do?

In one line: a new product becomes a findable product. Make watches Shopify for new products. When one appears, Claude writes an SEO title, meta description, and tags from its details, and Make updates the product with them. Your catalog gets optimized without you touching the SEO fields.

A few real cases, none of them the usual ones:

• The handmade-soap shop above, every new scent finally showing up in search.
• A guitar-pedal builder tuning meta for niche, high-intent searches.
• A plant nursery with hundreds of species pages that need real tags.
• A specialty-tea shop optimizing meta across a sprawling catalog.

Making the product is the craft. Writing the SEO fields for every one is the invisible chore that decides whether anyone finds it. That wording is exactly what Claude does well.

Why use Make if Claude can already read and write?

Reasonable question. Claude is good at writing an SEO title and meta from a product’s details. It is not built to watch Shopify and write fields back to the right product. That is plumbing, and Make does plumbing.

Make handles the no-judgment steps: catching the new product, updating its SEO fields, running on its own. Claude handles the one step that needs words, the optimization. Make is the clerk; Claude is the SEO writer. Together every product you add gets found, with no extra step from you.

What do you need before you start?

• A Make account. The free 1,000 operations a month covers a busy catalog.
• A Claude API key from the console, not the chat app. See how to use Claude.
• A Shopify store with products that have descriptions for Claude to work from.
• Nothing else. Claude reads the product and writes its own SEO.

Two Make words. A scenario is the whole product-to-SEO automation. A module is one box. Three boxes, one scenario.

How does the workflow work, step by step?

Three modules, left to right:

Module	App	What it does
1. Trigger	Shopify	Fires when a new product is created
2. Brain	Claude	Writes an SEO title, meta, and tags
3. Output	Shopify	Saves them back to the product

Step 1: Watch Shopify for new products

Create a scenario and add Shopify, Watch products, connect your store, and watch for new products. This trigger hands the next step the product’s title and description.

Step 2: Let Claude write the SEO

Add a Claude module, Create a Prompt, paste your key, pick Sonnet:

Write SEO fields for this product. Return one line, pipe-separated.
Product: {{title and description from Step 1}}

SEO title (under 60 chars, includes the main search term) | meta
description (under 155 chars, benefit-led) | 5 lowercase tags.
Use only what the product is; no keyword stuffing.

The character limits and the no-stuffing rule keep the output clean and useful, not spammy.

Step 3: Save the SEO back to Shopify

Add Shopify, Update a product, point it at the product from Step 1, and map Claude’s SEO title, meta description, and tags into the matching fields. The product is now optimized, automatically.

How do you run it and check the result?

Click Run once on a test product. When I tested this, the SEO fields were solid once I capped the lengths and banned keyword stuffing, which kept the meta readable. Tune it, then turn the scenario on so every new product optimizes itself.

After that, your catalog stops launching invisible. Each product you add shows up with a real search title, meta, and tags, and the long tail of niche searches starts finding you.

What does this cost to run?

Piece	Free tier	If you outgrow it
Make	1,000 operations/month free	Core plan from about $9/month
Claude API	Pay per use	SEO fields on Sonnet cost a fraction of a cent
Shopify	Your existing plan	No extra cost
SEO app	Not needed	Skip the monthly fee

Each product is three Make operations and a sliver of Claude, and it can replace a paid SEO app. More on tiers in our Make guide.

What can go wrong, and how do you avoid it?

• Keyword stuffing. Ban it in the prompt; stuffed meta reads badly and can hurt you.
• Titles too long. Cap the SEO title and meta lengths so search engines do not truncate them.
• It overwrites manual SEO. Run it on new products only, or check before it touches ones you tuned by hand.
• Tags multiply. Ask for a fixed number of lowercase tags so they stay tidy.

The same enrich-and-save pattern runs many jobs. See Make AI scenarios.

How do you build this in Zapier or n8n instead?

The three jobs do not change, only the names do.

Job	Make	Zapier	n8n
Catch a product	Watch products	New Product trigger	Shopify Trigger node
Write the SEO	Claude module	Claude (Anthropic) action	Anthropic node
Save it back	Update a product	Shopify Update Product	Shopify node

Make and Zapier are easiest to start. Zapier vs Make vs n8n compares all three.

Frequently asked questions

Will it mess up SEO I already wrote?

Run it on new products only, or add a check, so it does not overwrite pages you tuned by hand. New products are the safe target.

Does this replace an SEO app?

For the basics, often yes: titles, meta, and tags from the product itself. Dedicated apps add audits and tracking on top.

Can it pick keywords from search data?

Not on its own; it works from the product details. For keyword research, add a step that feeds in target terms.

Does it work with WooCommerce?

Yes. Swap the Shopify modules for WooCommerce ones; the Claude step is identical.

Is the chat app the same as the API?

Same models, different door. Make needs an API key from the console, not the chat login.

Sources and references

• Creating a scenario (Make Help)
• Claude API overview (Anthropic)
• Shopify SEO basics (Shopify)
• Shopify on Make (integrations)
• SEO — Grokipedia

Last reviewed: May 2026. Make, Claude, and Shopify update their interfaces; check the official pages for exact button names.

You may also like

• AI Automation for Beginners (the hub)
• Turn a blog post into LinkedIn and X posts with Claude
• Draft WordPress posts from a spreadsheet with Claude
• Make.com Complete Beginner’s Guide
• How to use Claude AI
• Make AI Scenarios: automations that save hours
• The AI Tools Directory