technical-seo-checklist
Apply technical SEO best practices for rendered pages, including metadata quality, semantic structure, crawlability, indexability, and performance-aware implementation choices.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- technical-seo-checklist
- description
- Apply technical SEO best practices for rendered pages, including metadata quality, semantic structure, crawlability, indexability, and performance-aware implementation choices.
02 资源文件 1
- 脚本scripts/check_seo_templates.py4.3 KB
03 SKILL.md 正文
Technical SEO Checklist
Use this skill when changing page templates, metadata, content structure, or linking that can affect search discoverability.
Quick Start
Run technical SEO checks across templates:
uv run python \
.github/skills/seo/technical-seo-checklist/scripts/check_seo_templates.py
Fail the run when issues are found:
uv run python \
.github/skills/seo/technical-seo-checklist/scripts/check_seo_templates.py \
--fail-on-issues
Required Behavior
- Ensure each user-facing page has a specific, non-placeholder title.
- Ensure each user-facing page has a meaningful meta description.
- Maintain semantic heading hierarchy and avoid skipped heading levels.
- Keep key content server-rendered and crawlable.
- Ensure internal links use valid anchor tags with stable URLs.
- Avoid introducing duplicate canonical targets or conflicting metadata.
Workflow
- Identify which routes/pages are SEO-impacting.
- Inspect template head metadata and heading structure.
- Add or adjust metadata (
title, description, canonical when relevant). - Verify links and page structure support crawlability.
- Confirm changes do not degrade initial render performance.
Review Checks
Before finalizing, confirm:
- Page title and meta description are present and specific.
- Heading hierarchy is logical (
h1then structured subsections). - Canonical usage is correct for pages where duplicate URLs are possible.
- New links are discoverable and not JS-only.
- No SEO-critical fields are left as placeholder text.
check_seo_templates.pyreports no unresolved issues (or issues are explicitly accepted by the user).
Best Practices
- Write title tags for intent and clarity first, then optimize length.
- Keep descriptions specific to the page value; avoid generic boilerplate.
- Prefer stable URLs and avoid unnecessary duplicate routes.
- Keep legal/privacy pages indexable unless there is a clear policy reason not to.
- When adding new public pages, link them from at least one crawlable page.
Notes
- Prefer practical, measurable SEO improvements over speculative additions.
- When a request is purely backend/API-only, do not force SEO changes that do not affect rendered pages.
04 同仓库更多 Skills
roadmap-todo-changelog-auto-updater
Update ROADMAP.md, TODO.md, and CHANGELOG.md automatically from merged PR metadata using deterministic role ownership rules.
pull-request-authoring-workflow
Create or update pull requests for this repo using the required process. Use when opening a PR, editing a PR body, preparing a PR title, checking the pull request template, applying conventional commit style to PR titles, linking tickets, or verifying GitHub PR rendering.
commit-message-guidelines
Prepare commit messages for this repo using the required conventional commit rules. Use when reviewing staged changes, choosing a commit type, selecting a scope, writing a commit summary, or checking whether a commit message follows the repository format.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
ui-implementation-standards
Implement or refactor frontend behavior in templates with consistent responsiveness, accessibility, and maintainable JavaScript patterns. Use when changing HTML/CSS/JS in rendered pages.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.