/seo-content-product-page

name: seo-content-product-page
description: "Optimize e-commerce product pages (PDPs) for Google and for AI assistants that now recommend products directly. Input: a product page or description (Shopify, WooCommerce, Magento, BigCommerce, PrestaShop, Wix, Webflow, or custom). Output: a rewritten PDP with unique copy, FAQ and definition blocks, review and real-photo rules, title/H1/slug/meta, out-of-stock handling, Product schema, and ChatGPT Shopping feed notes. Use to write, rewrite, or audit a product page, or when PDPs get no traffic or traffic without sales."
license: MIT
metadata:
  author: "Sorank (https://sorank.com)"
  version: "1.0.0"

Product Page SEO and GEO

This skill optimizes e-commerce product pages (PDPs) so they rank in Google and get recommended directly by AI assistants, using field rules derived from 115+ real agency audits combined with sourced 2026 practices.

Company knowledge first (Obsidian)

If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before acting: brand and product facts, target keywords, competitors, and the SEO action log of what was already tried. Ground every recommendation in that context instead of asking the user for facts the vault already holds. At the end of the session, append the actions taken to the vault's SEO action log so the next session starts informed. Vault structure, read-first and write-back protocols: the obsidian-brain skill.

When to use

Use this skill when the user:

• Writes or rewrites a product description or a full product page
• Audits a PDP with no rankings, no traffic, or traffic without sales
• Asks how to get products recommended by ChatGPT, Perplexity, Claude, Gemini, or Google AI Overviews
• Handles out-of-stock, seasonal, or discontinued product URLs
• Reviews PDP titles, H1s, slugs, meta descriptions, images, reviews, trust badges, or Product schema
• Works on Shopify, WooCommerce, Magento, BigCommerce, PrestaShop, Wix, Webflow Ecommerce, or a custom storefront

Hand off neighboring cases:

| Case | Skill | |---|---| | Category, collection, or listing pages (PLPs) | seo-content-collection-page | | Service or offer pages outside e-commerce | seo-content-service-page | | Supporting blog content for a product | seo-content-blog | | Keyword and intent mapping | seo-keyword-research | | Whole-site audit | seo-geo-audit | | Rendering, crawl access, AI crawler behavior | seo-technical | | JSON-LD implementation details | seo-schema-markup | | Passage-level citability writing | geo-visibility | | Measuring AI citations and referrals | geo-tracking |

Workflow

1. Confirm the target query and its intent. A PDP targets transactional queries only: product name searches, "buy X", "X price". If the query is informational ("how to choose X", "X vs Y"), stop and plan a blog post that links to the PDP instead; map this with the seo-keyword-research skill. Why: Google types its result pages by intent, so a PDP almost never ranks for an informational query regardless of quality. 2. Fetch the page as crawlers see it. Use curl to get the raw server HTML and compare it with the browser-rendered page. Anything absent from the raw HTML is invisible to AI assistants and unreliable for Google. For an automated full check, run the bundled audit script from the seo-geo-audit skill (scripts/seo_audit.py). 3. Score the page against the rules and thresholds below. Record every gap with a priority. 4. Rewrite the content blocks: description, specs, comparison table, FAQ, definitions. 5. Fix the metadata: title, H1, slug, meta description. 6. Check schema essentials (Product, Offer, AggregateRating, Review) and confirm the markup mirrors the visible page. Implementation belongs to the seo-schema-markup skill. 7. Apply the GEO layer below: every fact in server HTML, page self-sufficiency, product feed. 8. Deliver the result in the exact output format at the end of this document.

Rules and thresholds

| Element | Rule | Basis | |---|---|---| | Description length | 150-200 words minimum, unique, benefits first | Field heuristic from 115+ agency audits | | Description source | Never the manufacturer boilerplate | Duplicate content behavior (section 1) | | FAQ block | 3+ real buyer questions at the bottom of the PDP | Field heuristic from 115+ agency audits | | Definitions block | About 5 technical terms explained in plain language | Field heuristic from 115+ agency audits | | Reviews | Stars and count visible at the top of the page | Field heuristic from 115+ agency audits | | Images | Real product photos only on PDPs, never AI-generated | Trust + Merchant Center compliance | | Title tag | Product + category (+ brand), unique, about 60 characters | Standard practice | | H1 | The product name, exactly one H1 | Standard practice | | Slug | Main keyword, descriptive words, hyphens, no SKU codes | Measured correlation (Ahrefs, see Sources) | | Meta description | Handwritten, about 150-160 characters | Field heuristic from 115+ agency audits | | Out of stock | HTTP 200 + availability markup + alternatives, never 404 | Standard practice | | CRO threshold | Below about 100 organic visitors/day, build traffic before conversion tweaks | Field heuristic from 115+ agency audits | | Punctuation | Zero em dashes and zero en dashes, replaced by commas | House rule, most recognizable AI-writing tell |

Punctuation, non-negotiable: never leave an em dash (U+2014) or an en dash (U+2013) in copy that goes live on a client site. Replace every one with a comma; use a colon, a period or parentheses when a comma loses the sense. The em dash is the single most recognizable tell of AI-written text, and one is enough for a shopper, or the client, to file the page as machine output. The rule covers every field you deliver: description, FAQ answers, definitions block, title tag, H1, meta description, alt text, comparison table cells, schema