Forum Replies Created
-
AuthorPosts
-
theburgernerdMember
Hi guys,
I have tested the theme on Google’s Webmaster site https://www.google.com/webmasters/tools/richsnippets and it is filled full of errors. I mentioned in a previous post about H1 H2 headings that 2014 is bad example of what Google (the world’s largest search engine) expects for structure. If you run http://twentyfourteendemo.wordpress.com/ through the testing you will see what I mean.
Unfortunately Google is the king of search engines by a landslide. Therefore, what is good for Google is good for us. So if Google “suggests” a theme to have certain elements within it, then we can assume it has at the very least some small influence on page ranking for websites…which of course means it affects the amount of traffic we receive.
Aside from using 2014 as a guideline of the theme’s structure, is there a particular reason Themehorse has for not wanting to fix these errors? Does not fixing them have any benefit that outweighs fixing them to comply with what Google expects websites to have?
I hope you reconsider your decision.
Thanks,
Trevor
theburgernerdMemberHi Themehorse,
Thanks for the info regarding the _MACOSX file. I tried you suggestion of removing the file upon installation and it seemed to clear up the error.
Thank you for your help with this.
Trevor
theburgernerdMemberHi Guys,
Thanks for getting back to me. I tried your suggestion, downloaded a fresh copy of 1.7. Erased all traces of it, then reinstalled the theme. Same error occurs. I have all the same plugins for charmsandbracelet.com as I do on theBurgerNerd.com However, the burger nerd does not show this error because I’m running it with version 1.5. I have now installed a clean version of 1.5 on charms and bracelet and the error is no longer there.
Also, I have caching, parsing, and minifying plugins for my websites. Would this cause a false positive reading? Except for the broken theme warning, the website seems to be working fine with version 1.7. I haven’t noticed a loss of function. However, my big concern is that search bots would read this error (whether false or real) as a broken website, or broken pages and posts and then rank my website lower.
I also noticed in the themes section of my files it installs a separate _MACOSX file. I don’t know much about MACOSX, but in terms of this theme what exactly does it do? Apple/Windows compatibility? Should that file be located within the actual Clean Retina theme file and not as a separate file itself? I’m not sure, like I said I don’t know much about MACOSX files but I just find it strange that I get no errors using 1.5 but get the broken theme error when using 1.7.
Thanks again for your time and for looking into this matter.
Regards,
Trevor
theburgernerdMemberThanks, I look forward to the update.
theburgernerdMemberHi,
Wondering if someone there would mind responding to this. It’s been a few days already.
Thanks,
Trevor
theburgernerdMemberHI Themehorse,
I made a mistake. I just realized now that this was posted in Interface Pro but I thought this post was part of Clean Retina Pro support area. Any chance of getting Clean Retina Pro updated soon to fix the same problem Interface was having? I found my pages show up as Missing: Author, Missing: Updated for pages on Clean Retina Pro. I’ll also repost this topic in the correct forum. My apologies for the mix up.
Trevor “The Burger Nerd”.
theburgernerdMemberHi, I wanted to follow up about this and see when the updated theme will be ready for download?
Thanks,
Trevor
theburgernerdMemberI don’t have webmaster structure errors with my posts, just all my pages which show up as Missing: Author, Missing: Updated. I’d also be interested in a theme update to fix this problem instead of having to create a child theme for something that should be a normal part of any theme.
Thanks,
Trevor
theburgernerdMemberThanks Themehorse Gang, much appreciated. Cheers!
theburgernerdMemberGreat! Thank you for your response and for including this in your update plans.
Regards,
Trevor
theburgernerdMemberNoticed you have the update ready and wanted to say thanks for fixing the issue sooner than you initially planned.
Regards,
Trevor
theburgernerdMemberThanks for getting back to me.
I don’t mean this in a rude way, but a few weeks ago I was told the update would be out in a couple weeks and I’m a bit disappointed it has not happened yet. That’s why I was hoping for a more concise answer than “very soon” when I asked about a specific date. When you say “very soon” are we talking about next week, or 2 weeks, or more?
I’m sorry to keep nagging about this issue but not only am I losing traffic but I also have around 10 new posts that I’m holding off publishing until the update is done.
Regards,
Trevor
theburgernerdMemberThanks for getting back to me Sovit. I look forward for the update.
Regards,
Trevor
theburgernerdMemberGreat! Hopefully you can come up with a temporary solution to switch the h1 & h2 to get by with until the update is ready.
Thanks,
Trevor
April 23, 2014 at 2:53 pm in reply to: When I inspect my webpage I get – "Uncaught SyntaxError: Unexpected token < " #9671theburgernerdMemberHi Sunil,
I guess I didn’t communicate myself properly. What I was saying in my last comment is that it wasn’t a theme issue but a plugin issue and that I removed the plugin and all my code is error free. I wanted to make the above comment not to ask for further help, but did so in case anyone else was having a similar problem so that they could easily fix it by removing the plugin.
Thanks,
Trevor
-
AuthorPosts