Jamjar

We aimed to extract the existing value from the historical site and strategy, conserving link equity where possible. The domain had already acquired a number of high-quality backlinks when it was owned by RBS. However, amongst their profile were broken backlinks – from the BBC, for example – and several toxic domains. We redirected their broken backlinks and conducted a thorough disavow process to allow their profile to communicate relevancy and quality.

While Jamjar.com was a new venture, traces of its previous entity with the RBS group could be found online. We discovered their previous Wikipedia entry and updated this to detail how the brand had evolved over time. This, along with incorporating the “AutomotiveBusiness” structured data into their site, allowed us to rebuild the “Jamjar” entity from a search engine perspective.

Jamjar.com’s early website was predominantly built on Laravel to accommodate their comparison functionality. However, this was largely non-indexable and left little room for other core conversion-focused landing pages. We recommended migrating the Laravel site to a subdomain, comparison.jamjar.com, while introducing WordPress to feature on the main site. This migration also involved the introduction of Amazon Web Services (AWS), allowing for a performance-focused website.

From a proactive SEO perspective, we aimed to use content to better serve the cross-funnel needs of the end-user and broaden search visibility. We created a user-focused search journey with topics to target users throughout the entirety of the conversion funnel. At the top of the funnel, the content strategy featured longer-tail keywords that were less competitive, allowing us to demonstrate our short-term value; lower down the funnel, we created content that targeted shorter-tail queries and would become part of the longer-term strategy.

With the clearly defined objective of obtaining top rankings for three keywords (“sell my car”, “scrap my car”, and “sell my van”), we knew that a silo approach would be effective. The content was organised into a sitemap that clearly dictated our content schedule, separating out each of the topics into one of the three content silos.

When creating the content, we first tackled more conversion-focused landing pages with our team of content writers working collaboratively with our designers to introduce our core service pages. Once these were launched, it was then a process of writing the supporting guides until our content strategy was complete.

With each landing page that was created, careful considerations were made in terms of page segmentation, architecture, and internal linking whilst using TF*IDF to understand how competitors had framed each topic. This led to an incremental and thorough approach that was core to the campaign’s success.