Skip to main content
skill CX Codex

shopify-content — Claude Code skill: what it does

Creates and updates Shopify store content through the Admin API or browser automation. Use it for pages, blog posts, menus, redirects, and SEO fields.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jezweb/claude-skills --skill shopify-content -a claude-code
Open on GitHub

What shopify-content does

This skill handles Shopify pages, blog articles, navigation menus, redirects, SEO metadata, and metaobjects. It uses the GraphQL Admin API for pages, articles, and metaobjects, while redirects use the REST Admin API. Navigation changes are better handled through browser automation.

You need an Admin API token with read_content and write_content scopes. Menu work also requires read_online_store_navigation and write_online_store_navigation, so check token permissions before changing a store.

The workflow queries content again after edits to verify the result. Use pages for simple content such as About or FAQ material; use metaobjects for repeatable structured records with typed fields. Article publishing can be scheduled with publishDate.

What it helps with

  • create a Shopify page with HTML and SEO fields
  • publish an article in a Shopify blog
  • change store navigation menu items
  • add a redirect from an old path
  • update page SEO title and description

Example prompts for the agent

  • Create an About page in Shopify and fill in its SEO fields.
  • Add a Shopify blog article scheduled with publishDate.
  • Update the Shopify navigation menu by adding and reordering items.

How to install shopify-content

1Skills CLI (Vercel)

npx skills add jezweb/claude-skills --skill shopify-content -a claude-code

2Manually: put the files in place

~/.claude/skills/shopify-content/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/shopify-content/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about shopify-content

How do I install shopify-content in Claude Code?

Run npx skills add jezweb/claude-skills --skill shopify-content -a claude-code, then run npx skills add jezweb/claude-skills --skill shopify-content -a claude-code again. The skill file is at ~/.claude/skills/shopify-content/SKILL.md.

What does shopify-content do?

It manages Shopify pages, blog posts, navigation menus, redirects, and SEO metadata. It works through the Admin API or browser automation.

What permissions does shopify-content need?

Content work requires an Admin API token with read_content and write_content. Navigation updates also need read_online_store_navigation and write_online_store_navigation.

Source text

SKILL.md · MIT
---
name: shopify-content
description: "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."
compatibility: claude-code-only
---

# 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.

## Prerequisites

- Admin API access token with `read_content`, `write_content` scopes (use **shopify-setup** skill)
- For navigation: `read_online_store_navigation`, `write_online_store_navigation` scopes

## Workflow

### Step 1: Determine Content Type

| 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 |

### Step 2a: Create Pages

```bash
curl -s https://{store}/admin/api/2025-01/graphql.json \
  -H "Content-Type: application/json" \
  -H "X-Shopify-Access-Token: {token}" \
  -d '{
    "query": "mutation pageCreate($page: PageCreateInput!) { pageCreate(page: $page) { page { id title handle } userErrors { field message } } }",
    "variables": {
      "page": {
        "title": "About Us",
        "handle": "about",
        "body": "<h2>Our Story</h2><p>Content here...</p>",
        "isPublished": true,
        "seo": {
          "title": "About Us | Store Name",
          "description": "Learn about our story and mission."
        }
      }
    }
  }'
```

**Page body** accepts HTML. Keep it semantic:
- Use `<h2>` through `<h6>` for headings (the page title is `<h1>`)
- Use `<p>`, `<ul>`, `<ol>` for body text
- Use `<a href="...">` for links
- Avoid inline styles — the theme handles styling

### Step 2b: Create Blog Posts

Shopify blogs have a two-level structure: **Blog** (container) > **Article** (post).

**Find or create a blog**:

```graphql
{
  blogs(first: 10) {
    edges {
      node { id title handle }
    }
  }
}
```

Most stores have a default blog called "News". Create articles in it:

```graphql
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 }
  }
}
```

### Step 2c: Update Navigation Menus

Navigation menus have limited API support. Use browser automation:

1. Navigate to `https://{store}.myshopify.com/admin/menus`
2. Select the menu to edit (typically "Main menu" or "Footer menu")
3. Add, reorder, or remove menu items
4. Save changes

Alternatively, use the GraphQL `menuUpdate` mutation if the API version supports it:

```graphql
mutation menuUpdate($id: ID!, $items: [MenuItemInput!]!) {
  menuUpdate(id: $id, items: $items) {
    menu { id title }
    userErrors { field message }
  }
}
```

### Step 2d: Create Redirects

URL redirects use the REST API:

```bash
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"
    }
  }'
```

### Step 2e: Update SEO Metadata

SEO fields are on each resource (product, page, article). Update via the resource's mutation:

```graphql
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 }
  }
}
```

### Step 3: Verify

Query back the content to confirm:

```graphql
{
  pages(first: 10, reverse: true) {
    edges {
      node { id title handle isPublished createdAt }
    }
  }
}
```

Provide the admin URL and the live URL for the user to review:
- Admin: `https://{store}.myshopify.com/admin/pages`
- Live: `https://{store}.myshopify.com/pages/{handle}`

---

## Critical Patterns

### Page vs Metaobject

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.

### Blog SEO

Every blog post should have:
- **SEO title**: under 60 characters, includes primary keyword
- **Meta description**: under 160 characters, compelling summary
- **Handle**: clean URL slug with keywords
- **Image with alt text**: for social sharing and accessibility

### Content Scheduling

Use `publishDate` on articles for scheduled publishing. Pages publish immediately when `isPublished: true`.

### Bulk Content

For many pages (e.g. location pages, service pages), use a loop with rate limiting:

```bash
for page in pages_data:
    create_page(page)
    sleep(0.5)  # Respect rate limits
```

---

## Reference Files

- `references/content-types.md` — API endpoints, metaobject patterns, and browser-only operations

© jezweb · MIT · jezweb/claude-skills

Similar skills

Everything for Marketing and content →

From the same set54

react-native Performance guidelines and architecture patterns for React Native and Expo apps. Helps coding agents handle list virtualization, UI-thread animations, and navigation. CX Codex +1 1,300installs github-release Prepares a GitHub release by checking code for public publishing, creating a tag, and publishing through gh. Use it before making a repository public. CX Codex +1 1,300installs d1-migration Walks Cloudflare D1 migrations through Drizzle: generate the SQL, read it for traps, apply to local and remote, unstick partial runs. CX Codex +1 1,200installs proposal-writer Drafts client proposals, scopes of work, and quotes for service businesses. It helps web developers, agencies, and consultants close deals with structured terms. CX Codex +1 1,200installs project-docs project-docs scans your codebase to generate or refresh ARCHITECTURE.md, API_ENDPOINTS.md, and DATABASE_SCHEMA.md. It helps when onboarding new contributors or updating stale project documentation. CX Codex +1 1,200installs git-workflow Guides Git work for pull requests, merged-branch cleanup, conflict resolution, and monorepo release tags in Claude Code. CX Codex +1 1,200installs resume-cover-letter Writes a resume, CV or cover letter aimed at one specific job, with regional formatting and ATS rules in mind. CX Codex +1 1,200installs shopify-setup Configures Shopify CLI authentication and a stable Admin API access token for your store. Useful when connecting an agent to Shopify for product and content management. CX Codex +1 1,200installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor