The Category List View provides merchants with a structured, low-cognitive overview of all categories detected in their catalog and their relationship to enriched products. While categories are not enriched in isolation, they play a critical role in how product discovery, indexing, and navigation are structured across the storefront.

This view mirrors the Product List View in layout and behavior, with category-specific controls layered on top.

Purpose of the Category List View

The Category List View allows merchants to:

• See which categories are eligible for enrichment
  
• Control whether enriched category metadata is delivered to the storefront
  
• Navigate directly to related products within a category
  
• Review enrichment status without managing categories independently from products
  

Important: Categories exist to support and amplify product discovery. Only categories that contain products are eligible for enrichment.

Category Rows & Columns

Each row represents a single category and includes the following elements:

• Image
  
  Displays the category image when available.
  
  
• Enabled Toggle
  
  Controls whether enriched category metadata is actively delivered.
  
  
• Green: Enrichment delivery enabled.
  
• Orange: Enrichment delivery disabled (original storefront behavior only).
  
  
• Title
  
  The category name as defined by the platform.
  
  
• Language
  
  Indicates the language associated with the category record.
  
  
• Status
  
  
• Orange/Brown page icon: Category not yet enriched.
  
• Green checkmark: Category enriched and approved.
  
  
• Approved / Synced Date
  
  Shows when the category was last approved and delivered.
  
  
• Storefront Link Icon
  
  Opens the category directly on the live storefront.
  

Category → Product Relationship (Key Feature)

On the far right of each row is a purple eye icon with a number:

• The number indicates how many products belong to that category.
  
• Clicking the eye icon filters the Product List View to show only products within that category.
  
• Clicking the row itself opens the Category Gallery view.
  

This reinforces an important design principle:

Categories are not managed independently — they are always viewed in relation to their products.

Empty or Historical Categories

Some categories may appear with zero products. These are typically:

• Historical categories
  
• Legacy platform artifacts
  
• Empty organizational groupings
  

Categories with no products:

• Are displayed for visibility
  
• Are never enriched
  
• Do not affect billing or delivery
  

Delete Behavior

A red trash icon (left of the image column) allows merchants to delete a category record from CatalogPilot.

• Deleting a category removes it from CatalogPilot only.
  
• If the category still exists on the platform, it will be re-synced automatically and become eligible again in the future.
  

Header Controls & Filters

The Category List View includes the same global controls found in the Product List View:

• Not Yet Enriched (orange outline)
  
• View All Approved (green outline)
  
• Show All (neutral/gray outline)
  

Additional features include:

• Search field
  
• Filter drawer (status, inactive items)
  
• Column visibility selector
  
• Pagination controls at the bottom of the list
  

Review Awareness

If any products within categories are awaiting review:

• A blue badge appears in the header with the count.
  
• Clicking it redirects merchants to the Review Queue.
  

If no items are pending review:

• The badge turns green and displays zero.
  

Key Concept to Remember

Categories are structural amplifiers, not standalone entities.

They exist to:

• Support product discovery
  
• Improve crawler understanding of catalog hierarchy
  
• Extend enriched metadata across grouped products
  

Merchants are not expected to “manage” categories actively — the system handles this automatically based on product relationships.

The Category Gallery provides a consolidated, human-readable and machine-readable view of how CatalogPilot structures, enriches, and delivers category-level metadata.

Unlike the Product Gallery, which focuses on individual SKUs and variants, the Category Gallery exists primarily to support search engine and AI crawler understanding of category intent, hierarchy, and relevance.

Merchants should treat this view as informational and confirmatory, not as a primary editing surface.

Purpose of the Category Gallery

The Category Gallery is designed to:

• Anchor category-level intent for crawlers and AI systems
  
• Provide structured metadata that most platforms do not expose natively
  
• Strengthen discovery pathways for all products within a category
  
• Ensure consistent semantic framing across collections, assortments, and curated groups
  

Category enrichment is about machine comprehension, not storefront presentation.

Gallery Layout Overview

The Category Gallery uses the same three-column structure as the Product Gallery:

Left Column — Human-Readable Context

• Category image carousel (when available)
  
• Category title and alternative title
  
• Short and long descriptions
  

These descriptions are not typically displayed to storefront visitors on most platforms.

They exist to provide contextual grounding for the machine-readable metadata in the adjacent columns.

Middle Column — ADA, Social & Structural Metadata

This column includes:

• ADA image metadata (Title, Alt, Caption)
  
• OpenGraph metadata
  
• Twitter/X metadata (where applicable)
  

If all products within the category have been enriched, each related image will display unique ADA tags, ensuring accessibility compliance and consistent image interpretation by screen readers and crawlers.

Right Column — SEO, Legal & AI Anchors

This column contains:

• SEO metadata (Meta Title, Meta Description, Keywords, H1–H3)
  
• Legal/PCI provenance (merchant identity, address, policies)
  
• AI semantic fields (LLM summary, differentiator, target audience, shopping style)
  

These fields are explicitly optimized for non-human consumers:

• Search engines
  
• AI discovery systems
  
• Shopping feeds
  
• Knowledge graph ingestion
  

Original vs Approved Toggle

As with Product Gallery views, merchants can toggle between:

• Original — Content detected from the platform and storefront
  
• Approved — CatalogPilot-generated and approved metadata
  

In most cases, the Original view for categories contains little or no usable data, which reinforces the value of category-level enrichment.

Once approved, the Approved view becomes the authoritative semantic reference for that category.

Category Images & Inheritance Behavior

As merchants navigate through category images:

• Each image inherits structural context from the category
  
• ADA metadata is generated with awareness of both:
  
  
• The category theme
  
• The products associated with it
  
  

This ensures that category images do not exist in isolation but contribute meaningfully to overall discoverability.

Editing Guidance

Merchants are not required to edit category gallery fields.

• Most fields are generated deterministically
  
• Editing should only occur if the merchant has verified, factual information
  
• Invented or speculative edits should be avoided
  

Category enrichment is designed to be:

• Stable
  
• Low-maintenance
  
• Non-destructive
  

Why Category Galleries Matter

Most eCommerce platforms provide little to no structured category metadata for crawlers.

By enriching categories independently:

• CatalogPilot establishes clear semantic boundaries
  
• All products within a category benefit indirectly
  
• Discovery signals compound across the catalog
  

This is a foundational element of catalog-level intelligence, not an optional enhancement.

Key Takeaway for Merchants

The Category Gallery exists so machines understand what your category means, not just what it contains.

Merchants should:

• Review at a glance
  
• Approve with confidence
  
• Move on
  

The system is designed to do the heavy lifting automatically.

The Category tab provides a structured editing and reference view for individual product categories.

It mirrors the Product tab in layout, controls, and behavior, but applies those same principles at the category level rather than the individual product level.

This tab is secondary to the Category Gallery, which remains the primary overview for category enrichment. The Category tab exists to allow targeted review, confirmation, or adjustment when needed.

Purpose of the Category Tab

The Category tab allows merchants to:

• Review category-level metadata generated by CatalogPilot
  
• Make factual corrections or additions where appropriate
  
• Reference platform identifiers and source URLs
  
• Control whether CatalogPilot or the original platform content is used for specific fields
  

Merchants are not required to edit this tab for normal operation.

Field Behavior & Visual Indicators

Each field in the Category tab follows the same visual logic used throughout CatalogPilot:

• Green outline: Approved CatalogPilot content
  
• Yellow outline: Optional or incomplete field (not required)
  
• Eye icon (orange): Original platform content is being used
  
• Eye icon (gray): Approved CatalogPilot content is active
  
  

Toggling the eye icon allows merchants to switch between:

• Original platform data
  
• Approved CatalogPilot-generated data
  
  

This can be done field by field, without affecting other category metadata.

Editable Fields

Common editable fields include:

• Category Title
  
• Alternate Title
  
• Short Description
  
• Long Description
  

Editing is available via:

• Manual input
  
• Optional AI regeneration (where enabled)
  

As with all CatalogPilot tabs, merchants should only edit fields when they are confident the information is factually correct. Invented or speculative content should be avoided.

Platform Identifier & URL (Read-Only)

At the bottom of the Category tab, two reference fields are displayed:

• Platform Identifier
  
  A unique identifier assigned by the eCommerce platform (e.g., Lightspeed, Shopify).
  This field is read-only and used internally for synchronization and traceability.
  
  
• URL
  
  The canonical storefront URL for the category.
  This is provided for reference and verification only and should not be edited.
  
  

These fields help merchants confirm exact platform alignment without requiring external navigation.

Relationship to Category Gallery

The Category tab does not replace the Category Gallery.

• The Category Gallery is optimized for:
  
  
• Machine readability
  
• Discovery
  
• Indexing
  
• Semantic anchoring
  
  
• The Category tab is optimized for:
  
  
• Review
  
• Minor edits
  
• Confirmation
  
• Provenance reference
  
  

In most cases, merchants will review the Category Gallery and approve without modification, using the Category tab only when clarification is necessary.

Recommended Merchant Behavior

CatalogPilot recommends the following workflow:

1. Review category output in the Category Gallery
   
   
2. Approve if content appears accurate
   
   
3. Use the Category tab only for:
   
   • Small factual corrections
     
   • Adding known details
     
   • Verifying platform alignment
     

The system is designed to minimize manual intervention while preserving full merchant control.

Key Takeaway

The Category tab provides precision control, not required workload.

It exists to support accuracy and confidence, while CatalogPilot handles the heavy lifting automatically.

The Category SEO tab controls how category pages are described, structured, and indexed by search engines and AI crawlers.

Unlike the Category Gallery (which visualizes machine-readable output), this tab exposes the underlying SEO control fields that power that output.

This tab is machine-oriented, not customer-facing.

Purpose of the Category SEO Tab

The Category SEO tab exists to:

• Define how category pages are interpreted by search engines
  
• Provide structured semantic anchors for category-level indexing
  
• Ensure consistent, non-destructive SEO signals across the storefront
  

Most merchants do not need to edit this tab after initial enrichment.

SEO Fields Explained

The following fields are generated and managed by CatalogPilot:

• Meta Title
  
  The primary title used by search engines for the category page.
  Optimized for clarity, relevance, and length.
  
  
• Meta Description
  
  A concise, descriptive summary intended for search results and AI previews.
  
  
• Meta Keywords
  
  Included for legacy systems and broad semantic reinforcement.
  These do not control rankings directly but support contextual understanding.
  
  
• H1 / H2 / H3
  
  Logical heading hierarchy used to reinforce category intent and structure.
  These are aligned with modern SEO and accessibility standards.
  
  

Each field is outlined in green when approved and active.

Original vs. Approved Content

As with other tabs:

• Orange eye icon → Original platform content is shown
  
• Gray eye icon → Approved CatalogPilot content is shown
  
  

Merchants may toggle individual fields back to original content if needed, though this is rarely necessary.

Editing Behavior

Editing is available via:

• Manual text edits
  
• Optional AI-assisted regeneration (where enabled)
  
  

CatalogPilot recommends minimal editing in this tab.

SEO fields are tightly coupled to:

• Canonical URLs
  
• Structured data (JSON-LD)
  
• Downstream discovery behavior
  

Unnecessary changes can weaken consistency rather than improve results.

Source URL & Canonical URL

At the bottom of the tab:

• Source URL
  
  The platform-generated category URL from the storefront.
  
  
• Canonical URL
  
  The authoritative URL used for indexing.
  
  

These fields are read-only and exist to:

• Prevent duplication
  
• Preserve platform authority
  
• Ensure stable indexing
  

CatalogPilot does not alter canonical ownership.

JSON-LD (Structured Data)

The expandable JSON-LD section displays the structured data generated for the category.

This data is:

• Injected at render time
  
• Consumed by search engines and AI systems
  
• Synchronized with approved SEO fields
  

It is provided for inspection only and should not be manually edited.

Relationship to Category Gallery

• The Category Gallery shows how this SEO data is interpreted and delivered.
  
• The Category SEO tab shows where that data originates and how it is controlled.
  

Most merchants will:

1. Review the Category Gallery
   
2. Approve the output
   
3. Rarely revisit the SEO tab
   

Recommended Merchant Guidance

• Do not chase perfection in this tab
  
• Avoid speculative keyword stuffing
  
• Edit only when correcting factual errors or branding alignment
  

CatalogPilot’s defaults are designed to be safe, conservative, and index-stable.

Key Takeaway

The Category SEO tab is a precision control surface for search engines, not a marketing editor.

In most cases, approval without modification is the correct action.

The Category Social tab controls how category pages are represented when shared on social platforms such as Facebook, LinkedIn, X (Twitter), and similar networks.

This tab defines social preview metadata, not storefront presentation.

Purpose of the Category Social Tab

The Category Social tab exists to:

• Provide optimized preview titles and descriptions for social sharing
  
• Ensure consistent, brand-safe messaging when category links are shared
  
• Support social platforms that rely on OpenGraph and Twitter Card metadata
  

These fields are machine-read by social platforms, not by customers browsing the site.

OpenGraph Fields

OpenGraph metadata is primarily used by:

• Facebook
  
• LinkedIn
  
• Messaging platforms that generate link previews
  

Available fields include:

• OpenGraph Title
  
  The headline shown in social previews when a category link is shared.
  
  
• OpenGraph Description
  
  A concise description used beneath the title in previews.
  
  
• OpenGraph Image (optional)
  
  When present, defines the image shown in social previews.
  
  If not set, platforms fall back to default category imagery.
  
  
• OpenGraph Type (optional)
  
  Typically inferred automatically and rarely requires manual input.
  
  

Most merchants will not need to modify these fields after initial enrichment.

Twitter Fields

The Twitter section controls how category links appear on X (Twitter):

• Twitter Card (optional)
  
  Defines the card layout type. Defaults are usually sufficient.
  
  
• Twitter Title
  
  Optimized title used in the tweet preview.
  
  
• Twitter Description
  
  Short descriptive copy optimized for social consumption.
  
  
• Twitter Image (optional)
  
  Image used in Twitter previews when specified.
  
  

As with OpenGraph, these fields are not required to be completed manually unless a merchant has specific branding requirements.

Editing Behavior

All fields follow the same system-wide rules:

• Green outline → Approved CatalogPilot content
  
  
• Orange outline → Optional / not required
  
  
• Edit icon → Manual edits allowed
  
  
• Original-content icon → View or revert to platform-provided content
  
  

Edits should be made only when correcting factual issues or enforcing brand tone.

Relationship to Category SEO & Gallery

• The Category SEO tab governs how categories are indexed by search engines.
  
  
• The Category Gallery visualizes machine-readable output.
  
  
• The Category Social tab governs how categories appear when shared externally.
  
  

Each serves a different audience:

• Search engines
  
• AI crawlers
  
• Social platforms
  

Recommended Merchant Guidance

• Do not chase perfection in social metadata
  
• Avoid rewriting content simply for stylistic reasons
  
• Leave optional image fields blank unless there is a clear need
  

CatalogPilot’s defaults are designed to produce safe, consistent previews across platforms.

Key Takeaway

The Category Social tab is a preview-control layer, not a content editor.

In most cases, review and approve without modification is the correct action.

The Category ESG tab allows merchants to optionally associate ethical, sustainability, and suitability signals with an entire product category.

This section is supplementary, not required, and is designed primarily for machine-readable interpretation rather than direct customer-facing content.

Purpose of the Category ESG Tab

The Category ESG tab exists to:

• Attach high-level ethical or suitability indicators to categories
  
• Support future ESG-aware search, filtering, and AI discovery
  
• Provide structured context for platforms, marketplaces, and compliance systems
  

These fields are not required for successful enrichment or delivery.

Available Fields

Depending on category type, the following ESG-related fields may appear:

• Minimum Age
  
  Indicates an age threshold when a category contains products that may require age consideration.
  This is typically left blank unless the category clearly warrants it.
  
  
• Additional ESG Signals (context-dependent)
  
  Some categories may expose additional ESG-related fields depending on product makeup or compliance relevance.
  
  

Field Behavior & Visual Cues

• Yellow outline → Optional field
  The system has not auto-populated this value and does not require it.
  
  
• Edit icon → Manual entry allowed
  Merchants may enter values only when factual and applicable.
  
  
• No requirement to complete
  Leaving fields blank does not affect enrichment, approval, or delivery.
  

CatalogPilot intentionally avoids inventing ESG data.

Recommended Merchant Guidance

• Only populate ESG fields when the information is known, factual, and consistent
  
• Do not guess, infer, or “fill for completeness”
  
• Most merchants will leave this tab unchanged
  

Incorrect ESG data is worse than missing ESG data.

Relationship to Other Tabs

• Attributes define structured product traits
  
• SEO and Social define discovery and sharing behavior
  
• ESG provides ethical and suitability context for machines and future systems
  

The ESG tab complements the catalog — it does not control it.

Key Takeaway

The Category ESG tab is optional, conservative, and future-facing.

If you are unsure, leave it blank.

CatalogPilot prioritizes correctness over completeness.

The Category AI tab provides advanced, machine-oriented context that helps anchor a category within AI-driven search, recommendation, and discovery systems.

This tab is not required for daily operations, enrichment approval, or storefront delivery. It exists to future-proof your catalog and strengthen long-term semantic understanding.

Purpose of the Category AI Tab

The Category AI tab is designed to:

• Establish a high-level semantic identity for a category
  
• Support AI assistants, conversational search, and generative discovery
  
• Reinforce consistent interpretation across products within the category
  

These fields do not directly control storefront display or pricing.

Available Fields

The Category AI tab may include:

• LLM Summary
  
  A concise, natural-language description of the category’s purpose, style, and intent.
  This acts as a narrative anchor for AI systems.
  
  
• Differentiator
  
  Highlights what makes this category distinct relative to others.
  Used for contextual comparison and AI ranking signals.
  
  
• Target Audience
  
  Describes the intended audience in human-readable terms, optimized for AI interpretation.
  
  
• Shopping Style
  
  Indicates how this category is typically browsed or purchased (e.g., wardrobe building, essentials, gifting).
  

Field Behavior & Visual Cues

• Green outline → Approved, active AI context
  
• Edit icon → Manual adjustment permitted
  
• Original content icon → View previously generated or inherited values
  

Most fields are pre-generated and safe to leave unchanged.

Editing Guidance

Manual editing is optional and should be done sparingly.

Recommended best practices:

• Edit only when you have clear brand intent to express
  
• Avoid rewriting fields repeatedly
  
• Do not attempt to “optimize” for keywords or trends
  

CatalogPilot’s generated AI context is intentionally conservative and structured to avoid drift.

Relationship to Other Tabs

• SEO focuses on traditional search engines
  
• Social supports sharing and previews
  
• AI supports next-generation discovery systems
  

The AI tab complements — it does not replace — other enrichment layers.

Key Takeaway

The Category AI tab is a future-facing semantic layer.

It helps AI systems understand what this category is, who it’s for, and why it exists — without impacting day-to-day storefront behavior.

If you’re unsure, leave it as generated.