Shopware SEO: Understanding and Managing the Obsolete 'revisit-after' Meta Tag
Shopware SEO: Understanding and Managing the Obsolete 'revisit-after' Meta Tag
The Shopware community recently discussed the "revisit-after" meta tag, a topic that often surfaces when merchants or developers delve into their store's SEO configuration. The core question posed was: "Wo kann man revisit-after einstellen?" (Where can one set revisit-after?) – highlighting a common challenge with managing specific meta tags in Shopware.
The Challenge: No Direct Admin Setting for 'revisit-after'
The initial inquiry revealed that Shopware, by default, does not offer a direct setting in the administration panel to configure the "revisit-after" meta tag. This can be particularly frustrating for shop operators who prefer managing such aspects without diving into code. As one user, R4M, expressed, the absence of an admin setting is "sehr ungünstig für Shopbetreiber" (very inconvenient for shop operators).
For developers, however, specific locations within the Shopware core were identified where this meta tag might be present and could be adjusted:
- In the PHP logic:
shopware/src/Storefront/Page/GenericPageLoader.php#L31 - In the Twig template responsible for meta tags:
shopware/src/Storefront/Resources/views/storefront/layout/meta.html.twig#L29
Modifying these files directly, especially core files, is generally not recommended as it can lead to issues during updates. Theme customization is a more robust approach for developers.
The Crucial SEO Insight: 'revisit-after' is Obsolete
While the discussion started with where to configure the tag, the most significant insight came from user raymond-de, who researched the tag's relevance. It was conclusively stated that both revisit-after and revisit meta tags are outdated and offer no added value for search engine optimization. This finding is backed by Google's own statements dating back to 2007, indicating that these tags have long been ignored by major search engines like Google.
This revelation effectively shifts the focus from "how to set it" to "why bother setting it at all." Many older themes or custom implementations might still include this tag, as raymond-de noted their own custom theme had:
However, its presence is benign at best and does not contribute to improved crawling or indexing by modern search engines.
Workarounds for Template Management (If Still Desired)
Despite the tag's obsolescence, the thread also provided practical solutions for those who might still need to modify templates for other reasons or manage similar meta tags. DannyBO suggested using a plugin like the Custom Template Manager from the Shopware Store. This tool allows shop operators to create and edit custom templates directly via the web administration, bypassing the need for direct file system access or developer intervention for minor template adjustments.
This highlights a broader sentiment within the community, articulated by EikeBrandtWarneke, that Shopware's native handling of SEO topics is often "sehr stiefmütterlich" (very neglectful or poor), leading users to rely heavily on a "Vielzahl an starken Plugins" (multitude of strong plugins) to fill these gaps.
Conclusion: Focus on Modern SEO Practices
The discussion around the "revisit-after" meta tag in Shopware serves as an important reminder for e-commerce merchants and developers. While it's natural to seek control over every aspect of a website's SEO, it's crucial to stay updated on current search engine algorithms and best practices. The "revisit-after" tag is a relic of an older internet era and holds no sway with modern search engines.
Instead of attempting to configure or remove this outdated tag, resources are better spent on impactful SEO strategies such as optimizing content, improving site speed, ensuring mobile responsiveness, building quality backlinks, and utilizing relevant, actively supported SEO plugins for Shopware that address current ranking factors.