Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).
Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).
Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).
Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).
Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).
Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).
Your Microdata is fine.
Some HTML suggestions:
I wouldn’t use
p
as container foriframe
+ the map. I’d usediv
instead.Don’t use
<br>
after theiframe
(br
is for line breaks that are part of the content only). Your usage ofbr
in the postal address is correct.Don’t use
small
for the link to the map (as it doesn’t seem to be a side comment).You could use
rel
-external
for the external links to Google and Facebook.You could link the telephone number with the
tel
URI scheme. But then you should include the anchor text in aspan
element, as schema.org’stelephone
property expects "Text", not "URL" (which would be the value for theitemprop
if used ona
).<a href="tel:555..."><span itemprop=telephone>555 555-5555</span></a>
In contrast to what tomdemuyt answered, using
p
for the postal address seems to be fine (as it’s used in an example in the HTML5 spec).