SEO Setup
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
A skill your agent uses when generating or auditing any <script type='application/ld+json' blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or…
Install JSON Ld Valid
$ npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist json-ld-valid --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/json-ld-valid .claude/skills/json-ld-valid && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "json-ld-valid" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-valid into .claude/skills/json-ld-valid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "json-ld-valid", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-validType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist json-ld-valid --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/json-ld-valid .agents/skills/json-ld-valid && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "json-ld-valid" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-valid into .agents/skills/json-ld-valid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "json-ld-valid", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist json-ld-valid --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/json-ld-valid .cursor/skills/json-ld-valid && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "json-ld-valid" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-valid into .cursor/skills/json-ld-valid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "json-ld-valid", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/json-ld-valid--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist json-ld-valid --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/json-ld-valid .gemini/skills/json-ld-valid && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "json-ld-valid" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-valid into .gemini/skills/json-ld-valid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "json-ld-valid", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist json-ld-validInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/json-ld-valid .github/skills/json-ld-valid && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "json-ld-valid" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-valid into .github/skills/json-ld-valid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "json-ld-valid", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist json-ld-valid --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/json-ld-valid .opencode/skills/json-ld-valid && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "json-ld-valid" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/json-ld-valid into .opencode/skills/json-ld-valid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "json-ld-valid", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
json-ld-valid- GitHub stars
- 74k
- Token cost
- ~828 tokens
- SKILL.md length
- 367 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when generating or auditing any <script type='application/ld+json' blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or…
- Works in 6 steps: Parse the JSON-LD with JSON.parse() —… → Ensure @context is exactly… → Verify the @type value against… → …
- Auditing any <script type=application/ld+json blocks
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Reaches schema.org
What it does
JSON Ld Valid is an agent skill from thedaviddias/Front-End-Checklist. Use when generating or auditing any <script type='application/ld+json' blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or investigating why rich results are not appearing in Google Search Console.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Marketing & SEO, covering Schema markup. It works with Google Search Console. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Auditing any <script type=application/ld+json blocks
- Implementing structured data for articles
- Local businesses
- Investigating why rich results are not appearing in Google Search Console
Example prompts
- “application/ld+json”
- “/json-ld-valid”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Parse the JSON-LD with JSON.parse() — fix any syntax errors (trailing commas, single quotes, missing brackets).
- Ensure @context is exactly "https://schema.org" (not "http://schema.org" or omitted).
- Verify the @type value against schema.org types.
- Add required properties for the type
- Validate at https://search.google.com/test/rich-results
- Validate JSON syntax at https://jsonlint.com
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
schema.org
Also links to:
search.google.comjsonlint.comfrontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
JSON Ld Valid loads about 828 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 367 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 367 words, ~828 tokens.
Download SKILL.mdSave it as
.claude/skills/json-ld-valid/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- json-ld-valid
- description
- Use when generating or auditing any `<script type='application/ld+json'>` blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or investigating why rich results are not appearing in Google Search Console.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/json-ld-valid
Use valid JSON-LD structured data
Invalid JSON-LD is silently ignored by Google — there are no error messages in search results, only the absence of rich results. Invalid structured data means no eligibility for rich results (stars, FAQs, breadcrumbs, etc.) that increase click-through rates.
Quick Reference
- JSON-LD must be valid JSON, reference
@context: 'https://schema.org', and include all required properties for the chosen@type - Invalid JSON (unclosed brackets, missing commas) causes the entire block to be silently ignored by Google
- Validate with Google's Rich Results Test before deploying structured data changes
Check
Find all <script type='application/ld+json'> elements on the page. For each: (1) Attempt to parse the content as JSON — flag syntax errors. (2) Verify @context is set to 'https://schema.org'. (3) Verify @type is a valid schema.org type. (4) For the detected type, check required properties are present (e.g., Article requires headline, author, datePublished; Product requires name; FAQPage requires mainEntity). (5) Run through Google's Rich Results Test API if available.
Fix
- Parse the JSON-LD with
JSON.parse()— fix any syntax errors (trailing commas, single quotes, missing brackets). - Ensure
@contextis exactly"https://schema.org"(not"http://schema.org"or omitted). - Verify the
@typevalue against schema.org types. - Add required properties for the type:
- Article: headline, author (with @type Person and name), datePublished
- Product: name (and ideally offers, description)
- FAQPage: mainEntity array with Question and acceptedAnswer
- BreadcrumbList: itemListElement array with ListItem, position, name, item
- Validate at https://search.google.com/test/rich-results
- Validate JSON syntax at https://jsonlint.com
Show full SKILL.md (127 more words)Show less
Explain
Google uses JSON-LD structured data to generate rich results — enhanced search result formats that include stars, images, expandable Q&As, and other features. Invalid JSON-LD is ignored entirely: no rich results are generated, and no error is reported to you. Only by testing with the Rich Results Test can you discover validation failures. Correct, complete JSON-LD is a prerequisite for rich result eligibility.
Code Review
Extract all <script type='application/ld+json'> element contents. Run JSON.parse() on each — catch and report parse errors. Validate that @context equals 'https://schema.org'. Check @type against a whitelist of common valid types. For each type, validate required properties are present and non-empty. Report the first validation error found for each block.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/json-ld-valid
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/json-ld-valid of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
JSON Ld Valid next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| JSON Ld Valid this skillthedaviddias/Front-End-Checklist | 74k | — | ~828 | Automated safety check: Pass | MIT | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| Google Search SEO Guidelittleben/awesomeAgentskills | 188 | 2 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Global SEO Growthminhnv0807/ai-business-skills | 610 | — | ~5k | Automated safety check: Pass | MIT | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| 32 SEO Growthminhnv0807/ai-business-skills | 610 | — | ~5k | Automated safety check: Pass | MIT |
Similar skills
Google Search SEO Guide
littleben/awesomeAgentskills
Answers Google Search optimization questions from reference files covering crawling, indexing, structured data, Search Console and site visibility, drawn from Google's documentation.
Global SEO Growth
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
SEO
Nexus-JPF/note-companion
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
32 SEO Growth
minhnv0807/ai-business-skills
Khi nguoi dung muon tang traffic tu SEO, AI SEO, GEO/AEO, Google, ChatGPT, Perplexity, schema, structured data, llms.txt, programmatic SEO, local SEO, directory submissions, Product Hunt…
SEO Implement
indranilbanerjee/digital-marketing-pro
Execute approved SEO changes on a connected WordPress or Webflow CMS — meta title/description updates, JSON-LD schema deployment, canonical URLs, 301/302 redirects, and Search Console indexing…
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Works with
Categories
Questions about JSON Ld Valid
What does JSON Ld Valid do?
A skill your agent uses when generating or auditing any <script type='application/ld+json' blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or…. JSON Ld Valid is an agent skill from thedaviddias/Front-End-Checklist. Use when generating or auditing any <script type='application/ld+json' blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or investigating why rich results are not appearing in Google Search Console.
When should I use JSON Ld Valid?
JSON Ld Valid fits situations like: auditing any <script type=application/ld+json blocks; implementing structured data for articles; local businesses; investigating why rich results are not appearing in Google Search Console.
How do I install JSON Ld Valid in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a claude-code`. Or copy the skill folder (skills/json-ld-valid in thedaviddias/Front-End-Checklist) into .claude/skills/json-ld-valid in your project. Claude Code loads it when a task matches its description.
How do I install JSON Ld Valid in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a codex`. Or copy the skill folder (skills/json-ld-valid in thedaviddias/Front-End-Checklist) into .agents/skills/json-ld-valid in your project. Codex loads it when a task matches its description.
Can I use JSON Ld Valid in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill json-ld-valid -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/json-ld-valid, .gemini/skills/json-ld-valid, .github/skills/json-ld-valid and .opencode/skills/json-ld-valid in your project.
What does JSON Ld Valid need to run?
SKILL.md names no scripts, command-line tools or credentials: JSON Ld Valid is instructions for the agent only.
Does JSON Ld Valid access the network?
SKILL.md names 4 domains. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. As links in the text: search.google.com, jsonlint.com and frontendchecklist.io. This is read from the text; nothing was executed.
Is JSON Ld Valid safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does JSON Ld Valid use?
JSON Ld Valid is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does JSON Ld Valid use?
About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to JSON Ld Valid?
Skills that share tags, products or a category with JSON Ld Valid: SEO Setup (alisamadiii/Portfolio, 180 stars), Google Search SEO Guide (littleben/awesomeAgentskills, 188 stars), Global SEO Growth (minhnv0807/ai-business-skills, 610 stars) and SEO (Nexus-JPF/note-companion, 870 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains JSON Ld Valid?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,412 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.