Skip to content
Get packs

Indexability Conflicts Auditor

Finds pages with contradictory robots.txt, noindex, and canonical signals that confuse search engines

Source Download skill
Repository
thedaviddias/Front-End-Checklist
Stars
74,632
Licence
MIT
Files
2 files

What it does

Once installed, the agent knows the rules for spotting SEO settings that contradict each other on a website, such as a page blocked in robots.txt that also carries a noindex tag, which search engines can never read. When asked to audit a site, it checks each page's robots.txt rule, meta robots tag, X-Robots-Tag HTTP header and canonical link, reports the conflicts it finds, and suggests fixes such as removing the robots.txt block or pointing canonicals at indexable URLs. It is a checklist-style guide: the files describe the logic and do not include a ready-made tool.

Great for

  • Developers or SEO specialists auditing a website's indexing settings
  • Teams investigating why pages appear in Google results they should not, or are missing when they should appear
  • Front-end teams reviewing robots.txt and meta robots configuration before a launch or migration

Skip it if

  • Users who need a finished, tested crawler: the skill describes how to check pages but ships no working audit script, so the agent would have to write one
  • Non-technical users who cannot verify changes; editing robots.txt or canonical tags incorrectly can deindex important pages
  • Sites where the search-engine behaviour described has changed; the guidance reflects Google's documentation as summarised in the files and should be checked against current docs

Try asking

  • “Audit my site for pages that are blocked in robots.txt but also have a noindex tag”
  • “Check whether any canonical tags point to pages marked noindex and suggest fixes”
  • “Review my robots.txt and meta robots settings for conflicting directives”
  • “Explain why a page is still showing in Google even though I set noindex”
Step-by-step guide: how to use Indexability Conflicts AuditorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    indexability-conflicts.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip indexability-conflicts.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip indexability-conflicts.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Ask the agent to list each conflict type separately so you can decide which intent (exclude from index or block crawling) applies to each URL.
  • Verify fixes afterwards with Google Search Console URL Inspection, as the skill recommends.
  • If you want the agent to actually fetch your pages, provide the URLs and allow it to make HTTP requests; the skill itself does not perform network access.

What's inside

  • references/rule.md
  • SKILL.md

Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.