SEO: what stops this store being found, and for what
Internal working notes, pulled 1 Sep 2026. Not the client deliverable. Second person and byline treatment happens at the report-writing stage.
Scope per the controller ruling on this task family: Task 1 (docs/audit/10-shopify.md) recorded catalogue state as raw fact (product status, inventory, whether an SEO field is populated or empty, handles, publish state, redirects). This task owns the SEO interpretation of those facts and does not restate them as new findings. Where this document builds directly on a Task 1 fact, that fact is cited by its finding ID (SHOP-nn) rather than re-quoted as evidence of a new problem.
What would falsify these findings
- **If Google Search Console's index coverage report (not pulled in this
task; the Search Analytics API used here does not expose indexation status) shows the flagship case product indexed despite the noindex meta tag, SEO-01 is wrong about the practical consequence**, though the tag itself and the sitemap exclusion would remain HARD facts either way. Google can sometimes index a noindex page it discovered before the tag was added; this pull cannot distinguish "never indexed" from "de-indexing in progress" without that report.
- **If Search Console's 9-impression, 0-click sample (SEO-02) grows
substantially on a later re-pull covering more of the property's crawl history, the "near-zero real organic visibility" framing needs revision toward "new property still populating," not dismissed as noise.** This property was verified 31 Aug 2026 and one crawl date (30 Aug) has propagated as of this pull; a wider crawl history was not yet available at pull time. Re-pull before repeating this claim in any client-facing document written after today.
- **If a later, more thorough crawl finds problem-aware blog content, guest
posts, or forum threads for this brand that simply did not surface in the organic pulls and live AI-search test run here, SEO-07 (the solution- aware/problem-aware framing) overstates the content gap.** The same caveat Task 7 recorded for COMP-01/02 applies here; this task's own live AI-assistant test (see data/_snapshots/2026-09-01/seo-geo/ai-citation-test-results.md) is additional, not conclusive, evidence in the same direction.
- **If the PageSpeed Insights daily quota resets and a follow-up pull
produces real LCP/CLS/INP numbers, those numbers should replace the proxy timing data in this document's Core Web Vitals section entirely**, not sit alongside it. See that section for the exact tooling failure.
- **If Nuuk's Stage 1 has since shipped the multi-SKU conversion its June
audit recommends, SEO-07's "per-design SEO opportunity" framing (which that conversion would partially address) needs revision. Check Task 1's Stage 1 status check first, which as of 1 Sep 2026 found none of Stage 1's SOW-scoped deliverables shipped.**
Findings
ID format SEO-nn. Class: BLOCKS / CORRUPTS / WASTES / SUPPRESSES. Tier: HARD (pulled from a system, dated) / DERIVED (arithmetic or direct inference on HARD values) / INFERRED (reasoned from HARD facts, not measured) / UNKNOWN.
| ID | Finding | Evidence | Class | Tier | PRIOR-ART |
|---|---|---|---|---|---|
| SEO-01 | The flagship $59.99 case product page (/products/string-pro-tech®) carries <meta name="robots" content="noindex,nofollow"> and is absent from sitemap.xml's products feed, while the other two live products are present in both. This is Shopify's documented, automatic behavior for a product in UNLISTED status (Task 1, SHOP-03): the platform adds the noindex tag and strips the product from the sitemap the moment a product is set to Unlisted. The product resolves 200 OK on direct link (Task 1, SHOP-05) and gets real direct/paid traffic (GA4: 102 sessions to this URL, 90 days, 2026-06-03 to 2026-08-31), but has zero path to new organic discovery while it stays UNLISTED. | Meta tag and sitemap pull, 1 Sep 2026, data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md and sitemap-products.xml; Shopify's documented behavior confirmed via web search, 1 Sep 2026 (Shopify Help Center, "Hiding a page from search engines"; shopify.dev, "Unlisted product status") | BLOCKS | HARD | No |
| SEO-02 | Search Console now returns data (re-pulled 1 Sep 2026, one day earlier than the 4 Sep recheck estimated in the brief): 0 clicks and 9 total impressions across the full 2026-06-02 to 2026-08-31 window, concentrated on a single crawl date (30 Aug 2026). Of the four queries recorded, two are off-topic ("protech stringing service," position 91.0; "string micro rock," position 58.0) and two are on-topic but at negligible volume (1 impression each: "string cover guitar" position 7.0, "string protector" position 5.0). The property is no longer empty, and the underlying finding is now HARD rather than an artifact of the property being new: real organic search visibility for this domain is close to zero. | npm run query:gsc, re-run 1 Sep 2026, data/_snapshots/2026-09-01/gsc-recheck.txt | SUPPRESSES | HARD | No |
| SEO-03 | /pt returns 404 and, per GA4, still receives real traffic (established fact: 108 sessions, 90 days to 2026-08-31, so 2026-06-03 to 2026-08-31, 27 of them organic search) that lands on a dead end rather than the correct English-language product page. Task 1's SHOP-06 already established the mechanism (two urlRedirects exist, coverage is partial, one points to the homepage instead of the matching product). The SEO-specific consequence: this is scarce organic traffic (SEO-02, above) arriving at a page that cannot convert and cannot pass any residual authority forward, on a channel this store cannot currently afford to waste. The 9-impression GSC sample pulled for SEO-02 contains no /pt-related query or page, which is too small a sample to conclude anything about /pt's indexation status either way; recorded for completeness only. | GA4 established fact (docs/status.md); Task 1, SHOP-06; GSC recheck 1 Sep 2026, data/_snapshots/2026-09-01/gsc-recheck.txt | SUPPRESSES | DERIVED | Yes. PA-5/SHOP-06 (the /pt topic and its redirect gap are Nuuk's and Task 1's, respectively). Excluded from client-facing use at the topic level; recorded here only to answer the brief's Step 3 directly. |
| SEO-04 | All four products carry an empty SEO-title admin field (Task 1, raw fact). The rendered consequence, confirmed by crawling the live pages: Shopify falls back to an automatic {Product Title} – String ProTech <title> tag. This is not a blank title (a common but wrong assumption from the empty admin field alone) but it is generic, keyword-thin, and near-duplicate across the catalog (differs only by product name), missing the buyer-language terms this store does rank marginally for ("guitar string protector," "guitar string case," per Task 7 COMP-02). | Live crawl, 1 Sep 2026, data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md; empty field confirmed in Task 1's catalogue pull | WASTES | DERIVED | No |
| SEO-05 | /pages/about has zero <h1> elements anywhere in its HTML (checked case-insensitively against the full page). Every other page pulled in this crawl has exactly one. A page with real, unique brand-story content (Origin, patent, lab-test detail) and no top-level heading is both a weaker on-page signal for search engines and a worse landmark for screen readers/AI extraction. | Live crawl, 1 Sep 2026, data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md | CORRUPTS | HARD | No |
| SEO-06 | Product-level Review/AggregateRating structured data (Judge.me output) is present on the combo product (guitar-string-protection-case-and-custom-vinyl-sticker, the highest-traffic landing page in GA4 at 1,113 sessions, 90 days, 2026-06-03 to 2026-08-31) but absent from the flagship case product page. A search engine reading the flagship page's JSON-LD has no rich-result-eligible review signal for it at all, on top of that page already being excluded from indexing (SEO-01). | Live crawl, 1 Sep 2026, data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md | SUPPRESSES | HARD | No |
| SEO-07 | The site's SEO surface (page copy, titles, the only queries it ranks for at all) targets solution-aware search exclusively, and ranks weakly even there, while zero on-site content exists for the problem-aware queries that would introduce a buyer to this category in the first place. Task 7 found String ProTech absent from both problem-aware queries tested ("how to protect guitar strings," "keep guitar strings from rusting") and ranked 5th of 9 / 7th of 8 on the two solution-aware queries where it does appear. This task re-checked one problem-aware query against a second live index (Brave Search) and two additional problem-aware queries via a live AI-assistant search: absent from all three (see the solution-aware/problem-aware section below). No blog post, FAQ, or guide answering "why do guitar strings rust," "how often should I change guitar strings," or any adjacent problem-aware question exists anywhere on stringprotech.com (sitemap_blogs_1.xml's content was checked; /blogs/news renders but no problem-aware article was found in this pull). Paid and organic effort both point at people already searching for a case, a small and currently uncontested-but-unfound audience, while ceding the much larger population still searching for the underlying problem to competitors and to zero-cost DIY answers. | Task 7, docs/audit/70-competitive.md, COMP-01/COMP-02; this task's cross-check, 1 Sep 2026, data/_snapshots/2026-09-01/seo-geo/ai-citation-test-results.md; blog index crawl, data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md | WASTES | INFERRED | No |
| SEO-08 | Task 1's raw catalogue pull recorded the admin "Featured image alt text" field as empty for all four products (docs/audit/10-shopify.md, raw appendix table). Crawling the rendered page shows the practical, page-wide consequence is worse and different in shape than that single field implies. Flagship case page: 41 <img> tags, 0 missing the alt attribute, 21 carrying a completely empty alt="" on genuine product photography, not decorative icons, confirmed by their source filenames (String_Protech_4.png, CASE06.521.png, several literal unprocessed WhatsApp-export filenames, ten sequentially numbered gallery photos). Of the 20 populated alt values, 18 repeat the exact same string, the bare product title, with zero differentiation between images; the remaining 2 are the header logo's alt and one genuinely specific "Lab flask" alt. Combo page (the store's highest-traffic landing page): 56 images, 5 with no alt attribute at all, 14 empty, 37 populated, of which 35 repeat the bare product title, 1 is the logo, and 1 is a genuinely specific "Jeremy Launais review photo" alt on a customer review image. Sticker page: 22 images, 0 missing, 8 empty, 14 populated, of which 12 repeat the bare product title, 1 is the logo, 1 is "Lab flask." Across all three product pages, the large majority of populated alt text is the same duplicated product-title string carrying zero descriptive value, and the outright-empty share (half or more of every product page's images) sits on real photography, not decoration. | Live crawl, 1 Sep 2026, parsed image-by-image from raw HTML saved verbatim in data/_snapshots/2026-09-01/seo-geo/raw-html/; full per-page counts and file-by-file detail in data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md | SUPPRESSES | HARD | No |
Solution-aware versus problem-aware: which one this store should target
This is the most commercially useful question this task can answer, and the evidence points one direction consistently across every source available.
A buyer can enter this purchase decision at two different points. Solution- aware: they already know "guitar string protector" or "guitar string case" is a product category and are comparing options. Problem-aware: they only know their strings keep rusting, dying, or losing tone, and have not yet connected that problem to a purchasable product category at all. Most have not: the category is small enough that the language itself, "guitar string protection case," is not standard usage the way "guitar case" or "capo" is.
Every piece of evidence gathered across Task 7 and this task points the same way: there is close to no search volume in the solution-aware language this store's own pages and title tags are built around, and real, recurring, independent search volume in the problem-aware language the store has built nothing for.
- Task 7's organic-result pull (1 Sep 2026) found String ProTech absent
from both problem-aware queries tested and weakly ranked (5th/9, 7th/8) on the two solution-aware queries where it appears at all, ranked below general instrument-case retailers and an Etsy listing on one of them.
- This task's own re-check, via a live AI assistant actually queried today
(not a proxy), confirms the same pattern on three more queries: absent entirely on "why do guitar strings rust so fast" and "how often should I change guitar strings" (both problem-aware), and present but ranked 6th of 7 sources, behind a competitor's own category-priority claim, on "best guitar string protector case" (solution-aware).
- The independent content that already ranks on every problem-aware query
tested across both tasks (six sources: My New Microphone, GuitarNick, Rock Guitar Universe, Stamp Sound, Medium, Strings By Mail, plus five more found in this task's fresh pull: Quora, Range of Sounds, Ultimate Guitar, MusiciansHQ, BassGuitarJam, GuitarImp) teaches free or near-free fixes and does not mention a dedicated protection case as an expected purchase (Task 7, COMP-03).
- SEO-02 (this task) confirms the store's own organic footprint is close
to zero even for the solution-aware terms it does target: 9 impressions, 0 clicks, three months, one crawl date.
What this means in practice. Building more SEO content around "guitar string protector" or "guitar string case" language competes for a tiny, largely uncontested pool of searchers who mostly aren't looking to buy a $59.99 dedicated case (Task 7's category-demand section). Building content that answers the problem-aware questions (why strings rust, how often to change them, what actually works) puts the store in front of a real, recurring, currently-uncaptured search population, at the cost of having to do genuine category-creation work rather than capture existing intent: teaching a reader the problem is worth $59.99 to solve when every other page they find on that exact question tells them it's worth $0 to $17 (Task 7, COMP-03/COMP-04). Neither path is free. The problem-aware path is the one with actual traffic behind it; the solution-aware path, where this store's current title tags, meta descriptions, and the only GSC impressions it has all point, is not.
No revenue projection is offered here, consistent with this engagement's constraints; this section states a targeting direction, not a demand size.
Core Web Vitals: not measured, tooling limitation
PageSpeed Insights returned a daily-quota 429 on every call for both the homepage and the flagship product page, mobile strategy, and did not recover on retry. LCP, CLS, and INP are UNKNOWN tier for this pull, not soft-pedaled into a finding with invented numbers. Full detail, including the honestly-labeled proxy data that was captured instead (server TTFB, page weight, script/stylesheet counts) is in data/_snapshots/2026-09-01/seo-geo/cwv-notes.md. Summary: server time-to-first-byte is fast (~0.3-0.5s median on both pages tested), which is not itself a Core Web Vitals number and is not presented as one.
Cross-check against Nuuk's June 2026 audit
Nuuk's 22-page audit and 13-page SOW were grepped and read in full for robots.txt, llms.txt, noindex, structured data/schema.org, Search Console, Core Web Vitals, and any AI/answer-engine language: zero matches on every term. The only SEO-shaped topic Nuuk's audit touches at all is the single-SKU-to-multi-SKU architecture and its downstream "SEO opportunities per artist/band/album" (Task 1's PA-1/PA-16), which is a distinct claim from every finding in this document and is not restated here. SEO-03 is the one finding in this document that overlaps a Nuuk/Task-1 topic (/pt) and is marked PRIOR-ART accordingly.
Raw evidence appendix
Full crawl extracts (titles, meta descriptions, canonicals, robots meta, JSON-LD schema types, per-page patent/lab-claim text) are in data/_snapshots/2026-09-01/seo-geo/page-crawl-findings.md. Robots.txt, sitemap index, products sitemap, llms.txt, and agents.md are saved verbatim in the same directory. The Search Console recheck raw output is in data/_snapshots/2026-09-01/gsc-recheck.txt; the AI-citation live test transcript (queries, full answers, sources) is in data/_snapshots/2026-09-01/seo-geo/ai-citation-test-results.md; the Core Web Vitals tooling-failure detail and proxy timing data is in data/_snapshots/2026-09-01/seo-geo/cwv-notes.md.