mageworx / module-seomarkup-graph-ql
N/A
MageWorx_SeoMarkupGraphQl
GraphQL API module for MageWorx Magento 2 SEO Suite Ultimate.
Installation
-
Copy-to-paste method
Download this module and upload it to the
app/code/MageWorx/SeoMarkupGraphQldirectory. Create theSeoMarkupGraphQldirectory first if it does not exist. -
Installation using Composer (from Packagist)
composer require mageworx/module-seomarkup-graph-ql
How to use
SeoMarkupGraphQl extends the output attributes of the Product, Category and CMS Page queries with the mw_seo_markup field.
Supported fields
- Product
mw_seo_markupsocial_markuprich_snippetswebsitesellerproductbreadcrumbs
- Category
mw_seo_markupsocial_markuprich_snippetswebsitesellerbreadcrumbs
- CMS Page
mw_seo_markupsocial_markuprich_snippetswebsitesellerwebpagebreadcrumbs
Other attributes are defined according to the Magento GraphQL guide.
Product, Category and CMS Page queries use syntax similar to the Magento user guide.
Product query signature
products(
search: String
filter: ProductAttributeFilterInput
pageSize: Int
currentPage: Int
sort: ProductAttributeSortInput
): Products
Request
{
products(filter: {sku: {eq: "24-WB04"}}) {
items {
name
sku
mw_seo_markup {
social_markup
rich_snippets {
website
seller
product
breadcrumbs
}
}
}
}
}
Response
{
"data": {
"products": {
"items": [
{
"name": "Overnight Duffle",
"sku": "24-WB07",
"mw_seo_markup": {
"social_markup": "\\n<meta property=\\\"og:type\\\" content=\\\"product.item\\\"/>\\n<meta property=\\\"og:title\\\" content=\\\"Overnight Duffle\\\"/>\\n...",
"rich_snippets": {
"website": "<script type=\\\"application/ld+json\\\">{\\\"@context\\\":\\\"http://schema.org\\\",\\\"@type\\\":\\\"WebSite\\\",\\\"url\\\":\\\"https://store_url/\\\"}</script>",
"seller": "<script type=\\\"application/ld+json\\\">{...}</script>",
"product": "<script type=\\\"application/ld+json\\\">{...}</script>",
"breadcrumbs": "<script type=\\\"application/ld+json\\\">{...}</script>"
}
}
}
]
}
}
}
Known limitations
The breadcrumbs rich snippet rebuilds the category path directly from the current category/product so it stays correct across items in a list query. As a result, third-party plugins on Magento\Catalog\Helper\Data::getBreadcrumbPath() are not reflected in the GraphQL output, unlike on the storefront.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.2.1 | stable | Fail | Not compatible Details | 2026-07-22 18:03:20 |
| 1.2.0 | stable | Fail | Not compatible Details | 2026-07-16 13:30:21 |
| 1.1.1 | stable | Fail | Not compatible Details | 2026-02-12 15:46:35 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2021-04-30 11:46:37 |
Requires 2
| Package | Constraint |
|---|---|
| magento/framework | >=102.0.0 < 104 |
| mageworx/module-seomarkup | >= 2.13.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Pass | 0 | |
| PHPMD | Warning | 56 | 56 rule violations (UnusedFormalParameter:50, CyclomaticComplexity:2, NPathComplexity:2, ExcessiveMethodLength:1, MissingImport:1) |
| Cpd | Warning | 1 | 1 duplicated chunk spanning 42 total lines (min-lines=5, min-tokens=70) |
| Composer validate | Info | 2 | valid; 2 advisory notes (composer validate --strict) |
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from mageworx
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.