Mastering Your Shopify Footer: How to Correctly Place Widgets Above Copyright

Hey store owners!

Ever found yourself scratching your head, wondering why a newly installed widget isn't sitting quite right in your Shopify store's footer? It's a surprisingly common scenario, and it's exactly what came up in a recent community discussion I was following. Our fellow merchant, Arasca, ran into a classic case of a Google Review widget appearing underneath their copyright text, and they wanted to flip that order around.

It's a small detail, but these little things can really impact your site's professional look and user experience. Let's dive into what we learned from the community and how you can tackle this yourself.

The Footer Fumble: Widget vs. Copyright

Arasca's problem was pretty straightforward: after adding a Google Review widget, it landed at the very bottom of the page, pushing the crucial "Copyright © All rights reserved" line above it. The goal was to have the review section appear just above the copyright, making the footer flow more logically.

This is a common headache, especially when you're adding third-party apps or custom code. You expect things to fall into place, but sometimes the default placement just isn't what you need.

Navigating Community Advice: What Works (and What Doesn't)

The beauty of the Shopify Community is how everyone jumps in to help. In this thread, we saw a few different approaches, and it's a great example of why understanding the root cause is so important.

Initially, some suggestions revolved around using CSS to manipulate the copyright text. For example, Devcoder and Mustafa_Ali proposed adding CSS snippets like this:


And Devcoder also suggested adding .min-footer .col-left { display: none; } to files like base.css or styles.scss.css. Now, while these codes are valid CSS, they come with a big catch: they don't move the copyright text; they hide it completely! As liquidshop.co rightly pointed out, this isn't what Arasca needed, and it's definitely not ideal for your store's legal compliance or user trust.

Hiding your copyright information is generally a bad idea. It can make your site look unprofessional, and in some regions, it might even have legal implications. So, while CSS can be powerful for styling, it's not the tool for reordering major structural elements like this.

The key insight came from liquidshop.co, who correctly identified that the issue wasn't about hiding text, but about the placement of the widget itself. They advised:

"You need to change the placement of the widget... First, locate where the Google Review widget is currently installed. Then move it above the footer or just above the copyright section. This should resolve the issue."

This is the golden nugget of advice!

The Correct Approach: Repositioning Your Widget

To truly solve this, you need to find where the Google Review widget's code (or the code snippet that calls it) is embedded in your theme files and physically move it to the desired location. Think of your theme files as a blueprint; you're just rearranging a piece of the structure.

Here's how you can generally go about it:

Step-by-Step: Moving Your Footer Widget

  1. Access Your Theme Code:

    • From your Shopify Admin, go to Online Store > Themes.
    • Find your current theme, click on the Actions button (three dots), and select Edit code.
  2. Identify the Widget's Code Location:

    • Most footer elements are managed in files within the Sections folder (like footer.liquid) or directly in theme.liquid. Some apps might inject code into snippets (Snippets folder) that are then included in the footer.
    • Pro Tip: If you're unsure where the widget's code is, use your browser's developer tools (right-click on the widget on your live site and select "Inspect"). Look for unique IDs or classes associated with the widget. Then, use the search bar in your Shopify theme editor (top left) to search for those IDs or classes across your theme files.
    • You're looking for the actual HTML or Liquid code that renders the Google Review widget. It might be an