Stats
Actions
Tags
From silverbee
Pre-analysis validation of domain canonical status, HTTP resolution, variant consistency, and index status. Use at the start of any workflow that pulls data by domain or URL, checks indexation, or performs canonical analysis. Do not use as a standalone audit deliverable.
How this skill is triggered — by the user, by Claude, or both
Slash command
/silverbee:canonical-url-and-domain-validationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Pre-Analysis URL and Domain Canonical Target Validation**
Pre-Analysis URL and Domain Canonical Target Validation
Input: {Domain or URL} and consuming skill declaration (Validation level: Level 1 only / Level 1 + Level 2; Level 2 applies to: [which URLs and under what conditions]).
Pre-execution check (satisfy from context before fetching): confirm the canonical domain and indexation status have not already been confirmed from user context or earlier in the session; if both are already confirmed, validation is not required; if canonical domain is missing, proceed to Level 1; if index status is missing but canonical domain is confirmed, proceed to Check C only; if the consuming skill declares Level 2, run Level 2 after Level 1 passes regardless of cache state.
A — HTTP Status: fetch root domain, record HTTP status.
Active domain after Check A: set from the final resolved URL, propagates forward.
B — Canonical Domain: identify the canonical domain by checking the following signals in order — stop at the first signal that produces a clear result.
<head>Link response headerCanonical tag handling:
Conflict handling:
Circular conflict check: confirm the canonical domain does not 301 back to a variant, and no redirect destination has a canonical pointing back to the origin.
Variant stability check: once the canonical domain is confirmed, verify it is applied consistently across all common variants — www/non-www, http/https, trailing slash presence/absence, and common parameter-appended versions (e.g., ?ref=, ?utm_). Inconsistency across variants → flag, list the inconsistent variants, report to user.
Once the canonical domain is confirmed — if it differs from the domain provided in the input, apply the following:
Canonical domain confirmed after Check B: used for all subsequent analysis.
C — Homepage Index Status: identify index status using the following fallback chain — stop at the first signal that produces a result.
site:[homepage-url] → a yes/no result only, not conclusive on its own.Result handling:
site: search → flag, not conclusive, confirm with user.Level 2 runs only after Level 1 passes. If Level 1 produces a hard stop, do not proceed to Level 2. Consuming skill defines which URLs trigger Level 2 and under what conditions.
D — URL Status: fetch URL, record status.
E — Indexability and Index Status: a URL can be crawlable but excluded from the index — both must be confirmed independently.
Indexability: inspect meta robots tag in <head> and X-Robots-Tag in HTTP response headers for noindex directives.
<head> content, absence of expected meta tags, React/Next.js/Vue signatures in the HTML. If any proxy indicator is present → flag, note that indexability check may be incomplete.Index status: confirm using the following fallback chain — stop at the first signal that produces a result.
site:[url] → a yes/no result only, lower confidence, note accordingly.F — Canonical Target Status: if the subject URL carries a canonical tag, fetch the canonical target URL and record its HTTP status.
G — Canonical Target Indexability: once canonical target is confirmed as 200 (Check F), inspect the canonical target URL for noindex directives using the same method as Check E.
H — Canonical-Redirect Conflict: check whether the subject URL both carries a canonical pointing to URL-C and also issues a redirect to URL-R, where URL-C ≠ URL-R.
npx claudepluginhub silverbee-ai/claude-silverbee-marketplace --plugin silverbeeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.