One of the primary reasons for using structured data is identifying/disambiguating entities. For conveying to machines that all these pages are about the same product, you have to place the structured data on all these pages, too. Not necessarily repeating all the data, but at least providing a URI for that product.

For pages that contain documentation for the product, the primary entity should be TechArticle, not Product. The about property points to the specific product the documentation is for. Example in Microdata:

<body itemscope itemtype="http://schema.org/WebPage">

<article itemprop="mainEntity" itemscope itemtype="http://schema.org/TechArticle">

<div itemprop="about" itemscope itemtype="http://schema.org/Product">

</div>

</article>

</body>

10% popularity Vote Up Vote Down

Feed

: If I have multiple pages of documentation about a product can/should I place schema markup for that product on every page about that product? I'm guessing the answer is yes as long as the

More posts by @Gloria169

: Is there any SEO difference between /blog and /blogs? In trying to categorize posts in a blog I'd like to use /blogs in the domain. Will this have any negative SEO impact? Or is it the same

: How to prevent page counts by search indexers On a page I manage I store information about the most read pages and last read pages in the database. How can I manage to prevent taking into

: .htaccess redirect without changing url in users' address bar My website redirects to /temp when visiting the root, I'd like it to appear as the root, without the /temp in the URL address bar.

: Virtualmin: how to set ftp user's root directory? Under virtualmin's "edit users" panel, I set a new FTP user with the home directory being website subdirectory: medias. When I login to this

Login to post a comment!

1 Comments

Back to top | Use Dark Theme