weekly seo

docs/automations/qrmaster-seo-sprint-2026-05-11.md

@@ -0,0 +1,158 @@
+# QRMaster SEO Sprint: Tracking and Analytics
+
+Run date: 2026-05-11
+Automation: QRMaster SEO Sprint Machine
+Status: Recommendation package only; do not publish without human approval.
+
+## Input Notes
+
+- Used `docs/automations/qrmaster-seo-sprint-machine.md`, `docs/automations/qrmaster-pr-seo-review.md`, `.agents/product-marketing-context.md`, `marketing/programmatic-seo-top-50.md`, `seo-plan-april.md`, and `seo-keywords.csv`.
+- `marketing/keyword-strategy-seo-plan.md` was not present in this worktree. `seo-plan-april.md` appears to be the local keyword strategy fallback and includes the same cluster-level keyword data.
+- Existing routing redirects selected legacy `/guide/...` paths to `/learn/...`, so this sprint should avoid creating duplicate guide URLs without a clear canonical/routing decision.
+
+## Cluster Scoring
+
+| Cluster | Product fit /30 | Commercial intent /25 | Differentiation /15 | Cluster leverage /10 | Winability /10 | Effort /10 | Score | Decision |
+|---|---:|---:|---:|---:|---:|---:|---:|---|
+| Tracking and analytics | 29 | 24 | 15 | 10 | 8 | 8 | 94 | Select |
+| Dynamic QR buying decision | 30 | 24 | 13 | 10 | 7 | 7 | 91 | Next best |
+| Bulk QR generation | 27 | 19 | 14 | 8 | 9 | 8 | 85 | Hold for later |
+| Commercial alternatives | 22 | 25 | 12 | 8 | 6 | 5 | 78 | Needs current competitor verification |
+| Restaurant/menu QR | 25 | 16 | 12 | 8 | 7 | 7 | 75 | Good vertical support, weaker immediate demand |
+| Custom/design QR | 20 | 18 | 9 | 8 | 8 | 8 | 71 | Tool-led, less differentiated |
+| Print reliability | 21 | 13 | 10 | 7 | 9 | 8 | 68 | Useful support content, weaker commercial pull |
+
+## Rationale
+
+Tracking and analytics is the highest-fit weekly cluster because it maps directly to QRMaster's differentiators: dynamic QR redirects, scan analytics, placement comparison, and privacy-first reporting. The keyword set includes `qr code tracking` at 1k-10k monthly volume with +900% 3-month YoY trend, `track qr code scans` with +900% 3-month trend, and `trackable qr code` with the highest CPC ceiling in the file at EUR 34.25. The cluster also has strong internal-link leverage into `/dynamic-qr-code-generator`, `/qr-code-analytics`, `/qr-code-tracking`, `/qr-code-for-marketing-campaigns`, pricing, and use-case pages.
+
+## Selected Work
+
+| Type | URL | Score | Reason |
+|---|---|---:|---|
+| Refresh | `/qr-code-tracking` | 94 | Money page for `qr code tracking`, `track qr code scans`, and `trackable qr code`; already has schema but should strengthen privacy and placement examples. |
+| Refresh | `/qr-code-analytics` | 90 | Needs clearer separation from tracking: analytics should own dashboard interpretation, ROI, and performance insights. |
+| Refresh | `/blog/trackable-qr-codes` | 88 | Existing support article should capture `trackable qr code` and link strongly to `/qr-code-tracking`. |
+| Refresh | `/blog/utm-parameter-qr-codes` | 86 | Existing support article should capture fan-out intent around GA4, UTM naming, placement comparison, and offline attribution. |
+| New support page | `/use-cases/qr-codes-for-review-collection` | 86 | Existing backlog item with natural tracking CTA; use as a measurable review funnel page, not a generic Google reviews tool duplicate. |
+
+## Keyword Intent And Fan-Out
+
+| URL | Primary keyword | Intent | Fan-out subtopics |
+|---|---|---|---|
+| `/qr-code-tracking` | `qr code tracking` | Commercial | What can be tracked, static vs dynamic tracking, scan count vs unique scans, device/location/time context, privacy/GDPR, placement comparison, UTM pairing, dashboard workflow, pricing limits. |
+| `/qr-code-analytics` | `qr code analytics` | Commercial | Analytics dashboard, ROI interpretation, campaign attribution, useful metrics vs vanity metrics, offline-to-online measurement, reporting cadence, route naming, export/share needs. |
+| `/blog/trackable-qr-codes` | `trackable qr code` | Informational-commercial | Definition, how tracking works, dynamic redirect layer, privacy limits, examples by placement, pros/cons, setup checklist, when not to track. |
+| `/blog/utm-parameter-qr-codes` | `qr code UTM tracking` | Informational | GA4 source/medium/campaign/content conventions, examples for flyers/events/packaging, common mistakes, naming templates, QR destination testing. |
+| `/use-cases/qr-codes-for-review-collection` | `QR codes for review collection` | Commercial | Google review link workflow, in-store placement, happy-path routing, feedback triage, scan tracking, QR privacy, dynamic destination updates. |
+
+## 2026 On-Page And Agentic-Search Rules
+
+- Titles/H1s should put the target keyword near the start:
+  - `/qr-code-tracking`: `QR Code Tracking: Track QR Code Scans`
+  - `/qr-code-analytics`: `QR Code Analytics: Measure Offline Campaigns`
+  - `/blog/trackable-qr-codes`: `Trackable QR Codes: What You Can Measure`
+  - `/blog/utm-parameter-qr-codes`: `QR Code UTM Tracking: GA4 Setup Guide`
+  - `/use-cases/qr-codes-for-review-collection`: `QR Codes for Review Collection`
+- Each H2 should start with a direct answer in the first sentence.
+- Add compact tables for `static vs dynamic`, `tracking vs analytics`, and `UTM examples by placement`.
+- Add FAQ schema to refreshed informational pages where the existing blog system supports it; preserve SoftwareApplication and HowTo schema on money pages.
+- Use self-contained answer blocks of roughly 40-60 words for definitions and "can you track..." questions.
+- Visuals should be meaningful: dashboard screenshot/mockup, placement comparison example, UTM naming table, and review-flow diagram.
+- Robots/indexing: current `robots.ts` allows major search/AI crawlers and disallows private app/API paths. Keep these pages indexed, sitemap-included, and canonicalized to their final URLs.
+- Mobile/speed risks: avoid heavy dashboard imagery; use compressed static images and keep tables horizontally readable on mobile.
+
+## Recommended New Page
+
+### `/use-cases/qr-codes-for-review-collection`
+
+Purpose: Create a commercially useful support page for restaurants, cafes, retail, hotels, and service businesses that want measurable review capture.
+
+Required sections:
+
+1. Direct answer: a review-collection QR code sends satisfied customers to the right review or feedback flow and lets teams measure which physical prompts get scanned.
+2. Workflow: in-store sign, receipt, table card, counter card, packaging insert.
+3. Dynamic vs static: use dynamic if the review platform, routing rule, or offer changes.
+4. Tracking angle: compare scan volume by placement, store, or campaign.
+5. Privacy note: describe scan analytics without promising personally identifiable tracking.
+6. CTA: `Create a trackable review QR code` to `/qr-code-tracking` or `/signup`.
+7. Internal links: `/tools/google-review-qr-code`, `/qr-code-tracking`, `/dynamic-qr-code-generator`, `/restaurants`, `/use-cases/feedback-qr-codes`.
+8. Schema: FAQPage + BreadcrumbList; consider HowTo if step-by-step content is included.
+
+## Recommended Page Refreshes
+
+### `/qr-code-tracking`
+
+- Strengthen first-screen answer: "QR code tracking uses a dynamic redirect to record scan time, device context, and approximate location before sending the scanner to the final destination."
+- Add a privacy-first section explaining hashed/anonymized IP positioning from QRMaster.
+- Add a table: "What QRMaster tracks / what it does not track."
+- Add examples for flyer, menu, event booth, packaging, and review collection.
+- Link to `/qr-code-analytics`, `/blog/utm-parameter-qr-codes`, `/reprint-calculator`, `/pricing`, and the new review-collection page.
+
+### `/qr-code-analytics`
+
+- Separate from tracking: tracking collects scan events; analytics helps interpret placement and campaign performance.
+- Add an "analytics questions" table: which placement worked, when scans peaked, which destination converted, what to reprint.
+- Add a section on useful metrics vs vanity metrics.
+- Link back to `/qr-code-tracking`, `/qr-code-for-marketing-campaigns`, `/use-cases/flyer-qr-codes`, `/use-cases/packaging-qr-codes`, and `/pricing`.
+
+### `/blog/trackable-qr-codes`
+
+- Refresh title/meta around `trackable qr code`.
+- Add a 40-60 word definition block near the top.
+- Update FAQ to include "Can a static QR code be tracked?", "Are trackable QR codes GDPR-friendly?", and "Do trackable QR codes need a redirect?"
+- Link early to `/qr-code-tracking` with anchor `track QR code scans`.
+
+### `/blog/utm-parameter-qr-codes`
+
+- Add a QR-specific UTM template table by placement.
+- Add GA4 naming convention examples.
+- Clarify when to use separate QR codes versus one QR with different `utm_content` values.
+- Link to `/qr-code-analytics` and `/qr-code-tracking`.
+
+## Internal-Link Plan
+
+| Source | Destination | Anchor |
+|---|---|---|
+| `/dynamic-qr-code-generator` | `/qr-code-tracking` | `track QR code scans` |
+| `/dynamic-qr-code-generator` | `/qr-code-analytics` | `QR code analytics dashboard` |
+| `/qr-code-tracking` | `/qr-code-analytics` | `interpret QR scan analytics` |
+| `/qr-code-tracking` | `/blog/utm-parameter-qr-codes` | `use UTMs with QR codes` |
+| `/qr-code-analytics` | `/qr-code-tracking` | `collect QR scan data` |
+| `/qr-code-analytics` | `/qr-code-for-marketing-campaigns` | `measure offline QR campaigns` |
+| `/blog/trackable-qr-codes` | `/qr-code-tracking` | `QR code tracking` |
+| `/blog/utm-parameter-qr-codes` | `/qr-code-analytics` | `QR code analytics` |
+| `/use-cases/feedback-qr-codes` | `/use-cases/qr-codes-for-review-collection` | `review collection QR codes` |
+| `/tools/google-review-qr-code` | `/use-cases/qr-codes-for-review-collection` | `review collection workflow` |
+
+## PR Plan
+
+1. Add the new review-collection use-case content in the existing use-case page data/routing pattern.
+2. Refresh copy, FAQ, metadata, and link sections on `/qr-code-tracking` and `/qr-code-analytics`.
+3. Refresh the two support blog entries without creating duplicate `/guide/...` pages.
+4. Add internal links in both directions from money pages, blog support pages, and relevant use-case/tool pages.
+5. Update sitemap data only if the new page is not automatically included by the existing use-case sitemap mapping.
+6. Run the PR SEO review using `docs/automations/qrmaster-pr-seo-review.md`.
+
+## Verification Checklist
+
+- One H1 per rendered page.
+- Primary keyword appears naturally in title, H1, intro, and metadata.
+- Canonical URL points to the final public URL.
+- Page is public in middleware and included in sitemap.
+- No duplicate `/guide/...` URL is introduced without canonical strategy.
+- FAQ/schema validates where used.
+- Internal links resolve and use natural anchor text.
+- Each section begins with a direct answer.
+- Mobile tables do not overflow unreadably.
+- Visual assets are compressed and include descriptive alt text.
+- Robots rules continue to allow target pages and desired search/AI crawlers.
+- Build/lint pass before PR.
+
+## Social And Outreach Follow-Up
+
+- LinkedIn post: "Most QR campaigns fail because teams only count scans. The useful question is which printed placement created action."
+- X thread: "QR tracking setup in 5 steps: dynamic QR, placement naming, UTM convention, dashboard review, reprint decision."
+- Short demo video: show flyer A vs flyer B scan comparison and a destination update without reprinting.
+- Outreach angle for marketing newsletters: "Offline attribution checklist for QR campaigns."
+- Community answer target: questions around "Can I track a static QR code?" and "How do I track QR codes in GA4?"