I have a single page describing an organisation marked up with schema.org data, there are then multiple related pages with review data on.
At the moment these review pages have the same Organisation tag as the main page but this doesn't feel right to me, it seems like there should be one Organisation record for each company.
Does anyone have an experience or guidance on this matter or the best way of marking up review data on related pages?
-- I have thought about using the organisation url parameter on the review pages which points back to the main page but I am concerned this would eventually impact the listing of these review pages.
Updated with examples
This is an example of the main organisation page http://www.insidebuzz.co.uk/law/hogan-lovells
And this is one of the sub pages http://www.insidebuzz.co.uk/reviews/hogan-lovells/question/overall-satisfaction
[update 5/17/2013]
I've now found that the way we can link items from one to another is with itemid=". This link is to the WebSchemas/ExternalEnumerations page "Country" example. This example shows how this is done. Pay keen attention to the "itemid" usage.
NOT THE ANSWER:
Per HTML - Living Standard -- We can use the HTML5 Microdata "itemref" to accomplish your goal.
[example removed for brevity]
I've done this in MVC by placing the itemscope itemtype="... in the MVC equivalent of a Master Page and in the View's (child pages) used itemprop and itemref etc.
NOT THE ANSWER:
http://schema.org/CollectionPage
isPartOf = Indicates the collection or gallery to which the item belongs.
Hope this helps.
Related
I just want to know about the page object model thing. In an e commerce website if we have 100’s of products and each product has its own detail page.. Then do we need to have a separate page for each product to perform some action. Lets say I have a mobile page which have 15 products and whenever I click on specific product it will land on its details page. So do we need to create 15 separate class files, one for each page or do we have any other alternative for this.
You need ask yourself this question
Is this 15 different product details page has same structure or different, I am not asking about page data (obviously it is different)?
if it's same, you just need one Product Details Page. If not you need to use inheritance to check how you can club related sub page in separate pages and create maintainable page object.
Presumably you only need one ProductDetailsPage class as the details and layout on the page will be generic ?
I am developing a simple website and want to implement microdata on it.
The website is for a local business and simply has the default structure (about, services, contact, etc..).
My question is if microdata can be cloned on every page or if I should change from page to page. Logically I would say that I should change from page to page, but on the other hand information like facebook page, twitter and map will keep the same so I don't know what should I do.
I take the chance to ask if there is any better category to list a software company, I am using local business but maybe there should be better ones that I am missing (this applies for meta description and keywords also on the different sections of the site)
You should declare only the start- or contact/aboutme site with your Local Buissiness Information.
On all other site depend on the content like article, product etc.
I am trying to understand Schema data. My website has a Products page and a Reviews page. Do you know if I can implement enable the rich snippets for Reviews on a different page than the products? Can I 'hide' the reviews on the product pages? I am just trying to figure out the best way to implement.
If I have to redesign the markup for the products page to include the reviews, then that is what I will do
Yes, the documentation does ask for the reviews to be nested inside the item being reviewed.
"Make sure the review or ratings markup refers clearly to a specific product or service as shown in the examples above. Do this by nesting the review or ratings within the markup of another schema.org type — such as schema.org/Book or schema.org/LocalBusiness — or by using that schema.org typed element as a value for the itemReviewed property.
https://developers.google.com/structured-data/rich-snippets/reviews?hl=en&rd=1
I have sort of a problem how to use Google Analytics properly with Boostrap.
My page has 3 level deep subpages and the last subpage has it's own subdomain. In GA I see I can use max. 50 tracking codes within one service. What if I need more than that?
You are limited to 50 properties not 50 pages. Each property can track many pages and (up to 10 million hits a month for the free version) and events.
Typically you would use the same property code on all pages on the same site so you can see all that data together (though with option to drill down).
You would only use a new property code for a new site (though your subdomain might qualify for that if you want to track it separately).
So the two questions you want to ask yourself are:
Do you want to be able to report on two pages together? E.g. To see that your site gets 10,000 hits and 20% are for this page and 5% are for that page. Or people start at this page and then go to that page and then on to this page. If so it should be the same analytics property.
Do different people need to see these page stats? And is it a problem if they do? If so put as a separate property so you can permission separately.
It sounds like these are part of the same site so I'd be veering towards tracking them together on same property.
On a different note you should set one page as the main version (with a rel canonical tag) and redirect other version to that page to avoid confusing search engines thinking you have duplicated content. Do you have a reason for having the same content on two different addresses? It can cause SEO and other problems.
I'm implementing the hreview portion of microformats on a site to be indexed by Google.
http://www.google.com/support/webmasters/bin/answer.py?answer=146645
The item field of a review feels clunky to me, since I can't imagine why I'd included the name of the item being reviewed inside the review itself.
For example. If you are on Yelp there is a page about a restaurant. The name of the restaurant is at the top, but it wouldn't' make sense to repeat the restaurant name also inside each review block.
So I'm wondering if the item field is one of the ones that can be invisible to the user and still indexed by google? Incidentally, I just checked and it looks like Yelp has this field with a display: none; to the user.
Can anyone verify this?
Do you have some reason to believe there are fields that can't be hidden and still indexed by Google? It seems likely to me that Google will index all hidden fields, just because I doubt it's worth checking for them. But I'm not sure about that.
Hiding fields isn't recommended for microformats. A core idea behind microformats is you should be presenting the same content to both computers and humans. If the content isn't anywhere on the page, that violates that idea. If it's somewhere else on the page, which is often the case for reviews, you can use the include pattern.