Step 2: Result Card Content and Behavior

While the overall formatting and styling review takes a more holistic approach to the experience UI and page, here you’ll take a closer look at the results cards for each vertical, both in universal and vertical search. Check to make sure the result cards are behaving as expected and displaying clean entity content.

Here are several items to check for in terms of result card content and behavior:

Title and CTA Links Redirect Correctly

For each vertical, test out the link behavior for titles and buttons on result cards to ensure they are clickable and redirect as expected. For example, if a CTA on a product card unexpectedly redirects to a location page, that would be something to flag to the Admin. We recommend clicking into the title and at least one CTA link in each vertical. To quickly check subsequent CTA links, hover over the link and check out the link URL displayed in the bottom left corner of your browser.

Proofread Entity Content for Grammar/Spelling

While the data itself often comes directly from the client and isn’t expected to be edited by the Admin, it is worth checking for clear spelling/grammar issues that would distract from the user experience so the Admin can flag to the client or edit directly as they see fit. You don’t need to read through all the text in the experience, but be sure to notice in the course of your QA whether there are glaring errors.

Formatting of Unstructured Content

Entity Types that are not structured, such as FAQs or Blog Posts, can sometimes have undesired formatting on the frontend such as raw HTML unknowingly pulled in through a crawler or incorrectly formatting bullet points from an Excel upload. Do a cursory check for any obvious formatting issues on semi-structured and unstructured entity types. This includes any direct answers or featured snippets that may be included in the experience as well.

Overall Data Quantity and Completeness

A strong search experience requires a sufficient amount of complete, consistent data. A few examples to help in evalutating this:

1. If the client has an FAQs vertical with only two FAQs, push the client to provide more content for the vertical.
2. If the client has a products vertical and only half of the entities have images, push the client to provide images for the remaining entities if possible. If some images are blurry, push the client to provide higher quality images.
3. FAQs should usually have CTAs to increase engagement with the content, but this is often overlooked. We recommend adding CTAs to FAQs if many do not have them.

Image Size Consistency

For any vertical with images, especially those that use a grid layout, the size of the images should be consistent across each card for a clean look. This applies to both desktop and mobile.