Write Google titles and descriptions for a whole category
Every product in the category gets its own text in Google search results, in one afternoon's worth of clicks less.
What it replaces: an afternoon of back-office clicking
What you write to Claude
„write meta titles and meta descriptions for every product in Sofas that's missing them. under 60 and 160 characters, mention the fabric and the size”
The problem
Half my sofas have no description in Google results and the rest say the same thing. Doing it product by product in the back office takes forever.
What Claude does
- Claude finds the products in the category that are missing a Google title or description.
- It reads what makes each product different.
- It writes a unique title and description for each one.
- You see old and new side by side, and Claude saves only after your yes.
What you get
Every product in the category has its own title and description in Google. Product names and page addresses stay as they are.
You stay in control
You see every change before it is saved, nothing happens without your yes, and you can undo it later.
Related use cases
- Run a full SEO audit of your store
- Fix products that share the same title in Google
- Rewrite product descriptions in your brand's tone
For developers
- Area
- 1 · Content & SEO
- Connector
- daily connector
- In the free Audit
- no, paid version only
- For
- Store owner, Marketer / SEO
- Tools
- ps_search_products, ps_get_product, ps_update_product_content, ps_get_ready_job
Step by step
- Finds the products with ps_search_products (category_id, missing meta_title and meta_description, columns with features).
- Reads key data per product with ps_get_product: name, features, short description.
- Drafts unique titles and descriptions within the length limits, in your shop language.
- Calls ps_update_product_content without confirm for up to 50 products at once. Shows a preview with the old and new values side by side and waits for your approval.
- After your yes, saves it like the Save button in the back office and logs it in the change history. The batch shares one operation ID.
Safety
Every write shows a preview first and runs only after you approve it (one-time token, valid 30 minutes). Each change is logged and can be undone with ps_revert_change. A whole batch can be undone in one step by its operation ID.
Last updated: 2026-10-05