Today’s
article focuses on fixing W3C validation errors in Blogger XHTML template.
Bloglution has always shared quality post to make readers get most out of it in
easiest ways possible. In this post we would learn to minimize those W3C
validation errors, although it is nearly impossible to remove all of them but
we can fix about 95% of them in no time. When I checked Bloglution for the
first time I was shocked to see the results, it has 313 errors, I worked on it
and reduced it to only 11 errors. Almost all Blogger templates contain hundreds
of errors. These errors can cause crawl errors by search engine bots, resulting
improper crawling. Also it leads to slower page loading. Most of us are unaware
of these errors, and when we notice we got surprised by seeing hundreds of
them. Firstly let’s take a quick look on W3C before proceeding to our tutorial.
W3C-
It stands for ‘World Wide Web Consortium, the main international standards
organization for the world wide web. Their ultimate aim is the improvement of
online available documents for assuring quality to internet users. Secondly,
complying with them reduces browsers incompatibility issues. The Markup
validation service by W3C is a validator, which allows internet users to check
HTML and XHTML documents for well formed markup. Its impact on SEO is still not clear but
reducing them to minimum is always a good practice which definitely benefits
you. So, let’s start the tutorial.
Fixing
W3C Validation Errors in Blogger
The
first step towards fixing your W3C errors is to analyze them. Just go to W3Cvalidator, enter your blog’s URL and hit enter. You will be presented with your
validation report with your errors and warnings count. Now you know, how many
errors are there in your template. Don’t worry, follow the tutorial and you
will see the difference.
(1) Fixing DOCTYPE DECLARATION- This
is main root cause for most of the W3C errors, about 90% of your errors can be
fixed by declaring it correctly. Let’s see how.
(a) Go to your Blog’s dashboard.
(b) Click on ‘Template’ and then ‘Edit
HTML’.
(c) Find the below code using ctrl+f.
This code is present between <!DOCTYPE html> and <head> section.
<html b:version='2' class='v2' expr:dir='data:blog.languageDirection' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'>
(d) Replace the above code with the
below code.
<html b:version='2' class='v2' expr:dir='data:blog.languageDirection' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data'> <html xmlns:expr='http://www.google.com/2005/gml/expr'/>
(e) Remember to delete the Read more link.
(f) Save your template.
(2) Fixing Quickedits- Quickedits are
another major culprit which hurdles W3C validations. Actually Blogger provides
us this quickedits as a facility for editing our blog directly from the front
view. You have also noticed that when you are signed in, these quickedit icons
are present on the right bottom of every widget. Removing them from our
template can reduce up to 30 % validation errors. For removing them:-
(a) Go to your blog’s dashboard.
(b) Click on ‘Template’ and then
‘Edit HTML’.
(c) Find the below two codes and
delete all of them.
and<b:include data='post' name='postQuickEdit'/>
<b:include name='quickedit'/>
(d) Save your template.
NOTE- This code occurs multiple times in your
blog depending upon the number of your widgets, remember to remove this code
each time to add a widget in your blog.
(3) Fixing
Blogger images- Fixing Blogger images refers to the addition of ALT and TITLE
tags. As I have already discussed them in detail in my previous article, adding
ALT tag in your images can benefit you in many ways such as better SEO which
help in driving more visitors to your blog. Not only that, images without ALT
tag generates XHTML errors and warnings. Just go through the below articles to
understand this topic clearly.
The above mentioned methods will minimize your
validations errors up to 95%. After applying the above mentioned steps, once
again go to W3C validator and check errors on your blog, definitely you will be
surprised by the results as few negligible errors are left. These are
unavoidable errors which cannot be fixed by us. They can only be fixed by the
Blogger team.
Do let us know how many of you have minimized them
and by how much?
Subscribe Updates, Its FREE!
Article by Sandeep Gupta
Sandeep has written 55+ articles. If you like this post, you can follow Bloglution on Twitter. Subscribe to Bloglution feed via RSS or EMAIL to receive instant updates.
This post is really important for every blogger. No thanks for this information. Because thanks is SPAM.
ReplyDeleteThanks, keep visiting and follow us on social networks for latest updates.
DeleteWelcome to BioNick is the best way to stay on top of technology news, latest product reviews, opinions, analysis and more from India's biggest tech news site. This news service in English is updated once a day more info- https://www.bionick.in/search/label/Tech%20News?&max-results=5
DeleteYou have 11 errors:
ReplyDeletehttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.bloglution.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%2Fvalidator.w3.org%2Fservices
Nice Post by blogger. Its a really important discussion by blogger.You all always remind fix error may be indicate to W3 validation Error. More info visit on http://www.markupzone.com/
ReplyDeleteWow! Fixing Doc Type declaration decreases my blog errors from 78 errors to 8 errors, with 8 warnings to 5 warnings! I can't help myself to comment and thank you for this guide.
ReplyDeleteСпасибо ! Валидация DocType на моем блоге www.sirreindeer.ru уменьшило число ошибок со 167 до 8.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteFrom >>> 238 errors, 168 warnings.>>> To >>> 197 Errors, 79 warnings
ReplyDeleteHere is my blog - Twinbre.blogspot.com
I think I love you! Thank you so much! I went from almost 800 errors to 54 with the first code change. Now working on tags. I couldn't find the "quick edits" in my code though.
ReplyDeleteThis comment has been removed by the author.
DeleteWow! Thank you so much!
ReplyDeleteI was just in shock about all these errors!
But the first code switch seems to have cleared them up.
Thank you!!!
In "Fixing DOCTYPE DECLARATION" i have changed code so please help me out..
ReplyDeletehere is image link
https://imagizer.imageshack.us/v2/722x266q50/43/7ye0.png
www.urdupdfbooks.com
thanks for w3c my site erors are fixed
ReplyDeletemy site is boraonlinehayat.com site langue Turkish
great article...thnx bro
ReplyDeletehttp://learnurdublogging.blogspot.com/
Nice and unique post you have shared with us, Thanks for sharing.
ReplyDeleteFixed Build development
Well, it went from 160 to 8 by replacing the doctype. The poblem is... The 8th entry says: Fatal error. So it doesn't count any error after that. Let's keep trying.
ReplyDeleteThank you
ReplyDeleteAmazing blog post, thanks a lot friend
ReplyDeleteBerbagi damai
ReplyDeletethanks for your info
Visit ya >>> jalan utama
terimakasih ya
"I like this post,And I guess that they having fun to read this post,they shall take a good site to make a information,thanks for sharing it to me.
ReplyDeleteRead more here:
kim kardashian sex tape
porn sex video hd
mia khalifa sex video
sunny leone sexy movie"
This post is so facilitating.
ReplyDeleteThanks
ReplyDelete
ReplyDeleteUnesseccary emails irritate a lot. Many go to spam and many bounces back too. So to avoid all this we need email verification tools and software. Thank you for sharing this. You can also go through this , TheChecker.co is great for email verification and email list cleaning services.
As a lay man with XML and Html I was really in trouble to resolve issues for my site www.downloadapkpure.com in which there were 52 errors before implementing these codes. After reading the article I remove almost all the errors for my site. Thanks for this help
ReplyDeleteThanks For Sharing this......
ReplyDeleteVery nice article, I added above code and i resolved maximum errors.
ReplyDeleteplease help me about below errors.
1. Attribute xmlns:b not allowed here.
2. Attribute xmlns:data not allowed here.
3. Attribute xmlns:expr not allowed here.
Please help me asap.
Thanks,
Quickly this site might undoubtedly become well-known among most blogging and site-building people, for that painstaking posts as well as critiques. Web Template
ReplyDeleteI am sorry but this is not fixing the issue. Even your site is having so many error. Only change we get is that it stops processing after the Fatal Error and so number of errors are shown less.
ReplyDeleteThanks bro..... Previously my error in w3c was 86, after I fixed it now it was 10.
ReplyDeleteI was surprised because I've been looking for a way to fix it and haven't found it.I appreciate your knowledge
Voila.....
Don't forget to visit my site