Skip to content
Worix
BrowsePublish
Log inSign Up

task-product-seo-check

Multi-step TASK — checking how the merchant's product pages read to Google and AI shopping search — SEO titles, meta descriptions and the product data search relies on — shown on a card, with nothing in the store changed. Enter when: the merchant asks to check, audit or review the SEO of their products, or whether their products are ready for Google or AI search ("check my product SEO", "are my products ready for AI search?", "audit my best sellers' SEO"); the merchant chose products on the product SEO check card (its hidden note opens "The merchant chose products for the SEO check"). Do NOT enter: the merchant wants new SEO titles or meta descriptions written for their products (that is task-product-seo-rewrite); how much traffic or how many AI-assistant visits the store gets (read marketing-advice); a blog article or social post, or keywords for one (that is task-content-publish); a general analysis of the store, or Brand IQ (that is task-brand-iq-setup); greetings or small talk. Read this skill's full body BEFORE your first action — it carries the node graph you must report progress against, one node at a time.

4 downloads
Free
Reviewed
internal
task
marketing
requires-yepai-tools

Generated from tasks/product-seo-check/task.yaml by /task-authoring.

Do not edit here — edit the definition and regenerate.

name: task-product-seo-check description: >- Multi-step TASK — checking how the merchant's product pages read to Google and AI shopping search — SEO titles, meta descriptions and the product data search relies on — shown on a card, with nothing in the store changed. Enter when: the merchant asks to check, audit or review the SEO of their products, or whether their products are ready for Google or AI search ("check my product SEO", "are my products ready for AI search?", "audit my best sellers' SEO"); the merchant chose products on the product SEO check card (its hidden note opens "The merchant chose products for the SEO check"). Do NOT enter: the merchant wants new SEO titles or meta descriptions written for their products (that is task-product-seo-rewrite); how much traffic or how many AI-assistant visits the store gets (read marketing-advice); a blog article or social post, or keywords for one (that is task-content-publish); a general analysis of the store, or Brand IQ (that is task-brand-iq-setup); greetings or small talk. Read this skill's full body BEFORE your first action — it carries the node graph you must report progress against, one node at a time. kind: task task_name: "Product SEO check" label_template: "<products> SEO check" tags: [internal, task, marketing, requires-yepai-tools] license: MIT-0 nodes:

  • id: scope label: "Choosing products" purpose: "Put the product SEO check card up so the merchant picks which products to check — best sellers, a collection, the whole store or products they pick. The card stores their choice on the server." advance_by: user expects:
    • "the products to check, chosen on the card" tools:
    • yepairag_marketing__SHOW_SEO_CHECK_SCOPE next:
    • to: check when: "the merchant chose the products on the card — its hidden note says so"
  • id: check label: "Checking your products" purpose: "Run the check on the products the server holds and let the result card show it. The card is the reply and ends the task." advance_by: agent tools:
    • yepairag_marketing__RUN_PRODUCT_SEO_CHECK

Task — Product SEO check

Flow

flowchart TD
  scope("Choosing products") -->|the merchant chose the products on the card| check["Checking your products"]
  classDef terminal stroke-width:3px
  class check terminal

Rounded = waiting on the merchant · square = you are working · bold border = terminal.

scope

Choosing products — Put the product SEO check card up so the merchant picks which products to check — best sellers, a collection, the whole store or products they pick. The card stores their choice on the server.

  • The card is the only way products get chosen. Report scope, call SHOW_SEO_CHECK_SCOPE and end the turn with no text: the card is the whole reply. This holds when the merchant already named the products in their message ("my best sellers", "the Summer collection", "my whole store") — they pick that on the card, which stores it on the server; you have no other way to hand products to the check. Never call RUN_PRODUCT_SEO_CHECK before the card's note arrives.
  • If the tool answers duplicate: true, the card is already up — say nothing.

check

Checking your products — Run the check on the products the server holds and let the result card show it. The card is the reply and ends the task.

  • The card's note is the go-ahead. The hidden note "The merchant chose products for the SEO check: <label>. Next: call RUN_PRODUCT_SEO_CHECK." means the products are stored: report check, call RUN_PRODUCT_SEO_CHECK (it takes no arguments) and end the turn with no text — the result card is the whole reply, with every count, issue and store-wide item on it. If it answers duplicate: true, the card is already up — say nothing.

  • The same products again needs no card. Asked to check again ("check again", "run it again") with no other products named, report check and call RUN_PRODUCT_SEO_CHECK — the server still holds the products. Other products, or a check that answers that no products are chosen, is scope and its card.

  • A question about the result is answered from the result, in two or three plain sentences.

    • Name products by their title, never by an id.
    • Quote a figure exactly as the result gave it. Never count, add up or work out a share yourself, and never count the characters of a title or a description — the check already measured them.
    • Search issues (default title, title too long, duplicate title, stuffed title, missing, long, short or duplicate meta description, meta that repeats the title) are the ones you can rewrite: the merchant ticks those products on the card and presses Rewrite. Asked in chat to rewrite them, point to that button in one sentence — you cannot choose products for them.
    • Data issues (no barcode, no brand, no category, short description, missing alt text) and the store-wide items are the merchant's to fix in Shopify. Say what the item means and where they fix it in one sentence — for a store-wide item, from its own body. Never offer to write or change any of them.
    • A store-wide item marked unknown could not be read (usually a permission the store has not granted). Say exactly that; never guess it is fine or broken.
    • Never promise rankings, traffic or AI-search mentions from fixing anything.
  • Asked what to do for AI search ("do I need special markup for ChatGPT?", "should I make an AI version of my pages?", "should I block AI bots?"), answer from the store-wide items on the card and these rules — adapted from coreyhaines31/marketingskills, skills/ai-seo/SKILL.md (MIT, see NOTICE):

    Google's position (AI features optimization guide):

    "The best practices for SEO continue to be relevant because our generative AI features on Google Search are rooted in our core Search ranking and quality systems."

    Google explicitly says:

    • No special markup or files are required for AI Overviews or AI Mode
    • Don't chunk content for AI — write for people, organize with normal headings and paragraphs
    • Don't write separate content for AI — that risks "scaled content abuse" spam policy
    • Helpful, reliable, people-first content wins — same E-E-A-T standards as regular Search
    • No AI-specific Search Console reporting — use standard SEO metrics

    When in doubt, write for people and organize for clarity; that satisfies both camps.

    What NOT to do:

    • Write separate content "for AI". Same content should serve people and AI. Writing variants targeted at AI systems risks the scaled content abuse spam policy — Google's words.
    • Chunk pages into AI-bait fragments. Google's guide is direct: "Don't break your content into tiny pieces for AI to better understand it." Use normal paragraph + heading structure.
    • Pursue inauthentic mentions. Don't fabricate citations, invent awards, run "independent" review sites you own, or bulk-spam Reddit/Wikipedia for AI visibility. Fake or misleadingly sourced reviews can also break the FTC's 2024 reviews rule. Real participation only.
    • Treat every AI user agent as the same control. GPTBot, ClaudeBot, and Google-Extended have different documented purposes from OAI-SearchBot, Claude-SearchBot, and PerplexityBot. Decide separately for discovery, user retrieval, training, and grounding.
    • Keyword stuffing — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)

    Say it in the merchant's terms, in a few plain sentences — never paste this list.

How a task runs

This part is the same for every task; only the nodes differ.

1 — Entering the task. Report the first node before doing anything else. That report is what opens the run: it tells the backend a task has started and gives the merchant their first progress line.

2 — Entering each node. Report it the moment you enter, before doing that node's work. One report per node. A single turn usually passes through several nodes with no input from the merchant in between — reporting as you go is what lets them watch the work happen instead of staring at nothing until you finish. A node whose work is a single tool call still gets its report first.

3 — Reaching the end. A terminal node is one with no way out except back to itself. Reporting it completes the task — the backend works that out from the graph, so there is nothing extra for you to send.

4 — After completion. A completed task is not sealed. If the merchant later asks to change something, report the node that owns it again and the task is simply unfinished again. Never open a second task for a change to work you already did.

How to report

yepairag_task__REPORT_TASK_STEP
  task: "product-seo-check"
  node: "<the node you just entered>"
  • Two fields, both read straight off the graph above. The step's label, its number, the total and whether the task just completed are filled in by the backend — you cannot get them wrong because you do not send them.
  • The reply carries legal_next: the only nodes you may report next.
  • ok: false means nothing was recorded and the run has not moved. Correct the node id and report again rather than carrying on as if it had been accepted.
  • Never restate any of it to the merchant. It drives a progress bar they are already looking at.

Download

ZIP package — ready to use

Skill Info

Creator
Yepai
License
MIT-0
Downloads
4
Published
Nov 12, 2026
Updated
Nov 20, 2026