What is SearchFit SEO?
SearchFit SEO is a free plugin that brings
SEO tools right into Claude Code. It is made by SearchFit.ai. Once you install
it, you can check your website's SEO by typing a simple command.
The plugin's skills cover
site audits, technical SEO, on-page fixes, broken links, internal linking,
schema markup, content planning and keyword grouping. It can even check how
your site shows up in AI tools like ChatGPT and Gemini.
The best part is that it works on both a live website and your source code. So you can find a problem and fix it in the same place.
SEO audits at $0 cost
You do not need to pay for any SEO tool to use SearchFit SEO. The plugin itself is free. If you already have a Claude subscription, you can run every command in this post without spending a single extra rupee or dollar.
Paid SEO tools often charge a monthly fee. With this setup, your Claude subscription is all you need. The only thing to keep in mind is that these commands count toward your plan's normal usage limits, just like any other Claude Code task. A full audit of a large website uses more of your limit than a quick single-page check.
Getting started
Setting up SearchFit SEO takes three short
steps.
Step 1: Start Claude Code
Open your terminal, go to your project
folder and start Claude Code:
Step 2: Install the plugin
You can install it in one of two ways.
Option A: Inside Claude Code. Type this in the Claude Code session:
/plugin install
searchfit-seo@claude-plugins-official
This does not install the plugin right
away. It first opens the plugin details so you can see what it adds. Then you
pick a scope: just for you, for everyone on the project, or only for you in
this project.
Option B: From your regular command
prompt. You can also install it without opening
Claude Code:
claude plugin install
searchfit-seo@claude-plugins-official
This installs the plugin for your user
account by default.
The part after the @ sign, claude-plugins-official, is the name of Anthropic's official plugin marketplace. Claude
Code adds it for you the first time you start an interactive session. On a
brand new machine where you have never opened Claude Code, run claude plugin marketplace add
anthropics/claude-plugins-official first.
Step 3: Reload the plugins
If Claude Code is already open, load the
new plugin with:
You need this after installing from the
command prompt (Option B). With Option A, Claude Code usually tells you if a
reload is needed and often runs it for you. If you simply start a new Claude
Code session, the plugin loads on its own.
To confirm it worked, type /searchfit-seo: and you should see the plugin's commands in the list.
1. Full site audit: /searchfit-seo:seo-audit
This is the command to start with. It runs
a complete SEO audit on a live website or on a codebase.
How to use it
/searchfit-seo:seo-audit
<url> # audit a
live website
/searchfit-seo:seo-audit <path> # audit a codebase
/searchfit-seo:seo-audit # audit the current
project folder
/searchfit-seo:seo-audit <url> as an HTML file # same audit, saved as a report file
For example, to audit a website:
/searchfit-seo:seo-audit
https://example.com/
The results show up right there in your terminal.
If you want a report you can open in a browser or share with your
team, add "as an HTML file" at the end:
/searchfit-seo:seo-audit
https://example.com/ as an HTML file
This saves a standalone HTML report in your
current folder.
What it checks
•
Crawlability: robots.txt, sitemaps, noindex tags, canonical tags and orphan pages
•
Head tags: title, meta description, Open Graph, Twitter Card and viewport
•
Headings: a single H1, a clean heading order, keywords and no empty headings
•
Images: alt text quality, modern formats, width and height, and lazy
loading
•
Performance signals: render-blocking files and heavy client-side JavaScript
•
Structured data: whether JSON-LD is there, whether the type fits the page, and
whether required properties are filled
•
Internal linking: broken links, thin pages and anchor text
•
Mobile and accessibility: responsive layout, tap target size, font size and color contrast
What you get back
You get a score out of 100. The findings
are sorted into four groups: Critical, Warnings, Opportunities and Passing.
Every finding points to the exact URL, or to the file and line number in your
code.
2. Quick page check: /searchfit-seo:seo-check
This is the fast, single-page version of
the audit. It checks one page against a fixed checklist in a few seconds. It
looks at the title, meta tags, headings, images and structured data.
How to use it
/searchfit-seo:seo-check
<url> # check
one live page
/searchfit-seo:seo-check <file> # check a local HTML, Vue or
page component file
/searchfit-seo:seo-check # check the file open
in your editor
/searchfit-seo:seo-check <url> as an HTML file # save the result as a report
What it checks
•
Title: it exists, is 50 to 60 characters long and has the keyword
•
Meta description: it exists, is 150 to 160 characters long, and has the keyword and a
call to action
•
Headings: exactly one H1, no skipped levels, and keywords in the H1 and H2s
•
Images: alt text on every image, descriptive alt text and modern formats
•
Structured data: JSON-LD is present, the type matches the content and required
fields are filled
•
Links: internal links are present, anchors are descriptive and there are
no broken link patterns
•
Other tags: canonical, Open Graph and Twitter Card
What you get back
You get a score out of 100 and one line for
each check, marked Pass, Warn or Fail. After that comes a short list of fixes,
with the most important ones first. Keep in mind that this is a quick
pass-or-fail scan. It will not explain why something matters or rewrite your
content for you.
3. Optimize a page for a keyword:
/searchfit-seo:on-page-seo
This command improves a single page for one
target keyword. Instead of just listing problems, it gives you ready-to-use
fixes that you can copy and paste.
How to use it
/searchfit-seo:on-page-seo <url
or file> [keyword]
The keyword is optional. If you leave it
out, the command will ask you for it. It will also ask about the search intent
and your target audience before it starts the analysis.
What it checks
•
Title tag: where the keyword appears, the length and whether it is unique
•
Meta description: the keyword, the length and a call to action
•
URL slug: short and descriptive, with no IDs or parameters
•
Headings: the keyword in the H1, H2s that cover the subtopics and a clean
heading order
•
Content: depth, match with search intent, related keywords and no keyword
stuffing
•
Images: alt text, file names, file size and the hero image
•
Internal links: at least 3 to 5 links with descriptive anchor text
•
Schema: the right JSON-LD type with all required properties
What you get back
You get a before-and-after report with your
current score and the score you can expect after the fixes. Each fix is written
out in full. That includes a new title, a new meta description, a suggested
heading outline, content gaps to fill and ready-to-use internal links to add.
seo-audit, seo-check or on-page-seo: which one should you
use?
These three commands sound alike, but each
one has its own job.
|
Command |
Use
it when you want to |
|
seo-audit |
Check the whole site, including how well
search engines can crawl it |
|
seo-check |
Quickly confirm one page after an edit,
or find out which pages need work |
|
on-page-seo |
Get the title, description and headings
of one page rewritten for a keyword |
4. Find broken links: /searchfit-seo:broken-links
This command finds links that lead nowhere
and tells you how to fix each one. It can crawl a live site or scan your code.
How to use it
/searchfit-seo:broken-links
<url> # crawl a live site,
starting from this page
/searchfit-seo:broken-links <path>
# scan a codebase for dead links
/searchfit-seo:broken-links #
scan the current project folder
What it checks on a live site
•
Every internal and external
link it finds while crawling from the start URL
•
The HTTP status of each link:
404 and 500 errors are broken, 410 means the page was removed on purpose, and
timeouts are flagged
•
Redirect chains with three or
more hops
•
Mismatches in letter case and
trailing slashes
What it checks in a codebase
•
Anchor tags, framework link
components, Markdown links and CSS url() references
•
Each internal link compared
with the routes your app actually defines
•
Hardcoded absolute URLs, hash
links that point to missing IDs, and links in comments or docs
What you get back
The report starts with a count of pages
scanned, links checked, broken links and redirect chains. Broken links are
listed in tables with the source page, the URL, the status and a suggested fix.
At the end, a quick-fix section gives you redirect rules to add and the exact
file-and-line edits to make.
5. Technical SEO audit: /searchfit-seo:technical-seo
This command looks at the technical side of
SEO. It checks whether search engines can reach your site, crawl it, index it
and load it quickly.
How to use it
/searchfit-seo:technical-seo
<url> # audit a live site
/searchfit-seo:technical-seo <path>
# audit a codebase's config and routing
/searchfit-seo:technical-seo #
audit the current project, or the site you worked on earlier in the session
What it checks
•
Crawlability: robots.txt rules, sitemap validity and coverage, lastmod dates,
robots meta tags, X-Robots-Tag headers and canonical tags
•
Indexing: status codes, soft 404s, 301 versus 302 redirects, redirect chains,
and duplicate URLs caused by www, trailing slashes or letter case
•
Performance: compression, caching headers, HTTP/2 or HTTP/3, time to first byte
(TTFB), render-blocking CSS and JavaScript, font loading, image formats and
sizes, and bundle size
•
Mobile: viewport, horizontal scrolling, tap target size, body font size and
pop-ups that cover content
•
Security: HTTPS redirect, HSTS, CSP and other security headers, mixed content
and exposed dotfiles
•
Other: structured data validity, hreflang tags where needed, and URL
structure
What you get back
You get a score for each area plus an
overall score. Every finding is linked to a URL or a config file. The fix list
is sorted by priority and shows the exact change to make in your nginx config
or your framework.
6. Check your AI visibility: /searchfit-seo:ai-visibility
More and more people now ask AI assistants
like ChatGPT, Claude, Gemini and Perplexity for answers. This command checks
how your brand shows up in those answers and gives you a plan to improve it.
This practice is often called Generative Engine Optimization, or GEO.
How to use it
/searchfit-seo:ai-visibility
<brand or url>
For example:
/searchfit-seo:ai-visibility
Pranab Sharma
/searchfit-seo:ai-visibility https://pranabsharma.in/ "indian digital art
assets"
If you give only a brand name or a URL, the
command will ask a few more questions. It wants to know your category, your
main competitors, what makes you different, and the prompts you want your brand
to appear in.
What it does
1.
Builds a set of test prompts,
such as "best source for Indian art vectors" or "alternatives to
[competitor]".
2.
For each prompt, it checks
whether your brand is mentioned, in what position, how accurately and in what
tone.
3.
Scores your brand on six areas:
presence, accuracy, sentiment, position, completeness and consistency across
platforms.
4.
Compares you with your
competitors and creates a priority action plan, along with a list of content to
create.
What you get back
You get a visibility score out of 100, a
prompt-by-prompt table and a comparison with your competitors. You also get an
action plan in three parts:
•
Content signals: what to write and publish
•
Technical signals: such as schema markup and making your site crawlable for AI bots
•
Authority signals: such as mentions of your brand on other websites
One limitation to know
This command cannot query ChatGPT, Gemini
or Perplexity directly from Claude Code. Instead, it uses web search to see how
your brand is described in sources these AI tools learn from, along with
Claude's own knowledge. For a true reading across platforms, run the prompts
yourself in each assistant and paste the answers back in.
Final thoughts
SearchFit SEO turns Claude Code into a handy SEO assistant. Because it works on both live sites and code, you can find a problem and fix it without leaving your terminal.

