0

We are still getting error on Google Search Console about AMP: AMP validating: Missing required structured data element on this amp page.

With validator (https://validator.ampproject.org) we got Validation Status: PASS

We are using meta data and google structured data testing tools shows no errors and no warings.

This is one example url: (Don´t want to spam so additional space written to avoid linking)

https:// www. alpel.es/cosmo-nails-liquido-porcelana-uv-50-ml_amp

Thank you!

BaRRuKa
  • 9
  • 3
  • 4

2 Answers2

1

I think you need to check the Structure Data policies for this:

Multiple entities on the same page

When you have multiple entity types on a page, we recommend you mark up all entities on that page to help Google algorithms better understand and index your content. For example:

A recipe page might have text describing the recipe along with an accompanying video. Each of these types should be marked separately with schema.org/Recipe and schema.org/VideoObject respectively. A category page listing several different products (or recipes, videos, or any other type). Each entity should be marked up using the relevant schema.org type, such as schema.org/Product for product category pages. Marking up just one category entity from all listed on the page is against our guidelines. A video play page might have related videos embedded in a separate section on the page. In this case, mark up the main video as well as the related videos. Image markup guidelines

When marking up an image URL as a property of a type, make sure that the image actually belongs to the instance of that type. For example, if you mark up the schema.org/image property of schema.org/NewsArticle, the marked-up image must directly belong to that news article.

You may also check the Product Guidelines.

This SO thread and this discussion might help as well.

Community
  • 1
  • 1
ReyAnthonyRenacia
  • 17,219
  • 5
  • 37
  • 56
  • I think the problem was that we were using
    to products, we've remove it so hope the problem is solved. Thank you!
    – BaRRuKa Jul 15 '16 at 12:45
  • @noogui. I got error. Could you please see this link. http://stackoverflow.com/questions/42199925/external-style-sheet-is-not-working-in-amp-pages – Varun Sharma Feb 23 '17 at 06:29
  • @varunsharma I think it's on [disallowed list](https://www.ampproject.org/docs/guides/responsive/style_pages#disallowed-styles). – ReyAnthonyRenacia Feb 23 '17 at 07:57
  • @Noogui. thanks for response. I followed these thinks. But How to access external style sheet. Because I cant include in inline.Because it is so long. (MaterializeCss). http://stackoverflow.com/questions/42199925/external-style-sheet-is-not-valid-in-amp-pages – Varun Sharma Feb 23 '17 at 08:10
  • @noogui. My question link.http://stackoverflow.com/questions/42199925/external-style-sheet-is-not-valid-in-amp-pages – Varun Sharma Feb 23 '17 at 09:23
1

You're gonna need to add a JSON-LD structure using schema.org. You can use Microdata (itemprop) if you chose, but it is not a substitute for the JSON-LD structure. The structure can go in <body> (previously was limited to <head>) and can be adjacent to the Microdata specifications.

Here is a structure you can modify to meet your needs:

<script type="application/ld+json" id="20">
{
"@context":
 {
  "@vocab": "http://schema.org/",
  "id": "@id",
  "graph": "@graph",
  "type": "@type"
 },
"graph":
 [
  {
  "type": "Product",
  "id": "http://example.com/identifier/type/Product/19000000001001",
  "name": "",
  "alternateName": "",
  "description": "",
  "releaseDate": "2016-01-02",
  "manufacturer":
   {
   "type": "Corporation",
   "id": "Company IRI"
   },
  "offers":
   {
   "type": "Offer",
   "price": "",
   "priceCurrency": "USD",
   "id": "http://example.com/identifier/type/Intangible/Offer/14180000001007"
   },
  "isSimilarTo":
   [
    {
    "type": "Product",
    "id": "http://example.com/identifier/type/Product/1001"
    },
    {
    "type": "Product",
    "id": "http://example.com/identifier/type/Product/1002"
    }
   ],
  "isRelatedTo":
   [
    {
    "type": "Product",
    "id": "http://example.com/identifier/type/Product/1003"
    },
    {
    "type": "Product",
    "id": "http://example.com/identifier/type/Product/1004"
    }
   ],
  "audience":
   [
    {
    "type": "BusinessAudience",
    "id": "http://example.com/identifier/type/Intangible/Role/14290000001001"
    },
    {
    "type": "BusinessAudience",
    "id": "http://example.com/identifier/type/Intangible/Role/14290000001003"
    }
   ],
  "category":
   [
    {
    "type": "Thing",
    "id": "http://example.com/identifier/type/Product/1010"
    },
    {
    "type": "Thing",
    "id": "http://example.com/identifier/type/Product/1012"
    }
   ]
  }
 ]
}
</script>

You'll want to replace the technique-in-use for specifying unique identifiers ("id":) with your own technique.

Each of your @Product items (with their unique @id) should be included in the @graph.

Jay Gray
  • 1,706
  • 2
  • 20
  • 36