W3C and Doctype


my website needs W3C compliant code. When i check the webflow site (http://architekt-conen.webflow.io/) with firefox web developer, the html validator shows a lot of errors.

Before exporting webflow code i need to add a different doctype in the first line of the html code:
!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN

In the head tag i need:
meta http-equiv=“Content-Type” content="text/html; charset=iso-8859-1

How can i do that?

I have also hosted the site on my server:
The W3C validator (http://validator.w3.org/) shows 53 errors!

Here is my public share link:

Hi @Bettina_Lucas, thanks a lot for the post, sorry for the delay. Regarding the changing of the doctype, At the moment, it is not yet possible to do this in Webflow, so this is something that would have to be done after export.

On the errors/warnings on the W3C checker, I did a check on the Webflow site: architekt-conen.webflow.io
The W3C checker at https://validator.w3.org/nu/?doc=http%3A%2F%2Farchitekt-conen.webflow.io%2F reported 3 errors and 15 warnings.

Duplicate ID:

Although it should not happen, somehow there was two elements on the site with the same ID. I would suggest to change one of those IDs referenced in the html by line number. You can view the page source and search for "id=“kontakt” to find the instances and then change it in the designer (or on the exported page) and republish.

Error: Attribute wait not allowed on element input at this point:

This looks to be due to the Wait being used for backward compatibility with older browsers.

Element style not allowed as child of element body in this context:

This looks to be caused because there is some custom style used in the Footer of the site:


body {
	-webkit-hyphens: auto;
	-moz-hyphens: auto;
	-ms-hyphens: auto;
	hyphens: auto;


My suggestion would be to put that in the Head of the site, instead of the Footer.

As you indicated, there seems to be more validation issues on the exported site, with the ones that are different from the Webflow site, mainly being syntax related issues. I would check the edits that were made to the html after export on those.

I hope this helps!

Hi Dave,

i must know which doctype I can insert in the already exported code, so that the W3C check ( http://validator.w3.org ) indicates no more mistakes. Maybe the doctype is the reason for the error messages. The “iso 8859 1” is important to me with the Encoding.

PS: Sorry for my english :slight_smile: I´m from Germany.

Thanks a lot! I have solved the errors: smile:

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.