Update 3.25.0 brought back SEO-unfriendly slag for TOC widget links #29144
anatshecodes
started this conversation in
Feature Request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Prerequisites
What problem is your feature request going to solve? Please describe..
Until the last major update to Elementor, after clicking on a link in table of contents, the link brought to the correct location but didn't display the location in the URL.
The URL remains as it was, unchanged:
https://XXXX.com/YYYYYYYY
Now, after updating Elementor to version 3.25.0, after clicking on a link in the table of contents, the link in the URL looks like this:
https://XXXX.com/YYYYYYYY/#elementor-toc__heading-anchor-3
Describe the solution you'd like.
I would be very happy if there was a way to define something different from: #elementor-toc__heading-anchor-3
My text on the site is not in English, but the slag is in English. So I can't use a solution that automatically takes the text in the headings (h1/h2/h3).
The solution could be to add to the TOC widget an option to define the links that are created via CSS ID. Just as is the case for anchor links.
update:
It turns out that if you put a css id in the header it changes the link created by the TOC table.
Although it is not possible to give a CSS ID when the post content is not edited using Elementor, but it is possible to insert the id into the code.
More explanation here:
#10052 (comment)
At least if it is possible to shorten the long text that appears automatically in this generated link
For example from: #elementor-toc__heading-anchor-3
to: /#title-3
And it would help if there was an option to decide whether or not to show the table of contents link.
Maybe only if you open the link in a separate browser...
Describe alternatives you've considered.
If anyone is currently using a third-party plugin, which can be combined with Elementor and define the slug through the CSS ID definition, I would appreciate it if you could recommend it to me.
Or if there is a solution through CSS code.
Additional context
I understand that this is a problem that existed in the past and was reported, for example:
2024: https://github.com/orgs/elementor/discussions/24897
2020: #10052
That's why it's really frustrating that Elementor still hasn't given an adequate solution for this.
Agreement
Beta Was this translation helpful? Give feedback.
All reactions