Google is showing a different meta title than the one you set in Shopify

Short answer. The "Search engine listing" field in Shopify admin sets your page's <title>, and Google treats that tag as one of nine sources it may use for the headline it actually shows. Shopify's own help page states that search engines "can choose to rewrite page titles and meta descriptions", so the text in results "might not match what you entered". Google documents seven page conditions it adjusts for, and the stock Shopify theme edits your title before Google ever reads it.

Nine sources, one field

You opened the product in Shopify admin, scrolled to the bottom, and typed a title into the box under Search engine listing preview. Then you searched for the product and Google showed something else: a different phrase, your store name where you did not put one, or your store name missing where you did.

Nothing is broken. The field did what it says. It is the input that is smaller than it looks.

The complaint is not new. On a Shopify Community thread opened on 16 December 2022, a merchant reports that "Up until very recently google has started showing a different title to what I have provided in Shopify", and asks what it means for their rankings. Four replies later, covering crawl delays, requesting indexing and Google preferring a better-matching title, the thread closes without an answer to that question and is not marked solved.

Google's documentation on title links states that "Google Search uses the following sources to automatically determine title links", and then lists nine of them:

• Content in <title> elements
• Main visual title shown on the page
• Heading elements, such as <h1> elements
• Content in og:title meta tags
• Other content that is large and prominent through the use of style treatments
• Other text contained in the page
• Anchor text on the page
• Text within links that point to the page
• WebSite structured data

Shopify's field controls the first one. The same Google page adds that "Google's generation of title links on the Google Search results page is completely automated", and that where it detects a problem, "we may try to generate an improved title link from anchors, on-page text, or other sources".

Shopify says the same thing, in the same help article that tells you to fill the field in. Near the top: "The title is displayed as a clickable link in search engine results." Further down the same page: "Search engines, such as Google, can choose to rewrite page titles and meta descriptions based on the page content and other signals. This means that even after you update the SEO fields in your Shopify admin, the text that displays in search results might not match what you entered."

The label on the box is Search engine listing preview. It previews one of nine inputs, and it is the only one of the nine the admin shows you.

Shopify edits your title before Google reads it

Before any of Google's nine sources come into play, the text you typed passes through your theme. Shopify's documentation on theme SEO metadata publishes the pattern, in layouts/theme.liquid:

<title>
  {{ page_title -}}
  {%- if current_tags %} &ndash; tagged "{{ current_tags | join: ', ' }}"{% endif -%}
  {%- if current_page != 1 %} &ndash; Page {{ current_page }}{% endif -%}
  {%- unless page_title contains shop.name %} &ndash; {{ shop.name }}{% endunless -%}
</title>

Three of those four lines add text you never typed. A tag-filtered collection URL gains the tag list. Page two of a collection gains – Page 2. And every page gains your store name, on one condition.

That condition is the interesting one. unless page_title contains shop.name is a substring test, so whether your brand appears in your own title depends on whether the title you typed happens to contain your store name somewhere inside it. For a store called Pine, a "Pine Console Table" satisfies the test and gets no suffix; a "Console Table" does not and gets one. Two products in the same catalogue, two title shapes, one template, no setting.

That is visible in the sample below, as a consistency rather than a proof. Two of the thirteen storefronts had a product whose admin title contained the store name as a substring, and the one store whose served <title> was exactly its admin product title, with no brand anywhere in it, was one of those two.

One more mismatch lives in the same Shopify help page. It states that "You can enter up to 70 characters in the title" and, in its own guidance, "Enter a title that is 60 characters or fewer. Most search engines shorten longer titles." The field accepts ten characters more than the advice beside it recommends, and the suffix above is appended after you have counted.

The seven conditions Google adjusts for

Google does not describe this as a judgement call. Its title-link documentation names seven specific conditions, and two of them are produced by the template quoted above.

• Half-empty <title> elements. Google's example is literally <title>| Site Name</title>, and its response is to look "at information in header elements or other large and prominent text on the page". That is what an empty Page title field produces through the template above, which appends the shop name with a separator precisely because the empty title does not contain it.
• Obsolete <title> elements. Google's example replaces a 2020 date in a title with 2021. A title naming a year or last season's model goes stale with the page untouched.
• Inaccurate <title> elements. Google "tries to determine if the <title> element isn't accurately showing what a page is about". Its example narrows "Giant stuffed animals, teddy bears, polar bears" to "Stuffed animals".
• Micro-boilerplate text in <title> elements. The documented trigger is "When there are repeated boilerplate text in <title> elements for a subset of pages within a site". A bulk edit that gives a run of products the same title pattern, or a theme fallback used wherever the field is empty, is exactly that shape.
• No clear main title. "When there's more than one large, prominent heading, and it isn't clear which text is the main title of the page", Google says "it may use the first heading as the text for the title link". The first heading on a Shopify product page is not always the product.
• Mismatch of writing system or language. Google's example is a page in Hindi whose title carries English or transliterated text. A translated storefront whose SEO fields were not translated with it is the same mismatch.
• Duplication of the site name. Google "may omit the site name from the title link, if it's repetitive". The stock theme appends the shop name to every page that does not already contain it.

Read the last two together and the loop closes: the template adds your store name because that is what it is written to do, and Google may take it out again as repetitive. Neither system is misbehaving, and only the outcome is visible to you.

What thirteen live storefronts actually send

The documentation says what Google chooses between. It does not say what a Shopify product page puts in front of it, so we measured.

On 10 October 2026 we fetched one product page from each of thirteen live storefronts, every one confirmed Shopify-served by its own response header, with a Googlebot user agent and redirects followed. The product handle on each store came from that store's own public catalogue endpoint, so the page we read is the page the store publishes. For every page we recorded four of Google's nine sources: the <title>, the og:title, the first <h1>, and the product name in the page's own Product structured data. That last block is the one whose other fields drive the two Search Console reports on product markup.

• The <title> matched the product's admin title on 1 of the 13. On the other twelve the served title had been shortened, extended, suffixed or rewritten relative to the name the product carries in the catalogue.
• It ended in the store's own brand string on 8 of the 13. On one it led with the brand instead, on two the brand sat somewhere in the middle, and on two it appeared nowhere in the title at all.
• og:title was present on 10 of the 13, and on 5 of those 10 it differed from the <title> on the same page. Both are on Google's list of sources. Half the pages that declare both declare two different answers.
• On the nine pages that served an <h1> at all, its text appeared inside the <title> on 8. On the ninth the heading carried a word the title did not.
• Five of the thirteen served two or more <h1> elements on one product page, and one served four, which is the condition Google describes as no clear main title. Four served exactly one, and four served none at all.

One storefront is worth describing on its own, because it is the inaccurate-title case rather than a near miss. Its product page served a <title> and a Product structured-data name that share no word: the schema and the catalogue both name the product one way, the title describes it another, and the og:title agreed with the title rather than with the schema. The canonical tag was correct and self-referencing, so this is not a wrong page being served. The page simply tells Google the product's name twice, differently.

Three caveats belong with that measurement rather than underneath it. These were well-known storefronts picked because they answer a request, not a random sample of Shopify, and thirteen pages are thirteen pages: the counts above are a sample, not a rate. Our requests came from a datacentre address, where Google crawls from ranges it publishes. And the four pages that served no <h1> are the HTML of a first fetch: a raw fetch cannot settle whether an element arrives later through JavaScript, which is why the confirm step below uses Search Console's rendered view instead. One note on scope rather than a caveat: three of the thirteen ran Shopify's headless stack, identified from their response header, where theme.liquid is not what builds the title, so the template in the previous section does not describe them.

The site name is a separate decision, made on your home page

The headline of your result has two parts. Beside the title, Google shows a site name, and that one is not decided on the product page at all. In a Shopify Community thread about setting it, a merchant writing on 20 August 2024 asks whether to hand-write a WebSite JSON-LD block into the theme to get the name they want, and says they are not familiar with editing code. That is the position the documentation below puts a merchant in.

Google's documentation on site names names its inputs as "og:site_name, <title>, heading elements, and other text on a home page", and then ranks them: "However, WebSite structured data is most important, if you want to specify a preference." Three constraints follow from the same page, and each one changes where the fix has to go:

• "The WebSite structured data must be on the home page of the site." Adding it to a product page does nothing for this.
• "Google Search does not support site names at the subdirectory level." A store serving markets as locale subfolders cannot give one of them its own site name.
• "While we can't manually change automatically selected site names", the documented lever is alternateName, which "allows Google to consider other options if your preferred choice isn't selected". Google adds that if its site name system "isn't confident enough to use your preferred name, it strongly considers this option".

So we read the home page of the same storefronts. Fourteen of them served a home page we could parse, and within that sample Google's most important input was the one least often present.

• WebSite structured data: present on 6 of 14.
• og:site_name: present on 10 of 14.
• Neither signal: 4 of 14, leaving the home page <title> and prominent text as the only inputs Google has.
• alternateName: present on 0 of the 6 that carried a WebSite block. The documented fallback was unused by every store that had somewhere to put it.
• Five of the 14 served no <h1> on the home page, with the same first-fetch caveat as above.

This is where the two halves meet: WebSite structured data is on Google's list of title-link sources and is its most important site-name input, so one block on one page feeds both decisions. That block is also one more thing your home page tells machines about your store with no screen in admin to show it.

Two things we do not claim. We measured what these pages declare, not which site name Google displays for any of them. And because the selection is "completely automated", a store with no WebSite block is not thereby showing a wrong name: it has left the choice to Google's reading of its home page.

Confirm it on your own store in five minutes

Google's title-link documentation does not send you to a report. Having described the behaviour, it says to "check whether your page has one of the issues" listed above, and for anything beyond that it points to Google's Search Central Help Community. Shopify admin, for its part, shows you your own field. So the place the outcome is visible is the result itself.

1. Search your exact product title in quotation marks and read the headline of your own result, both lines of it: the title and the site name beside it. Write down what you see before changing anything: it is the only record of the current state you will have afterwards.
2. Read the four strings the page sends. Open the product URL and look at the served HTML, not only the rendered layout: the <title>, the og:title, the first <h1>, and the name in the Product structured data. Google's Rich Results Test parses the last one for you, and reports nothing at all where the block failed to parse rather than where it is absent. Where those four disagree, you have found the documented trigger rather than a cosmetic detail.
3. Count the <h1> elements on that page. More than one prominent heading is the no-clear-main-title condition, and an announcement bar, a logo rendered as text or a section heading can each be the first one.
4. Compare the admin preview against the page. The preview shows the field. The page serves the field after the theme has appended the shop name, the tag list or the page number. If they differ, the template is doing it, not Google.
5. For the site name, read your home page. Look for a WebSite block with a name, then og:site_name, then the home page <title>. Whichever is the first one present is what you have told Google, whether you meant to or not.
6. Use URL Inspection and read the rendered view, plus the last crawl date. The rendered view settles whether a heading you cannot see in a raw fetch is actually there; the crawl date tells you whether Google has seen your edit yet. Crawling takes days to weeks, and Google says a site-name change "can take anywhere from several days to several weeks" to be recrawled.

The fix, and why it comes back

Each documented condition has a corresponding edit, and they are worth doing in this order because the first three remove the reasons Google has to go looking elsewhere.

• Give every product a Page title, and make it describe that product. An empty field is the half-empty-title case, and a field holding the product's actual name is what that one controllable source is for.
• Make the titles distinct from each other. Repeated patterns across a subset of products are the micro-boilerplate condition by Google's own definition. A catalogue filled by a bulk edit or by a template fallback is where this lives, and it is the only one of the seven conditions Google defines across a set of pages rather than on one page.
• Decide the brand suffix deliberately. You cannot control it by typing it: the template appends the shop name unless your title already contains it, so adding the brand yourself removes the automatic suffix and omitting it adds one. Pick which behaviour you want and write the titles to match it.
• Make the <title>, the og:title, the <h1> and the Product name describe the same product. They need not be identical strings, but they do have to agree, and strings written by different systems drift. Where an app writes your markup or your meta tags, that is where it breaks first, the way it does for review stars, for the warnings Search Console raises on product markup, and for a noindex tag nobody set by hand.
• Leave one prominent <h1> per product page. If a section heading or a text logo is marked up as a second one, it is a candidate for your title.
• For the site name, put a WebSite block on the home page with the name you want and an alternateName as a fallback. Google documents the fallback as something it strongly considers, and none of the six stores that had somewhere to put it was using it.

What none of that buys you is finality, and this is the part worth planning for. Every one of those edits sits in a place something else writes to. A theme update restores the template. An app that rewrites meta tags, or the leftovers of one that was uninstalled, writes over the og:title. A bulk edit flattens distinct titles into one shared pattern in a single pass. Adding a market adds a locale whose SEO fields are not translated with the storefront. Renaming a product can break the contains test in either direction and silently move the brand into or out of that page's title.

None of those edits announces itself in Shopify admin, which goes on showing you your own field, correct, throughout. The Search Console reports that cover a Shopify store are about whether a page is indexed, not about what its headline says once it is. So the useful question is not how to make Google use your title once. The question is what tells you, without you searching for your own products, that your pages and Google have stopped agreeing about what you sell. That puts this next to the image Google picks and the price it shows, the other two listing elements assembled automatically from whatever your pages declare, and inside the wider set of ways a Shopify store loses Google visibility quietly.

Is this happening on your store right now?

Search Console will not page you when this happens. The product page loads fine in a browser, the sitemap looks clean, and Google quietly stops crawling or indexing it anyway. The only way to know is to check the pages the way Google sees them.

• 90+ checks, the way Google crawls and indexes your store. Noindex tags, canonicals, redirects, robots.txt, sitemap coverage.
• Read-only. No app to install, no admin access, nothing changes on your store.
• The exact fix for each page, in plain English, so you or your developer can act the same day.

Across full-catalog scans of more than 90,000 Shopify product pages, about 1 in 4 stores had at least one critical Google visibility issue.

Scan my store for free

Free scan: issue types, counts and first fixes. Full report on every product page, not a sample: $49 once, no subscription.