Skip to main content
Content Audit

Learn how Kapoq's Content Audit Operates

Shelby Rothenberg avatar
Written by Shelby Rothenberg
Updated over 2 years ago

The Kapoq Content Audit identifies listing optimization opportunities that exist across all active products in an account's catalog.

For context, Kapoq's Content Audit checks ASIN Titles, Descriptions, Bullet Points, Imagery, and A+ Content found on the Product Detail Page. The Content Audit runs daily and checks product detail page content against Amazon's Style Guides and is powered by the Amazon APIs. Furthermore, the style guides referenced are category specific.

To view what is audited based on Amazon's style guides, please take a look at the templates found in Seller Central - https://sellercentral.amazon.com/help/hub/reference/G1641 .

To access the Content Audit, navigate to the Content Module then to the Content Audit. Within you'll see all active ASINs displayed, a corresponding Listing Score, and all elements audited on the Product Detail Page.

The icons beneath each column represent how well your ASIN performed against the benchmarks. Hovering over each icon will showcase how many benchmarks passed or failed the check.

To evaluate the full audit at the ASIN level, simply click the zoom icon to the left of the Product name column. Here you'll see all the missed benchmarks and the successes.

In the example above, the ASIN passed 5 of 6 benchmarks.

The one benchmark that did not pass the test was the related to the product description. As mentioned in Amazon's style guides, this products description should contain at least 25 words, yet there are only 6 words present today.

Because of this, Amazon suggests you update the content to best reflect the style guides and doing so will offer a better customer experience.

To learn how to push content changes using Kapoq's Edit Listing feature, please see the following guide - How to Edit Content within Kapoq.

That covers the Content Audit for now. If you have any questions, please do not hesitate to reach out to our team.

Did this answer your question?