When you add a field or a field group to the text, sh404sef puts the raw tags in the meta description instead of putting the outputted content... I think it's because the plugin tags are converted after sh404sef already generated the description? Is it possible to make sh404sef generate it after plugin tags have been converted?
Last post
10 min ago
Posts last week
94
Average response time last week
34 min
All time posts
67889
All time tickets
10493
All time avg. posts per day
20
Helpdesk is open from Monday through Friday CET
Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.
#4508 – {field } and {fieldgroup} shouldn't go in meta description
Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
TheSDHotel
wb_weeblr
Hi
Agreed, we will remove them in next version. I will have a test version soon.
Rgds
Agreed, we will remove them in next version. I will have a test version soon.
Rgds
TheSDHotel
Ok cool, will you just remove the tags or will it actually show the outputted content of the fields? :)
wb_weeblr
HI
Remove the tag. The possible fields contents varies too much, it's not possible to decide what to keep or not for a description field, it just go too far.
There's actually a filter on the list of regular expressions used to filter out things in the meta description, so if you care to change the list of things to remove on the fly, based on on the current page being displayed or something, you can do that also.
Here is the filter definition
The dev version should do that now. We have also expanded the auto-generated description to around 250 characters.
Rgds
Remove the tag. The possible fields contents varies too much, it's not possible to decide what to keep or not for a description field, it just go too far.
There's actually a filter on the list of regular expressions used to filter out things in the meta description, so if you care to change the list of things to remove on the fly, based on on the current page being displayed or something, you can do that also.
Here is the filter definition
/** * Filter a list of regular expressions that will be used to remove unwanted content in automatically generated meta description. * * @api * @package sh404SEF\filter\metadata * @var sh404sef_auto_fallback_description * @since 4.13.2 * * @param array $expressions List of regular expressions, ready to use in preg_replace. * @param string $content The original content from which description should be extracted. * * @return array */
The dev version should do that now. We have also expanded the auto-generated description to around 250 characters.
Rgds
TheSDHotel
I've noticed that in some articles the description was generated with the {plugin tags} (which is not desired) while in some article the actual content of the field was indexed for Google in the description (which is the desired outcome), how is it possible?
Take a look:
https://www.google.it/xxxx
Take a look:
https://www.google.it/xxxx
TheSDHotel
I don't know how it happened but I think it would be preferrable to keep the content of the fields, and not remove them. They are part of the Joomla core and they do not harm in anyway, for example these pages are completely field-based, so removing the fields means removing all the content which is very valuable for the description and search engines.
wb_weeblr
Hi
Rgds
the actual content of the field was indexed for Google in the description (which is the desired outcome), how is it possible?It likely means that Google did not use the description in the meta description, but instead pick their own. This roughly happens for about half the pages Google indexes (Yes, your efforts to produce a good description are 50% of the times pointles ;) ).
I don't know how it happened but I think it would be preferrable to keep the content of the fields, and not remove them. They are part of the Joomla core and they do not harm in anyway, for example these pages are completely field-based, so removing the fields means removing all the content which is very valuable for the description and search engines.That's not an option. At the time the (auto-generated) meta description is computed, Joomla has not made the replacement, so the actual content is simply not available.
Rgds
TheSDHotel
I understand...
And I assume it's not possible for you to move the process of the auto generated description to after the replacement is made? Just wondering... :)
Thank anyway!
And I assume it's not possible for you to move the process of the auto generated description to after the replacement is made? Just wondering... :)
Thank anyway!
wb_weeblr
Hi
Rgds
And I assume it's not possible for you to move the process of the auto generated description to after the replacement is made? Just wondering... :)This is how it was quite some times ago and we moved it there so that we get access to the actual main content of the page, rather than trying to extract a description from the fully rendered page - which is nearly impossible.
Rgds
TheSDHotel
Oh yeah, I perfectly understand where you're coming from... you would have to figure out where the actual content is inserted in the whole page, which I understand how it's nearly impossible.
So basically you only have two options when deciding when to run the auto generated description.
1) Access the actual content of the page before it's rendered
or 2) Access the whole page
I assume there isn't an "option 1.5" in between 1 and 2 where you can access just the content part but already rendered, which is a shame if there isn't. In this case I understand you have to choose option 1.
So basically you only have two options when deciding when to run the auto generated description.
1) Access the actual content of the page before it's rendered
or 2) Access the whole page
I assume there isn't an "option 1.5" in between 1 and 2 where you can access just the content part but already rendered, which is a shame if there isn't. In this case I understand you have to choose option 1.
wb_weeblr
Hi
Indeed, there's no mid-way to get the actual content with fields rendered.
Rgds
Indeed, there's no mid-way to get the actual content with fields rendered.
Rgds
TheSDHotel
Ok, then i guess the solution is only to remove them, which you already did, so we can close this. Thanks :)
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.