Audit and fix technical SEO in code, with your agent
Audits and fixes crawlability, indexing, robots.txt, XML sitemaps, canonicals, redirect chains, server-rendered HTML and security headers in your site’s codebase, then checks every fix live with clickd.
Add it, from the top of the site’s repositorynpx skills add subinternal/clickd --skill clickd-technical-seo
Then ask your agentRun a technical SEO audit on example.com with clickd, fix the indexing, canonical and sitemap issues in our repo, and verify live.
Your agent inspects the live site first, fixes the router, middleware or templates in code, and rescans to confirm every blocker cleared.
1Read the live site and rank technical blockersclickd_brief
2Fix crawl access, sitemaps and canonical URLs
3Ensure server-rendered HTML for crawlers and agentsclickd_check
4Tighten status codes, security headers and page speed
5Rescan and prove every fix on the live siteclickd_rescan
What a technical SEO pass fixes in code
A sample read before and after your agent fixes crawl access, canonicals, server rendering and headers on example.com.
example.com technical read
5 blockers cleared in code, proved by clickd_changes.
Sample
robots.txt & sitemapBlocked /guides/ and listed 14 redirected URLs in sitemap.xml200 status, AI & search crawlers allowed, 88 canonical URLs in sitemap.xml
Canonical tagsMissing on 19 routes; http:// host on blog postsSelf-referencing https://example.com/... canonical on all 88 routes
Server-rendered HTMLEmpty <div id="root"> shell on /pricing without JSFull h1, pricing table and FAQ rendered in initial HTML response
Redirects & status codes3-hop redirect chain on /docs; soft-404 returning 200Direct 200 links internally; real 404 status on missing routes
What clickd verifies on the live site
Every change is checked against the public URL after deploy, never taken on trust from local files.
clickd_brief & clickd_structureRanks technical blockers by worth and checks status codes, canonicals and crawl depth across the site.
clickd_check (kind: "agent" & "ssl")Verifies what an HTML-only crawler reads without JavaScript and checks the TLS certificate chain on port 443.
clickd_rescan & clickd_changesRe-reads the live site after deploy and confirms which technical rules moved to fixed.
When to reach for it
Reach for it when
Pages sit as “Crawled - currently not indexed” or “Discovered - currently not indexed” in Search Console.
Your site uses React, Vue or Next.js and you want to be sure crawlers receive server-rendered HTML.5
You need robots.txt, XML sitemaps, canonicals, redirects and security headers cleaned up in code.2,3
Leave it when
Every technical check already passes and the real gap is content depth or search intent.
You cannot edit or deploy the site’s templates, router or edge configuration.
More things to ask your agent
Everyday prompts that load the Technical SEO skill in Claude Code, Codex or Cursor.
Pages not indexed in GSCCheck why 20 of our pages sit as "Crawled - currently not indexed", fix canonicals, sitemaps and thin shells in code, and rescan.
JS rendering auditRun clickd_check (kind: "agent") on our key routes to see what crawlers read without JavaScript and move client-only copy to SSR.
Clean up redirects and headersFind all internal redirect chains, missing canonicals and missing security headers with clickd_structure and fix them in our router.
Technical SEO skill vs the alternatives
Why pairing an open repository skill with a live crawler beats manual audits and prompt-only checklists.
How it reads your siteBy hand: Manual spot-checks in a browser · Prompt-only skill: Reads local source files only; misses live headers, redirects and JS shellsReads the live URL, HTTP headers, raw HTML and Search Console via clickd MCP
How changes are madeBy hand: Copy-pasting between docs, spreadsheets and editors · Prompt-only skill: Suggests generic copy in chat with no repo contextEdits your actual templates, routes and schema in the repository
How fixes are provedBy hand: Checking pages one by one after deploy · Prompt-only skill: Agent grades its own homework with no live checkRuns clickd_rescan and clickd_changes on the deployed site to prove rules passed
Skills to use alongside it
Included when you run npx skills add subinternal/clickd.
Site architectureAudits and fixes your site’s internal link graph, orphan pages, topic hubs, crawl depth and BreadcrumbList schema in code, then verifies the updated structure on the live site with clickd.See skill
Page systemBuilds a site’s page templates and shared components so crawlers and assistants read every page well, and proves each pattern with clickd. About structure and spacing, not color, type or brand.See skill
AI visibilityAudits and fixes your site’s visibility in ChatGPT, Claude, Perplexity and Google AI Overviews: AI crawler access, non-JS HTML readability, answer-first passages, entity sameAs schema and live citation tracking.See skill
Questions about the Technical SEO skill
Why can’t an AI agent audit technical SEO from repo files alone?
Because redirects, HTTP headers (X-Robots-Tag, Strict-Transport-Security), TLS certificates, CDN caching and client-rendered empty shells only show up when fetching the live URL.
How does the skill check JavaScript rendering issues?
It calls clickd_check with kind: "agent" on the live URL to compare the raw server-rendered HTML against what a browser renders, then fixes the framework template so primary copy ships in HTML.
Install it by hand
The line at the top adds it for any agent. Or fetch its 1 files where your agent looks. Your agent also needs clickd connected over MCP: connecting an agent shows how.
Loads skills from .claude/skills/ in the repository, for everyone who works in it, or ~/.claude/skills/ for every project on your machine. Claude uses it when a request matches its description, or type /clickd-technical-seo.
Puts the files in .claude/skills/clickd-technical-seo/.
Loads skills from .agents/skills/ in the repository and its parent folders, or ~/.agents/skills/ for every project. Codex uses it when a task matches its description, or mention it as $clickd-technical-seo; /skills lists them.
Puts the files in .agents/skills/clickd-technical-seo/.
Loads skills from .cursor/skills/ or .agents/skills/ in the repository, or ~/.cursor/skills/ for every project. It also reads .claude/skills/, so one copy there serves both. The agent uses it when it is relevant, or type / in Agent chat and pick it.
Puts the files in .cursor/skills/clickd-technical-seo/.
An agent that does not load skills can still follow the file. Save the folder in the repository and point its standing instructions at it, with a line in AGENTS.md, which many agents read. The agent reads AGENTS.md when it starts, and follows the file when the task matches.
Terminal, for Any other agent
mkdir -p docs/clickd-technical-seo
curl -fsSL https://clickd.com/skills/technical-seo/SKILL.md -o docs/clickd-technical-seo/SKILL.md
echo "For technical SEO audits and fixes, follow docs/clickd-technical-seo/SKILL.md." >> AGENTS.md
SKILL.md stays short and sends your agent to a reference when a step needs it.
SKILL.mdThe five steps from reading live technical blockers to fixing robots.txt, sitemaps, canonicals, server-rendered HTML and security headers, then rescanning with clickd.99 lines