-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEO Duplicate Content (page included) #16
Comments
Update: |
It seems to work Google Search Console
|
This was how it looked before Google Search Console
|
Now it is not purposeful if you have to use the plugin OGra_XH to get the script into the head of the page. |
I wouldn't do this with JS anyway. Either leave it to the user (manually via meta_tags plugin), or do it automatically by assigning to |
Unfortunately, there is no solution with only one variant. A bot without JS would find only the links to the corresponding content (a1 - a4) on the page with the plugin call for expandcontract, but would find "index, follow" on pages a1 - a4 - so everything is correct. A bot with JS finds the entire content on the page with the plugin call for expandcontract, but on the pages a1 - a4 "noindex, nofollow" - again everything correct. Since it depends on JS, I see no other way than to regulate this also via JS. |
I actually do not believe that. There are also variants where hidden pages should be indexed, sometimes it is just that it should not appear in the menu. |
It's not about functions for the user or the handling, only about SEO.
Shortly declared: A Page with expandcontract and subpages a1, a2, a3, a4, ...
Now we have the texts that are individually on the pages a1, a2, a3, and a4, all also on page a. --> DC (page included)
My idea for this, add "noindex, nofollow" via JS for pages a1 - a4.
If the bot can JS, it finds on a1 - a2 "noindex, nofollow", if it can not JS, there is the default setting of the page from the plugin meta or the global setting from the configuration, so most likely "index, follow".
The text was updated successfully, but these errors were encountered: