Rich Snippets

[Johnny4B]

Hi guys,

Working with a client that we did not design, build or code their website. And further more they are happy with their website, and to be fair, its all fine.

We are there to try help them improve their poor overall ranking positions website contains an e-commerce solution and as part of the project we are implementing Rich Snippets.

Anytime we have used Rich Snippets, we have always followed Google's guidelines and well structured each product page to adhere to how Google advise. (we have also designed and coded the clients website in these cases, or indeed restructured certain pages).

Problem with this website is the product layout is all over the place.

So my question for people who have used Rich Snippets, have you ever deviated from the layout as advised by Google

For example, with this clients current structure ,we would need to open the product snippet like example below, mark up what we want to use, but between the opening and closing tags, we have content that is not being used for Rich Snippets

Their Product£39Client has a section here containing information we will not use for rich snippets<.div>Anther section containing more irrelevant stuffProduct DescriptionProduct ID: SKUCode

<--- Close Schema product ---->

I have tested the above structure out with Google's tool, and well its finding all the rich content fine, I am just worried that the two divs in-between the opening and closing tag for the Product Div may cause problems.

Has anyone deviated from the exact flow as outlined by Google and still got their snippets displayed fine

Thanks in advance

John

[BlueprintMarketing]

Great question. I actually have deviated from the format many many times. When we were experimenting with Rich  benefits and found that we got the same results regardless. I know Google guidelines and I believe them to be very good. I do not believe the division will make a difference overall.

Sincerely,

Thomas

[Johnny4B]

Hi Thomas,

Thats great to know, and might make our life a lot easier in the future.

Thanks

John