AGENT SKILL

seo-programmatic

Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", or "data-driven SEO".

License 许可
MIT
最近更新
2026-10-22
Stars
★ 1
Forks
0

01 前言 Front Matter

name
seo-programmatic
license
MIT
metadata
{ "author": "AgriciDaniel", "version": "2.2.5", "category": "seo" }
description
Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", or "data-driven SEO".
argument-hint
[url or plan]
user-invocable
true

02 资源文件 1

03 SKILL.md 正文

Programmatic SEO Analysis & Planning

Build and audit SEO pages generated at scale from structured data sources. Enforces quality gates to prevent thin content penalties and index bloat.

Data Source Assessment

Evaluate the data powering programmatic pages:

  • CSV/JSON files: Row count, column uniqueness, missing values
  • API endpoints: Response structure, data freshness, rate limits
  • Database queries: Record count, field completeness, update frequency
  • Data quality checks:
    • Each record must have enough unique attributes to generate distinct content
    • Flag duplicate or near-duplicate records (>80% field overlap)
    • Verify data freshness; stale data produces stale pages

Template Engine Planning

Design templates that produce unique, valuable pages:

  • Variable injection points: Title, H1, body sections, meta description, schema
  • Content blocks: Static (shared across pages) vs dynamic (unique per page)
  • Conditional logic: Show/hide sections based on data availability
  • Supplementary content: Related items, contextual tips, user-generated content
  • Template review checklist:
    • Each page must read as a standalone, valuable resource
    • No "mad-libs" patterns (just swapping city/product names in identical text)
    • Dynamic sections must add genuine information, not just keyword variations

URL Pattern Strategy

Common Patterns

  • /tools/[tool-name]: Tool/product directory pages
  • /[city]/[service]: Location + service pages
  • /integrations/[platform]: Integration landing pages
  • /glossary/[term]: Definition/reference pages
  • /templates/[template-name]: Downloadable template pages

URL Rules

  • Lowercase, hyphenated slugs derived from data
  • Logical hierarchy reflecting site architecture
  • No duplicate slugs; enforce uniqueness at generation time
  • Keep URLs under 100 characters
  • No query parameters for primary content URLs
  • Consistent trailing slash usage (match existing site pattern)

Internal Linking Automation

  • Hub/spoke model: Category hub pages linking to individual programmatic pages
  • Related items: Auto-link to 3-5 related pages based on data attributes
  • Breadcrumbs: Generate BreadcrumbList schema from URL hierarchy
  • Cross-linking: Link between programmatic pages sharing attributes (same category, same city, same feature)
  • Anchor text: Use descriptive, varied anchor text. Avoid exact-match keyword repetition
  • Link density: 3-5 internal links per 1000 words (match seo-content guidelines)

Thin Content Safeguards

Quality Gates

Metric Threshold Action
Pages without content review 100+ ⚠️ WARNING: require content audit before publishing
Pages without justification 500+ 🛑 HARD STOP: require explicit user approval and thin content audit
Unique content per page <40% ❌ Flag as thin content (likely penalty risk)
Word count per page <300 ⚠️ Flag for review (may lack sufficient value)

Scaled Content Abuse: Enforcement Context (2025-2026)

Google's Scaled Content Abuse policy (introduced March 2024) saw major enforcement escalation in 2025:

  • June 2025: Wave of manual actions targeting websites with AI-generated content at scale
  • August 2025: Third-party/SEO-community reporting described stronger SpamBrain detection for AI-generated link schemes and content farms
  • Result: Google reported 45% reduction in low-quality, unoriginal content in search results post-March 2024 enforcement

Enhanced quality gates for programmatic pages:

  • Content differentiation: ≥30-40% of content must be genuinely unique between any two programmatic pages (not just city/keyword string replacement)
  • Human review: Minimum 5-10% sample review of generated pages before publishing
  • Progressive rollout: Publish in batches of 50-100 pages. Monitor indexing and rankings for 2-4 weeks before expanding. Never publish 500+ programmatic pages simultaneously without explicit quality review.
  • Standalone value test: Each page should pass: "Would this page be worth publishing even if no other similar pages existed?"
  • Site reputation abuse: Google clarified site reputation abuse language on 2024-11-19; treat third-party/hosted programmatic content as a policy risk.

Recommendation: The WARNING gate at <40% unique content remains appropriate. Consider a HARD STOP at <30% unique content to prevent scaled content abuse risk.

Safe Programmatic Pages (OK at scale)

✅ Integration pages (with real setup docs, API details, screenshots) ✅ Template/tool pages (with downloadable content, usage instructions) ✅ Glossary pages (200+ word definitions with examples, related terms) ✅ Product pages (unique specs, reviews, comparison data) ✅ Data-driven pages (unique statistics, charts, analysis per record)

Penalty Risk (avoid at scale)

❌ Location pages with only city name swapped in identical text ❌ "Best [tool] for [industry]" without industry-specific value ❌ "[Competitor] alternative" without real comparison data ❌ AI-generated pages without human review and unique value-add ❌ Pages where >60% of content is shared template boilerplate

Uniqueness Calculation

Unique content % = (words unique to this page) / (total words on page) × 100

Measure against all other pages in the programmatic set. Shared headers, footers, and navigation are excluded from the calculation. Template boilerplate text IS included.

Canonical Strategy

  • Every programmatic page must have a self-referencing canonical tag
  • Parameter variations (sort, filter) canonical to the base URL when duplicate or low-value
  • Paginated series: use self-canonical paginated pages when content differs; keep crawlable links
  • If programmatic pages overlap with manual pages, the manual page is canonical
  • No canonical to a different domain unless intentional cross-domain setup

Sitemap Integration

  • Auto-generate sitemap entries for all programmatic pages
  • Split at 50,000 URLs or 50MB uncompressed per sitemap file, whichever comes first (protocol limit)
  • Use sitemap index if multiple sitemap files needed
  • <lastmod> reflects actual data update timestamp (not generation time)
  • Exclude noindexed programmatic pages from sitemap
  • Register sitemap in robots.txt
  • Update sitemap dynamically as new records are added to data source

Index Bloat Prevention

  • Noindex low-value pages: Pages that don't meet quality gates
  • Pagination: Reserve noindex/canonical consolidation for true duplicates or low-value filtered views
  • Faceted navigation: Reserve noindex/canonical to base category for true duplicates or low-value filtered views
  • Crawl budget: For sites with >10k programmatic pages, monitor crawl stats in Search Console
  • Thin page consolidation: Merge records with insufficient data into aggregated pages
  • Regular audits: Monthly review of indexed page count vs intended count

Output

Programmatic SEO Score: XX/100

Assessment Summary

Category Status Score
Data Quality ✅/⚠️/❌ XX/100
Template Uniqueness ✅/⚠️/❌ XX/100
URL Structure ✅/⚠️/❌ XX/100
Internal Linking ✅/⚠️/❌ XX/100
Thin Content Risk ✅/⚠️/❌ XX/100
Index Management ✅/⚠️/❌ XX/100

Critical Issues (fix immediately)

High Priority (fix within 1 week)

Medium Priority (fix within 1 month)

Low Priority (backlog)

Recommendations

  • Data source improvements
  • Template modifications
  • URL pattern adjustments
  • Quality gate compliance actions

Error Handling

Scenario Action
URL unreachable Report connection error with status code. Suggest verifying URL accessibility and checking for authentication requirements.
No programmatic pages detected Inform user that no template-generated or data-driven page patterns were found. Suggest checking if pages use client-side rendering or if the URL points to the correct section.
Thin content threshold exceeded Trigger quality gate warning. Report the unique content percentage and flag pages below 40% uniqueness. Require user acknowledgment before proceeding.
Quality gate violation Halt analysis at the HARD STOP threshold (500+ pages without justification or <30% unique content). Present findings and require explicit user approval to continue.

04 同仓库更多 Skills

Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

infer-conventions

Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

inertia-react-development

Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

★ 1