AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
4.8K members online now
4.8K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Doctype requirement in Customer Reviews

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

I'm trying to troubleshoot why the Customer Ratings pop-over isn't showing up when an order is placed.  I'm investigating to see if the Customer Ratings code is being run after onload, but there's another issue that I've discovered could be causing a problem, too.

 

There is an HTML5 doctype requirement, but unfortunately there's not much helpful documentation on it.

 

The Help Center document says that it's to make sure that your website does "render your pages in standard mode instead of quirks mode":  https://support.google.com/merchants/answer/7106244

 

But I'm not sure that I've ever seen a free plugin on the Internet that has an HTML5 doctype requirement.  For a large e-commerce website, this could require a significant amount of quality-assurance effort to ensure that "upgrading" to the HTML5 doctype doesn't cause regression issues elsewhere on the site.

 

For a fully-responsive e-commerce website built on a commercial-grade platform (Magento) with design/dev best-practices, it doesn't seem like a non-HTML5 doctype should be an issue at all.

 

  • Does anybody know if this requirement is intended solely for older IE browsers?
  • Or, does Customer Ratings work without the HTML5 doctype?
  • Or, does Google simply flat-out disable Customer Ratings for any website where the HTML5 doctype isn't found?

 

Screen Shot 2018-02-08 at 3.39.43 PM.png

 

I'll probably have to reach out to AdWords support, but they don't always have very helpful answers when it comes to advanced questions like this!

 

thanks!

--Chris Baker

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
February

Doctype requirement in Customer Reviews

[ Edited ]
Top Contributor
# 2
Top Contributor

having the doctype is the specific requirement --
generally, google-customer-reviews requires that
the page is compliant with the html5 standard as
defined by w3c/ietf and related specifications and

is the underlying stipulation of the opt-in module.

before any integration, the best likely course is to be certain the page has

no errors or warnings when submitted to the w3c html5-validation service,

and the page renders properly for both mobile and desktops, as seen on

pagespeed-insights, and looks reasonable on both actual desktops and

actual desktop devices -- in addition to the html5 doctype, on the first line.

anything short is likely not guaranteed to render any
integration detail related to google-customer-reviews
and results are likely undefined, or by chance correct.

the more critical policy is likely that the opt-in survey
must be displayed to all customers after checkout --
display being the critical, relevant, requirement.

 

if the opt-in-survey displays, that should

meet the other fundamental requirement.

for any follow-up questions, including what is officially supported,
or what may trigger a suspension for non-compliance, there is also
a separate google-customer-reviews support contact-form:
https://support.google.com/merchants/contact/gcr_merchant_contact

see also
https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.celebird.com%2Fresources%2Fpla%2Fitem-templates%2F...
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.celebird.com%2Fresource...

View solution in original post

Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
February

Doctype requirement in Customer Reviews

[ Edited ]
Top Contributor
# 2
Top Contributor

having the doctype is the specific requirement --
generally, google-customer-reviews requires that
the page is compliant with the html5 standard as
defined by w3c/ietf and related specifications and

is the underlying stipulation of the opt-in module.

before any integration, the best likely course is to be certain the page has

no errors or warnings when submitted to the w3c html5-validation service,

and the page renders properly for both mobile and desktops, as seen on

pagespeed-insights, and looks reasonable on both actual desktops and

actual desktop devices -- in addition to the html5 doctype, on the first line.

anything short is likely not guaranteed to render any
integration detail related to google-customer-reviews
and results are likely undefined, or by chance correct.

the more critical policy is likely that the opt-in survey
must be displayed to all customers after checkout --
display being the critical, relevant, requirement.

 

if the opt-in-survey displays, that should

meet the other fundamental requirement.

for any follow-up questions, including what is officially supported,
or what may trigger a suspension for non-compliance, there is also
a separate google-customer-reviews support contact-form:
https://support.google.com/merchants/contact/gcr_merchant_contact

see also
https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.celebird.com%2Fresources%2Fpla%2Fitem-templates%2F...
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.celebird.com%2Fresource...