# Shopify Admin Agentic Organization Schema > Inject an Organization JSON-LD block (name, logo, sameAs social links, contactPoint) into the theme so AI agents can verify the store is a real, trusted brand and link it to its public identity. - Skill: `40rty-ai/shopify-admin-agentic-organization-schema` (Agent Skill) - Install (CLI): `npx skillmds@latest add 40rty-ai/shopify-admin-agentic-organization-schema` - Raw SKILL.md: https://api.skillmd.com/api/skills/40rty-ai/shopify-admin-agentic-organization-schema/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Design & Media - Author: 40rty-ai (https://skillmd.com/u/40rty-ai) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/40rty-ai/shopify-admin-agentic-organization-schema --- ## Purpose AI assistants check a site's `schema.org/Organization` JSON-LD to confirm it's the real brand (not a counterfeit or reseller) and to connect it to its public identity via `sameAs` (official socials, Wikipedia/Wikidata) and a machine-readable `contactPoint`. Without it, agents hesitate to recommend the store or send buyers to it. This skill builds an Organization JSON-LD block from the shop's data + supplied social links and injects it into the theme layout via a managed snippet. Fixes `org-schema`, `machine-contact`, and supports `wikidata-qid` (through `sameAs`). ## Prerequisites - Authenticated Shopify CLI session (`shopify auth login --store `) - Required API scopes: `read_themes`, `write_themes` ## Parameters All skills accept these universal parameters: | Parameter | Type | Required | Default | Description | |-----------|--------|----------|---------|-------------| | store | string | yes | — | Store domain (e.g., mystore.myshopify.com) | | format | string | no | human | Output format: `human` (default) or `json` | | dry_run | bool | no | true | Preview the snippet + injection without writing (defaults ON — edits the live theme) | Skill-specific parameters: | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | theme_id | string | no | — | Theme GID (defaults to published MAIN theme) | | logo_url | string | no | — | Absolute logo URL (else inferred from theme settings if available) | | same_as | string | no | — | Comma list of official profile URLs (Instagram, TikTok, LinkedIn, Wikipedia, Wikidata) | | contact_email | string | no | — | Customer-support email for `contactPoint` (else shop contactEmail) | | contact_phone | string | no | — | Optional support phone for `contactPoint` | ## Safety > ⚠️ Step 3 (`themeFilesUpsert`) writes a snippet and edits `layout/theme.liquid` in the LIVE theme. The change is additive (a `{% render %}` in ``), but it publishes immediately and a malformed edit to `theme.liquid` can break rendering. The skill writes the JSON-LD into its own snippet file and inserts a single managed `{% render 'agentic-organization-schema' %}` line inside a `# BEGIN/END` marker block. Defaults `dry_run: true`; duplicate the theme first. ## Workflow Steps 1. **OPERATION:** `shop` — query **Inputs:** none **Expected output:** Shop name, primary domain, contact email — the core Organization fields. 2. **OPERATION:** `themes` — query **Inputs:** `roles: [MAIN]`, `theme.files(filenames: ["layout/theme.liquid", "snippets/agentic-organization-schema.liquid"])` **Expected output:** Current layout (to inject the render tag) + whether the snippet already exists. 3. **OPERATION:** `themeFilesUpsert` — mutation **Inputs:** write `snippets/agentic-organization-schema.liquid` (the JSON-LD ` ``` ## Session Tracking **Claude MUST emit the following output at each stage. This is mandatory.** **On start**, emit: ``` ╔══════════════════════════════════════════════╗ ║ SKILL: ║ ║ Store: ║ ║ Started: ║ ╚══════════════════════════════════════════════╝ ``` **After each step**, emit: ``` [N/TOTAL] → Params: → Result: ``` If `dry_run: true`, prefix every mutation step with `[DRY RUN]` and do not execute it. **On completion**, emit: For `format: human` (default): ``` ══════════════════════════════════════════════ OUTCOME SUMMARY : Errors: 0 Output: ══════════════════════════════════════════════ ``` For `format: json`, emit: ```json { "skill": "", "store": "", "started_at": "", "completed_at": "", "dry_run": false, "steps": [ { "step": 1, "operation": "", "type": "query", "params_summary": "", "result_summary": "", "skipped": false } ], "outcome": { "metric_key": 0, "errors": 0, "output_file": null } } ``` ## Output Format `human`: the generated JSON-LD + the layout diff showing the one inserted render line. `json`: `{ theme_id, json_ld, layout_modified: true|false, wrote: true|false, errors }`. ## Error Handling | Error | Cause | Recovery | |-------|-------|----------| | `THROTTLED` | API rate limit | Wait 2s, retry up to 3 times | | `ACCESS_DENIED` | Missing `write_themes` | Abort; output the snippet so it can be pasted manually | | `userErrors` on layout upsert | Liquid syntax issue | Write the snippet only, skip the layout edit, surface the manual `{% render %}` instruction | ## Best Practices - Only put REAL, official URLs in `sameAs` — a wrong profile undermines trust rather than building it. Wikipedia/Wikidata links are especially strong identity signals. - Inject via a snippet + a single managed render line; never paste JSON-LD inline into `theme.liquid` so re-runs and rollback stay clean. - Use an absolute, HTTPS `logo` URL (a square PNG works best for knowledge panels). - Duplicate the theme first and keep `dry_run: true` until you've read the layout diff.