OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add jezweb/claude-skills --skill shopify-content
Create and manage Shopify pages, blog posts, navigation menus, redirects, and SEO metadata via the Admin API or browser automation. Use whenever the user wants to add a page to a Shopify store, write a Shopify blog post, update the storefront navigation, manage redirects, or tune SEO metadata on a Shopify site.
npx skills add jezweb/claude-skills --skill shopify-content
Create and manage Shopify store content — pages, blog posts, navigation menus, and SEO metadata. Produces live content in the store via the Admin API or browser automation.
read_content, write_content scopes (use shopify-setup skill)read_online_store_navigation, write_online_store_navigation scopes| Content Type | API Support | Method |
|---|---|---|
| Pages | Full | GraphQL Admin API |
| Blog posts | Full | GraphQL Admin API |
| Navigation menus | Limited | Browser automation preferred |
| Redirects | Full | REST Admin API |
| SEO metadata | Per-resource | GraphQL on the resource |
| Metaobjects | Full | GraphQL Admin API |
Page body accepts HTML. Keep it semantic:
<h2> through <h6> for headings (the page title is <h1>)<p>, <ul>, <ol> for body text<a href="..."> for linksShopify blogs have a two-level structure: Blog (container) > Article (post).
Find or create a blog:
Most stores have a default blog called "News". Create articles in it:
Navigation menus have limited API support. Use browser automation:
https://{store}.myshopify.com/admin/menusAlternatively, use the GraphQL menuUpdate mutation if the API version supports it:
URL redirects use the REST API:
SEO fields are on each resource (product, page, article). Update via the resource's mutation:
Query back the content to confirm:
Provide the admin URL and the live URL for the user to review:
https://{store}.myshopify.com/admin/pageshttps://{store}.myshopify.com/pages/{handle}For simple content (About, Contact, FAQ), use pages. For structured, repeatable content (team members, testimonials, locations), use metaobjects — they have typed fields and can be queried programmatically.
Every blog post should have:
Use publishDate on articles for scheduled publishing. Pages publish immediately when isPublished: true.
For many pages (e.g. location pages, service pages), use a loop with rate limiting:
references/content-types.md — API endpoints, metaobject patterns, and browser-only operations{
blogs(first: 10) {
edges {
node { id title handle }
}
}
}mutation {
articleCreate(article: {
blogId: "gid://shopify/Blog/123"
title: "New Product Launch"
handle: "new-product-launch"
contentHtml: "<p>We're excited to announce...</p>"
author: { name: "Store Team" }
tags: ["news", "products"]
isPublished: true
publishDate: "2026-02-22T00:00:00Z"
seo: {
title: "New Product Launch | Store Name"
description: "Announcing our latest product range."
}
image: {
src: "https://example.com/blog-image.jpg"
altText: "New product collection"
}
}) {
article { id title handle }
userErrors { field message }
}
}mutation menuUpdate($id: ID!, $items: [MenuItemInput!]!) {
menuUpdate(id: $id, items: $items) {
menu { id title }
userErrors { field message }
}
}curl -s https://{store}/admin/api/2025-01/redirects.json \
-H "Content-Type: application/json" \
-H "X-Shopify-Access-Token: {token}" \
-d '{
"redirect": {
"path": "/old-page",
"target": "/new-page"
}
}'mutation {
pageUpdate(page: {
id: "gid://shopify/Page/123"
seo: {
title: "Updated SEO Title"
description: "Updated meta description under 160 chars."
}
}) {
page { id title }
userErrors { field message }
}
}{
pages(first: 10, reverse: true) {
edges {
node { id title handle isPublished createdAt }
}
}
}for page in pages_data:
create_page(page)
sleep(0.5) # Respect rate limits