Skip to content

JT SEO Control Center v1.0.67 – Joomla Schema Compatibility Fixes

Latest

Choose a tag to compare

@joomtheme joomtheme released this 18 Aug 21:42
· 2 commits to main since this release
9c6d774

JT SEO Control Center v1.0.67 focuses on the structured-data issues reported after v1.0.66 and improves coexistence with Joomla's native Schema.org output.

Fixed

  • Fixed Joomla Article output so datePublished uses the real Joomla publication date and falls back to the created date.
  • Fixed dateModified so it uses the real modification date and falls back to datePublished when necessary.
  • Fixed relative Schema image/logo URLs that could resolve below multilingual paths such as /en/products/images/... and return 404 errors.
  • Fixed multilingual WebSite.name and og:site_name by adding a dedicated website-name value globally and per language.
  • Improved duplicate handling with Joomla core Schema.org output: when Joomla's native graph exists, JT SEO now enriches that graph instead of publishing a competing Article/WebPage graph.

Multilingual identity

Language-specific Schema settings now support both:

  • Organization / LocalBusiness name
  • WebSite name
  • Logo
  • Alternate name and description
  • Email and telephone
  • Address fields

Empty language-specific values continue to fall back to the global configuration.

Joomla core Schema compatibility

Joomla core Schema.org support may remain enabled. JT SEO detects the native Joomla graph and enriches it with the configured multilingual identity, absolute media URLs and Article publication/modification dates.

If Joomla core Schema output is unavailable, JT SEO continues to generate its own JSON-LD graph.

Template Microdata note

JSON-LD duplicate protection cannot safely remove Article Microdata embedded directly by a template using itemscope, itemtype and itemprop. If a template produces a separate Article Microdata entity, remove that Article Microdata from the template when using Joomla/JT SEO JSON-LD Article output to avoid two Article entities in validators.

Page builders

SP Page Builder and other non-article component pages continue to use WebPage structured data. Article publication/modification dates are not added to generic WebPage output.

Thanks

Special thanks to @niaziblog for the detailed multilingual and structured-data testing that helped identify these issues.