Thistle Tavern×

Data-driven strategy · thistletavern.com

What the data says. What we do about it.

Our first review looked at your site from the outside. This one starts from your own Search Console and GA4: where you already win, where you lose clicks, what search earns today, and the order we would fix things in. Your stated aim is for half of the business to be online. This is how search gets it there.

Prepared forThistle Tavern
Builds onTechnical SEO priorities, 10 Nov
Prepared bySearchflex
Date17 November 2026

See the data ↓ The strategy ↓

The headline, from Search Console
2,817 → 9,254

Google clicks to the site each month, November 2025 to October 2026. Clicks more than tripled, with the biggest step in July 2026.

Where the data comes from
  • Carried overFirst reviewCrawl findings, 10 Nov proposal
  • LiveSearch ConsoleClicks and queries, 17 Jul 2025 to 15 Nov 2026
  • LiveGA4Purchase revenue, 12 months to 16 Nov 2026
  • LiveAhrefsSearch volumes and backlinks
  • SuppliedYour screenshotsIndexing, crawl, page speed and markup, 17 Nov 2026

01 · What the data shows

Clicks have tripled, led by collections for newer games.

Four views of the same site: how Google sees it, how it performs, what organic search earns and where its authority sits. Two terms to know: click-through rate (CTR) is the share of people who see you in Google and click, and position is where you appear, with 1 at the top.

Dead booking links
103

Internal links to the broken events page (92) and room booking page (11), from the 10 November proposal.

Blank pickup fragments
~3,400

Pickup availability fragments our crawler found, with no title or content. The theme requests them when a product page loads.

Collections over 2MB
76

Googlebot fetches the first 2MB of a page’s HTML, uncompressed. Anything past that point is not read.

Filter URLs
~5,000

Extra addresses created by the rarity filters.

What Google reports

Google has indexed 20,600 pages and knows of 100,919 it has not. Your sitemap lists 15,233.

The addresses Google has not indexed are about 6.6 times the sitemap, which suggests most come from links, filters and variants rather than from pages you list on purpose. On a Shopify store of this size that is common. What matters is which of them are normal and which are costing you.

Indexed
20.6k

Pages Google has indexed. More than the sitemap lists, so some indexed pages are not in it.

Not indexed
101k

Exactly 100,919, across 11 reasons, grouped into seven below.

Share indexed
17%

20,600 of the 121,500 or so addresses Google knows of. Many of the rest are duplicates that are meant to be ignored.

Trend
↓1/3

Indexed pages fell from about 32,000 in early September to 20,600 (read from the chart). Was that a clean-up, or pages being lost?

Why Google has not indexed these addresses, in plain English

Duplicate versions pointing to the main page39,615
Looked at, then left out by Google36,126
Page not found (404)18,688
Blocked by robots.txt5,732
Found, not yet visited554
Excluded by noindex tag94
Other: soft 404, redirect, server error, duplicates110

Source: Search Console, Indexing, Pages, “Why pages aren’t indexed”, screenshot of 17 November 2026. Google’s labels in order: alternate page with proper canonical tag, crawled currently not indexed, not found (404), blocked by robots.txt, discovered currently not indexed, excluded by noindex, other. The seven groups add up to 100,919.

Duplicate versions

39,615. On Shopify this is mostly the same product reached through a collection address or a variant link, pointing back to the main page. Normal. The fix is for the theme to link to the main product address (remove the collection-scoped product link). They are already canonicalised, so we expect little harm.

Looked at, then left out

36,126. Usually thin or near-identical pages. The screenshot shows validation as failed, which would mean Google re-checked and still left them out. We would confirm that in Search Console.

Page not found (404)

18,688. About 18% of Googlebot’s 1.89 million requests in 90 days hit a 404, roughly 340,000 visits. That is about 18 visits for each of the 18,688 listed addresses, so we would also look for addresses made by scripts or old links that are not listed.

Blocked by robots.txt

5,732. Your rules keep Google out of these. A blocked address can still be listed without being read, so we check that none are pages meant to sell.

What Google says is in good shape
The good news

The speed data we have is good. The heaviest pages are not in it.

The URLs Google holds speed data for (371 on mobile) are good, the product details it has read are valid, and Merchant Centre has your delivery policy, returns policy and store ratings set up. We do not know whether the 76 oversized collections are in that sample, which is why move 3 still matters.

Page speed, mobile
371

Good URLs (Core Web Vitals), with 0 poor and 0 needing improvement.

Page speed, desktop
360

Good URLs, with 0 poor and 11 needing improvement.

Product details Google reads
276

Valid items, 0 invalid. 257 have no ratings or reviews markup, which should only be added from genuine reviews.

Merchant listings
496

Valid items, 1 invalid (missing image). 136 have a barcode (GTIN) problem (130 invalid, 6 not globally valid). 497 lack shipping and returns fields in the markup, which is optional when Merchant Centre already has them.

Merchant Centre

About 33,200 items approved and visible (likely variants, not products), 132 not approved for reasons we have not yet seen. Delivery policy, returns policy and store ratings are all set.

The sitemap

The main sitemap was read on 16 November and lists 15,233 pages. A second entry, /a/llms, has not been fetched since 9 July and shows 0 pages. It is not a sitemap, so it should be removed from that list.

Googlebot

1.89 million requests in 90 days: 66% for HTML pages, 78% answered OK, 18% not found, 4% other client errors. Average response time is 328 ms. On this volume, crawl budget is probably not the limit, so we say the clean-up may help rather than will.

Source: the first review crawl behind the 10 November proposal, carried over unchanged. Everything under “What Google reports” is from your Search Console and Merchant Centre screenshots on 17 November 2026. Structured data counts are the items Google has read, not the whole catalogue.

02 · Does this look right?

Seven numbers worth checking together.

Some figures in your data look odd. Each has two possible explanations: it is right and there is a reason, or it is wrong and we fix it. For each we give our lead theory and how we would settle it, usually in one call with your developer.

7things to check2possible answers each1call to settle most of them

Measurement you can trust is part of the work.

Every priority and every result we show you rests on these numbers, so settling them early protects the plan.

Go to next steps ↓

03 · The core range

Flesh and Blood is your core range. The pages we can identify earn about one Google click in ten.

We understand Flesh and Blood is the game that drives your business, and, by your account, that its 5,000-product collection breaks the standard filters. Here is what Search Console shows for it, and where we would start.

Check
Is this the right picture? The 9.5% is a floor: it only counts pages we can identify by address, and players also search by hero and card name. Search demand for Flesh and Blood may also be smaller than its share of sales, because the game sells through community and direct visits. In GA4 only one Flesh and Blood item (£8,974) is in the top eight sellers, but item categories are product types, not games, so we cannot yet read revenue by game. Tell us the real split, or we will rebuild it from Shopify order lines.
The first thing we would fix

The Flesh and Blood hub page is shown 43,259 times and clicked 383.

That is a 0.89% click-through at a blended average position of 4.2. A blend can hide a top spot for a few searches and a low one for the main “flesh and blood” search, so we cannot yet say it is low. We would split it by search first. We would also decide which address should own the head term: this page, or /collections/flesh-and-blood and the singles collection. It is your most-seen Flesh and Blood page, so it is where we begin.

Share of Google clicks

9.5% of clicks to your top 1,000 pages go to Flesh and Blood pages. That is 176 pages and 6,553 clicks. One tile is one percent. It is a floor: it only matches addresses containing flesh-and-blood, fab or armory (excluding some Lorcana “fabled” pages), and players also search for hero and card names.

Three lanes a Flesh and Blood player travels

Flesh and Blood searches in the top-query data, grouped by what the player wants. Anonymised searches are not included.

Six cards. Tap to see what we would do.

Source: Search Console, Web, 17 July 2025 to 15 November 2026. Flesh and Blood pages are those with flesh-and-blood, fab, or armory in the address, within the top 1,000 pages. Searches come from the Flesh and Blood search export plus the “fab” searches in the top-queries export, and the three lanes are our grouping. Counts are approximate for these reasons.

04 · Opportunities

Five places to go next.

The proposal called these “beyond the fixes”. With your own data in hand, each one now has evidence behind it, and a fifth has appeared.

A

Win more of the clicks you already earn impressions for

Pages and searches where Google shows you often but few people click. Two tables below: pages first, then searches.

Proposal: Rankings audit ↗
B

Answer the searches you barely appear for

“pokemon cards” is searched 148,000 times a month in the UK. Search Console shows 654 impressions for it across 16 months. Board games (24,000 a month) and Pokémon booster boxes (16,000) are in the same position.

Proposal: Content gaps ↗
C

Give the huge catalogues a structure

By your account, Flesh and Blood can run to around 5,000 products in one collection, which breaks Shopify’s filters. Its two playmat searches alone show 7,126 impressions, so there is steady demand at the edges.

Proposal: Fixes 5 and 6 ↗
D

Be ready before each release

New-game collections already drive six of your top ten pages. A plan that runs two to three months ahead of releases makes that deliberate.

Proposal: Opportunities, continuously ↗
E · New

Serve the overseas demand you already have

31% of clicks come from outside the UK: the US (5,187), Japan (5,158), Canada, France, Germany, Australia and Singapore. Your 70 Japanese-language pages in the top 1,000 earn 4,243 clicks.

Pages Google shows often and people rarely click

Pages with at least 20,000 impressions and a click-through rate under 3%, excluding the contact, events, store and catalogue pages that people reach by searching for your name. Some of these are snippet problems and some are position problems, so we split them by search before changing anything.

PageImpressionsClicksCTRAvg position

Source: Search Console, Web, 17 July 2025 to 15 November 2026.

Searches where you sit just below the top

A selection of 14 of the 27 searches with at least 1,700 impressions where you average position 4 to 11. The others are mainly Riftbound, Palworld, Gundam, Commander and Japanese-language variants. Combined impressions for the selection below: . Filter by theme.

SearchImpressionsClicksCTRAvg position

Source: Search Console, Web, 17 July 2025 to 15 November 2026. Average position over the whole period.

Edinburgh

“thistle tavern edinburgh” already earns 1,281 clicks, and Pokémon searches for Edinburgh sit around position 7 to 8. We need to confirm whether you have a presence in Edinburgh. If so, a page per shop, built for its own local searches, is the usual fix.

Aberdeen

“pokemon cards aberdeen” averages position 3.3 with a 10% click-through rate, which is what a well-matched page looks like. The search table below starts at position 4, so this search is not listed in it. Calls, directions and map views do not show in Search Console; Business Profile Insights has them. It is worth repeating for Edinburgh if that shop exists.

Japan

Searches in Japanese, such as the Riftbound terms, bring 1,854 clicks from just 44 queries. The pages exist and already earn clicks. Whether those visitors can buy and have orders shipped to them is worth a closer look.

05 · The strategy

Twelve moves, grouped by when they start.

Grouped by when each can start and what it unlocks. Open any card for the reasoning and the link back to the proposal. The impact and effort ratings are our judgement from the first review and your data, and clean GA4 revenue will re-rank them.

06 · Roadmap

Three months, one re-scan after each step.

The same rhythm as the proposal: clear specs for your developers, a re-scan of the site to check the work, then the next group. Numbers refer to the twelve moves above.

What we will measure

The baseline is set before any work starts, so every result can be shown against it.

MeasureSourceBaseline
Method, sources and what we could not check
  • Search Console. Property thistletavern.com, Web search, 17 July 2025 to 15 November 2026. Query and page tables are capped at the top 1,000 rows and omit anonymised queries, so real totals are slightly higher. The first and last months hold 15 days each.
  • GA4. Purchase revenue only, 17 November 2025 to 16 November 2026, in GBP. Session counts are not used: Direct sessions are about nine times last year and the reasons are set out in section 02. Event values were unusable, item categories are mostly blank so the item-name report is used, and purchase tracking appears to have changed in June 2025, so no year-on-year change is claimed. Channel attribution looks loose, with £111k Unassigned.
  • First review. The crawl findings (broken links, blank pages, heavy collections, filter URLs, titles and images) are carried over from the 10 November proposal. We have not re-measured them here.
  • Ahrefs. Used for backlinks and for the Pokémon, board game and booster box search volumes in the proposal. It is not used for traffic or site-audit figures.
  • Search Console screenshots. Indexing, crawl stats, sitemaps, Core Web Vitals, product snippets, merchant listings and Merchant Centre, supplied by your team on 17 November 2026. We have used the figures as supplied. The Indexed total of 20.6k comes from the same report. URL lists per reason are capped at 1,000 rows in Search Console, so we do not use them here.
  • Not checked. Which URLs sit behind each indexing reason, reliable GA4 sessions, whether the July 2026 jump has a known cause, the quality of the 1,095 referring domains, and the location of each shop. Nothing here is estimated.
  • Call notes. Points attributed to your team come from the introduction call on 12 November and are your account, not a finding.

07 · Next steps

Agree the order. Fill the gaps.

Thank you for the Search Console and GA4 access. This page runs on your own figures. The checks in section 02 are the one thing still to settle, and the order of work will be weighted again by what each fix turns out to be worth.

01

Agree group one

Moves 1, 2 and 10 can start straight away. They need no design change and no new content, only clear specs for your developers.

02

Name a developer contact

One person we can send redirect lists, robots rules and template changes to, and who can tell us what is easy and what is not.

03

Answer seven questions

They shape the local pages, the overseas work, the release calendar and the GA4 fix. They are below.

If you wait

What the data says is already happening

Indexed pages fell by about a third from early September. We do not yet know whether that was a clean-up or a loss, and settling it is the first job in move 2. 29% of your clicks ride on one page. Every new set that launches without a ready page is a window you do not get back.

How we work

Your data first, then proof

Every move starts from Search Console, GA4 and Ahrefs. We re-scan the site after each step to confirm it worked, fix a baseline before any work starts, and send one monthly report you can hold us to. We do not forecast revenue; we report against the baseline.

The first 12 weeks

What you will see

By week 2, the indexing drop explained, redirect and robots specs delivered and blank pages closed. By week 6, collections readable and new titles live. By week 12, shop and overseas pages live, first guides published and a monthly report running.

Questions for you

  1. Where is each shop? Is the second one in Edinburgh, and which should the local pages lead with?
  2. Which games bring in the most online revenue today? Flesh and Blood was named as the core, and we want to compare it with what GA4 shows.
  3. Where do you get set release dates, and how far ahead do you know them?
  4. For Pokémon items shown online only to signal stock, should those pages exist for search at all, or point people to the shop?
  5. Monthly Google clicks more than doubled from June to July 2026. Do you know what changed that month: a launch, a site change, a campaign?
  6. GA4 shows more than five times the sessions of last year without more purchases, which looks like bot or mis-attributed traffic. Can your developer check bot filtering and whether GA4 is installed twice?
  7. What was total business revenue over the last twelve months, shops and online together, or what share is online today? You aim for half the business online, and we need that starting point to report against it.

Next call: Tuesday 24 November, 12:00.

We will walk through this page, settle the checks in section 02, and agree the order of work.

  • 1Confirm the order of the twelve moves
  • 2A contact for your developers
  • 3Your go-ahead to start group one
See the strategy again ↑