bulk-metadata

Audit and update bulk metadata across Adobe Edge Delivery Services pages.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill bulk-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bulk-metadata
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/bulk-metadata
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill bulk-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk-metadata removes the time-consuming task of manually finding missing or inconsistent SEO metadata across many Adobe Edge Delivery Services (EDS) pages, replacing it with a single audit-and-fix workflow that produces a paste-ready spreadsheet.

Core Features & Use Cases

  • Query index + fallback page discovery: Scans pages via the site query index, or falls back to sitemap/manual listing when needed.
  • Metadata completeness auditing: Detects missing or inconsistent titles, descriptions, og:image, and robots directives across indexed pages.
  • Paste-ready corrected bulk spreadsheet generation: Produces an updated URL-pattern rulesheet for Google Sheets/Excel, including recommended severity-driven fixes.

Quick Start

Use the bulk-metadata skill to audit your EDS site metadata from the query index and generate a corrected bulk metadata spreadsheet ready to paste into Google Sheets.

Frequently Asked Questions about bulk-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bulk audit missing SEO metadata across Adobe Edge Delivery Services pages?

To fix inconsistent metadata in bulk, you generate a paste-ready metadata spreadsheet containing ordered pattern rules and appropriate fallbacks, applying precedence-aware logic where page overrides folder and bulk settings.

What is the best way to standardize EDS metadata before a site launch?

If your query index is incomplete, you can perform fetch-safe page discovery using sitemap fallbacks or manual URL listing to ensure all pages are audited for missing metadata before generating the spreadsheet.

Can I use this to fix missing og:image and robots directives across many URL patterns?

When standardizing metadata, the system applies precedence-aware rule design where page-level settings take priority over folder-level, which overrides bulk configurations in the generated spreadsheet.

Does bulk metadata cleanup for Edge Delivery Services require a specific spreadsheet format?

After completing the metadata audit, you receive a paste-ready metadata.xlsx or spreadsheet table with ordered pattern rules and appropriate fallbacks to directly import into Google Sheets.