AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Seo Migration Check

skill-lionkiii-claude-seo-skills-seo-migration-check · by lionkiii

>

No reviews yet
0 installs
45 views
0.0% view→install

Install

$ agentstack add skill-lionkiii-claude-seo-skills-seo-migration-check

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-lionkiii-claude-seo-skills-seo-migration-check)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Seo Migration Check? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Site Migration SEO Validator

Validates redirect chains, canonical tags, metadata, and content preservation during site migrations.

Inputs

Either:

  • old and new: Two URLs for a single-page check (e.g., https://old.com/page https://new.com/page)
  • file: Path to CSV/text file with URL pairs, one per line: old_url,new_url

If file provided: Read it and process each line. Skip blank lines and lines starting with #. For large files (>50 URL pairs), process first 50 and note truncation.

Execution

For each URL pair, run checks a-f:

Check a: Redirect Chain Validation

Fetch old URL with WebFetch and follow redirects (track each hop):

  1. Record redirect type: 301 (permanent), 302 (temporary), 307, 308
  2. Count redirect hops
  3. Record final destination URL

Evaluate:

  • Final destination matches expected new URL: PASS — mismatch: FAIL
  • Redirect type is 301: PASS — 302/307: WARN (temporary redirects pass less link equity)
  • Hop count 1: PASS — hop count 2: WARN — hop count >2: FAIL (redirect chain too long)
  • Direct 200 on old URL (no redirect): FAIL (old page still live, not redirected)

Check b: Canonical Consistency

Fetch new URL, extract ` from `.

  • Canonical matches new URL exactly: PASS
  • Canonical missing: WARN (Google will infer, but explicit is better)
  • Canonical points to old URL: FAIL (critical — tells Google old is authoritative)
  • Canonical points to third URL: WARN

Check c: Title and Meta Preservation

Compare title and meta description between old URL (before redirect) and new URL. Note: old URL may already redirect, so if old URL is not directly fetchable, skip comparison and note.

If comparable:

  • Title: Extract both. Compare word overlap.
  • >70% word overlap: PASS
  • 40-70% overlap: WARN (may be intentional change)
  • = 80% of old: PASS
  • New page word count 50-80% of old: WARN (possible content reduction)
  • New page word count < 50% of old: FAIL (significant content loss)

If old URL not directly fetchable (already redirects): skip and note.

Check f: Schema Preservation

Extract @type values from JSON-LD blocks on both pages.

  • Same schema types present: PASS
  • Schema types reduced: WARN (lost structured data)
  • Key schema missing on new (e.g., Product, Article, LocalBusiness): WARN
  • No schema on either: NOTE (not a regression)

Overall Per-URL Result

FAIL: any check is FAIL WARN: no FAILs but any check is WARN PASS: all checks PASS or NOTE

Output Format

## Migration Validation: [old URL] → [new URL]
(or: ## Migration Validation: [N] URL pairs from [filename])

### Summary

| Status | Count |
|--------|-------|
| PASS | N |
| WARN | N |
| FAIL | N |
| Total | N |

### Per-URL Results

| Old URL | New URL | Redirect | Canonical | Title | Meta | Status Code | Schema | Overall |
|---|---|---|---|---|---|---|---|---|
| /old | /new | 301✓ | PASS | PASS | WARN | 200 | PASS | WARN |

### Failed Items Detail

For each FAIL result, expanded information:

**[old URL] → [new URL]**
- Redirect: [issue description]
- Canonical: [issue description]
- [etc.]
- Recommended fix: [specific action]

### Recommendations

[Prioritized list of actions based on failures and warnings]

## Data Sources

- Live URL fetching via WebFetch
- Redirect chain analysis (following HTTP headers)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.