SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
A skill your agent uses when applies to any site that uses structured data for rich results.
Install Schema Noindex Conflict
$ npx skills add thedaviddias/Front-End-Checklist --skill schema-noindex-conflict -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist schema-noindex-conflict --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/schema-noindex-conflict .claude/skills/schema-noindex-conflict && 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 "schema-noindex-conflict" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/schema-noindex-conflict into .claude/skills/schema-noindex-conflict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-noindex-conflict", 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/schema-noindex-conflictType 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 schema-noindex-conflict -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist schema-noindex-conflict --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/schema-noindex-conflict .agents/skills/schema-noindex-conflict && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "schema-noindex-conflict" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/schema-noindex-conflict into .agents/skills/schema-noindex-conflict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-noindex-conflict", 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 schema-noindex-conflict -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist schema-noindex-conflict --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/schema-noindex-conflict .cursor/skills/schema-noindex-conflict && 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 "schema-noindex-conflict" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/schema-noindex-conflict into .cursor/skills/schema-noindex-conflict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-noindex-conflict", 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/schema-noindex-conflict--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 schema-noindex-conflict -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist schema-noindex-conflict --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/schema-noindex-conflict .gemini/skills/schema-noindex-conflict && 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 "schema-noindex-conflict" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/schema-noindex-conflict into .gemini/skills/schema-noindex-conflict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-noindex-conflict", 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 schema-noindex-conflictInstalls 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 schema-noindex-conflict -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/schema-noindex-conflict .github/skills/schema-noindex-conflict && 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 "schema-noindex-conflict" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/schema-noindex-conflict into .github/skills/schema-noindex-conflict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-noindex-conflict", 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 schema-noindex-conflict -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 schema-noindex-conflict --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/schema-noindex-conflict .opencode/skills/schema-noindex-conflict && 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 "schema-noindex-conflict" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/schema-noindex-conflict into .opencode/skills/schema-noindex-conflict/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-noindex-conflict", 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
schema-noindex-conflict- GitHub stars
- 74k
- Token cost
- ~550 tokens
- SKILL.md length
- 255 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when applies to any site that uses structured data for rich results.
- Applies to any site that uses structured data for rich results
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Investigating why valid schema markup does not produce rich results in Google Search
What it does
Schema Noindex Conflict is an agent skill from thedaviddias/Front-End-Checklist. Use when applies to any site that uses structured data for rich results. Use when investigating why valid schema markup does not produce rich results in Google Search.
Its SKILL.md is about 550 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. 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
- Applies to any site that uses structured data for rich results
- Investigating why valid schema markup does not produce rich results in Google Search
Example prompts
- “/schema-noindex-conflict”
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
Links to these hosts (documentation or services it may open):
frontendchecklist.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
Schema Noindex Conflict loads about 550 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 255 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). 255 words, ~550 tokens.
Download SKILL.mdSave it as
.claude/skills/schema-noindex-conflict/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- schema-noindex-conflict
- description
- Use when applies to any site that uses structured data for rich results. Use when investigating why valid schema markup does not produce rich results in Google Search.
- metadata.category
- seo
- metadata.priority
- high
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/schema-noindex-conflict
Schema + Noindex Conflict
Investing in rich result schema on pages that are blocked from indexing wastes development effort — Google explicitly states it does not process structured data on noindexed pages.
Quick Reference
- Rich result schema (Review, Product, FAQ, etc.) has no effect on pages Google cannot index
- A page with
noindexwill not earn rich results even if it has valid structured data - Pages blocked in robots.txt are never fetched, so their schema is never processed
- Audit all pages with schema markup to confirm they are crawlable and indexable
Check
For every page containing a <script type='application/ld+json'> block with a rich result schema type, check: (1) Is the page blocked by robots.txt? (2) Does <meta name='robots'> contain noindex? (3) Does the canonical tag point to a different URL? Flag any conflicts.
Fix
For pages where rich results are desired: remove the noindex directive, unblock the URL in robots.txt, and ensure the canonical tag is self-referencing. If the page must remain noindexed, remove the schema markup — it serves no purpose.
Explain
Explain why Google does not process structured data on pages it cannot index, how to identify schema+noindex conflicts in a large site, and how to prioritize which pages need indexing to unlock rich results.
Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Schema + Noindex Conflict. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/schema-noindex-conflict
© 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/schema-noindex-conflict of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Schema Noindex Conflict 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 |
|---|---|---|---|---|---|---|
| Schema Noindex Conflict this skillthedaviddias/Front-End-Checklist | 74k | — | ~550 | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | MIT | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 455 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Portaljs Add Dcatdatopian/portaljs | 2.4k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Schema Markupfreekmurze/dotfiles | 1k | 15 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
SEO Optimizer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
Portaljs Add Dcat
datopian/portaljs
Make a PortalJS portal harvestable by national/EU/US open-data portals — emit standards-compliant DCAT catalog feeds (DCAT 2/3, DCAT-AP, DCAT-US, national profiles) in JSON-LD, Turtle, and RDF/XML…
Schema Markup
freekmurze/dotfiles
When the user wants to add, fix, or optimize schema markup and structured data on their site.
Geo
liangdabiao/GEO-Content-Optimizer-Skill
完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料， 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 （llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。
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
Categories
Questions about Schema Noindex Conflict
What does Schema Noindex Conflict do?
A skill your agent uses when applies to any site that uses structured data for rich results. Schema Noindex Conflict is an agent skill from thedaviddias/Front-End-Checklist. Use when applies to any site that uses structured data for rich results.
When should I use Schema Noindex Conflict?
Schema Noindex Conflict fits situations like: applies to any site that uses structured data for rich results; investigating why valid schema markup does not produce rich results in Google Search.
How do I install Schema Noindex Conflict in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill schema-noindex-conflict -a claude-code`. Or copy the skill folder (skills/schema-noindex-conflict in thedaviddias/Front-End-Checklist) into .claude/skills/schema-noindex-conflict in your project. Claude Code loads it when a task matches its description.
How do I install Schema Noindex Conflict in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill schema-noindex-conflict -a codex`. Or copy the skill folder (skills/schema-noindex-conflict in thedaviddias/Front-End-Checklist) into .agents/skills/schema-noindex-conflict in your project. Codex loads it when a task matches its description.
Can I use Schema Noindex Conflict 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 schema-noindex-conflict -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schema-noindex-conflict, .gemini/skills/schema-noindex-conflict, .github/skills/schema-noindex-conflict and .opencode/skills/schema-noindex-conflict in your project.
What does Schema Noindex Conflict need to run?
SKILL.md names no scripts, command-line tools or credentials: Schema Noindex Conflict is instructions for the agent only.
Does Schema Noindex Conflict access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Schema Noindex Conflict 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 Schema Noindex Conflict use?
Schema Noindex Conflict 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 Schema Noindex Conflict use?
About 550 tokens (SKILL.md is roughly 2.2k 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.1k tokens, read only when the agent opens those files.
What are the alternatives to Schema Noindex Conflict?
Skills that share tags, products or a category with Schema Noindex Conflict: SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars) and Portaljs Add Dcat (datopian/portaljs, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Schema Noindex Conflict?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 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.