agentsclimarketplace

Technical seo checklist

Skill Solonnikov/agent-skills/skills/technical-seo-checklist

Public collection of agent skills — reusable capabilities, prompts, and workflows for Claude Code and other agentic coding tools.

Install
npx -y skills add Solonnikov/agent-skills --skill technical-seo-checklist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audits and implements the technical SEO basics any modern web app should ship with — metadata, structured data, crawlability, Core Web Vitals, and international targeting. Use when launching a new site, auditing an existing one, or reviewing a PR that touches routing, rendering, or head tags.

SKILL.md

4.5 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

Technical SEO Checklist

Practical technical SEO for modern web apps (Next.js, Angular, SvelteKit, plain HTML). Covers the pieces that actually move search ranking — not link-building, not content strategy.

When to use

  • Launching a new site and making sure it's indexable.
  • Auditing an existing site where organic traffic is below expectations.
  • Reviewing a PR that touches <head>, routing, or rendering.
  • Migrating frameworks (e.g. React CSR → Next.js SSR) and wanting to preserve rankings.
  • Rolling out internationalization.

Before you start

Know these:

  1. Rendering model — CSR, SSR, SSG, or ISR? Google indexes all of them now, but CSR still costs you. Anything commerce- or SEO-critical should be server-rendered.
  2. Target audience and language(s) — one language or many? Same content or localized?
  3. Existing ranking, if any. Migrations that break URLs lose rankings; you need a 301 map before launch, not after.
  4. What tooling you have — Google Search Console, Lighthouse, CrUX, Ahrefs/Semrush, PageSpeed Insights. At minimum, Search Console + Lighthouse + a crawler (Screaming Frog free tier).
  5. What "success" looks like — organic clicks, keyword rankings, indexed-page count, Core Web Vitals scores. Pick 2–3 metrics and track them monthly.

Audit workflow

  1. Crawl the site. Screaming Frog (or equivalent) — get a list of every URL, status code, title, description, canonical, indexability.
  2. Check indexability of every important page. robots.txt, meta robots, canonical, blocked by auth, noindex accidentally set. Most "why isn't this ranking" bugs live here.
  3. Check the <head> on representative pages — title, description, canonical, Open Graph, viewport, lang, charset.
  4. Check structured data. Rich Results Test for templates that should qualify (article, product, recipe, FAQ, breadcrumb).
  5. Check Core Web Vitals on real traffic via CrUX or Search Console → Core Web Vitals.
  6. Check mobile usability — viewport, tap targets, text legibility, responsive breakpoints.
  7. Check international setup if multi-language — hreflang, language-specific URLs, consistent canonical strategy.
  8. Submit sitemap. Every discovered URL in sitemap.xml; sitemap registered in Search Console.

Non-negotiable rules

  • Every indexable page has a unique <title> and <meta description>. Duplicates waste crawl budget and confuse ranking.
  • Every page has a canonical URL. Self-referencing on originals, pointing to the canonical on duplicates. Don't set canonical to the homepage for every page — that's a common bug that tanks indexation.
  • One <h1> per page, describing the page content. Not the site name.
  • Images have alt text, width, and height. Alt helps accessibility and image search. Width/height prevents Cumulative Layout Shift (CLS).
  • Mobile viewport meta tag is set: <meta name="viewport" content="width=device-width, initial-scale=1">. Missing this fails mobile usability immediately.
  • Don't rely on client-side rendering alone for content you want indexed. Googlebot renders JS, but slowly and inconsistently. SSR or SSG your important pages.
  • Never redirect 302 for permanent moves. Use 301. 302s don't pass ranking.
  • Never noindex pages unintentionally. Check staging configs don't leak X-Robots-Tag: noindex into production. This is the #1 traffic-killer at launch.

References

  • Metadata and head tags — title, description, canonical, Open Graph, Twitter cards, favicons, viewport.
  • Structured data (Schema.org / JSON-LD) — which types actually show rich results, how to implement, how to validate.
  • Crawlability — robots.txt, sitemap.xml, meta robots, X-Robots-Tag, pagination, faceted navigation traps.
  • Core Web Vitals — LCP, INP, CLS — what they are, how to measure, the specific patterns that fix each one.
  • International SEO — hreflang, URL patterns for i18n, language detection vs explicit selection.

Gives 1 of the 12 instructions most seo skills give in ~1.0k tokens

Counted across 454 of the 460 authors here whose files we hold, read 2026-08-06

  • implement structured data using JSON-LDin 30 of 454, across 26 files
  • write unique meta descriptions under 160 charactersin 27 of 454, across 20 files
  • verify one H1 exists per pagein 24 of 454, across 15 files
  • maintain a single h1 per pagein 24 of 454, across 15 files
  • use JSON-LD format for all schema markupin 23 of 454, across 15 files
  • use descriptive anchor text for internal linksin 21 of 454, across 16 files
  • add descriptive alt text to imagesin 19 of 454, across 15 files
  • read product marketing context before auditingin 19 of 454, across 10 files
  • write unique title tags under 60 charactersin 19 of 454, across 14 files
  • add unique title and meta description per pagehere, and in 19 of 454, across 17 files
  • Reference the sitemap in robots.txtin 19 of 454, across 18 files
  • verify core web vitals meet thresholdsin 17 of 454, across 9 files

Said here and by no other author read

  • crawl the site to list urls and status codes
  • check head tags on representative pages
  • check mobile usability
  • check international setup if multi-language

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.