Cause & Effect Strategic Partners 01 / 20

Wanayi Camouflage
Live Site SEO Sprint

Eight days of work. Twenty checklist points gained. Here's what shipped, what's left, and what we're proposing for the next sprint — every proposal grounded in a concrete impact estimate and a brand-faithful path forward.

Prepared by Drake @ Cause & Effect · 2026-05-01 · For Luke + the Wanayi team
2026-05-01 02 / 20
Where we are

Live site jumped from 25 → 45 on the 100-point checklist.

All gains came from store-level Shopify edits — zero theme files touched, zero customer-facing copy changed. The lift carried over to every theme on the store.

2026-04-22 · 25
2026-04-30 · 45
+20
points gained
in 8 days
232
images affected
100% alt-text coverage
9
products restructured
vendor + product type
0
words changed
brand voice intact
What shipped — invisible to shoppers 03 / 20
This week's shipped work

Four store-level changes. All live now.

1 · Image alt text

60 / 60 nulls filled

Across sage-pants (26), the-mid-season-hoodie (19), sage-jacket (11), sage-long-sleeve-hoodie (4). Total store-wide coverage now 232/232.

+5 ptsGoogle Image Search eligible

2 · Vendor field

8 of 9 trimmed

"Wanayi Camouflage ""Wanayi Camouflage". Cleans Google Shopping feed + structured-data brand entity.

+5 pts

3 · Product type

9 of 9 classified

Hunting Jacket · Hunting Pants · Hunting Shirt · Hunting Hoodie · Hunting Hat (×2) · Hunting Beanie · Hunting Neck Gaiter · Hunting Knee Pads.

+5 ptsMerchant Center ready

4 · Blog SEO meta

/blogs/news fixed

Title and description metafields now set. Western-US-targeted: "Hunting Tips & Camo Pattern Guides."

+5 pts

Two settings clicks · ~1 minute 04 / 20
Luke's manual asks

Two clicks in Shopify Settings → +20 checklist points.

Both are one-line edits in Settings → General. Neither needs a developer. Both fix issues that propagate site-wide and across every theme.

+15 pts

1 · Trim the store name

Settings → General → Store name

"Wanayi Camouflage ""Wanayi Camouflage"

A trailing space in the store name is the root cause of every broken page title on the site. Once trimmed, all 9 product titles, FAQ, About, and homepage titles render cleanly. Also cleans og:site_name on social shares.

Anticipated objection
"Is changing this going to break anything?"
No. The current value already has a trailing space — Shopify treats trailing whitespace as part of the string, but no system on the store relies on the space. Removing it only resolves rendering bugs.
+5 pts

2 · Replace the store description

Settings → General → Store description

Current (53 chars — Google truncates short and pads with surrounding text):

American-Made camouflage apparel for the western U.S.

Suggested (148 chars — pick one on slide 12):

American-made hunting camouflage in proprietary Sage, Aspen, and Pinyon Pine patterns. Built for Western US hunters by a family-owned PA workshop.

Where it shows: only Google search results. Not on the website. Customers visiting wanayicamo.com see no change.

The biggest opportunity 05 / 20
Where the next 20 points live

Schema markup — invisible to shoppers, decisive to Google.

Schema is hidden code that tells Google exactly what each page is. Right now Wanayi has only Organization schema. Four types are missing — each one unlocks a different kind of rich result on Google.

What's there now

  • Organization (basic — brand only)
  • ProductGroup on PDPs (Shopify default)

2,605 words of FAQ content on /pages/faq → invisible to FAQ rich results.

PA workshop, real address, real hours → no LocalBusiness schema → no Google knowledge panel.

9 products with breadcrumb-able paths → no BreadcrumbList → no breadcrumb trail in SERPs.

What we're proposing (slides 6–9)

  • FAQPage schema on /pages/faq
  • LocalBusiness schema on home + Contact
  • BreadcrumbList schema sitewide
  • WebSite + SearchAction schema on home

Combined impact: +20 pts on the checklist.

Zero copy changes. All four are HTML markup additions in the theme template.

Schema · 1 of 4 06 / 20
FAQ schema · /pages/faq

Tag the existing FAQ. Don't change a word.

+5 pts

What we add

One JSON-LD block in the FAQ template that wraps the existing 2,605-word Q&A in FAQPage schema.

What it unlocks

  • FAQ accordion appears directly under the Wanayi listing in Google search results
  • Doubles the SERP real estate for branded queries
  • Eligible immediately — no waiting period

What the schema looks like (invisible to shoppers)

{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How do your camo patterns work?", "acceptedAnswer": { "@type": "Answer", "text": "[existing answer]" } }, ... ] }
Anticipated objection
"I don't want to change the FAQ wording."
We're not changing a single word. Schema is metadata about the existing content. The FAQ page renders identically to shoppers. Only Google reads the markup.
Schema · 2 of 4 07 / 20
LocalBusiness schema · home + Contact

Tell Google about the PA workshop.

+5 pts

What we add

JSON-LD block declaring Wanayi as a local business with address, phone, hours, and category.

What it unlocks

  • Google knowledge panel on branded searches (right side of SERP)
  • Hours, photos, directions surface natively
  • Feeds Google Business Profile signal-amplification

The fields it populates

{ "@type": "LocalBusiness", "name": "Wanayi Camouflage", "address": { "streetAddress": "216 Second Street", "addressLocality": "Monongahela", "addressRegion": "PA", "postalCode": "15063" }, "telephone": "+1-406-836-9186", "openingHours": "Mo-Fr 09:00-17:00", "priceRange": "$$" }
Anticipated objection
"I'm not really a local business — I sell nationally."
LocalBusiness schema for an e-comm site with a physical workshop is standard practice. It powers the branded knowledge panel, not Maps results for non-local searches. Big national brands with one HQ still use it.
Schema · 3 of 4 08 / 20
BreadcrumbList schema · sitewide

Show navigation paths to Google.

+5 pts

What we add

BreadcrumbList JSON-LD on every PDP and collection page. Visible breadcrumb component above each PDP title (small, can be styled in brand voice).

What it unlocks

  • "Wanayi > Outerwear > Mid Season Jacket" trail in SERPs instead of bare URL
  • Higher click-through rate (~10–15% lift, industry data)
  • Stronger internal linking signal

Visible component on each PDP

Home Outerwear The Mid Season Jacket
Anticipated objection
"I don't want extra elements cluttering the PDP."
Breadcrumbs are typically 14px small text in muted color above the product title. Major hunting brands (Sitka, First Lite, KUIU) all use them. They reduce bounce by giving shoppers a "back to category" anchor.
Schema · 4 of 4 09 / 20
WebSite + SearchAction schema · home

Get a search box inside Google's listing.

+5 pts

What we add

WebSite schema with a SearchAction that wires Google's sitelinks search box to wanayicamo.com's internal search.

What it unlocks

  • Google adds an in-SERP search box specific to Wanayi when someone searches the brand
  • Customers can type "jackets" and land on the collection directly from Google
  • Cuts a click from the funnel
{ "@type": "WebSite", "url": "https://wanayicamo.com/", "potentialAction": { "@type": "SearchAction", "target": "https://wanayicamo.com/search?q={query}", "query-input": "required name=query" } }

Wanayi already has built-in Shopify search at /search. This schema just tells Google about it.

Heading hierarchy fix 10 / 20
Home page · structural fix

Three H1s on home → exactly one. Pick the wording.

The home page currently has three H1 tags ("Wanayi Camouflage", "DAMN Good Camo", "Explore Camo Patterns"). Google reads multiple H1s as weak hierarchy. We'd promote one to H1 and demote the other two to H2.

Pick a primary H1 (or write one in the same voice):

A
American-Made Hunting Camouflage Built for Western Hunters
58 chars · keyword-balanced · neutral voice
B
Damn Good Camo. Made in America. Built for the West.
52 chars · brand voice forward · no SEO loss (kept "camo")
C
Wanayi Camouflage — Hunting Apparel That Disappears
52 chars · evokes the product benefit · brand-led
D
Proprietary Camo Patterns for Montana, Wyoming, Utah & Washington Hunters
75 chars · maximum geo-SEO punch
Anticipated objection
"All three should look equally important visually."
They can — visually identical. We change the HTML tag (h1 vs h2), not the CSS. Google sees a clean hierarchy; shoppers see no difference. The styling stays exactly the same.
SERP-only copy · pick one 11 / 20
Home page meta description · only shows in Google search results

Replace 53 characters with 140–150. Pick the voice.

A
"American-made hunting camouflage in proprietary Sage, Aspen, and Pinyon Pine patterns. Built for Western US hunters by a family-owned PA workshop."
148 chars · pattern-forward · family-owned trust signal
B
"Damn good camo built in Pennsylvania for hunters across Montana, Wyoming, Utah, and Washington. Proprietary patterns. Father-son family-owned."
147 chars · brand voice forward · geographic targeting
C
"Hunting camo engineered to disappear — Sage, Aspen, and Pinyon Pine patterns. American-made by a family workshop. Built for Western US hunters."
146 chars · benefit-led · evocative
Where this shows
"What does this change about the website?"
Nothing visible to shoppers on the website. The meta description is the gray text under the page title in Google search results. Visitors who hit wanayicamo.com see no change. Only people on Google deciding whether to click see it.
Homepage CRO · 1 of 4 12 / 20
From the 4/27 sprint plan

Reviews carousel below the hero.

Build

5–7 review cards in an autoscroll carousel below the homepage hero. Pulled from Shopify Reviews app, Etsy testimonials, social comments, or GBP reviews once seeded.

Why now

Hero → reviews → product is the canonical converting flow. Hunting apparel is a high-trust purchase ($150+ jackets) — social proof above the fold lifts add-to-cart rate ~8–15% on this category.

Source options (pick or stack)

  • Shopify Product Reviews app (already installed?)
  • Manual import from Etsy/Instagram comments
  • Pre-launch testimonials from beta hunters
  • GBP reviews once seeded (target 25+ from family/friends)
Anticipated objection
"We don't have many reviews yet."
The GBP push (slide 19) seeds 25+ reviews fast. Plus we can ingest existing Etsy and IG comments as testimonials. Even 4 hand-picked quotes is enough to start.
Homepage CRO · 2 of 4 13 / 20
From the 4/27 sprint plan

Reorder featured products. Lead with revenue.

Today's order

  • Hats first (lowest AOV)
  • Beanie / gaiter mid-stack
  • Jackets / pants buried

Hunters land on home, see hats, scroll past, leave.

Proposed order

  • Mid Season Jacket ($$$ flagship)
  • Early Season Pants ($$$ flagship)
  • Long Sleeve / Hoodie ($$)
  • Headwear (hat / beanie / gaiter)
  • Knee Pads + Accessories

Aligns with how a hunter shops: outer layer → mid layer → accessories.

Impact estimate
"Will this hurt the lower-AOV products?"
Per-customer revenue typically rises ~10% when high-AOV items lead. Hats become impulse adds in the cart, not the entry point.
PDP improvements · 3 of 4 14 / 20
From the 4/27 sprint plan

Three additions to every product page.

1 · FAQ dropdowns

5–7 product-specific Q&As in collapsible toggles below the buy box. Same FAQPage schema bake-in (slide 6).

CRO + Schema lift

2 · Sizing chart tab

Existing size chart relocated to a clean tab/modal. Reduces "what size am I" bounce — currently a top exit reason on hunting apparel.

CRO

3 · Shipping info tab

Free shipping threshold, delivery time, return policy in one place. Builds trust at the buy box.

CRO

Anticipated objection
"What goes in the FAQ — I don't want generic questions."
Drake drafts 7 specific questions per product (sizing for layering, sound when moving, wash care, fitment for saddle hunting, etc.) and Luke + dad approve / edit. No copy ships without your sign-off.
Contact page · 4 of 4 15 / 20
From the 4/27 sprint plan

Two trust signals on Contact.

1 · Founder photo (Luke + dad)

A real photo of the father-son team — workshop, field, or a clean portrait. Humanizes the brand instantly. The "American-made by a family" claim only lands when shoppers see faces.

Luke + dad provide the photo. Drake's team handles placement.

2 · Montana phone explanation

One sentence under the phone number explaining the (406) area code on a PA address.

"Our (406) line traces back to the Montana hunting roots of our founder — even though our workshop is in Monongahela, PA, the brand was forged in the West."

Or any version Luke prefers. We can talk this through together.

Homepage content block · for Luke + dad 16 / 20
Homepage About Us block

Between the hero and featured products. Luke + dad write this.

This is where the brand voice lives, so we're not drafting it for you. Below is the structure that performs best — fill in your words.

Recommended structure (80–120 words)

  • Origin sentence — who started it, where, when. (1 line)
  • Why proprietary patterns — what gap in the market drove it. (1–2 lines)
  • Made-in-America anchor — what that means for fabric, stitching, durability. (1 line)
  • Field promise — what hunters can expect when they wear it. (1 line)
  • CTA bridge — "see the patterns" or "shop the lineup" → links to /pages/our-camo
How we'll handle this together
"I want to write this myself."
That's the plan. Luke + dad draft 80–120 words in voice. Drake formats and pastes into the theme. We can review together before it ships.
Items for our next call 17 / 20
Things we'll work through together

Not proposing edits to these — flagging for discussion.

These all involve voice and brand judgment that should be a conversation, not a one-way proposal. Each is something we can calendar 30 minutes to settle.

Hero copy + CTA

Current hero text and button. Direct, product-led, brand-faithful. Discussion needed.

Product description rewrites

PDP body copy is currently a mix of older AI-assisted drafts. Rewrite in Luke's voice — discussion needed.

Slug rename

"the-mid-season-hoodie" lives at a URL that says "mid-season" but the product is "Early Season Hoodie." Auto-redirects when changed.

Body paragraphs site-wide

Smaller copy on About, Our Camo, FAQ. Where wording feels off — flag it, we rewrite together.

The path to 90/100 18 / 20
Score projection

From 45 today to 90+ in two more sprints.

NowLive = 45 / 100
45
+ Luke's 2 settings clicks→ 60 / 100
60
+ Schema sprint (slides 6–9)→ 80 / 100
80
+ H1 fix + meta + CRO→ 90+ / 100
90+

For reference: Sitka Gear, First Lite, and KUIU all score in the 88–95 range on the same checklist. 90+ puts Wanayi at competitive parity with the major hunting apparel brands — earned without changing the brand voice.

Parallel work · Drake handles 19 / 20
Google Business Profile · wave 1

Off-site authority play, no Wanayi work needed.

All seven of these get done by Drake's team this week. Visible to hunters searching "American-made hunting camo near me," "PA hunting apparel," and branded queries.

100+

photos uploaded — workshop, field, founder, product.

25+

reviews collected from family, friends, beta customers.

8+

secondary categories incl. "Hunting and fishing store."

8+

Q&As seeded via burner account — branded discovery.

3

special-hours seasons — PA archery 9/28, rifle 11/20, turkey 4/30.

1

family-owned attribute (NOT veteran-owned) + payment methods.

Plus: post-purchase email automation requesting reviews. Once running, GBP reviews backfill the homepage carousel (slide 12).

2026-05-01 · Wanayi · Cause & Effect 20 / 20
Decisions for tomorrow

What we need from Luke this week.

This week — minutes of work

  • Trim shop name in Settings (slide 4)
  • Replace store description in Settings (slide 4)
  • Pick H1 from options A / B / C / D (slide 10)
  • Pick meta description from A / B / C (slide 11)
  • Send 1 founder photo (slide 15)

Next 2 weeks — to discuss together

  • About Us block — Luke + dad draft (slide 16)
  • FAQ dropdown questions — Drake drafts, Luke approves (slide 14)
  • Hero copy + CTA call (slide 17)
  • Product description rewrites — work session (slide 17)

Drake's commits

  • Schema sprint authored and pushed (FAQ, LocalBusiness, BreadcrumbList, WebSite/SearchAction) — within 1 week of Luke's go-ahead
  • GBP wave 1 complete (slide 19) — within 5 business days
  • Reviews carousel + featured-product reorder — within 1 week
  • Score audit re-run after each push — Notion log per session

Questions? Drake @ Cause & Effect Strategic Partners · drakegriffith8@gmail.com · (770) 501-3959