Shopify Content

Create and manage Shopify pages, blog posts, navigation menus, redirects, and SEO metadata via the Admin API or browser automation.

You say
Buy it · $69 Read it before you buy $69 Written by jezweb · unverified publisher
Context cost
2.1k tokensestimated from the bundle, loaded when it triggers
Bundle
2 files · 8.6 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

e-commerceseoshopify

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md5.7 kB · 210 lines
--- 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 ---
7# Shopify Content
8
9Create 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.
10
11## Prerequisites
12
13- Admin API access token with read_content, write_content scopes (use **shopify-setup** skill)
14- For navigation: read_online_store_navigation, write_online_store_navigation scopes
15
16## Workflow
17
18### Step 1: Determine Content Type
19
20| Content Type | API Support | Method |
21|-------------|-------------|--------|
22| Pages | Full | GraphQL Admin API |
23| Blog posts | Full | GraphQL Admin API |
24| Navigation menus | Limited | Browser automation preferred |
25| Redirects | Full | REST Admin API |
26| SEO metadata | Per-resource | GraphQL on the resource |
27| Metaobjects | Full | GraphQL Admin API |
28
29### Step 2a: Create Pages
30
31```bash
32curl -s https://{store}/admin/api/2025-01/graphql.json \
33 -H "Content-Type: application/json" \
34 -H "X-Shopify-Access-Token: {token}" \
35 -d '{
36 "query": "mutation pageCreate($page: PageCreateInput!) { pageCreate(page: $page) { page { id title handle } userErrors { field message } } }",
37 "variables": {
38 "page": {
39 "title": "About Us",
40 "handle": "about",
41 "body": "<h2>Our Story</h2><p>Content here...</p>",
42 "isPublished": true,
43 "seo": {
44 "title": "About Us | Store Name",
45 "description": "Learn about our story and mission."
46 }
47 }
48 }
49 }'
50```
51
52**Page body** accepts HTML. Keep it semantic:
53- Use <h2> through <h6> for headings (the page title is <h1>)
54- Use <p>, <ul>, <ol> for body text
55- Use <a href="..."> for links
56- Avoid inline styles — the theme handles styling
57
58### Step 2b: Create Blog Posts
59
60Shopify blogs have a two-level structure: **Blog** (container) > **Article** (post).
61
62**Find or create a blog**:
63
64```graphql
65{
66 blogs(first: 10) {
67 edges {
68 node { id title handle }
69 }
70 }
71}
72```
73
74Most stores have a default blog called "News". Create articles in it:
75
76```graphql
77mutation {
78 articleCreate(article: {
79 blogId: "gid://shopify/Blog/123"
80 title: "New Product Launch"
81 handle: "new-product-launch"
82 contentHtml: "<p>We're excited to announce...</p>"
83 author: { name: "Store Team" }
84 tags: ["news", "products"]
85 isPublished: true
86 publishDate: "2026-02-22T00:00:00Z"
87 seo: {
88 title: "New Product Launch | Store Name"
89 description: "Announcing our latest product range."
90 }
91 image: {
92 src: "https://example.com/blog-image.jpg"
93 altText: "New product collection"
94 }
95 }) {
96 article { id title handle }
97 userErrors { field message }
98 }
99}
100```
101
102### Step 2c: Update Navigation Menus
103
104Navigation menus have limited API support. Use browser automation:
105
1061. Navigate to https://{store}.myshopify.com/admin/menus
1072. Select the menu to edit (typically "Main menu" or "Footer menu")
1083. Add, reorder, or remove menu items
1094. Save changes
110
111Alternatively, use the GraphQL menuUpdate mutation if the API version supports it:
112
113```graphql
114mutation menuUpdate($id: ID!, $items: [MenuItemInput!]!) {
115 menuUpdate(id: $id, items: $items) {
116 menu { id title }
117 userErrors { field message }
118 }
119}
120```
121
122### Step 2d: Create Redirects
123
124URL redirects use the REST API:
125
126```bash
127curl -s https://{store}/admin/api/2025-01/redirects.json \
128 -H "Content-Type: application/json" \
129 -H "X-Shopify-Access-Token: {token}" \
130 -d '{
131 "redirect": {
132 "path": "/old-page",
133 "target": "/new-page"
134 }
135 }'
136```
137
138### Step 2e: Update SEO Metadata
139
140SEO fields are on each resource (product, page, article). Update via the resource's mutation:
141
142```graphql
143mutation {
144 pageUpdate(page: {
145 id: "gid://shopify/Page/123"
146 seo: {
147 title: "Updated SEO Title"
148 description: "Updated meta description under 160 chars."
149 }
150 }) {
151 page { id title }
152 userErrors { field message }
153 }
154}
155```
156
157### Step 3: Verify
158
159Query back the content to confirm:
160
161```graphql
162{
163 pages(first: 10, reverse: true) {
164 edges {
165 node { id title handle isPublished createdAt }
166 }
167 }
168}
169```
170
171Provide the admin URL and the live URL for the user to review:
172- Admin: https://{store}.myshopify.com/admin/pages
173- Live: https://{store}.myshopify.com/pages/{handle}
174
175---
176
177## Critical Patterns
178
179### Page vs Metaobject
180
181For 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.
182
183### Blog SEO
184
185Every blog post should have:
186- **SEO title**: under 60 characters, includes primary keyword
187- **Meta description**: under 160 characters, compelling summary
188- **Handle**: clean URL slug with keywords
189- **Image with alt text**: for social sharing and accessibility
190
191### Content Scheduling
192
193Use publishDate on articles for scheduled publishing. Pages publish immediately when isPublished: true.
194
195### Bulk Content
196
197For many pages (e.g. location pages, service pages), use a loop with rate limiting:
198
199```bash
200for page in pages_data:
201 create_page(page)
202 sleep(0.5) # Respect rate limits
203```
204
205---
206
207## Reference Files
208
209- references/content-types.md — API endpoints, metaobject patterns, and browser-only operations
210
In the file
SKILL.md783 words
Files2
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈100
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,050
on trigger
The instruction body and 1 supporting file, read only when the skill fires.
1.1%
of a 200k window
Ten skills this size would take about 11% of the window before you open a file.
050k100k150k200k context window

2.1k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

2 files, 8.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md5.7 kB
  • references/content-types.md2.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 2 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$69 once
Shopify Content · MIT · jezweb
one-time
Price$69 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$69
Referencejezweb/shopify-content

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

JE
jezweb

Publishes on mcprush.

0 servers listed3 skills listednot claimed
Profile
Publisher
Servers0