-
AuthorPosts
-
October 22, 2014 at 8:22 pm #339720
Instead of selecting the blog page under reading settings in wordpress I have used the ‘blog’ module on the blog page to display the blog on a site.
The problem is that google is now indexing subpages of archives which creates duplicate content and indexing issues. This is normally resolved by ticking a box in WordPress SEO by yoast to ‘noindex subpages of archives’ but when you do this it doesnt work for the avia builder.
So if I search the source on page 2 of the blog for ‘noindex’ it’s not there. I am not sure if this is something that can be added manually in the template files or if this should be a feature request.
Thanks – Raleigh
October 23, 2014 at 2:36 am #339896Hey pageladder!
Thank you for using Enfold.
Please set the Blog on Enfold > Theme Options > Where do you want to display blog? option then go to Blog Layout panel. Set the Blog Style to “Use the advance layout builder”. We would like to check the actual website. Please post it here. Make sure that you’re running Enfold 3.0.2 on WordPress 4.0.
Cheers!
IsmaelOctober 23, 2014 at 7:11 pm #340297This reply has been marked as private.October 27, 2014 at 12:06 am #341188Hey!
I’m sorry but the blog is still not set as the blog page on Enfold > Theme Options > Where do you want to display blog? option. It is not being recognized as an archive or blog page.
Cheers!
IsmaelOctober 27, 2014 at 5:37 pm #341611Hey Ismael –
Thanks for the response.
Yes actually the blog IS set as the blog page on Enfold > Theme Options > Where do you want to display the blog option.I’ll post a screencast video in another private reply so you can see.
Thanks – Raleigh
October 27, 2014 at 5:40 pm #341613This reply has been marked as private.October 28, 2014 at 12:53 pm #342189Hi!
Thank you for the screencast. Did you also set this page as Posts page on Settings > Reading panel? If yes, please reset the settings to default. Please post the login details here. We would like check it.
Cheers!
IsmaelOctober 28, 2014 at 4:55 pm #342313So yea I tried it every which way and yes if I use the default wordpress setting in Setting > Reading it works as desired. But then I lose my custom layout builder setup which I would like to use…
Login details to be provided…
October 28, 2014 at 4:57 pm #342314This reply has been marked as private.October 29, 2014 at 9:42 pm #343005Hi!
Thank you for the info.
I added this code on the functions.php file:
function add_meta_noindex(){ global $wp_query; $paged = $wp_query->get( 'paged' ); if ( ! $paged || $paged < 2 ) { return; } else { echo '<meta name="robots" content="noindex,follow">'; } } add_action('wp_head', 'add_meta_noindex', 1);
It’s not being recognized as an archive page when you set the blog to advance layout builder. I’ll ask Kriesi to take a look.
Cheers!
IsmaelOctober 29, 2014 at 10:39 pm #343043Hey Ismael – I really appreciate the temporary fix you put in place. Looks like it’s working for now so I’m happy. You guys rock.
Yea I’d definitely encourage you to ask Kriesi about it as from an SEO perspective this is an important setting. When doing branded searches we were seeing a lot of these subpages of archives being index often time out ranking the actual blog page. So definitely worth addressing!
I got called out by my business parter “that’s the first time I’ve ever seen an indexing issue on a site you’ve built” haha snuck by me.
Thanks again.
November 4, 2014 at 11:26 pm #346215Hi!
The problem in this case is that due to the flexibility of the builder you are actually using a default “page” as a blog. However wordpress and other seo plugins usually dont want to prevent indexing of those pages, because most of the time they are actually not overview pages like in this case but pages with unique content that is distributed among several subpages.
I will see if there is a smart solution that I can apply but right now I am afraid you will indeed need to use the approach that Isamel suggested
Best regards,
Kriesi -
AuthorPosts
- The topic ‘Noindex subpages of archives when using avia builder 'blog'’ is closed to new replies.