Talk to Franz

Article

About Targeted List Landing Page Hashes

A list landing page hash is a sort independent, comparable identifier of the visible items on a list landing page. Two pages with the same hash show the same list: internal duplicate content.

seo-franz-fullstackoptimization-enzenhofer

Key takeaways

  • Calculate the hashes once per day, for the first page of every list only.
  • Collisions in 1% of the cases: ignore. Above 5%: high priority. Above 20%: critical, high risk of self spam.
  • Fix the listing logic first. If a collision cannot be solved, choose a winner and make the loser disappear.
  • This is for huge sites with generated list pages, not for small and medium sized sites.

My book Understanding SEO only touched upon list landing page hashes. Here is the whole concept.

A targeted list landing page answers “query deserves list”

Somebody searching for “cheap apartments manhattan” does not have one specific flat in mind, but wants to see a list: “query deserves list.” A targeted list landing page is a list page that wants to get found for that specific search intent.

Other queries with list intent:

  • “PHP jobs Seattle”
  • “vegan restaurants little rock Arkansas”
  • “tennis courts Brighton”
  • “online yoga classes”

The challenge: millions of combinations, the same items

Your web property does not only want to get found for “cheap apartments manhattan” but also for “apartments manhattan,” “ground floor apartments manhattan,” “one-bedroom apartments manhattan,” “cheap apartments new york” and a few 100k or millions of additional combinations.

If all cheap apartments in Manhattan in your database are on the ground floor, or all are one-bedroom apartments, these list pages return the same items. Same main content: internal duplicate content.

List pages that visibly show the same lists, regardless of sorting, compete with each other:

  • Google does not know where to send the traffic.
  • Google lets the pages compete to determine the winner, which is not the page that you might have chosen.
  • Google might even de-index some of them.

When it happens sometimes: annoying, no big deal. On scale, with logic that creates more and more list landing pages over time: growing underperformance in Google.

The hash: sort the visible items, concatenate them

Take the identities of the listed items, sort them (ascending or descending, doesn’t matter) and concatenate them.

PageTargeted atListsHash
P1“cheap apartments manhattan”A, B, C, Da-b-c-d
P2“apartments manhattan”A, B, C, D, Ea-b-c-d-e
P3“one bedroom apartments manhattan”A, B, D, Ca-b-c-d

P1 and P3 are equal. P2 is different, and we can even say that P2 is 20% different from P1 and P3.

Hash only the first page and the items visible there. Paginated pages (page 2, page 3, …) are never targeted landing pages.

Strategy 1: quality assurance with a daily collision report

Calculate the hashes once per day, most of the time in the same process that creates the sitemap.xml. Then check if there are collisions.

CollisionsWhat to do
1% of the casesIgnore them.
Between 1% and 20%Your wiggle room. I personally see everything above 5% as a high priority area of optimization.
20% of the casesAct now. Anything above is critical, with a high risk of self spam.

Then act based on the daily hash collision report. One case: “men’s shoes” constantly collided with its subcategory “men’s sports shoes,” as all of the listed men’s shoes were sport shoes. Two fixes:

  • We made sure we always had one “men’s shoe” offer that was not a sports shoe.
  • We changed the listing logic: all categories must list at least 1 item of their subcategories.

Over many iterations we eliminated nearly all recurring hash collisions in all categories and sub-categories.

Strategy 2: choose a winner

The more hardcore strategy. If collisions like P1 and P3 happen systematically (above 5% to 20% of all cases) and you can not solve them in another way, choose winners and losers systematically.

  • Winners are communicated to Google, listed in the sitemap.xml, and linked internally.
  • Losers do not exist, either get deleted or are set to noindex, not listed in the sitemap.xml, and are not internally linked.

Both pages are equal in content, so the winner needs another metric: shorter URL, more search demand, bigger city, higher margins. There is no perfect logic but “a winner choose you must”.

Only for huge sites with generated list pages

List landing page hashes are for huge websites with a vast and growing inventory of stuff and of pages: yellow pages, real estate aggregators, huge online shops, job marketplaces, aggregators.

How the list landing pages are createdHashes?
EditoriallyDo not bother.
Search based, metadata multiplication (a.k.a. filter pages), expanding category and sub-category logicsDefinitely, at least as quality control: to know how big an issue internal duplicate lists actually are.

Easy to implement when you keep it in mind from the start, hard on top of a historically grown list landing page logic.

All articles