Unknown source from a .ru website, use at own riak. Fails VT.Новая версия 4SEO 5.4.0
Techrad 's signature
Unknown source from a .ru website, use at own riak. Fails VT.Новая версия 4SEO 5.4.0
Thank you very much 'rivanov'!Новая версия 4SEO 5.4.0
Version 6.1.0
newAll types of rules can now execute based on the domain used to access a page: redirect, metadata, inject content, analytics, error pages, content replacement,...
newAll types of rules can now execute based on visitor user groups, as well as IP addresses: redirects, inject content, analytics, error pages, content replacement,...
chgEasier to use confirmation popups, do not change page scroll position when opening or closing
chgPrevent deprecation notices...
Version 6.3.1
chg Increased fuzziness of update access key display in system configuration for more privacy
chg Ensure no spaces around update access key, in case the key is entered through Joomla update site page
chg Addded option to enable/disable structured data generation on SP PageBuilders pages
bug Finnish translation uses in a single string, can prevent 4SEO admin to work if using a template that adds CSS classes to body element also in the admin
bug Possible...
Version 6.5.0
chg Only use local illustrative images instead of loading them from Weeblr CDN, allows restrictive Joomla CSP configuration
bug Legacy SP PageBuilder version 3 pages cannot be analyzed
bug Language strings for 16 months duration was deleted
bug Accessibility: notification list icon button should not have an aria-owns attribute when the list is closed
Version 6.6.0
chgNow disabling native breadcrumb structured data output on Joomla 4+ to avoid duplicate with ours, and also prevent some Google Search Console warnings.
chgAdded support for either Person or Organization type in ProfilePage structured data rules
chgAdded x.com to list of domains to not crawl by default
chgNow using native dialog element for deletion confirmation
chgRemoved Weeblr Google Maps API key following Google Maps pricing change
chgBetter cleanup...
Version 6.6.1
chg Added warning about Google only triggering Event experience in search results for events with a physical location, not online
chg Detect if a structured data FAQ rule with CSS selector does not detect anything and do not output any structured data if so
bug Frontend editing does not sort images by size as expected
bug Frontend dialog broken after last update
bug Structured data output for the Course type is invalid if the provider is a custom value...
Thanks Thanks Thanks Thanks Thanks7.0.0.2735 - changelog
This is is a feature and maintenance release, with an important bug fix. As always compatible with Joomla 3 to 6 without compatibility plugin.
Here are the highlights:
- Refreshed user interface, less distraction and more compact
- Generation of Markdown alternate version of your pages automatically. Supports Content Signals policy to tell bots what they can do with your content. Also: content negotiation, canonical/alternate link management, structured data, configurable caching. Particularly useful for software or product documentation for instance
- Support for llms.txt file generation. Not used for SEO/AEO/GEO but can be useful for product or software documentation pages
- Added support for Content Signals policy. Tell bots which use of your content you allow.
- Added option to decide if automatic change detection runs on entire page or on just main content. Use the latter if your pages have modules with random or often updated content, causing 4SEO to re-analyze pages too often
- Joomla light/dark mode switch in User menu now also control our light/dark mode
- Prevent Joomla using null as an array offset on 404s, which causes PHP deprecation warnings
- YooTheme Pro template can now display 4SEO error pages in full - Joomla 5+ only
- Sitemaps are now served without cookies
- Prefer the live meta description possibly set by Joomla, if any, over the one stored during analysis, in case the page has not been re-analyzed yet
- Under rare circumstances, Joomla may redirect some 404s to home page, when a 4SEO error page is active
- Redesigned notifications icon, was not accessible
- Some toolbar buttons may fail WCAG 2.2 AAA in light mode
- Changed striped tables dark rows background color, was not WCAG 2.2 AAA compliant
- FAQPage and ListItem structured data types use wrong letter case
- Dutch language shows HTML tags in initial setup wizard title
- Some expansion variables may not be available (published date)
thanks dano appreciated it ^^^^^^7.0.0.2735 - changelog
This is is a feature and maintenance release, with an important bug fix. As always compatible with Joomla 3 to 6 without compatibility plugin.
Here are the highlights:
- Refreshed user interface, less distraction and more compact
- Generation of Markdown alternate version of your pages automatically. Supports Content Signals policy to tell bots what they can do with your content. Also: content negotiation, canonical/alternate link management, structured data, configurable caching. Particularly useful for software or product documentation for instance
- Support for llms.txt file generation. Not used for SEO/AEO/GEO but can be useful for product or software documentation pages
- Added support for Content Signals policy. Tell bots which use of your content you allow.
- Added option to decide if automatic change detection runs on entire page or on just main content. Use the latter if your pages have modules with random or often updated content, causing 4SEO to re-analyze pages too often
- Joomla light/dark mode switch in User menu now also control our light/dark mode
- Prevent Joomla using null as an array offset on 404s, which causes PHP deprecation warnings
- YooTheme Pro template can now display 4SEO error pages in full - Joomla 5+ only
- Sitemaps are now served without cookies
- Prefer the live meta description possibly set by Joomla, if any, over the one stored during analysis, in case the page has not been re-analyzed yet
- Under rare circumstances, Joomla may redirect some 404s to home page, when a 4SEO error page is active
- Redesigned notifications icon, was not accessible
- Some toolbar buttons may fail WCAG 2.2 AAA in light mode
- Changed striped tables dark rows background color, was not WCAG 2.2 AAA compliant
- FAQPage and ListItem structured data types use wrong letter case
- Dutch language shows HTML tags in initial setup wizard title
- Some expansion variables may not be available (published date)