site-crawlability▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides crawlability improvements: robots, X-Robots-Tag, site structure, and internal linking.
SEO Technical: Crawlability
Guides crawlability improvements: robots, X-Robots-Tag, site structure, and internal linking.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (Technical SEO)
- Redirect chains & loops: Fix multi-hop redirects; point directly to final URL
- Broken links (4xx): Fix broken internal/external links; 301 or remove
- Site architecture: Logical hierarchy; pages within 3–4 clicks from homepage
- Orphan pages: Add internal links to pages with no incoming links
- Pagination: Prefer pagination over infinite scroll for crawlability
- Crawl budget: Reduce waste on duplicates, redirects, low-value URLs (see below)
- AI crawler optimization: SSR for critical content; URL management; reduce 404/redirect waste (see below)
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site structure.
Identify:
- Site structure: Flat vs. deep hierarchy
- Framework: Next.js, static, SPA, etc.
- Key paths: Sitemap, robots.txt, API, static assets
Best Practices
Redirect Chains & Loops
- Fix multi-hop redirects; point directly to final URL
- Loops: URLs redirecting back to themselves; break the cycle
Broken Links (4xx)
- Fix broken internal/external links; 301 or remove
- Audit regularly; update or remove broken links
Site Architecture
| Principle | Guideline |
|---|---|
| Depth | Important pages within 3–4 clicks from homepage |
| Orphan pages | Add internal links to pages with no incoming links; see internal-links for link strategy |
| Hierarchy | Logical structure; hub pages link to content |
Pagination vs Infinite Scroll
Problem: With infinite scroll, crawlers cannot emulate user behavior (scroll, click "Load more"); content loaded after initial page load is not discoverable. Same applies to masonry + infinite scroll, lazy-loaded lists, and similar patterns.
Solution: Prefer pagination for key content. If keeping infinite scroll, make it search-friendly per Google's recommendations:
| Requirement | Practice |
|---|---|
| Component pages | Chunk content into paginated pages accessible without JavaScript |
| Full URLs | Each page has unique URL (e.g. ?page=1, ?lastid=567); avoid #1 |
| No overlap | Each item listed once in series; no duplication across pages |
| Direct access | URL works in new tab; no cookie/history dependency |
| pushState/replaceState | Update URL as user scrolls; enables back/forward, shareable links |
| 404 for out-of-bounds | ?page=999 returns 404 when only 998 pages exist |
Reference: Infinite scroll search-friendly recommendations (Google Search Central, 2014)
Pagination (Traditional)
- Reference links to next/previous pages;
rel="prev"/rel="next"where applicable - Avoid dynamic-only loading; ensure links in HTML
Crawl Budget
Crawl budget is the number of URLs Googlebot will crawl on your site in a given period. Large sites (10,000+ pages) may waste up to 30% of crawl budget on duplicates, redirects, and low-value URLs.
| Waste source | Fix |
|---|---|
| Duplicate URLs | Canonical; consolidate; 301 to preferred |
| Redirect chains | Point directly to final URL |
| Parameter proliferation | Use rel="canonical"; consider Clean-param (Yandex) |
| Low-value pages | noindex for thin/duplicate; see indexing |
| Crawl traps | Avoid infinite URL generation (e.g. faceted filters) |
Sitemap: Include only indexable, canonical URLs. See xml-sitemap, canonical-tag.
AI Crawler Optimization
AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) now represent ~28% of Googlebot's crawl volume. Their behavior differs from search engines—optimizing for both improves GEO (AI search visibility). See generative-engine-optimization for GEO strategy. Vercel/MERJ study (Dec 2024):
| Factor | AI Crawlers (GPTBot, Claude) | Googlebot |
|---|---|---|
| JavaScript | Do not execute JS; cannot read client-side rendered content | Full JS rendering |
| 404 rate | ~34% of fetches hit 404s | ~8% |
| Redirects | ~14% of fetches follow redirects | ~1.5% |
| Content in initial HTML | JSON, RSC in initial response can be indexed | Same |
Recommendations for AI crawlability:
| Practice | Action |
|---|---|
| Server-side rendering | Critical content in initial HTML. Use SSR, ISR, or SSG. See rendering-strategies for full guide. |
| URL management | Keep sitemaps updated; use consistent URL patterns; avoid outdated /static/ assets that cause 404s. AI crawlers frequently hit outdated URLs. |
| Redirects | Fix redirect chains; point directly to final URL. AI crawlers waste ~14% of fetches on redirects. |
| 404 handling | Fix broken links; remove or redirect outdated URLs. High 404 rates suggest AI crawlers may use stale URL lists. |
Reference: The rise of the AI crawler (Vercel, 2024)
Common Issues
| Issue | Check |
|---|---|
| Redirect chains | Update links to point directly to final URL |
| Broken links | 301 or remove; audit internal and external |
| Orphan pages | Add internal links from hub or navigation; see internal-links for strategy |
| Infinite scroll | Provide paginated component pages; or replace with pagination for key content; see above |
| AI crawlers missing content | Ensure critical content in initial HTML; see rendering-strategies |
Output Format
- Redirect audit: Chains and loops to fix
- Broken link audit: 4xx links to fix
- Site structure: Orphan pages, hierarchy
- Pagination: Implementation for crawlable content
- AI crawler: SSR/URL/redirect checks if GEO or AI visibility is a goal
Related Skills
- seo-strategy: SEO workflow; crawlability is Technical phase (P0)
- website-structure: Plan which pages to build, page priority, structure planning; use before or alongside crawlability audit
- robots-txt: robots.txt configuration; AI crawler allow/block (GPTBot, ClaudeBot)
- xml-sitemap: URL discovery; keep updated to reduce AI crawler 404s
- google-search-console: Index status, Coverage report
- indexing: Fix indexing issues
- internal-links: Internal linking best practices
- masonry: Masonry + infinite scroll has same crawl issue; layout skill references this for SEO
- generative-engine-optimization: GEO strategy; AI search visibility; crawlability enables AI citation
- canonical-tag: Canonical reduces crawl budget waste on duplicates
- rendering-strategies: SSR, SSG, CSR; content in initial HTML; crawler visibility
How to use site-crawlability on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add site-crawlability
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches site-crawlability from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate site-crawlability. Access the skill through slash commands (e.g., /site-crawlability) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★46 reviews- ★★★★★Ira Tandon· Dec 28, 2024
site-crawlability fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Dec 24, 2024
site-crawlability reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ren Martin· Dec 24, 2024
I recommend site-crawlability for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ganesh Mohane· Dec 20, 2024
Solid pick for teams standardizing on skills: site-crawlability is focused, and the summary matches what you get after install.
- ★★★★★Benjamin Okafor· Dec 8, 2024
Keeps context tight: site-crawlability is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sofia Diallo· Nov 27, 2024
We added site-crawlability from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Benjamin Mensah· Nov 19, 2024
site-crawlability is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yash Thakker· Nov 15, 2024
I recommend site-crawlability for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Nikhil Sethi· Nov 15, 2024
site-crawlability reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Daniel Malhotra· Oct 18, 2024
site-crawlability fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 46