Selected task: 1 — BUYER-INTENT KEYWORD MAP **Primary task:** Buyer-intent keyword mapping **Supporting tasks:** None **Artifact status:** Provisional. The four customer-language phrases were supplied, but the actual 90-day search-term rows and module-level product contents were not. ## 1. SUPPLIED FACTS * The fictional shop sells **printable bilingual wedding-planning spreadsheets in English and Spanish**. * A set of **46 customer messages** commonly uses these phrases: * `wedding budget spreadsheet` * `bilingual wedding planner` * `guest list template` * `wedding checklist in Spanish` * An Etsy search-term export exists for the last 90 days and contains: * Exact query * Impressions * Visits * Orders * The actual export rows and values were not supplied. * The product includes: * XLSX * Google Sheets instructions * The product is **not a mobile app**. * No external keyword-volume or competition data was supplied. ## 2. DERIVATIONS These are interpretations of the supplied evidence, not Etsy ranking claims. 1. The customer language covers four distinguishable purchase needs: * Budget management * Bilingual wedding planning * Guest-list management * Spanish-language checklist use 2. `bilingual wedding planner` is the closest supplied phrase to the confirmed overall product category, but the word **planner** could imply a broader package than the spreadsheet actually contains. 3. The other three supplied phrases cannot be treated as confirmed product-fit keywords until the owner verifies that this specific product includes: * A wedding-budget module * A guest-list module * A wedding-checklist module 4. The 46-message set provides direct qualitative buyer-language evidence, but it does not establish: * How often each phrase occurred * Which phrase generated the most interest * Which phrase generated orders * Search volume or competition 5. Impressions alone would indicate observed exposure, not purchase quality. The supplied export can support three useful calculations once its rows are provided: [ \text{Visit rate}=\frac{\text{Visits}}{\text{Impressions}} ] [ \text{Order rate from visits}=\frac{\text{Orders}}{\text{Visits}} ] [ \text{Order yield}=\frac{\text{Orders}}{\text{Impressions}} ] These calculations should not be interpreted when the denominator is zero and should be treated cautiously when the number of observations is small. ## 3. ASSUMPTIONS No assumption is required to build the initial map. The following possibilities are deliberately **not** being treated as facts: * That all 46 messages used all four phrases * That the product includes budget, guest-list, and checklist modules * That the XLSX file is natively hosted in Google Sheets * That “printable” means every worksheet is formatted for clean printing * That any phrase has high Etsy search volume * That any proposed placement will improve ranking or sales ## 4. NEEDED EVIDENCE | Evidence needed | Why it matters | How the owner should verify it | | ---------------------------------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Actual 90-day search-term export rows | Required to compare exact-query impressions, visits, and orders | Export or paste the unedited Etsy search-term table | | Phrase counts within the 46 customer messages | Establishes relative prominence in direct customer language | Code each message by phrase and count unique messages, not repeated mentions | | Exact workbook contents | Determines whether budget, guest-list, and checklist phrases are truthful | Mark every included sheet, tab, feature, and language | | Print readiness | Prevents an unsupported interpretation of “printable” | Print-test or export each relevant sheet to PDF | | Google Sheets delivery method | Distinguishes a native template from instructions for importing XLSX | Document the actual customer workflow | | Current title, description, tags, and listing images | Needed to identify duplication and existing placement | Copy the live listing exactly | | Shop-wide keyword matrix | Needed to evaluate cross-listing collision | List the primary purpose and target phrase of every similar listing | | Current Etsy title and tag restrictions | Required before final title or tag implementation | **NEEDED FOR OWNER VERIFICATION** in the current Etsy listing editor and official Etsy seller documentation | | Current brand-use requirements for “Google Sheets” | Third-party brand use should be factual and non-affiliative | **NEEDED FOR OWNER VERIFICATION** through current Google brand guidance and qualified review where necessary | --- # 5. BUYER-INTENT MAP ## Intent architecture | Intent cluster | Supplied buyer language | Implied purchase job | Specificity | Confirmed product match | | -------------------------- | ----------------------------------- | ------------------------------------------------------ | -------------------: | -------------------------------------------------------------------------------------------- | | Bilingual overall planning | `bilingual wedding planner` | Organize wedding planning in English and Spanish | Broad | Partially confirmed: bilingual wedding-planning spreadsheet is supplied | | Budget planning | `wedding budget spreadsheet` | Track or organize wedding finances | Specific | Spreadsheet format confirmed; budget functionality not confirmed | | Guest management | `guest list template` | Organize invitees or guest information | Specific | Template-like spreadsheet format is plausible, but guest-list functionality is not confirmed | | Spanish checklist | `wedding checklist in Spanish` | Follow wedding tasks using Spanish-language content | Specific | Spanish language confirmed; checklist functionality not confirmed | | File/access format | XLSX and Google Sheets instructions | Open or use the product through a spreadsheet workflow | Technical | Confirmed as supplied, subject to clarifying the Google Sheets workflow | | Format exclusion | Not a mobile app | Avoid an incorrect software expectation | Objection-prevention | Confirmed | ## Provisional hierarchy A defensible final priority cannot be assigned until the search-term metrics and product contents are supplied. The provisional hierarchy is: 1. **Closest confirmed category match:** `bilingual wedding planner` 2. **Potential high-specificity use case:** `wedding budget spreadsheet`, subject to budget-module confirmation 3. **Potential high-specificity use case:** `guest list template`, subject to guest-list confirmation 4. **Language-plus-task use case:** `wedding checklist in Spanish`, subject to checklist confirmation This hierarchy reflects product-message fit only. It does not represent Etsy demand, competition, or ranking potential. --- # 6. EVIDENCE TABLE | Phrase | Evidence source | Evidence strength | Buyer intent | Confirmed fit | Missing proof | Provisional placement | Collision or mismatch risk | | ------------------------------ | ------------------------------------------------------------------------ | ----------------------------------------------------------------------- | --------------------------------- | ------------------------------------------------------ | -------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | `wedding budget spreadsheet` | Language observed among the 46 customer messages | Direct qualitative evidence; phrase count and search metrics absent | Budget tracking or planning | Spreadsheet format only | A budget sheet and its actual functions | Title support phrase, feature heading, description, or keyword field only after module confirmation | Could promise budget functionality that is not included | | `bilingual wedding planner` | Language observed among the 46 customer messages; bilingual product fact | Strongest direct match to the confirmed overall offer, but unquantified | Broad bilingual planning solution | Bilingual English/Spanish wedding-planning spreadsheet | Breadth and contents of the “planner” | Candidate primary phrase in the title opening and first description line | “Planner” may imply a complete planning system rather than a narrower spreadsheet | | `guest list template` | Language observed among the 46 customer messages | Direct qualitative evidence; phrase count and search metrics absent | Guest organization | Spreadsheet/template format only | Guest-list sheet and included fields | Feature heading, description, or keyword field after confirmation | Could attract buyers seeking a standalone guest-list product | | `wedding checklist in Spanish` | Language observed among the 46 customer messages; Spanish product fact | Direct language-plus-task evidence, but unquantified | Spanish-language task management | Spanish language only | Checklist existence, scope, and editability | Feature heading, description, or keyword field after confirmation | Could imply Spanish-only content rather than bilingual content | | `XLSX` | Supplied file fact | Direct product evidence | File-format compatibility | Confirmed | Supported software versions and device limitations | Specifications or file-information section | Technical term may not reflect buyer language | | `Google Sheets instructions` | Supplied product fact | Direct product evidence | Access or import guidance | Instructions confirmed | Whether a native Google Sheets copy is included | Compatibility section and FAQ | “Google Sheets template” could overstate what is delivered | | `not a mobile app` | Supplied exclusion | Direct product evidence | Expectation management | Confirmed | None for the basic statement | File-information section and FAQ | Targeting “app” queries could attract mismatched traffic | ## Search-export evidence worksheet No values are inserted because the export was not supplied. | Exact query | Impressions | Visits | Orders | Visit rate | Order rate | Order yield | Intent cluster | Exact product fit? | Action | | ------------ | ----------: | -----: | -----: | ---------: | ---------: | ----------: | -------------- | ------------------ | ------------ | | NOT SUPPLIED | — | — | — | — | — | — | — | — | Await export | Recommended formulas: ```text Visit rate = Visits / Impressions Order rate = Orders / Visits Order yield = Orders / Impressions ``` Recommended selection order for a primary phrase: 1. Truthful match to the exact product 2. Evidence of orders from the exact query 3. Evidence of visits relative to impressions 4. Impressions as a secondary reach indicator 5. Readability and consistency with customer language This sequence is an analytical recommendation, not a claim about Etsy’s current ranking system. --- # 7. PLACEMENT RECOMMENDATIONS ## A. Title opening Use one primary phrase that accurately represents the entire product. Based only on confirmed facts, `bilingual wedding planner` is the strongest provisional candidate. Before implementation: * Verify that “planner” does not exaggerate the workbook’s scope. * Compare it against the actual order-producing search queries. * Verify the current title limit and other applicable Etsy requirements. Do not place all four supplied phrases into the title merely because they were observed. That would introduce repetition and potentially combine unsupported functions. ## B. Remaining title space Use at most one or two meaningfully different supporting intents, selected from the search export and confirmed product contents. Possible roles: * Primary category: bilingual planning * Secondary function: budget, guest list, or checklist * Format clarification: spreadsheet A feature phrase should be excluded when that feature is not present. ## C. First description paragraph A fact-grounded opening can communicate the confirmed format and language without making unsupported feature claims: > Printable bilingual wedding-planning spreadsheet in English and Spanish. Includes an XLSX file and instructions for using Google Sheets. This product is not a mobile app. The final wording should be adjusted when the owner confirms exactly how the Google Sheets workflow functions. ## D. Feature headings Use buyer-language headings only for included modules: * `Wedding budget spreadsheet` — only if a budget module exists * `Guest list template` — only if a guest-list module exists * `Wedding checklist in Spanish` — only if a Spanish checklist exists Under each heading, state the exact fields or functions rather than repeating the keyword without proof. ## E. File and compatibility section Clearly distinguish: * What file is delivered * Whether the customer receives an XLSX file * Whether Google Sheets is accessed through import instructions or a native copy * Whether printing has been tested * That the product is not a mobile app ## F. Keyword or tag fields Use nonredundant phrases representing different purchase jobs rather than minor word-order variations. Final tag count, character limits, and implementation compliance are **NEEDED FOR OWNER VERIFICATION**. No recommendation here assumes a current Etsy tag rule. ## G. FAQ or expectation-management section Recommended factual question: **Is this a mobile wedding-planning app?** Answer: > No. This is a spreadsheet product and not a mobile app. Any device-compatibility statements beyond that require verified testing. --- # 8. TEN TESTABLE KEYWORD HYPOTHESES Every phrase below is a **HYPOTHESIS**. No search volume, competition level, or ranking potential is claimed. | # | Keyword hypothesis | Intended buyer need | Basis for hypothesis | Required product confirmation | Collision or claim risk | Initial test location | | -: | ----------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------- | --------------------------------------------- | | 1 | `bilingual wedding planning spreadsheet` | Broad bilingual spreadsheet solution | Combines confirmed bilingual, wedding-planning, and spreadsheet facts | Verify overall workbook scope | Low relative risk if scope is accurate | Candidate title phrase or description opening | | 2 | `English Spanish wedding planner` | Explicit two-language planning | Combines supplied languages with customer phrase `bilingual wedding planner` | Verify “planner” breadth | May imply a comprehensive planner | Description or keyword field | | 3 | `bilingual wedding budget spreadsheet` | Budget planning in both languages | Combines two supplied customer phrases | Confirm bilingual budget module | High risk if no budget sheet exists | Feature heading or keyword field | | 4 | `Spanish wedding budget spreadsheet` | Spanish-language budget organization | Combines Spanish language with supplied budget phrase | Confirm Spanish budget module | Could imply Spanish-only delivery | Description or keyword field | | 5 | `bilingual guest list template` | Guest organization in both languages | Combines bilingual product fact with supplied guest-list phrase | Confirm bilingual guest-list module | Could attract standalone-template buyers | Feature heading or keyword field | | 6 | `Spanish guest list spreadsheet` | Spreadsheet-based guest management in Spanish | Combines confirmed format and language with supplied guest-list intent | Confirm Spanish guest-list module | “Spreadsheet” and “template” expectations may differ | Description or keyword field | | 7 | `bilingual wedding checklist` | Checklist available in two languages | Combines supplied bilingual and checklist language | Confirm checklist module in both languages | Could overstate the number or depth of tasks | Feature heading or keyword field | | 8 | `printable wedding checklist in Spanish` | Printed Spanish-language task checklist | Combines supplied printable format and exact checklist language | Confirm checklist and print-ready layout | High risk if printing is awkward or untested | Description after print test | | 9 | `XLSX bilingual wedding planner` | Buyer seeking a specific editable file type | Combines confirmed XLSX and bilingual product facts | Verify the file opens and functions as described | Technical wording may not match normal buyer language | Specifications or low-priority test | | 10 | `Google Sheets bilingual wedding planner` | Buyer seeking a Google Sheets workflow | Combines confirmed instructions with bilingual planner intent | Verify whether this is native, import-based, or instructions-only | High claim and third-party-brand risk | Compatibility section only after verification | ## Hypotheses that should not be targeted * `wedding planning app` * `mobile wedding planner` * Any phrase promising automatic synchronization, reminders, collaboration, or app functionality * Any budget, checklist, or guest-list phrase before the corresponding module is confirmed These phrases would conflict with or go beyond the supplied product facts. --- # 9. COLLISION CHECK ## Within-listing semantic collision The following phrases overlap heavily: * `bilingual wedding planner` * `bilingual wedding planning spreadsheet` * `English Spanish wedding planner` They express nearly the same broad intent. Using all three prominently would add repetition without testing a distinct buyer job. Similarly: * `wedding checklist in Spanish` * `bilingual wedding checklist` * `printable wedding checklist in Spanish` These should not all occupy scarce keyword placements unless the search export shows meaningfully distinct query behavior. ## Product-scope collision The main risk is using customer language for functions that have not been verified as product contents: | Phrase family | Required product proof | | ------------- | ------------------------------------------------------ | | Budget | Budget tab, fields, formulas, and language coverage | | Guest list | Guest-list tab, fields, and language coverage | | Checklist | Checklist tab, tasks, and language coverage | | Printable | Tested print or PDF layout | | Google Sheets | Exact access/import workflow | | Planner | Evidence that the workbook’s breadth supports the term | ## Format collision `Printable`, `XLSX`, and `Google Sheets` can create different expectations: * “Printable” may suggest a print-first PDF or page layout. * “XLSX” indicates an editable spreadsheet file. * “Google Sheets” may suggest a native online template. * “Planner” may suggest a complete planning system. * “Not a mobile app” excludes an app-based workflow. The listing should explain how these elements relate rather than treating them as interchangeable. ## Language collision `Bilingual` and `in Spanish` are related but not identical: * `Bilingual` implies English and Spanish are both available. * `In Spanish` may attract someone seeking Spanish-only content. The listing should state the actual language arrangement, such as whether both languages appear: * Side by side * On separate tabs * In separate files * Through user-selectable fields That arrangement was not supplied. ## Cross-listing collision Cannot be assessed without the shop’s other listings. Needed comparison fields: | Listing | Primary buyer job | Primary phrase | Secondary phrase | Language | Format | Overlap concern | | ------------ | ----------------- | -------------- | ---------------- | -------- | ------ | -------------------- | | NOT SUPPLIED | — | — | — | — | — | Await shop inventory | --- # 10. TRADEMARK AND RIGHTS CHECK This is not a legal or intellectual-property conclusion. * The supplied wedding-planning phrases appear descriptive in ordinary language, but no formal clearance has been performed. * `Google Sheets` refers to a third-party brand. * Use that name only to describe a verified, factual compatibility or instruction workflow. * Do not imply endorsement, partnership, certification, or affiliation. * Do not use third-party logos or branded visual assets without verified permission. * Search the exact final wording against current relevant trademark records and Etsy’s current intellectual-property policies before publication. * Platform and legal requirements are **NEEDED FOR OWNER VERIFICATION**. Qualified review may be appropriate where a brand reference is commercially important. --- # 11. FOUR-WEEK VALIDATION PLAN The purpose is to test message-to-query fit, not to guarantee rankings or sales. ## Week 1 — Establish the evidence baseline **Actions** 1. Import the full 90-day search-term export without modifying exact-query wording. 2. Calculate visit rate, order rate, and order yield. 3. Assign each exact query to: * One of the four supplied intent clusters * One of the ten hypothesis clusters * Unrelated or mismatched traffic 4. Count how many of the 46 messages contain each supplied phrase or close wording. 5. Confirm whether the product contains budget, guest-list, and checklist modules. 6. Record the current listing title, description, tags, images, price, advertising state, and date. **Listing changes:** None. **Output:** Baseline query table and product-fit matrix. ## Week 2 — Select and implement one primary test Choose one exact phrase using this sequence: 1. Exact product fit 2. Orders 3. Visits relative to impressions 4. Impressions 5. Readability Change **one primary layer only**. The preferred first layer is the title’s primary phrase, subject to current owner-verified Etsy requirements. Keep unchanged: * Description * Images * Price * Tags * Advertising settings * Product contents * Promotions Record the exact wording and implementation date. ## Week 3 — Hold the test and inspect query quality Do not add another major keyword change. Track: * Exact queries generating impressions * Visits from those queries * Orders from those queries * Customer questions indicating confusion * Mismatched app-related traffic * Whether buyers appear to expect absent modules Interpretation guide: | Observation | Supported interpretation | What it does not prove | | -------------------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------- | | Impressions rise, but visit rate falls | The listing may be appearing for a broader or weaker-fit query mix | That the phrase is inherently bad | | Visits rise, but orders do not | Message-to-product fit or listing conversion may need investigation | That price, images, or description are definitely the cause | | Exact-query orders appear | The phrase has observed order evidence in this sample | Future sales or stable demand | | App-related visits appear | The wording may be creating a format mismatch | That all visitors misunderstood the product | | No meaningful traffic appears | The sample may be insufficient or the phrase may have limited observed reach | Zero demand | ## Week 4 — Make a controlled decision Compare the test period with a consistent baseline while documenting: * Different traffic sources * Advertising changes * Price or promotion changes * Seasonality * Product changes * Small sample size Decision options: ### Keep Keep the tested phrase when: * It remains fully truthful. * It produces relevant exact queries. * The visit and order evidence is directionally favorable. * Customer confusion does not increase. ### Revert Revert when: * The phrase misrepresents the product. * Mismatched queries increase. * Buyer questions reveal an expectation the product cannot satisfy. * Relevant query quality deteriorates sufficiently for the owner to reject the trade-off. ### Extend Extend the unchanged test when: * The observation count is too small. * No order-level conclusion is supportable. * External changes prevent a fair comparison. Do not introduce a second primary keyword test until the first test has been documented and evaluated. --- # 12. QA CHECKLIST * [x] Selected only Task 1 as the primary task. * [x] Used the four supplied customer-language phrases. * [x] Did not invent phrase counts within the 46 messages. * [x] Did not invent search-term export values. * [x] Did not claim search volume or competition. * [x] Did not state an Etsy ranking factor. * [x] Labeled all ten new phrases as hypotheses. * [x] Distinguished confirmed spreadsheet/language facts from unverified modules. * [x] Did not describe the product as a mobile app. * [x] Flagged possible overstatement involving Google Sheets. * [x] Flagged current Etsy limits and policies for owner verification. * [x] Included collision and trademark checks without presenting a legal conclusion. * [x] Proposed one primary listing change at a time. * [x] Included sample-size and attribution limitations. * [x] Did not guarantee rankings, traffic, conversion, orders, or revenue. # 13. OWNER DECISIONS The owner must decide or verify: 1. Whether this specific product includes a budget module. 2. Whether it includes a guest-list module. 3. Whether it includes a wedding checklist. 4. How English and Spanish are presented. 5. Whether every relevant worksheet is print-ready. 6. Whether customers receive a native Google Sheets product or only instructions for using the XLSX file with Google Sheets. 7. Whether `bilingual wedding planner` accurately represents the product’s breadth. 8. Which exact query has the strongest order evidence after the export is analyzed. 9. Which current Etsy title and tag requirements apply at publication. 10. Whether third-party brand wording has been appropriately verified. # 14. SINGLE NEXT ACTION **Send one evidence packet containing the actual 90-day search-term export and a yes/no product-content matrix for the budget, guest-list, checklist, print-ready, and Google Sheets-native features.**