ワンクリックでManusで任意のスキルを実行

technical-seo-checklist

スター2

フォーク1

更新日2026年4月23日 13:26

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Solonnikov

Solonnikov/agent-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ウェブ開発者コンピュータ・数学職·SOC 15-1254

ファイルエクスプローラー

6 ファイル

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

dapp-architect

Solonnikov/agent-skills

Designs decentralized apps from brief to production — user + trust-boundary mapping, contract architecture, client layer, indexing strategy, off-chain components, deployment pipeline, and ops. Use when starting a new dApp and needing a coherent plan before code, auditing an existing dApp for architectural gaps, or teaching a team to think through dApp design instead of stumbling into it.

2026-04-232

content-repurposing

Solonnikov/agent-skills

Turns one piece of content into multiple surfaces — blog post → Twitter/X thread → LinkedIn post → newsletter issue — matching each platform's conventions. Use when a user has shipped a long-form piece and wants to extract shorter variants for other channels, or is planning a content launch across multiple platforms.

2026-04-232

email-drafting

Solonnikov/agent-skills

Drafts emails in the right tone and length for the situation — cold outreach, follow-up, introduction, apology, thank-you, difficult conversation. Use when a user needs to write an email they're stuck on, rewrite an email that sounds off, or draft a template they'll reuse for similar situations.

2026-04-232

meeting-notes-structure

Solonnikov/agent-skills

Produces meeting notes that capture decisions and action items — not transcription. Attendees, agenda, decisions, action items with owners and deadlines. Use when a user needs notes from a meeting that's about to happen, is happening, or just ended, or wants a template for recurring meetings.

2026-04-232

research-brief-structure

Solonnikov/agent-skills

Produces research briefs that answer a question — sources, synthesis, gaps, recommendation — rather than summaries that describe a topic. Use when a user needs to research a decision, investigate a market or tool, understand an unfamiliar domain quickly, or present findings to a stakeholder who wants an answer, not a report.

2026-04-232

resume-tailor

Solonnikov/agent-skills

Tailors a résumé to a specific job description — parses the JD for priorities, reorders and rewrites bullets to match, quantifies achievements, and passes ATS filters. Use when a user is applying to a specific role and wants their résumé to match the JD, or when their bullets are weak ("responsible for...") and need tightening.

2026-04-232

name	technical-seo-checklist
description	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.

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:

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.
Target audience and language(s) — one language or many? Same content or localized?
Existing ranking, if any. Migrations that break URLs lose rankings; you need a 301 map before launch, not after.
What tooling you have — Google Search Console, Lighthouse, CrUX, Ahrefs/Semrush, PageSpeed Insights. At minimum, Search Console + Lighthouse + a crawler (Screaming Frog free tier).
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

Crawl the site. Screaming Frog (or equivalent) — get a list of every URL, status code, title, description, canonical, indexability.
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.
Check the <head> on representative pages — title, description, canonical, Open Graph, viewport, lang, charset.
Check structured data. Rich Results Test for templates that should qualify (article, product, recipe, FAQ, breadcrumb).
Check Core Web Vitals on real traffic via CrUX or Search Console → Core Web Vitals.
Check mobile usability — viewport, tap targets, text legibility, responsive breakpoints.
Check international setup if multi-language — hreflang, language-specific URLs, consistent canonical strategy.
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.