Table of Contents
ToggleStage 2: Visibility
Format: Hands-On Live Project A–Z | aiseojournal.net | March 2026 Store: shopifystore1.co.uk | Platform: Shopify | UK-based DTC store Applied: Shopify SEO
SECTION 9 — KEYWORD ARCHITECTURE
The Visibility Problem Stage 1 Confirmed
Stage 1 exported the GSC data. Stage 1 ran the competitor snapshots. The picture is the same for almost every mid-size UK Shopify store at this point in the programme: the store has organic impressions but almost no organic clicks because the pages earning impressions are titled wrong, described wrong, and structured wrong for the queries they appear in.
The keyword architecture in Stage 2 does not start from zero. It starts from the near-miss keywords identified in Section 8B and the competitor gap findings from Section 8C. The Ahrefs and Semrush research adds volume data and discovers keywords the store is not yet ranking for. The combination produces a complete, prioritised keyword map across all four tiers.
Pro Tip: The fastest revenue impact from Stage 2 comes from fixing the Category A near-miss keywords first — the ones where a collection page already ranks positions 11–30. A correctly optimised collection description for a keyword at position 14 will typically move to position 5–8 within 4–6 weeks of Googlebot re-indexing the updated page. That is existing traffic being recaptured, not new traffic being generated.
9.1 — Keyword Research Method
Run keyword research in this order. Each step builds on the previous one.
Step 1 — GSC near-miss import (from Section 8B): Paste the near-miss keyword list from Section 8B into a working spreadsheet. These are confirmed opportunities — the store already has some ranking history for them.
Step 2 — Ahrefs competitor gap: Ahrefs → Site Explorer → enter top 3 competitor domains from Section 8C → Content Gap → filter: competitors rank but shopifystore1.co.uk does not → export → filter to UK volume > 100/month
Step 3 — Shopify collection-by-collection research: For each collection, open Ahrefs Keyword Explorer → enter the collection’s most obvious head term → check: UK volume, KD, SERP top 10 DR range, PAA questions, related keywords → record all Tier 1–4 keywords
Step 4 — Google Autocomplete and PAA: Search each collection’s head term in Google incognito (UK location) → screenshot Autocomplete suggestions → screenshot PAA block → these feed directly into H2 subheadings and FAQ blocks in Section 10 collection descriptions
Step 5 — UK modifier testing: For every Tier 1 keyword, test volume with and without “UK” modifier. Some keywords have higher volume without the UK suffix (“merino wool jumpers” > “merino wool jumpers UK”) — in those cases use the modifier in the meta description and body copy rather than the title tag, to capture both.
9.2 — Complete 4-Tier Keyword Architecture
The following architecture is the Stage 2 working document. Replace [VARIABLE] fields with actual research data. The structure below is production-ready for a UK Shopify fashion/lifestyle store — adapt category names to the actual shopifystore1.co.uk product range.
TIER 1 — Collection Head Terms
These are the primary commercial queries each collection page must rank for. One Tier 1 keyword per collection. The collection page owns this keyword exclusively — no other page on the store targets it.
| Collection | URL | Tier 1 Keyword | UK Vol/mo (est.) | KD | Top 3 DR avg | Realistic timeline |
|---|---|---|---|---|---|---|
| [Collection 1 name] | /collections/[handle-1] | [PRIMARY KW] | [X,XXX] | Low/Med/High | [DR XX] | [X weeks to top 10] |
| [Collection 2 name] | /collections/[handle-2] | [PRIMARY KW] | [X,XXX] | Low/Med/High | [DR XX] | [X weeks] |
| [Collection 3 name] | /collections/[handle-3] | [PRIMARY KW] | [X,XXX] | Low/Med/High | [DR XX] | [X weeks] |
| [Collection 4 name] | /collections/[handle-4] | [PRIMARY KW] | [X,XXX] | Low/Med/High | [DR XX] | [X weeks] |
| [Collection 5 name] | /collections/[handle-5] | [PRIMARY KW] | [X,XXX] | Low/Med/High | [DR XX] | [X weeks] |
Cannibalisation rule — Tier 1: Before assigning a Tier 1 keyword to a collection, confirm via site:shopifystore1.co.uk "[keyword]" that no other page (homepage, blog post, Shopify page, other collection) targets the same query. If a conflict exists, resolve it before publishing the collection description. Resolution options: UPDATE the competing page to a different keyword, NOINDEX the weaker competing page, or CONSOLIDATE via a 301 redirect to the intended collection.
TIER 2 — Product Page Mid-Tail Targets
These are the specific product queries. Each product page in the Tier 1 priority list (top 10 bestsellers + top 10 near-miss products from GSC) gets its own Tier 2 keyword cluster: one primary keyword + 3–5 modifier variants.
| Product | URL | Primary T2 Keyword | Modifier variants | UK Vol/mo (est.) | KD |
|---|---|---|---|---|---|
| [Product 1] | /products/[handle] | [SPECIFIC KW] | [colour + material + size variants] | [XXX] | Low |
| [Product 2] | /products/[handle] | [SPECIFIC KW] | [style + gender + occasion] | [XXX] | Low |
| [Product 3] | /products/[handle] | [SPECIFIC KW] | [material + weight + care] | [XXX] | Low |
| [Product 4] | /products/[handle] | [SPECIFIC KW] | [colour + size + fit] | [XXX] | Low |
| [Product 5] | /products/[handle] | [SPECIFIC KW] | [collection + brand + year] | [XXX] | Low |
Tier 2 rule — UK specificity: Every Tier 2 keyword must include at least one UK-specific modifier: UK size notation, “UK” geographic signal, UK delivery term, or UK-specific buyer intent signal. “Navy merino jumper” is a US-and-UK query. “Navy merino jumper UK size 12” is a UK-specific query that converts at higher rates because the buyer is committing to a UK-specific size.
TIER 3 — Blog Content Informational Targets
These are the educational and comparison queries that funnel buyers into collection and product pages. Each Tier 3 keyword becomes a blog post brief in Section 12.
| Blog post topic | Target keyword | UK Vol/mo (est.) | Intent | Target collection | Target product |
|---|---|---|---|---|---|
| Cluster 1 — Pillar | [PILLAR KEYWORD] | [X,XXX] | Commercial investigation | /collections/[handle] | — |
| Cluster 1 — Support 1 | [SUPPORT KW 1] | [XXX] | Informational | /collections/[handle] | [product] |
| Cluster 1 — Support 2 | [SUPPORT KW 2] | [XXX] | Informational | /collections/[handle] | [product] |
| Cluster 1 — Support 3 | [SUPPORT KW 3] | [XXX] | Commercial investigation | /collections/[handle] | [product] |
| Cluster 2 — Pillar | [PILLAR KEYWORD 2] | [X,XXX] | Commercial investigation | /collections/[handle-2] | — |
| Cluster 2 — Support 1 | [SUPPORT KW 4] | [XXX] | Informational | /collections/[handle-2] | [product] |
TIER 4 — AI/Voice/PAA Targets
These queries appear in People Also Ask blocks and AI Overviews. They are targeted via FAQ blocks on collection pages and product pages — not via standalone blog posts (unless volume justifies a dedicated post).
| Query | Appears in | Target page | Implementation |
|---|---|---|---|
| “How do I [use case for product]?” | PAA on Tier 1 SERP | Collection page FAQ block | Add to H2-4 FAQ section in collection description |
| “What is the best [product] for [use case]?” | PAA + AI Overview | Blog pillar post | Blog content brief S12 |
| “Is [product material] warm enough for [UK season]?” | PAA on product query | Product page FAQ | Add to product FAQ block |
| “How do I wash [material] at home UK?” | PAA + AI Overview | Support blog post | Blog support post brief S12 |
| “What size [product] should I order?” | PAA on product query | Size guide page + product FAQ | /pages/size-guide/ + product page |
| “Does [brand] offer free delivery UK?” | AI Overview | Homepage + collection pages | Add to meta descriptions + Quick Answer blocks |
9.3 — UK Keyword Modifier Reference
Apply this to every keyword during research. Test each modifier — some increase volume significantly, some reduce it.
| Modifier type | UK variant | US variant to avoid | Test both? |
|---|---|---|---|
| Spelling | colour, grey, centre, jewellery | color, gray, center, jewelry | No — UK spelling only |
| Size notation | UK 8/10/12/14, UK size 8 | US 4/6/8, XS/S/M/L | Test both — UK site ranks for UK searches |
| Geographic | UK, England, British, British made | USA, American | Always include “UK” in title tag test |
| Currency | from £X, under £50 | $X, under $50 | UK currency in all UK-targeted copy |
| Delivery | free UK delivery, next-day UK, UK dispatch | free shipping, 2-day delivery | UK delivery language in meta descriptions |
| Season | autumn/winter, spring/summer, Christmas | fall/winter, holiday | UK seasonal language in collection descriptions |
| Occasion | smart casual, work wear, Sunday best | business casual, weekend | UK occasion language in product copy |
| Certification | organic cotton UK, GOTS certified UK | organic cotton, GOTS | Include “UK” if certification matters to UK buyers |
9.4 — Cannibalisation Map — Full Store
Run this check before any Stage 2 content is published. It is easier to fix cannibalisation in a spreadsheet than to diagnose it in GSC six months later.
Method:
- Export all page titles from Screaming Frog (Page Titles tab → Export)
- Export all H1s (H1 tab → Export)
- Open the combined export in a spreadsheet
- Sort by title tag alphabetically
- Flag any two pages with the same or near-identical primary keyword in the title tag
Most common Shopify cannibalisation patterns:
| Pattern | Example conflict | Detection method | Resolution |
|---|---|---|---|
| /collections/ vs /pages/ | “Sustainable Knitwear” collection vs “Sustainability” page | Both rank for “sustainable knitwear UK” | Update /pages/ to target brand sustainability story, not product keywords |
| /collections/ vs /blogs/ | “Wool Coats UK” collection vs blog post “Best Wool Coats UK” | Blog post outranks collection page | Blog targets informational intent; collection targets transactional. Change blog title to “How to Choose a Wool Coat UK” |
| Two collections | “Winter Coats” and “Wool Coats” both targeting “wool coats UK” | Both title tags contain “wool coats” | Differentiate: “Winter Coats” → transactional for all coat types; “Wool Coats UK” → material-specific |
| Product page vs collection | Specific product outranking the collection for the category query | Product title contains the collection keyword exactly | Product should target a more specific long-tail; collection owns the head term |
| /collections/all vs best collection | /collections/all indexed, ranking for category terms | GSC Performance → /collections/all appears in pages | Noindex /collections/all via robots.txt (Section 2, Stage 1) |
✅ CHECKPOINT — SECTION 9
- [ ] Keyword research: Steps 1–5 completed — GSC near-miss imported, competitor gap run, collection-by-collection research done
- [ ] Tier 1 table: all collections — primary keyword, volume, KD, top 3 DR, timeline confirmed
- [ ] Tier 2 table: top 20 priority products — primary keyword + modifier cluster confirmed
- [ ] Tier 3 table: two content clusters planned — pillar + 3 support posts per cluster
- [ ] Tier 4 table: PAA questions captured per Tier 1 keyword — assigned to FAQ blocks
- [ ] Cannibalisation map: all conflicts identified and resolved before any content is published
- [ ] UK modifier testing: all Tier 1 and Tier 2 keywords tested with UK modifiers
SECTION 10 — COLLECTION PAGE OPTIMISATION BRIEFS
Why Collection Pages Are the Commercial Heart of a Shopify Store
A Shopify store is not a blog. The primary revenue-generating URLs are collection pages — not blog posts, not the homepage, not individual product pages in isolation. A buyer searching “women’s wool coats UK” does not want to land on a blog post about the history of wool. They want to land on a page where they can browse, filter, and buy.
The collection descriptions written in Stage 2 are the most commercially impactful content produced in the entire 4-stage programme. They are also the most technically constrained: Shopify’s collection description field is a standard rich-text editor, the description sits either above or below the product grid depending on the theme, and the word count must balance SEO depth against conversion path disruption.
Pro Tip: The single most impactful structural decision for a Shopify collection page is where the description sits. Below-grid placement consistently produces better conversion rates because buyers land on products immediately rather than reading copy. Above-grid placement can produce better rankings if the collection targets a buyer who needs guidance before product selection — a buyer searching “sustainable knitwear UK” is often education-first. Default to below-grid. Move to above-grid only if bounce rate data (GA4 → Pages → Bounce rate → filter by collection page) shows buyers leaving without engaging with the product grid.
10.1 — Collection Page SEO Specification — Standard Template
Every collection brief follows this structure. Completed for the three highest-priority collections first based on the Section 9 Tier 1 keyword research and the Section 8C competitor snapshot findings.
COLLECTION BRIEF 1
| Element | Value |
|---|---|
| Collection name | [COLLECTION NAME — confirm in Shopify Admin] |
| URL | https://www.shopifystore1.co.uk/collections/[handle] |
| Shopify handle | /collections/[handle] — confirm optimal or flag suboptimal |
| Product count | [X products — confirm live count] |
| Primary Tier 1 keyword | [TARGET KEYWORD from Section 9.2] |
| Secondary keywords | [3–5 Tier 2 modifiers for this collection] |
| GSC current position | [From GSC Performance — average position for primary keyword] |
| GSC current impressions | [90-day impressions for primary keyword] |
| Competitor gap finding | [From Section 8C: “X of 5 competitors have Quick Answer block”] |
| Top competitor URL | [URL of page ranking #1 for primary keyword] |
| Top competitor word count | [Word count of #1 ranking page description] |
| Top competitor DR | [From Section 8C competitor table] |
| Realistic ranking timeline | [From Section 8C timeline assessment] |
Title tag (≤60 chars): Formula: [Primary Keyword] — [Signal] | shopifystore1 Draft: “[DRAFT TITLE — complete with actual keyword]” Character count: [X chars]
Meta description (140–155 chars): Formula: [Benefit + key spec] + [UK delivery or price signal] + [CTA with price anchor] Draft: “[DRAFT META — complete with actual copy]” Character count: [X chars]
H1 (= collection title in Shopify Admin → Collections → Title): Set Shopify collection title to: [Primary Keyword or SEO-optimised variant] Note: this changes the displayed storefront heading. Confirm it reads naturally in context of the store design before deploying.
Collection description — full copy brief:
Position: Below product grid ✅ / Above product grid (justify if education-first audience) Word count target: 400–500 words Description field in Shopify: Admin → Products → Collections → [collection] → Description (HTML editor)
QUICK ANSWER PARAGRAPH (80–120 words — before first H2 tag):
Write this paragraph to directly answer the question implied by the primary keyword. It must contain:
- The primary keyword used naturally — once, in the first or second sentence
- A price anchor (“from £[X]”)
- A UK delivery signal (“free UK delivery on orders over £[X]”)
- A trust signal (certification, review count, founding year, or specific expertise claim)
- A range signal (“X+ styles”, “available in UK sizes X–X”, “in X colourways”)
- Minimum 3 numbers in the paragraph
Example format (adapt to actual store): “[Collection name] at shopifystore1.co.uk [what they are + key material/attribute]. [Differentiating claim vs competitors]. Available in UK sizes [range] and [X] colourways, from £[price]. [Certification or trust signal]. Free UK delivery on orders over £[X] — returns accepted within [X] days under the Consumer Rights Act 2015.”
H2-1: [Question format — counterintuitive or differentiating claim]
Example H2 topic: “What makes our [product type] different from [common alternative]?”
- 100–150 words
- One counterintuitive claim or production/material detail that most competitors do not publish
- The Insight Rule: this section must contain something a buyer could not find on any top-5 competitor page
- Reference to 1 specific product in the collection with an inline anchor text link
Example content direction: if the collection is GOTS-certified knitwear, the counterintuitive claim is that GOTS certification covers the full supply chain (not just the final fabric) — which is what most “organic” labels miss. Name the specific certification standard, state the percentage of factories certified, and link to the certifying body’s public database. No competitor does this.
H2-2: [Material / specification / production detail]
- 100–150 words
- Full material composition for the products in this collection
- UK-specific care detail: “machine washable at 30°C” or “dry clean only — UK dry cleaners accepting [material] listed at [link]”
- Weight or warmth rating where applicable
- Country of origin statement (if publishable)
- Reference to 1–2 additional products with inline links
H2-3: [UK-specific buying context]
Options per collection type:
UK size guide reference with link to /pages/size-guide/
UK seasonal context: “ideal for [UK season/occasion]” with specific example
UK delivery and returns: specific delivery times, Consumer Rights Act 2015 return rights stated
UK certification relevance: why [certification] matters specifically to UK buyers
80–120 words
Must contain a UK-specific element not present on any competitor page (from Section 8C gap table)
Link to /pages/size-guide/ or /pages/delivery-and-returns/ as appropriate
H2-4: FAQ Block (3 questions — sourced from People Also Ask for primary keyword)
Sourced from Google PAA for [primary keyword] (from Section 9.1 Step 4):
Q: [PAA Question 1] A: [Answer — 2–4 sentences, specific and verifiable, includes primary keyword naturally]
Q: [PAA Question 2] A: [Answer — 2–4 sentences]
Q: [PAA Question 3] A: [Answer — 2–4 sentences, ends with soft CTA: “Browse our full [collection name] →”]
FAQPage schema for this block: deploy via collection.liquid or SEO app on this collection specifically. Each Q&A pair outputs as a Question/Answer pair in the FAQPage block.
Internal link plan for this collection:
| Link type | Target URL | Anchor text | Where in copy |
|---|---|---|---|
| Product inline #1 | /products/[handle] | [product name or key attribute] | H2-1 body |
| Product inline #2 | /products/[handle] | [product name or key attribute] | H2-2 body |
| Product inline #3 | /products/[handle] | [product name or key attribute] | H2-3 body |
| Related collection | /collections/[related-handle] | [natural anchor — e.g. “our full knitwear range”] | End of H2-3 or H2-4 |
| Blog post | /blogs/guides/[relevant-post] | [natural anchor] | H2-1 or H2-2 |
| Size guide | /pages/size-guide/ | “our UK size guide” | H2-3 |
Receives links from:
| Source page | Where to add the link | Anchor text |
|---|---|---|
| Homepage | Navigation menu + homepage featured collections section | [collection name] |
| Related collection description | End of related collection’s H2-4 | “[This collection name] →” |
| Hub page (/pages/collections-hub if it exists) | Hub page body | [collection name] |
| Blog post cluster (Section 12) | Body of relevant blog posts | “shop our [collection name]” |
Schema for this collection:
FAQPage schema: add to collection.liquid or via SEO app when H2-4 FAQ block is published. BreadcrumbList: confirm theme outputs this for collection pages — verify via Rich Results Test. CollectionPage or ItemList: optional — requires custom Liquid code but produces a richer SERP display.
Shopify implementation checklist:
- [ ] Collection title updated: Admin → Collections → [collection] → Title field
- [ ] Collection SEO title: Admin → [collection] → Search engine listing preview → Edit → Title
- [ ] Collection meta description: Admin → [collection] → Search engine listing preview → Edit → Description
- [ ] Collection description: Admin → [collection] → Description (HTML mode for H2 tags and links)
- [ ] FAQPage schema: deployed and validated at validator.schema.org — 0 errors
- [ ] Internal links: all 6 links confirmed live in published description
- [ ] “Receives links from” pages: all source pages updated to link to this collection
COLLECTION BRIEF 2
(Complete all fields as per Collection Brief 1 template — for the second-priority collection by revenue contribution or near-miss keyword opportunity)
| Element | Value |
|---|---|
| Collection name | [COLLECTION NAME] |
| URL | https://www.shopifystore1.co.uk/collections/[handle-2] |
| Primary Tier 1 keyword | [TARGET KEYWORD] |
| GSC current position | [X] |
| Competitor gap finding | [X of 5 competitors have Quick Answer block] |
Title tag: “[DRAFT — ≤60 chars]” Meta description: “[DRAFT — 140–155 chars]” H1: “[Primary keyword or variant]”
Collection description brief: (Follow the same H2-1 through H2-4 structure as Collection Brief 1 — all four H2 sections required. Unique content per section — do not replicate from Collection 1.)
COLLECTION BRIEF 3
(Complete all fields as per Collection Brief 1 template — for the third-priority collection)
| Element | Value |
|---|---|
| Collection name | [COLLECTION NAME] |
| URL | https://www.shopifystore1.co.uk/collections/[handle-3] |
| Primary Tier 1 keyword | [TARGET KEYWORD] |
| GSC current position | [X] |
| Competitor gap finding | [X of 5 competitors have Quick Answer block] |
Title tag: “[DRAFT — ≤60 chars]” Meta description: “[DRAFT — 140–155 chars]”
10.2 — Collection Page Content Standards (Confirmed for Stage 2)
These standards apply to every collection description produced in Stage 2. They supersede any previous drafts.
Word count floor: 350 words minimum for any collection with fewer than 8 products. 400–500 words for primary commercial collections. No collection description exceeds 600 words — beyond this, the description risks burying the product grid on mobile.
Keyword density: Primary keyword appears 2–3 times naturally across the full description. Secondary keywords appear once each. No paragraph stuffs the keyword — if a paragraph reads unnaturally, remove one instance.
Forbidden phrases (from Shopify SEO Master Prompt v1.0 Rule 4): Every collection description is checked against the full forbidden phrases list before publishing. The most common violations in collection copy are: “high quality”, “perfect for every occasion”, “we are passionate about”, “wide range of” (always specify the actual range), “seamless shopping experience”, “don’t miss out”, “shop now” as a generic CTA (replace with “Browse our [specific collection name]”).
The Insight Rule (Rule 2): Every H2 within a collection description must contain one counterintuitive claim, a Shopify-specific trade-off, a genuine material/production detail, or a UK-specific buying consideration that no top-5 competitor page contains. If a section is purely descriptive with no new information, it is cut — not padded.
E-E-A-T minimum per collection description:
- Named certification with certificate verification method
- Specific price anchor with “from £X” — not “affordable prices”
- UK delivery statement with specific timeframe
- Material composition stated with precise percentages (not “premium materials”)
- At least one claim only the brand can make — sourcing detail, production process, year of founding
10.3 — Collections Pending Stage 2 Optimisation (Priority Queue)
All collections not completed in the first Stage 2 sprint enter this priority queue for subsequent weeks.
| Collection | URL | Tier 1 Keyword | Current position | Priority | Target publish date |
|---|---|---|---|---|---|
| [Collection 4] | /collections/[h] | [KW] | [X] | Medium | Week 3 |
| [Collection 5] | /collections/[h] | [KW] | [X] | Medium | Week 4 |
| [Collection 6] | /collections/[h] | [KW] | [X] | Low | Week 5 |
| [Collection 7] | /collections/[h] | [KW] | [X] | Low | Week 6 |
Completion rule: Every collection page on the store must have an optimised description before Stage 3 begins. No collection should be left with a blank description or a single generic paragraph.
✅ CHECKPOINT — SECTION 10
- [ ] Collection briefs 1–3: fully written and published in Shopify Admin
- [ ] Title tags + meta descriptions: updated for all 3 priority collections
- [ ] H1s (collection titles): updated in Shopify Admin — confirmed correct on live storefront
- [ ] FAQPage schema: deployed and validated for all 3 priority collections — 0 errors at Rich Results Test
- [ ] Internal links: all 18 internal links (6 per collection) confirmed live in published descriptions
- [ ] Receiving pages: all source pages updated with links to the 3 priority collections
- [ ] Collections 4–7: brief dates assigned, copy in progress or scheduled
SECTION 11 — PRODUCT PAGE SEO BRIEFS
Products: Long-Tail Traffic, High Purchase Intent
Collection pages earn head-term traffic. Product pages earn long-tail transactional traffic — the queries where a buyer has already decided what they want and is searching for the specific item.
“Women’s wool coat UK” is a collection page query. “Navy blue merino wool wrap coat women UK size 14” is a product page query. The buyer typing the second query converts at 8–14% on a well-optimised product page. The collection page buyer converts at 2–4% because they are still browsing.
Product page SEO in Stage 2 does not attempt to write descriptions for all 200+ products in the catalogue. It writes detailed briefs for the Tier 1 priority products: the top 10 bestsellers by revenue and the top 10 near-miss products from Section 8B (closest to page 1 in GSC).
Pro Tip: The highest-ROI product page fix in Stage 2 is the title tag and meta description update — not the full description rewrite. A product at GSC position 14 with 800 impressions and 12 clicks has a 1.5% CTR. A rewritten title tag and meta description targeting the specific long-tail query typically moves CTR to 4–6% within 4–6 weeks. That is 3–4x more clicks from the same ranking position, with no change to the page content depth.
11.1 — Product Page SEO Brief — Standard Template
Complete one brief per Tier 1 priority product. Brief structure is identical across all products — the content changes per product.
PRODUCT BRIEF 1
| Element | Current | Recommended |
|---|---|---|
| Product name (displayed) | [CURRENT TITLE] | [Keep as-is or update] |
| SEO title tag | [CURRENT — usually = product title + | shopifystore1.co.uk] | [SEO-OPTIMISED — see formula below] |
| Meta description | [CURRENT — usually auto-generated] | [REWRITTEN — see formula below] |
| URL handle | /products/[handle] | [Confirm — flag suboptimal handles] |
| H1 (= product title) | [= product title in Shopify] | [Update product title if SEO benefit warrants it] |
| Primary keyword | — | [LONG-TAIL SPECIFIC KW — colour + material + type + gender + UK] |
| Parent collection | — | [/collections/[handle]] |
| Price | — | £[X.XX] |
| Review count | — | [X reviews — which app?] |
| In-stock variants | — | [List all active size/colour variants] |
| GSC position (if tracked) | — | [Position for primary keyword if available] |
Title tag formula (≤60 chars): [Colour] [Material] [Product Type] [Gender] UK | shopifystore1
Draft title tag: “[DRAFT — insert with actual product attributes]” Character count: [X chars — must be ≤60]
Title tag reasoning: The current title ([CURRENT TITLE]) targets [current intent]. The rewritten title targets “[SPECIFIC LONG-TAIL QUERY]” which has [XXX] monthly UK searches and [LOW/MEDIUM] keyword difficulty in Ahrefs. The colour and material modifiers are the key differentiators — buyers searching at this specificity level are ready to purchase.
Meta description (140–155 chars): Formula: [Key spec — material + attribute]. [UK size range]. [UK delivery + returns]. [Price CTA].
Draft meta: “[DRAFT — insert with actual product copy]” Character count: [X chars]
Product title update (if warranted): Current product title: “[CURRENT]” Recommended product title: “[RECOMMENDED — if the SEO benefit of updating the H1 outweighs the UX disruption]” Note: changing the product title changes the H1 on the product page AND the product name shown in the collection grid and cart. Confirm with the merchant that the updated name works in all contexts before deploying.
Product description brief:
Word count target: 300–450 words across all sections Structure: Quick Answer paragraph → Key Features (5–7 bullets) → Materials + Care → Fit + Use case → FAQ block (3 questions)
Quick Answer paragraph (first paragraph — 80–120 words): “The [Product Name] is a [material + key attribute] [product type] designed for [target buyer + primary use case]. [Key differentiator — the one claim that separates this product from its closest competitor]. Available in UK sizes [range] and [X] colourways, from £[price]. [Certification or provenance claim with verifiable detail]. Free UK delivery on orders over £[threshold] — [X]-day free returns under the Consumer Rights Act 2015.”
Numbers required: minimum 3 (price, UK size range, delivery threshold or returns period, or week production timeline if applicable).
Key Features section (5–7 bullet points — each must be specific and verifiable):
Each bullet follows this format: [Spec name]: [Value] — [why it matters to the buyer]
| Bullet # | Spec name | Value | Why it matters |
|---|---|---|---|
| 1 | Material composition | [e.g. 100% GOTS-certified merino wool] | [e.g. independently certified — certificate no. verifiable at global-standard.org] |
| 2 | Weight / warmth | [e.g. 180GSM / 4.5-tog equivalent] | [e.g. warm enough for UK autumn, not too heavy for centrally heated offices] |
| 3 | Care | [e.g. machine washable 30°C, cold rinse] | [e.g. no dry cleaning cost — extends garment life significantly] |
| 4 | UK size range | [e.g. UK 6–22] | [e.g. full UK size range — see our size guide for measurements in cm] |
| 5 | Country of manufacture | [e.g. Portugal] | [e.g. EU production — no import duty for UK buyers, 6–8 week lead time] |
| 6 | Certification | [e.g. GOTS certificate no. XXXX] | [e.g. verifiable directly at global-standard.org/public-db] |
| 7 | Fit type | [e.g. relaxed fit, slightly oversized] | [e.g. model is UK 10 and wears size 10 — true to size] |
Materials + Care section (50–80 words): State full material composition with percentages. State care instructions in plain English — decode the wash care symbols. Include: “Will it shrink? [Yes/No + how much and under what conditions].” Include: “Does it pill? [Yes/No + care tip to prevent].” These two questions are the most-searched product care queries for textile products — answering them in the product description captures the search intent AND reduces returns.
Fit + Use Case section (50–100 words): “The model is [height, e.g. 5’8″] and wears a UK size [X]. [Fit description — slim/regular/relaxed, any notable design features]. Recommended for: [3 specific occasions or use cases — be specific, not generic]. [One styling note that references another product in the collection with an inline link].”
FAQ Block (3 questions — from PAA for this product’s primary keyword):
Q: [PAA Question 1 specific to this product type and keyword] A: [Answer — 2–3 sentences, specific to this product. Mentions a verifiable fact.]
Q: [PAA Question 2] A: [Answer — 2–3 sentences]
Q: [PAA Question 3 — often about delivery, returns, or sizing] A: [Answer — 2–3 sentences. Ends with: “See our full delivery and returns policy at [link].”]
Image SEO brief for this product:
| Image | Current alt text | Recommended alt text | File name to use on upload |
|---|---|---|---|
| Main front image | [CURRENT] | [Colour] [material] [product name] [brand] — [brief context] | [colour]-[material]-[product-name]-shopifystore1.jpg |
| Back / side image | [CURRENT] | [Product name] [brand] — [angle/detail shown] | [product-name]-back-shopifystore1.jpg |
| Detail shot | [CURRENT] | [Specific detail — e.g. “merino wool rib texture detail”] on [product name] [brand] | [product-name]-detail-shopifystore1.jpg |
| Lifestyle image | [CURRENT] | [Product name] styled on model, UK size [X] shown — [brief context] | [product-name]-lifestyle-shopifystore1.jpg |
Internal link plan:
| Link | Target | Anchor text | Where |
|---|---|---|---|
| This product → parent collection | /collections/[handle] | “Browse our full [collection name] →” | Below FAQ block |
| This product → related product 1 | /products/[related-handle] | [related product name] | Fit + Use Case section |
| This product → size guide | /pages/size-guide/ | “our UK size guide” | Key Features bullet 4 |
| Parent collection → this product | /collections/[handle] description | [product name or key attribute] | H2-2 of collection description |
Schema note: Product schema is auto-generated by Dawn or the store’s theme. Confirm via Rich Results Test that:
- All required fields are present (name, image, price, currency, availability)
- aggregateRating is outputting (requires reviews app metafield integration — Section 8D app audit)
- BreadcrumbList outputs Home → Collection → Product If any field is missing: follow the schema deployment guide from Stage 1 Section 4.
Shopify implementation:
- SEO title tag: Admin → Products → [product] → Search engine listing preview → Edit → Title
- Meta description: Admin → Products → [product] → Search engine listing preview → Edit → Description
- Product title (H1): Admin → Products → [product] → Title field
- Description: Admin → Products → [product] → Description (HTML mode for section structure and inline links)
- Image alt text: Admin → Products → [product] → Media → click each image → Alt text field
PRODUCT BRIEF 2
(Complete all fields following the Product Brief 1 template — second-priority product by revenue or GSC near-miss ranking)
| Element | Current | Recommended |
|---|---|---|
| Product name | [CURRENT] | [UPDATED if warranted] |
| SEO title tag | [CURRENT] | “[DRAFT — ≤60 chars]” |
| Meta description | [CURRENT] | “[DRAFT — 140–155 chars]” |
| Primary keyword | — | [SPECIFIC LONG-TAIL KW] |
(All sections: Quick Answer paragraph, Key Features, Materials + Care, Fit + Use Case, FAQ block, Image SEO brief, Internal link plan — complete per template above)
PRODUCT BRIEFS 3–10
(Identical template applied to products 3 through 10. Priority order from Section 9.2 Tier 2 keyword table. Each brief is fully unique — no copy repeated between products.)
Product 3: [Product name] — primary keyword: [KW] Product 4: [Product name] — primary keyword: [KW] Product 5: [Product name] — primary keyword: [KW] Product 6: [Product name] — primary keyword: [KW] Product 7: [Product name] — primary keyword: [KW] Product 8: [Product name] — primary keyword: [KW] Product 9: [Product name] — primary keyword: [KW] Product 10: [Product name] — primary keyword: [KW]
11.2 — Shopify Variant SEO: Confirmed Rules
| Decision | Rule | Shopify implementation |
|---|---|---|
| Colour-only difference | Use variants on one product page | Colour picker on product page — all SEO on canonical /products/[handle] |
| Material difference | Separate products, separate URLs | Create separate product per material — do not use variants |
| Size difference (UK 6–22) | Use variants | Size selector on product page |
| Fit difference (slim vs relaxed) | Separate products if distinct search demand exists | Check Ahrefs: “slim [product]” and “relaxed [product]” — if both >100 vol/mo: separate products |
| Bundle vs single | Separate product | Bundles have distinct purchase intent — separate URL |
Variant URL SEO note: /products/[handle]?variant=XXXXXXXXXX is NOT indexed by Google. All ranking occurs on /products/[handle]. If the store’s most commercially important variant is a specific colour or material, ensure that variant’s attributes are prominently featured in the canonical URL’s title tag, meta description, and opening paragraph — not buried in the variant selector.
11.3 — Product Page Priority Queue for Stage 2
| Priority | Product | URL | Primary keyword | Brief status | Target date |
|---|---|---|---|---|---|
| 1 | [Top seller #1] | /products/[h] | [KW] | In progress | Week 1 |
| 2 | [Top seller #2] | /products/[h] | [KW] | Queued | Week 1 |
| 3 | [Top seller #3] | /products/[h] | [KW] | Queued | Week 2 |
| 4 | [Near-miss #1 from GSC] | /products/[h] | [KW] | Queued | Week 2 |
| 5 | [Near-miss #2 from GSC] | /products/[h] | [KW] | Queued | Week 3 |
| 6–10 | [Remaining products] | Queued | Weeks 3–4 |
✅ CHECKPOINT — SECTION 11
- [ ] Product briefs 1–10: all fully written — Quick Answer, Key Features, Materials, Fit, FAQ, Image SEO, Internal links
- [ ] SEO title tags: updated in Shopify Admin for all 10 priority products
- [ ] Meta descriptions: updated in Shopify Admin for all 10 priority products
- [ ] Image alt text: all images on 10 priority products updated
- [ ] Product descriptions: published in Shopify Admin for all 10 priority products
- [ ] Internal links: all outgoing links confirmed live within product descriptions
- [ ] Receiving links: parent collection descriptions updated to link to these products
- [ ] Schema: Product schema validated via Rich Results Test — all fields present
SECTION 12 — BLOG CONTENT ARCHITECTURE & BRIEFS
Blog Content: The Authority Infrastructure
A Shopify blog has one job in Stage 2: build topical authority around the collection keywords and funnel buyers into the product range.
A buyer at the top of the funnel searches “how to style a wool jumper for work UK.” A buyer at the bottom of the funnel searches “navy merino roll-neck jumper women UK size 12.” Blog content captures the top-of-funnel buyer and walks them toward the bottom.
Every blog post in Stage 2 is engineered for two outcomes: first, it ranks for an informational or commercial-investigation keyword. Second, it contains 2–3 specific product recommendations with direct links that convert informational visitors into buyers.
Pro Tip: The fastest way to earn a Featured Snippet or AI Overview citation from a Shopify blog post is the Quick Answer block structure — 80–120 words, in the first section before the first H2, answering the primary query directly with at least 3 specific data points. Google’s Featured Snippet extraction algorithm prioritises concise, directly-answering text blocks that appear early in the page. An AI Overview citation requires the same structure plus a named author with verifiable credentials and at least one primary source citation.
12.1 — Blog Architecture
Blog structure for shopifystore1.co.uk:
| Blog name | Shopify URL | Handle | Purpose | Schema type |
|---|---|---|---|---|
| Guides | /blogs/guides/ | guides | Long-form evergreen how-to and buying guides | Article |
| Style | /blogs/style/ | style | Outfit styling and trend content — social shareable | Article |
| [Brand story] | /blogs/[brand]/ | [brand] | Sustainability, certifications, founder story — E-E-A-T | Article |
Create each blog in: Shopify Admin → Online Store → Blog Posts → Manage Blogs → Add Blog.
Name the blog with the handle above — the handle determines the URL structure for all posts in that blog and cannot be changed after posts are published.
12.2 — Content Cluster 1 — Pillar + Supporting Posts
Cluster topic: [PRIMARY COLLECTION CATEGORY — e.g. wool knitwear / sustainable fashion / home textiles] Pillar keyword: [PILLAR KEYWORD — Tier 3 from Section 9.2] Target collection: /collections/[handle-1]
PILLAR POST BRIEF
| Element | Value |
|---|---|
| Blog | /blogs/guides/ |
| URL handle | /blogs/guides/[slug] — set BEFORE publishing (cannot change after) |
| H1 | [Question format — 50–60 chars — contains pillar keyword] |
| SEO title tag | [Can differ from H1 — ≤60 chars] |
| Meta description | [140–155 chars — answers the search intent + brand signal] |
| Primary keyword | [PILLAR KEYWORD] |
| Secondary keywords | [5–8 related terms from Section 9.2 Tier 3] |
| Search intent | Commercial investigation / Informational |
| Target word count | 2,000–2,500 words |
| Named author | [AUTHOR NAME] — [credentials: role + years experience + verifiable qualification] |
| Author page URL | /pages/[author-name] or /blogs/guides/authors/[name] |
| Target collection | /collections/[handle-1] |
| Target products | [2–3 specific products this post funnels to] |
| Publication date | [DATE] |
| Update schedule | Annually — or triggered by product range change |
H1 (question format): [Craft a question that contains the pillar keyword and matches buyer search language exactly] Example format: “How to [action related to product type]: [specific context UK] [2026]”
Quick Answer block (80–120 words — before H2-1): This block must:
- Answer the H1 question directly in the first sentence
- Include the primary keyword naturally — once
- Contain minimum 3 data points (numbers, specifications, percentages, price anchors)
- Include 1 specific product recommendation with an inline link
- Reference a verifiable source for any factual claim
Draft: “[Complete Quick Answer block — do not write ‘here is a quick answer.’ Write the actual answer paragraph.]”
H2 structure (question format — mirrors buyer search language):
H2-1: [Question that the primary keyword most directly implies] Content brief: [100–150 words addressing this question specifically] Insight Rule: [What counterintuitive claim or genuine trade-off does this section contain?] Product link: [Which product does this section reference? With what anchor text?]
H2-2: [Related question — deeper specification or secondary keyword] Content brief: [100–150 words] Insight Rule: [Material/technical detail most guides do not include] Product link: [Second product recommendation with inline link]
H2-3: [Use case or comparison question — UK-specific context] Content brief: [100–150 words] Insight Rule: [UK-specific consideration — sizing, occasion, climate, Consumer Rights Act] Product link: [Third product recommendation]
H2-4: [Practical guide element — how-to, care, or maintenance] Content brief: [100–150 words with specific steps or data] Source: [Named source for any factual claim in this section]
H2-5: [FAQ block — 3 PAA questions from target SERP]
Q: [PAA Question 1 — from Google PAA for pillar keyword] A: [Direct answer — 2–3 sentences — verifiable, specific]
Q: [PAA Question 2] A: [Direct answer]
Q: [PAA Question 3] A: [Direct answer — final sentence: “Browse our full [collection name] →”]
Product integration (conversion engineering):
| Integration point | Target product | URL | Anchor text | Section |
|---|---|---|---|---|
| Inline recommendation 1 | [Product name] | /products/[handle] | [natural anchor] | H2-1 body |
| Inline recommendation 2 | [Product name] | /products/[handle] | [natural anchor] | H2-2 body |
| Inline recommendation 3 | [Product name] | /products/[handle] | [natural anchor] | H2-3 body |
| End of post CTA | [Collection] | /collections/[handle] | “Shop our [collection name] →” | After H2-5 |
E-E-A-T signals required (minimum 4):
| Signal | Implementation |
|---|---|
| Named author + credentials | “[NAME], [Role], [Years experience]” — linked to author page |
| Named primary source | Citation to [certifying body / industry body / published research] with live URL |
| Verifiable brand claim | “[Brand-specific detail only shopifystore1.co.uk can state — production detail, specific certification number, founding story]” |
| UK-specific detail | “[UK standard or regulation referenced — e.g. UK Care Label Regulations / Consumer Rights Act 2015]” |
| Third-party validation | Press mention OR Trustpilot review count OR named industry membership |
Internal linking plan:
| Link type | Target | Anchor text |
|---|---|---|
| This post → pillar collection | /collections/[handle] | “shop our [collection name]” (3 times in body + once in CTA) |
| This post → Support Post 1 | /blogs/guides/[support-1-handle] | [natural anchor referencing that post’s topic] |
| This post → Support Post 2 | /blogs/guides/[support-2-handle] | [natural anchor] |
| This post → size guide | /pages/size-guide/ | “our UK size guide” |
| Support posts → this pillar | [all 3 support posts link back to pillar] | “our complete guide to [pillar topic]” |
Schema: Article schema: confirm article.liquid outputs for this blog. Fields: headline, image, datePublished, dateModified, author (Person with name + URL), publisher (Organization). FAQPage schema: deploy for H2-5 FAQ block — minimum 3 Q&A pairs.
SUPPORT POST BRIEF 1
| Element | Value |
|---|---|
| Blog | /blogs/guides/ |
| URL handle | /blogs/guides/[support-1-slug] |
| H1 | [Question — specific, long-tail — 50–60 chars] |
| Primary keyword | [SUPPORT KEYWORD 1 from Section 9.2 Tier 3] |
| Target word count | 1,200–1,800 words |
| Named author | [SAME AUTHOR or different named author with credentials] |
| Target collection | /collections/[handle] |
| Target product | [1–2 specific products] |
| Publication date | [DATE — ideally same week as pillar] |
H1: [Specific how-to or comparison question]
Quick Answer block (80–120 words): [Draft — answers the H1 directly, 3 data points, 1 product link]
H2 structure (3–4 H2s for support posts — not 5 like the pillar):
H2-1: [Direct answer expanded] H2-2: [Step-by-step or specification detail] H2-3: [UK-specific consideration or alternative] H2-4 (optional): [FAQ — 2–3 PAA questions for this specific keyword]
Links from this post:
- → Pillar post: [anchor text]
- → Target collection: [anchor text]
- → 1–2 product pages: [anchor text per product]
SUPPORT POST BRIEF 2
| Element | Value |
|---|---|
| Blog | /blogs/guides/ |
| URL handle | /blogs/guides/[support-2-slug] |
| H1 | [Question — different angle from Support Post 1] |
| Primary keyword | [SUPPORT KEYWORD 2] |
| Target word count | 1,200–1,800 words |
| Target collection | /collections/[handle] |
(Follow Support Post Brief 1 structure — all sections required)
SUPPORT POST BRIEF 3
| Element | Value |
|---|---|
| Blog | /blogs/style/ |
| URL handle | /blogs/style/[support-3-slug] |
| H1 | [Styling or outfit question — social shareable format] |
| Primary keyword | [STYLING/OCCASION KEYWORD from Section 9.2 Tier 3] |
| Target word count | 1,000–1,500 words |
| Target collection | /collections/[handle] |
(Follow Support Post Brief 1 structure — adapted for styling content: replace Material/Spec H2 with specific outfit suggestion H2s)
12.3 — Blog Content Production Standards
Author page requirement (non-negotiable for E-E-A-T): Every named blog author must have an author page live before their first post is published. An article schema pointing to an author page URL that returns a 404 is worse than no author schema at all.
Author page minimum URL options for Shopify:
- /pages/[author-name] — created in Shopify Admin → Online Store → Pages → Add Page
- /blogs/guides/tagged/[author-name] — Shopify auto-generates this via post tags
Author page minimum content: full name, role or expertise, specific credentials (years of experience + qualification or publication), list of published articles on the store, LinkedIn URL or other verifiable external profile.
Publication schedule: Pillar post and first two support posts should publish within the same 7-day window. This creates a topical cluster that Google’s crawlers can connect on re-indexing — rather than isolated posts published weeks apart.
Subsequent support posts: one per week for 2 more weeks. Total cluster 1 complete in 4 weeks.
Update schedule: Every blog post must have a published date AND a last-modified date in the Article schema. The dateModified should only be updated when genuine content changes are made — adding new product recommendations, updating statistics, or correcting information. Bumping the CMS date without content changes is a manipulation signal that Google ignores.
✅ CHECKPOINT — SECTION 12
- [ ] Blog structure: /blogs/guides, /blogs/style, /blogs/[brand] — all created in Shopify Admin
- [ ] Author pages: created for all named blog authors — URL confirmed live, Article schema sameAs updated
- [ ] Cluster 1 — Pillar post: published at correct URL handle, Article + FAQPage schema deployed
- [ ] Cluster 1 — Support Posts 1–3: all published, all linking to pillar and collection
- [ ] Internal link matrix: confirmed — every post links correctly, pillar receives links from all 3 support posts
- [ ] GSC: Request Indexing run on all 4 new posts immediately after publication
SECTION 13 — STAGE 2 KPI TARGETS & REPORTING
What to Measure in Visibility Stage
Stage 2 does not produce immediate organic revenue increases. It produces the structural conditions for revenue increases to appear in Months 4–6. The metrics that matter in Stage 2 are leading indicators — not lagging revenue outcomes.
The correct Stage 2 question is not “how much revenue did organic produce this month?” It is: “are our collection pages moving up in GSC? Are our blog posts earning impressions? Are title tag updates producing CTR improvements?”
Pro Tip: The clearest early signal that Stage 2 collection optimisation is working is an increase in impressions (not clicks) on collection page URLs in GSC. Impressions increase first as Google re-indexes updated pages and tests them in more SERPs. Clicks follow 2–4 weeks later as positions improve. If impressions are flat 4 weeks after publishing a collection description: the page has not been re-crawled — use GSC URL Inspection → Request Indexing to force it.
13.1 — Stage 2 KPI Dashboard
Record all values at the start of Stage 2 (from Section 8B baseline) and update monthly.
| KPI | Stage 1 Baseline | Month 4 Target | Month 6 Target | Source |
|---|---|---|---|---|
| Organic sessions / month | [Record from S8B] | +20–35% | +40–60% | GA4 |
| GSC impressions / month | [Record] | +50–80% | +100–150% | GSC |
| GSC clicks / month | [Record] | +30–50% | +70–100% | GSC |
| Average CTR across all pages | [Record] | +0.8–1.2pp | +1.5–2.5pp | GSC |
| Collection pages in top 10 (count) | [Record] | [+2–3 collections] | [All core collections top 10] | GSC / Semrush |
| Near-miss keywords moved to top 10 | 0 | 3–5 | 8–12 | GSC |
| Blog posts with impressions | 0 | 4 (all Stage 2 posts) | 8+ | GSC |
| Product pages in top 10 (count) | [Record] | [+3–5 products] | [+8–12 products] | GSC |
| Organic conversion rate | [Record] | Maintained | Maintained or +0.2pp | GA4 |
| Organic revenue / month | [Record] | Maintained | +20–30% | GA4 |
13.2 — Monthly Reporting Template (Stage 2)
Monthly report — Visibility stage — [Month X]
Traffic summary (GA4):
- Organic sessions this month vs last month: [+X%]
- Organic sessions vs Stage 1 baseline: [+X%]
- Top 3 organic landing pages by sessions: [list URLs + sessions]
- Collections earning most organic sessions: [list top 3]
- Blog posts earning most sessions: [list all new posts]
Visibility summary (GSC):
- Total impressions vs previous month: [+X%]
- Total clicks vs previous month: [+X%]
- Average CTR vs previous month: [+Xpp]
- Collections in top 10 this month: [list keywords + positions]
- Near-miss keywords moved to top 10 this month: [list — these are wins to report]
- Blog posts with new impressions: [list post URL + keyword + position]
Content output this month:
- Collection descriptions published: [count + collection names]
- Product descriptions updated: [count]
- Blog posts published: [list with primary keyword]
- Title tags updated: [count]
One insight from data (not from the plan): [The single most important finding from the data this month — what does it tell us about what to prioritise next month?]
Next month priorities (data-driven — not plan-driven):
- [Action — from data: what the data shows → specific action → expected metric outcome]
- [Action]
- [Action]
13.3 — Stage 2 to Stage 3 Handoff Criteria
Stage 3 (Authority) begins when these conditions are met — not on a fixed date.
| Condition | Status |
|---|---|
| All collection page descriptions: published and indexed | ✅ / ❌ |
| All Tier 1 priority products: title tags + meta descriptions updated | ✅ / ❌ |
| Cluster 1 blog content: all 4 posts published and indexed | ✅ / ❌ |
| FAQPage schema: deployed on all collection pages with FAQ blocks | ✅ / ❌ |
| GSC: collection pages showing impression improvements vs Stage 1 baseline | ✅ / ❌ |
| GA4: organic conversion rate maintained vs Stage 1 baseline | ✅ / ❌ |
If any condition is not met: Stage 2 work continues. Stage 3 starts when all six conditions are confirmed. Starting Stage 3 link building on a store that still has thin collection descriptions produces links to weak landing pages — the link equity is diluted by the page quality.
✅ CHECKPOINT — SECTION 13
- [ ] KPI dashboard: all Stage 1 baseline values recorded in tracking spreadsheet
- [ ] Month 4 targets: confirmed with store owner
- [ ] Month 6 targets: confirmed
- [ ] Monthly reporting template: set up in GA4 + GSC — first report due 30 days after Stage 2 content publication begins
- [ ] Stage 3 handoff criteria: all 6 conditions reviewed — date for next review set
CITATIONS :
1. Google. Title link best practices. Google Search Central, 2024. https://developers.google.com/search/docs/appearance/title-link Supports: Title tag character limits, formula recommendations, and product title impact on H1 throughout Sections 10 and 11.
2. Google. Write high quality content. Google Search Central, 2024. https://developers.google.com/search/docs/fundamentals/creating-helpful-content Supports: Quick Answer block standards, E-E-A-T requirements, and content quality rules throughout Sections 10, 11, and 12.
3. Google. FAQ structured data. Google Search Central, 2024. https://developers.google.com/search/docs/appearance/structured-data/faqpage Supports: FAQPage schema deployment requirements on collection and product pages throughout Sections 10 and 12.
4. Google. How Google search works. Google Search Central, 2024. https://developers.google.com/search/docs/fundamentals/how-search-works Supports: Featured Snippet extraction criteria — Quick Answer block structure in Section 12.
5. Google. Article structured data. Google Search Central, 2024. https://developers.google.com/search/docs/appearance/structured-data/article Supports: Article schema required fields (headline, image, datePublished, dateModified, author, publisher) throughout Section 12.
6. Shopify. Collection pages — add a description. Shopify Help Centre, 2024. https://help.shopify.com/en/manual/products/collections/collection-layout Supports: Collection description placement options (above/below product grid) and Shopify Admin implementation path in Section 10.
7. Shopify. Edit a product. Shopify Help Centre, 2024. https://help.shopify.com/en/manual/products/add-update-products Supports: Product description field, SEO title and meta description implementation path throughout Section 11.
8. Shopify. Blog posts in Shopify. Shopify Help Centre, 2024. https://help.shopify.com/en/manual/online-store/blogs/writing-blogs Supports: Blog structure, URL handle creation, and post publication workflow in Section 12.
9. Google. Search Quality Evaluator Guidelines. Google, 2024. https://static.googleusercontent.com/media/guidelines.raterhub.com/en//searchqualityevaluatorguidelines.pdf Supports: E-E-A-T framework requirements — author credentials, named sources, verifiable claims throughout Section 12.
10. UK Government. Consumer Rights Act 2015. Legislation.gov.uk, 2015 (amended 2024). https://www.legislation.gov.uk/ukpga/2015/15/contents Supports: Consumer Rights Act 2015 return rights referenced in collection descriptions and product FAQ blocks throughout Sections 10 and 11.
shopifystore1.co.uk — Shopify SEO Live Project Stage 2: Visibility Applied: Shopify SEO
