product-page-seo

Audit AEM Edge Delivery Services product pages for crawlability and indexing gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

product-page-seo identifies why AEM Edge Delivery Services (EDS) commerce product pages fail to get indexed when critical product content and SEO signals are rendered only after JavaScript runs, and it provides targeted remediation to restore crawlability and rich-result eligibility.

Core Features & Use Cases

  • Client-side rendering crawlability audit: compares what search crawlers see in raw HTML versus what is added by JavaScript/API rendering, highlighting product content that is missing from the initial response.
  • Technical PDP SEO checks: validates product-specific meta tags (title, description, Open Graph), canonical URLs, robots.txt directives, and sitemap inclusion for route-based product URLs.
  • Product structured data validation: checks Product schema.org JSON-LD presence and required fields for offers/price/availability to support rich results and avoid policy failures.
  • Image optimization review: evaluates alt text quality, width/height attributes, and loading strategy (including LCP image priority) for product images.

Quick Start

Use this skill to audit at least three storefront product URLs by analyzing their raw HTML crawl surface and verifying meta tags, canonical tags, Product JSON-LD, robots.txt/sitemap coverage, and product image SEO.

Frequently Asked Questions about product-page-seo

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

FAQPage Schema
Why are my AEM Edge Delivery Services product pages discovered but not indexed by search engines?

AEM Edge Delivery Services product pages are discovered but not indexed when critical product content and SEO signals like meta tags are rendered only after JavaScript runs, making them invisible to crawlers in the initial raw HTML response.

How do I audit client-side rendering crawlability for commerce product pages?

Audit client-side rendering crawlability by comparing the initial raw HTML search crawlers receive against the final JavaScript-rendered catalog content to identify missing product data, delayed meta tags, and inconsistent SEO signals.

What is the best way to validate Product schema.org JSON-LD for rich results eligibility?

The best way to validate Product schema.org JSON-LD is to check for the presence of required structured data fields including offers, price, and availability to support rich results and avoid search policy failures.

How do I fix missing canonical URLs and sitemap coverage for AEM EDS product routes?

Fix missing canonical URLs and sitemap coverage by validating robots.txt directives, checking route-based product URL inclusion in the sitemap, and ensuring canonical tags point to the correct crawlable product destinations.

Does this approach work for optimizing LCP product images and alt text for SEO?

Yes, this approach works for optimizing LCP product images by evaluating loading strategy, prioritizing the largest contentful paint image, validating width and height attributes, and reviewing alt text quality to reduce indexing risk.

What are the limitations of auditing technical PDP SEO for JavaScript-rendered content?

A limitation of auditing technical PDP SEO for JavaScript-rendered content is that it requires analyzing at least three storefront product URLs to accurately map the gap between the static HTML crawl surface and the dynamic API-rendered catalog data.