Thanasis Chrysovergis
Build··5 min read

I built a Google Reviews plugin for WooCommerce. Here's how it ranks.

A custom WooCommerce plugin that collects Google Customer Reviews, adds product GTINs, and ranks on Google for its own keyword. Code, results, and process.

Thanasis Chrysovergis

Thanasis Chrysovergis

AI Systems + Conversion-Focused Web

On this page

In late 2024 a WooCommerce client needed Google Customer Reviews on their store. The existing free plugins were either abandoned, broken, or missing product-level review support. I wrote one from scratch.

A few months later the post documenting the plugin started ranking on Google for "customer reviews for woocommerce plugin", a keyword with real commercial intent. This is the story.

The problem

Google Customer Reviews is a free service from Google that shows a seller rating badge on your store and collects post-purchase reviews. For it to work you need to:

  1. Add an opt-in snippet to your order confirmation page
  2. Pass the order details back to Google
  3. For product-level reviews, include GTINs (barcodes) so Google knows which product is being reviewed

Most WordPress plugins for this are half-built. They handle the opt-in and stop. No GTIN support means no product review data flowing back, which is where most of the SEO value lives.

The build

Plain PHP, no bloat. A few hundred lines total.

Key features

  • Automatic opt-in injection on the thank-you page after a WooCommerce order
  • GTIN field added to WooCommerce products via _gtin custom field
  • Email reminder logic that respects the 5-day delay Google requires
  • Badge placement control (bottom-right, bottom-left, inline shortcode)
  • Admin log view for debugging which emails went out

The tricky part

Google's docs for this are from 2019 and incomplete. The GTIN field integration required reading the raw HTML Google expects in the opt-in JSON payload. Once I had that right, the rest was CRUD.

Total build time: about six hours spread across two afternoons. Most of that was testing the email reminder logic to make sure it did not fire twice.

Why I wrote the blog post

Two reasons.

First, I wanted to document the code in case I hit the same problem later. Good engineering hygiene.

Second, I was curious whether a technical post on a niche plugin would rank. The keyword "customer reviews for woocommerce plugin" has low volume (about 40 searches per month) but high commercial intent. If someone is searching that, they are shopping for a solution.

I did not do anything fancy. Wrote the post in one sitting. Used the keyword in the title, H1, first paragraph, and a few times in the body. Linked to it from the homepage.

The ranking

Six months after publishing, the post sits at #36 for "customer reviews for woocommerce plugin" and #51 for "customer reviews for woocommerce" in Google US. Not front page yet. But climbing from #78 to #36 in three months without any link building suggests the post can make it to the top 10 with some work.

That is fine for a side-project blog post. It is also a useful proof of concept for something I tell clients all the time:

You do not need 10,000 words and 50 backlinks to rank. You need to be the best answer for a specific question. For narrow technical keywords, that bar is lower than people think.

What I would do next

A few things to push this post into the top 10:

  1. Add a comparison section. Me vs the top 3 existing plugins, feature-by-feature. Google loves comparison content for commercial keywords.
  2. Add code snippets. Actual working PHP snippets with copy-paste buttons. Increases dwell time dramatically.
  3. Video walkthrough. A 3-minute install-and-configure screencast embedded at the top.
  4. Internal linking. Link to this post from 2-3 other WordPress posts I will write.

I have not done these yet because the post is working fine at its current level. But when the broader /blog/ content on this site launches and I need a ranking anchor, this post gets the upgrade.

The plugin itself

Not public yet. It runs on the client's store and a couple of other builds I have done. If you are a developer doing WooCommerce work and want the source, ping me on a call and we can figure out a license.

The broader lesson is not about the plugin. It is about writing technical posts that rank. Small businesses and solo builders often overlook this. You do not need SEO as a full-time strategy. You need to write down what you did when you solved something, with clear titles and an eye toward the keyword someone would use to find you.

Most of the time that is enough.

If you are building or maintaining a WooCommerce or Shopify store, a few other posts from this series worth your time:

If you are stuck on a similar problem (custom plugin, data pipeline, review system) and wondering whether to build it or buy it, book a 25-minute call and I will give you a straight answer.

wordpresswoocommerceseoplugin

Found this useful? Share it.

Share·LinkedInX·
Thanasis Chrysovergis

Written by

Thanasis Chrysovergis

I build custom AI systems and conversion-focused web for teams tired of demos. 15 years of shipping. Based in Athens, working worldwide.