Guide · Agent skill
How to use the Indexability Auditor agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Indexability Auditor is an agent skill from the Front-End Checklist project (thedaviddias/Front-End-Checklist, skills/indexability, MIT licensed). It teaches an AI agent to check whether important pages are blocked from Google Search by noindex directives, HTTP headers or robots.txt rules. This guide explains what the skill does, how to install it, how to ask for an audit and what to check afterwards.
Indexability Auditorthedaviddias/Front-End-Checklist · MIT Download the skill Quick start
- 1Download the ZIP. Get the indexability skill ZIP from this directory page.
- 2Unzip the skill. Extract it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder.
- 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill there.
- 4List your important pages. Pick the homepage, key landing pages, product pages and top blog posts you want audited.
- 5Ask for an audit. Describe the problem in plain words and name the site and pages to check.
- 6Review the findings. Check each flagged noindex tag, header or Disallow rule and decide whether it should be removed.
- 7Confirm in Search Console. Use URL Inspection to check indexing, request indexing for fixed pages, and watch the Coverage report.
What is an agent skill?
An agent skill is a folder of instructions that an AI agent loads when a task matches the skill's description. The skill tells the agent what to check, in what order, and how to report the results. The folder for this skill includes a SKILL.md file and a references/rule.md file with more detail.
What the Indexability Auditor makes the agent do
Once installed, the agent checks important pages such as the homepage, landing pages, product pages and top blog posts. For each page it looks at three possible blocks: a robots meta tag containing noindex, an X-Robots-Tag HTTP response header containing noindex, and a robots.txt Disallow rule that matches the page's path. It then flags any important page with one of these blocks.
The skill also suggests fixes for common frameworks and servers, such as removing a noindex tag, editing server or CDN header rules, checking vercel.json headers, or narrowing a Disallow rule. It reminds you to confirm the result in Google Search Console.
- Checks robots meta tags for noindex
- Checks X-Robots-Tag headers for noindex
- Checks robots.txt Disallow rules against the page path
- Suggests fixes for Next.js, Nginx, Apache, CDNs and Vercel
- Reminds you to use URL Inspection and the Coverage report in Search Console
Install the skill from the ZIP download
Download the ZIP for the indexability skill from this directory page. Then unzip it into one of these locations, depending on who should use it:
- Personal skills: unzip into ~/.claude/skills/
- Project skills: unzip into the project's .claude/skills/ folder
- Claude apps: upload the skill under Settings → Capabilities → Skills
Trigger the skill with a natural request
You do not need a special command. The skill's description says it applies when you ask for an audit for accidental noindex directives, ask why important pages are not appearing in Google Search, or ask about CMS settings that control indexing by page or category. Describe the problem in your own words and include the pages or site involved.
- Audit https://example.com's key landing pages for noindex tags and robots.txt blocks
- Why are my product pages not showing up in Google Search? Check the headers and robots.txt
- Review our CMS indexing settings before we move staging to production
- Our organic traffic dropped last week. Check whether we blocked any important pages from indexing
What the skill needs and how it stays safe
The skill needs access to the site's HTML, HTTP response headers and robots.txt, either through browsing or through files you provide. Checking Google Search Console for URL Inspection and requesting indexing is a manual step that you do yourself; the skill describes it but does not connect to Search Console. The skill runs no scripts and uses no network access of its own.
The skill pushes toward removing blocks. That is the right move for pages you want in search, but it can weaken privacy or draft controls if applied to pages that should stay out of search. Review each suggested change before you apply it.
- Runs scripts: no
- Uses network: no
- Does not change live settings automatically
- Does not connect to Google Search Console
Tips for a useful audit
Give the agent a short list of pages that matter most, such as the homepage and a few product or landing pages. The skill is built around important pages, so a focused list gives clearer results than a whole-site request.
After you remove a block, use URL Inspection in Google Search Console and request indexing, then watch the Coverage report over the following weeks. Indexing does not happen instantly.
- Start with a list of 5 to 10 important URLs
- Check staging-to-production moves for leftover noindex settings
- Confirm each fix in Search Console rather than assuming it worked
What people use it for
- An SEO specialist checking why organic traffic fell after a site change
- A developer reviewing a staging site before it goes live
- A site owner checking CMS settings that apply noindex to whole page categories
- A developer checking vercel.json or server header config for X-Robots-Tag rules
Frequently asked questions
How do I install the Indexability Auditor skill?
Download the ZIP from the directory page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
Is the Indexability Auditor free?
The skill is published under the MIT licence in the thedaviddias/Front-End-Checklist repository. Check the licence file in that repository for the full terms. Any model or app subscription you use with it is separate.
What does the skill check for?
It checks important pages for a robots meta tag containing noindex, an X-Robots-Tag HTTP header containing noindex, and robots.txt Disallow rules that block the page's path. It then suggests how to remove those blocks.
Does it need access to Google Search Console?
No. The skill does not connect to Search Console. It tells you to use URL Inspection and request indexing yourself, and to watch the Coverage report.
Why is my page not showing up in Google?
A page blocked by noindex, an X-Robots-Tag header or a robots.txt rule cannot appear in search results. Run the audit on that page, then confirm its status with URL Inspection in Search Console.
Does the skill run scripts or use the network?
According to its listing, it runs no scripts and uses no network access. It works from the HTML, headers and robots.txt you provide or that the agent can browse.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are an SEO specialist, developer or site owner who needs a focused check for accidental indexing blocks on key pages. Pick something else if you want content quality or keyword advice, or if your pages should intentionally stay out of search, since the skill pushes toward removing blocks.
Download the skill