-
AuthorPosts
-
May 2, 2016 at 10:02 am #625583
Hi,
I want to create a new business theme and I have already bought Enfold. Now I talked to a website developer and he said, that the SEOWPTheme (www.seowptheme.com) is much faster and the websites are better rated at google.
I don’t want to use all the specific “Enfold Features” for which the enfold shortcodes are included.
It is very important for me, to have the possibility to change everytime to another theme without complete rebuild of my website.So please can you tell me something about SEO and loading time. I know your installation package is very big, so if I don’t need your indeed very cool and nice features, would you recommend, that I use a small theme like twenty-sixteen or SEOWP?
Please tell me a few facts so I have arguments discussing with the webdeveloper.Thank you!
May 3, 2016 at 3:48 pm #626556Hey sunshineh,
As you might already know SEO ranking depends on more than 200 factors. Just for argument sake not all themes that use the seotheme mentioned above are ranked higher there may be few themes which rank well so is the case with Enfold a lot of sites that use Enfold also rank very well.
Usually if you use a SEO plugin like Yoast you will have most of the seo features which are required to rank higher.
Enfold uses it’s own advanced layout builder which is tightly integrated into the theme if you like to switch themes we recommend using an alternate layout builder with enfold so when you switch the theme other themes can work with.
Enfold is a very mature theme and we have put in a lot of effort to make it one of the best themes out there with great support team. one should really use it to know how easy it is to setup and build your site we hope you will like it :)
Best regards,
VinnieNovember 11, 2017 at 3:50 am #875422unfortunately 18 months later and enfold is still not w3c compliant – in fact Template SEO Checker states
” Your template looks like trash speaking in SEO terms.
I hope you did not pay for this theme. Because it’s not SEO friendly and a lot of things can be done better.”Now that is pretty gutting as i am now on my 6th enfold site build and i have been racking my brains on how to get better search engine rankings,
so it looks like the enfold team are not in much of a rush to fix these bugs and i am looking for an alternative theme that i can carry all my hard work over to. Any suggestions would be great btwthanks :(
November 12, 2017 at 9:30 pm #875824Hi,
There are web sites, that are ranking to Number 1 position and they are using Enfold.
SEO is not magic and it can not rank a web site just with a Theme.
There are a lot of factors that will make a site rank and template is not the number 1.
As we can use so many elements, what you will use be a part of how the template will be ranking.Best regards,
BasilisNovember 13, 2017 at 3:23 am #875910Hey!
” Your template looks like trash speaking in SEO terms.
I hope you did not pay for this theme. Because it’s not SEO friendly and a lot of things can be done better.”Please read the plugin author’s FAQ section. Let us know if you think he’s credible and someone you’d like to put your faith on. This is an example from his FAQ section.
This plugin, tries to help you to optimize your SEO On page by telling you which things you could change in order to improve your ranking at SERP. Because you should never forget that if your website ranks better than other, more visits you will have and more money will you earn. (because all this is about the money, isn’t it?)
If you really like your current theme, you can try to fix the errors manually. And if you don’t have the knowledge to fix the errors manually you can try to hir e me.
The plugin author didn’t even bother to update the plugin. What do you think? I don’t know who recommended that plugin but there are far better SEO plugins available in the library that monitors the pages’ SEO status and actually helps with rankings. Check the following plugins.
// https://wordpress.org/plugins/wordpress-seo/
// https://wordpress.org/plugins/all-in-one-seo-pack/Best regards,
IsmaelNovember 14, 2017 at 1:30 am #876405You dont honestly think i am relying on the word of one person who hasnt updated their plugin (although i am sure it would only get updated if it needed to be)
I am already using yoast and smush it and hummingbird and w3cache and loads of other things which are giving me a rating in the 90s with GT Metric but googles own pages are still giving me problems.
I have run through the official W3C Validator and these are the errors that it found :
Warning: The banner role is unnecessary for element header.
From line 65, column 1; to line 66, column 402
rap_all’>↩<header↩id=’header’ class=’all_colors header_color light_bg_color av_header_top av_logo_left av_main_nav_he…eader_border_disabled’ role=”banner” itemscope=”itemscope” itemtype=”https://schema.org/WPHeader” ><div↩i
Warning: The navigation role is unnecessary for element nav.
From line 78, column 167; to line 79, column 144
/a></span><nav↩class=’main_menu’ data-selectname=’Select a page’ role=”navigation” itemscope=”itemscope” itemtype=”https://schema.org/SiteNavigationElement” ><div↩c
Warning: Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)
At line 330, column 47
t; value="" id=&quo
Warning: The main role is unnecessary for element main.
From line 351, column 20; to line 352, column 101
ntainer’ ><main↩role=”main” itemprop=”mainContentOfPage” class=’template-page content av-content-full alpha units’><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 358, column 1; to line 359, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Error: No p element in scope but a p end tag seen.
From line 386, column 128; to line 386, column 131
div></div></p><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 404, column 1; to line 405, column 97
iv></div>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 413, column 1; to line 414, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 419, column 1; to line 420, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 429, column 1; to line 430, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 435, column 1; to line 436, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 445, column 1; to line 446, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 451, column 1; to line 452, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 463, column 1; to line 464, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 468, column 1; to line 469, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 478, column 1; to line 479, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 482, column 1; to line 483, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 495, column 1; to line 496, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 500, column 1; to line 501, column 97
/section>↩<section↩class=”av_textblock_section ” itemscope=”itemscope” itemtype=”https://schema.org/CreativeWork” ><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 545, column 54; to line 546, column 49
</section><section↩id=”text-13″ class=”widget clearfix widget_text”><div↩c
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
From line 569, column 85; to line 570, column 47
_fourth ‘><section↩id=”newsbox-5″ class=”widget clearfix newsbox”><ul↩clPlease forgive me if i am wrong, i am still learning, but From what i can see these are source code issues that have been there a long time but now google is penalising sites for not being up to scratch.
Please tell me how i go about fixing this issues.
surely if i change anything in the source it will get overwritten in the next update – wouldn’t it be better if these things were addressed for everyones benefit?- This reply was modified 7 years ago by PhatJ.
November 14, 2017 at 1:37 am #876407in response to your reply Basilis “There are web sites, that are ranking to Number 1 position and they are using Enfold.”
If anyone is using enfold and has reached a number 1 position please list your site so i can take a look.
November 16, 2017 at 3:47 am #877325Hi,
Those notifications are not critical, only warnings, which you can ignore. If you want to satisfy the validator, you can do the following.
Warning: Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections.
You can add a Special Heading element or a text or code block with the heading tags in every color sections.
Warning: Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)
You can’t remove this warning because the theme requires the character code inside the av_icon data attribute to render the icon elements properly. Again, this is not a critical error.
For the other notifications, please review this thread.
// https://github.com/validator/validator/issues/270#issuecomment-225524928
Best regards,
Ismael -
AuthorPosts
- You must be logged in to reply to this topic.