Section 26 — Storefront: Schema & Brand Identity Settings

This section controls how your brand, policies, and business identity are represented in structured data (JSON-LD) and social previews across your storefront. These settings do not change how your site looks to customers, but they are critical for trust, compliance, and search engine understanding.

Schema Logo

The Schema Logo is used in your site’s structured data to establish brand provenance.

  • This logo is embedded into JSON-LD as your official brand mark
  • It helps search engines and AI systems associate products with your business entity
  • The logo does not affect storefront visuals

Best practice:

Use your primary brand logo in a clean, square or horizontal format.

Social Links

You may optionally add social profile URLs (e.g. brand social accounts).

  • These links are included in structured data
  • They support brand verification and entity trust
  • They are not required

Leaving this blank does not affect enrichment quality.

Policy & Company Page Links

These fields link your existing policy and company pages into structured metadata:

  • Privacy Policy
  • Terms & Conditions
  • About Us
  • Return Policy

These links are used for:

  • Compliance signaling
  • Trust indicators for crawlers
  • Merchant identity validation

Important note:

If your site uses a single page that contains multiple policies, it is acceptable to reuse the same URL in multiple fields as long as the page contains relevant content.

Address Information

Your business address is used to:

  • Anchor your merchant entity
  • Support trust and compliance signals
  • Improve consistency across product and category schema

This information does not need to match a public storefront address exactly, but it should represent a real business location.

Twitter / Social Metadata

Optional fields for:

  • Twitter Site
  • Twitter Creator

These are used only for social preview enrichment and structured metadata.

If you do not actively use Twitter/X, these can be left blank without impact.

Saving & Updates

  • Changes here are applied immediately to structured data
  • No storefront downtime is required
  • Updates affect future renders and crawls, not historical data

Key Takeaway

This section defines who you are, not what you sell.

CatalogPilot uses these settings to:

  • Establish merchant identity
  • Strengthen trust signals
  • Support compliance and discoverability

You do not need to perfect every field — accurate, honest information is sufficient.

Follow
Reply