Question 1

Will this slow down my storefront?

Accepted Answer

No. The head block is cacheable="true" so the full JSON-LD payload is baked into full-page cache. Providers only run on uncached renders; cached hits serve the pre-rendered tag with zero PHP evaluation.

Question 2

Is it GDPR compliant?

Accepted Answer

The module only emits data already public on your storefront, product details, store identity, and aggregate review stats. It does not render personally identifiable data in structured-data form.

Question 3

Can I disable individual schemas?

Accepted Answer

Yes. Every provider has a Yes/No toggle under Stores → Configuration → Panth Extensions → Structured Data, Product, Breadcrumb, Organization, WebSite, FAQ, Article, Review, VideoObject, Brand, Seller, Product List (ItemList), ProductGroup, Pros/Cons, Energy Label, Certifications, Sale Event, Remove Native Markup.

Question 4

Does it work with Hyvä?

Accepted Answer

Yes. No JS, no RequireJS, no x-magento-init. The head block attaches via view/frontend/layout/default.xml to the head.additional container which every Magento theme exposes. Identical output on Hyvä, Luma, Breeze, and any custom theme.

Question 5

Does it support multi-store / multi-language?

Accepted Answer

Yes. Every admin field is [store view]-scoped, so different store views can ship different Organization data, social profiles, toggles, and attribute codes. URLs in the JSON-LD are scoped to the current store's base URL.

Question 6

Can I customize the emitted JSON?

Accepted Answer

Three ways, in increasing order of effort: Custom JSON-LD Properties (Product), admin field that accepts a JSON object; merged into the Product node on every PDP. Per-product EAV attributes, the resolver reads product attributes like meta_description, short_description, manufacturer, gender, populate those for per-product overrides. Custom provider class, implement StructuredDataProviderInterface, register in di.xml under the providers argument of Panth\StructuredData\Model\StructuredData\Composite (and Aggregator). The aggregator will pick it up automatically.

Question 7

Can I override a provider's output?

Accepted Answer

Yes, declare a virtualType in your own module's di.xml with the same class name as the provider you want to replace, or use a preference on Panth\StructuredData\Api\StructuredDataProviderInterface with a type constraint.

Question 8

Does it interact with `Panth_AdvancedSEO`, `Panth_Faq`, `Panth_Testimonials`?

Accepted Answer

Yes, friendly: Panth_AdvancedSEO: shares the panth_seo/general/enabled master switch when installed; defaults are set locally so standalone installs still work. Panth_Faq: FaqExtractor defers to Panth_Faq on its own routes and when the faq.schema block is mounted and producing data. Panth_Testimonials: ReviewProvider defers on the testimonials route when the module is enabled.

Question 9

Is `Panth_Core` required?

Accepted Answer

Yes. mage2kishan/module-core is a required dependency and is pulled in automatically by Composer.

Question 10

Does it emit `itemprop` / microdata?

Accepted Answer

No, only JSON-LD. Microdata is legacy and mixing the two often produces duplicate-structured-data warnings in Search Console. The RemoveNativeMarkupPlugin actively strips native Magento microdata from the target blocks.

Structured Data JSON-LD for Magento 2

Questions about Structured Data JSON-LD