Resources
Extended information on product and variant documents.
Overview
Include the URL for your product resources with the resources field. These resources appear to potential buyers. Resources are displayed to users in order equal to their position in the array. e.g. the first resource URL in the resources array will be used as the first resource.
When to use
Optional for each product and variant
Format
Follow these formatting guidelines to make sure that Axiom understands the data that you're submitting.
Type | URL (including http or https ), ASCII characters only, and RFC 3986 compliant |
---|---|
Limits | 1-2,000 characters |
Repeated field | Yes |
Variant Inherits | Yes |
Guidelines
Follow these guidelines to make sure that your resource URL is formatted so that we can understand it.
Minimum requirements
These are the requirements that you'll need to meet to show your product. If you don't follow these requirements, we could reject your product.
- Use a URL that points to a resource in a supported file format.
- Start with
http
orhttps
and comply with RFC 3986. For example:http://www.example.com/document1.pdf
. - Replace any symbols or spaces with URL encoded entities. For example, if your URL contains an ampersand (
&
), then replace it with%26
. If your URL contains a comma (,
), then replace it with%2C
. - Make sure that your URL can be crawled by Axiom. Make sure authentication is not required to view the resource.
Best practices
These best practices can help you go beyond the basic requirements to optimise your product data for performance.
- Use a stable URL. The URL that you include shouldn't change unless your resource moves or is replaced. For example, don't use URLs with timestamps or parts that could change every time you submit your product data.