website-seo-guardrailslisted
Audit, design, write, and validate comprehensive website SEO while preventing indexing, quality, spam-policy, crawling, structured-data, scaling, migration, backlink, keyword, Lighthouse, and measurement failures. Use for technical or on-page audits; standardized Google Lighthouse runs; interpreting Lighthouse JSON, HTML, screenshots, or pasted recommendations; prioritized improvements and comparable before/after retests; Google Trends brand, product, category, seasonal, regional, or content research; deciding whether pages, blogs, courses, tools, directories, or generated content should be indexed; SEO writing; Google Search Console, Bing Webmaster Tools, IndexNow, Ahrefs, sitemaps, robots, canonicals, schema, and AI-search visibility; or pre-launch reviews. Apply to new sites, redesigns, migrations, programmatic content, ecommerce, local, multilingual, and JavaScript-rendered sites.
apnatvar/web-development-and-online-marketing-skills · ★ 0 · Web & Frontend · score 60
Install: claude install-skill apnatvar/web-development-and-online-marketing-skills
# Website SEO Guardrails
Prevent material search risks before chasing marginal optimizations. Treat crawlability, indexability, content value, policy compliance, and measurement as separate gates.
## Operating principles
1. Protect users and the domain before pursuing traffic.
2. Make every indexable URL independently useful; public does not automatically mean indexable.
3. Prefer a smaller coherent index over many thin, repetitive, or speculative pages.
4. Keep visible content, metadata, structured data, canonicals, sitemaps, and robots directives consistent.
5. Treat tool scores and character counts as operational heuristics, not ranking guarantees.
6. Separate observed facts, tool findings, hypotheses, and recommendations.
7. Never guarantee ranking, indexing, rich results, backlinks, or AI citations.
8. Distinguish implementation from account operations: an audit does not authorize submitting URLs, changing settings, linking products, enabling ads, or accepting terms.
## Mandatory workflow
### 1. Establish scope and evidence
Identify the canonical production origin, site purpose, audiences, markets, content types, framework/CMS, rendering mode, analytics, webmaster access, recent migrations, and business constraints. Inspect rendered output as well as source code when possible.
Record evidence from crawls, HTTP responses, rendered HTML, Search Console, Bing Webmaster Tools, analytics, server/CDN logs, backlink tools, and repository tests. Do not report an unverifie