A complete audit and fix pack, before you pay for one

So the tags are there, in the theme. GA4 and the Meta Pixel are both installed. The audit can also see where. Both are in theme code, which Shopify does not load on checkout, so neither can see a sale from there. Whether they send the events your reporting and your ad spend depend on is a different question, and it takes a test order to answer. What the audit checks, and what it cannot see →

An alert, for the week a theme update went out. This is the kind of message the tags above are watched for. The snippet hash is a 12 character fingerprint of the tag's code. It is worked out from the pixel snippet in this store's own theme, so a hash that no longer appears on any page tells you the snippet was edited or removed.

Neither design says whether a purchase fired, because Guardrails reads the same served pages the free audit does and cannot know. How Guardrails works →

• PACK_NOTES.md
• README.md
• site/index.html
• site/blogs/journal/dialling-in-espresso-at-home.html
• site/collections/coffee.html
• site/pages/about.html
• site/products/ethiopia-guji.html
• site/products/house-espresso.html
• shopify/snippets/audittag-seo.liquid
• shopify/seo-fields.csv
• shopify/products.csv
• shopify/INSTALL.md

# Read this first

This pack is for ashcombecoffee.example. We read all 6 pages on 1 September 2026.

Nothing in this pack has been applied to your live site. These are files for you to review and use yourself.

## What we wrote

This pack writes 3 titles, 6 descriptions, 10 alt texts and 4 structured data blocks.

The copy comes from your own page text. We told the writing step not to add facts from outside it, and an automated check looks for some kinds of claim that your pages do not make, such as prices, numbers, delivery and returns promises, reviews and superlatives. It is a safety net and can miss wording, so read the copy before you use it.

## What still needs a person

6 things need a decision from you.

- 2 H1 headings on one page
- Article has no named author
- Heading order jumps from H1 to H3
- GA4 is only in your theme code, which does not run on checkout
- Your Meta Pixel is only in theme code, which does not run on checkout

README.md has the full list under Needs a human.

## What this pack does not do

It fixes the tags and fields on your pages, such as titles, meta descriptions, headings, image alt text, canonical links, structured data, social tags, robots.txt and sitemap.xml. It does not fix tracking, and it does not promise rankings.

The audit that came before it is a presence check. It reads the HTML your pages serve, so it shows which tags are installed, not whether a purchase actually fires.

The audit saw GA4, Meta Pixel and Universal Analytics in your pages. It did not see Google Tag Manager and Google Ads, which is fine if you do not use them.

After you deploy, place a test order and watch it arrive in GA4 DebugView and, if you run ads, in Meta Test Events and Google Tag Assistant. Only a test order shows that a purchase fires.

## Where to start

Open shopify/INSTALL.md. It takes you through the admin fields and the one theme snippet.

The full change log is README.md.

{%- comment -%}
  AuditTag head tags for ashcombecoffee.example

  Generated from an audit of your live pages. Every tag below was
  ABSENT when we crawled; nothing here duplicates or overrides a tag
  your theme already prints.

  Install: put this file at snippets/audittag-seo.liquid, then add
    {% render 'audittag-seo' %}
  immediately before </head> in layout/theme.liquid.

  Nothing here calls out to a remote service.
{%- endcomment -%}

{%- comment -%}
  Each block below targets a page by its own resource
  (product.handle, collection.handle, page.handle, …), not by URL.
  A product reached through a collection is served at
  /collections/x/products/y, so matching request.path would miss it;
  the resource handle is the same however the page was reached.
{%- endcomment -%}

{%- if request.path == '/' -%}
  {%- comment -%} https://ashcombecoffee.example/ {%- endcomment -%}
  <meta name="twitter:card" content="summary">
  <meta name="twitter:title" content="Speciality coffee roasted to order | Ashcombe Coffee">
  <meta name="twitter:description" content="Small-batch speciality coffee roasted twice a week in Frome and posted the day it is roasted. Free UK delivery over £30.">
  <script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Ashcombe Coffee Roasters","url":"https://ashcombecoffee.example/","logo":"https://ashcombecoffee.example/cdn/shop/files/ashcombe-logo.png","address":{"@type":"PostalAddress","streetAddress":"Unit 4, Mill Yard","addressLocality":"Frome","postalCode":"BA11 1AB","addressCountry":"GB"},"sameAs":["https://www.instagram.com/ashcombecoffee"]}</script>
{%- endif -%}

{%- if article.handle == 'dialling-in-espresso-at-home' -%}
  {%- comment -%} https://ashcombecoffee.example/blogs/journal/dialling-in-espresso-at-home {%- endcomment -%}
  <meta name="twitter:card" content="summary">
  <meta name="twitter:title" content="Dialling in espresso at home - Ashcombe Journal">
  <meta name="twitter:description" content="Most bad home espresso is the grind. Set a dose and a yield, change one thing at a time, and expect to grind finer as a bag ages.">
  <script type="application/ld+json">{"@context":"https://schema.org","@type":"BlogPosting","headline":"Dialling in espresso at home","datePublished":"2026-07-02","url":"https://ashcombecoffee.example/blogs/journal/dialling-in-espresso-at-home","publisher":{"@type":"Organization","name":"Ashcombe Coffee Roasters"}}</script>
{%- endif -%}

{%- if product.handle == 'ethiopia-guji' -%}
  {%- comment -%} https://ashcombecoffee.example/products/ethiopia-guji {%- endcomment -%}
  <meta name="twitter:card" content="summary">
  <meta name="twitter:title" content="Ethiopia Guji Natural coffee, 250g | Ashcombe">
  <meta name="twitter:description" content="A natural-process heirloom lot from Guji, light roast. Strawberry, bergamot and a honeyed finish, best as pour-over or AeroPress. 250g, £13.00.">
  <script type="application/ld+json">{"@context":"https://schema.org","@type":"Product","name":"Ethiopia Guji Natural","sku":"ASH-EG-250","description":"A natural-process heirloom lot from the Guji zone, light roast. Strawberry, bergamot and a honeyed finish.","image":"https://ashcombecoffee.example/cdn/shop/products/ethiopia-guji-250g.jpg","brand":{"@type":"Brand","name":"Ashcombe Coffee Roasters"},"offers":{"@type":"Offer","price":"13.00","priceCurrency":"GBP","url":"https://ashcombecoffee.example/products/ethiopia-guji"}}</script>
{%- endif -%}

{%- if product.handle == 'house-espresso' -%}
  {%- comment -%} https://ashcombecoffee.example/products/house-espresso {%- endcomment -%}
  <meta name="twitter:card" content="summary">
  <meta name="twitter:title" content="House Espresso - Ashcombe Coffee Roasters">
  <meta name="twitter:description" content="Brazil Cerrado and Colombia Huila, roasted medium-dark. Chocolate, hazelnut and dried fruit, for espresso or a moka pot. 250g, £11.50.">
  <script type="application/ld+json">{"@context":"https://schema.org","@type":"Product","name":"House Espresso","sku":"ASH-HE-250","description":"Brazil Cerrado and Colombia Huila, roasted medium-dark. Chocolate, hazelnut and a little dried fruit.","image":"https://ashcombecoffee.example/cdn/shop/products/house-espresso-1kg.jpg","brand":{"@type":"Brand","name":"Ashcombe Coffee Roasters"},"offers":{"@type":"Offer","price":"11.50","priceCurrency":"GBP","url":"https://ashcombecoffee.example/products/house-espresso"}}</script>
{%- endif -%}

{%- if collection.handle == 'coffee' -%}
  {%- comment -%} https://ashcombecoffee.example/collections/coffee {%- endcomment -%}
  <meta name="twitter:card" content="summary">
  <meta name="twitter:title" content="Coffee - Ashcombe Coffee Roasters">
  <meta name="twitter:description" content="Every coffee Ashcombe roasts, from House Espresso to Ethiopia Guji Natural. Whole bean or ground to order, posted the day it is roasted.">
{%- endif -%}

{%- if page.handle == 'about' -%}
  {%- comment -%} https://ashcombecoffee.example/pages/about {%- endcomment -%}
  <meta name="twitter:card" content="summary">
  <meta name="twitter:title" content="Our story: roasting in Frome since 2018 | Ashcombe">
  <meta name="twitter:description" content="Ashcombe began in 2018 with a 5kg roaster in a Frome garage. We now roast twice a week in Mill Yard and publish the price paid for every lot.">
{%- endif -%}

• 2 H1 headings on one page Keep "Speciality coffee, roasted to order in Frome" as the H1. Your logo image ("Ashcombe Coffee Roasters") is also wrapped in an H1. A logo does not need to be a heading at all, so change that wrapper to a <div>, checking the styling still holds.
• Article has no named author Add a named author with a real bio, and mark it up with Person schema or a rel="author" link. We cannot invent an author for you.
• Heading order jumps from H1 to H3 Change "Where we source" to an H2, or add the missing level above it.
• Open Graph is incomplete Some Open Graph tags are already present, so adding more from a snippet would leave you with both sets. Complete them in snippets/meta-tags.liquid instead. Affects 6 pages.

• A missing llms.txt file.Google has said it does not use one, so not having one costs you nothing in search.
• An empty alt on a decorative image.That is the correct markup. It tells screen readers to skip the image.
• A folder blocked in robots.txt.That is usually deliberate, so we only speak up when robots.txt blocks the whole site.
• Keyword density and word counts.Google does not rank pages on either.
• The meta keywords tag.Google has ignored it since 2009.

Check my tracking, free