search console SEO ableitungen
This commit is contained in:
@@ -1,78 +1,78 @@
|
||||
---
|
||||
name: qrmaster-growth-system
|
||||
description: Use when working on QRMaster growth for qrmaster.net. Covers the QRMaster SEO/GEO/SaaS wedge, baseline audit, competitor gap analysis, Top 30 page backlog, internal linking, scoring, and measurement. Also use when planning or executing use-case hubs, commercial QR landing pages, or marketing tracking for QRMaster.
|
||||
---
|
||||
|
||||
# QRMaster Growth System
|
||||
|
||||
Use this skill only for `qrmaster.net` work.
|
||||
|
||||
## Goal
|
||||
|
||||
Turn QRMaster from a generic QR tool site into a measurable SaaS growth system built around dynamic, trackable QR workflows.
|
||||
|
||||
## Default context
|
||||
|
||||
- Domain: `qrmaster.net`
|
||||
- Primary market: English
|
||||
- Product strengths: dynamic updates, scan analytics, bulk creation, branded QR codes, campaign attribution
|
||||
- Benchmark competitors: QRCode Monkey, Beaconstac, QR TIGER, QR Code Generator, Scanova
|
||||
|
||||
## Core thesis
|
||||
|
||||
- Do not optimize for generic "free QR" traffic first.
|
||||
- Win where dynamic updates and tracking clearly matter.
|
||||
- Treat use-case pages as acquisition assets, not blog filler.
|
||||
- Every page must map to a workflow pain, a commercial parent, and a tracked CTA.
|
||||
|
||||
## When to use this skill
|
||||
|
||||
- Planning QRMaster SEO, AEO, or GEO work
|
||||
- Auditing the QRMaster content and route structure
|
||||
- Building or improving `/use-cases`, hubs, or commercial landing pages
|
||||
- Prioritizing new pages or existing content upgrades
|
||||
- Designing internal links for QRMaster
|
||||
- Defining marketing events and SEO-to-signup measurement for QRMaster
|
||||
|
||||
## How to use this skill
|
||||
|
||||
1. Read `references/current-state-findings.md` if the current repo state is unknown.
|
||||
2. Read `references/core-plan.md` for the operating model, wedge, internal links, and scoring.
|
||||
3. Read `references/top-30-backlog.md` when planning or building page inventory.
|
||||
4. Read `references/tracking-spec.md` when implementing page-level or funnel tracking.
|
||||
5. If you are not inside the QRMaster repo, produce plans, specs, or content only. Do not mutate product files.
|
||||
|
||||
## Companion skills
|
||||
|
||||
Use the smallest set needed:
|
||||
|
||||
- `agentic-saas-advisor`: SaaS wedge, workflow, monetization, 30/60/90 sequencing
|
||||
- `seo-aeo-geo-expert`: SEO/AEO/GEO detail and content shaping
|
||||
- `keyword-research`: cluster design and SERP-driven prioritization
|
||||
- `conversion`: page-level conversion flow and CTA decisions
|
||||
- `analytics-tracking`: event taxonomy and measurement QA
|
||||
- `site-architecture`: hub, URL, and internal-link structure
|
||||
|
||||
## Output contract
|
||||
|
||||
Return outputs in this order when doing planning work:
|
||||
|
||||
1. `TL;DR`
|
||||
2. `Sub-Niche Thesis`
|
||||
3. `QRMaster Baseline Audit`
|
||||
4. `Competitor Gap Analysis`
|
||||
5. `SERP Pattern Summary`
|
||||
6. `Top 30 Page Backlog`
|
||||
7. `Internal Linking Model`
|
||||
8. `Priority Scores`
|
||||
9. `30/60/90 Plan`
|
||||
10. `Tracking Spec`
|
||||
11. `Assumptions`
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Do not treat all QR traffic as equal; prioritize workflows with update or tracking value.
|
||||
- Do not add pages without a real product-fit angle.
|
||||
- Do not separate SEO from signup and activation measurement.
|
||||
- Do not expand beyond the core wedge until the first cluster set shows repeatable ROI.
|
||||
|
||||
---
|
||||
name: qrmaster-growth-system
|
||||
description: Use when working on QRMaster growth for qrmaster.net. Covers the QRMaster SEO/GEO/SaaS wedge, baseline audit, competitor gap analysis, Top 30 page backlog, internal linking, scoring, and measurement. Also use when planning or executing use-case hubs, commercial QR landing pages, or marketing tracking for QRMaster.
|
||||
---
|
||||
|
||||
# QRMaster Growth System
|
||||
|
||||
Use this skill only for `qrmaster.net` work.
|
||||
|
||||
## Goal
|
||||
|
||||
Turn QRMaster from a generic QR tool site into a measurable SaaS growth system built around dynamic, trackable QR workflows.
|
||||
|
||||
## Default context
|
||||
|
||||
- Domain: `qrmaster.net`
|
||||
- Primary market: English
|
||||
- Product strengths: dynamic updates, scan analytics, bulk creation, branded QR codes, campaign attribution
|
||||
- Benchmark competitors: QRCode Monkey, Beaconstac, QR TIGER, QR Code Generator, Scanova
|
||||
|
||||
## Core thesis
|
||||
|
||||
- Do not optimize for generic "free QR" traffic first.
|
||||
- Win where dynamic updates and tracking clearly matter.
|
||||
- Treat use-case pages as acquisition assets, not blog filler.
|
||||
- Every page must map to a workflow pain, a commercial parent, and a tracked CTA.
|
||||
|
||||
## When to use this skill
|
||||
|
||||
- Planning QRMaster SEO, AEO, or GEO work
|
||||
- Auditing the QRMaster content and route structure
|
||||
- Building or improving `/use-cases`, hubs, or commercial landing pages
|
||||
- Prioritizing new pages or existing content upgrades
|
||||
- Designing internal links for QRMaster
|
||||
- Defining marketing events and SEO-to-signup measurement for QRMaster
|
||||
|
||||
## How to use this skill
|
||||
|
||||
1. Read `references/current-state-findings.md` if the current repo state is unknown.
|
||||
2. Read `references/core-plan.md` for the operating model, wedge, internal links, and scoring.
|
||||
3. Read `references/top-30-backlog.md` when planning or building page inventory.
|
||||
4. Read `references/tracking-spec.md` when implementing page-level or funnel tracking.
|
||||
5. If you are not inside the QRMaster repo, produce plans, specs, or content only. Do not mutate product files.
|
||||
|
||||
## Companion skills
|
||||
|
||||
Use the smallest set needed:
|
||||
|
||||
- `agentic-saas-advisor`: SaaS wedge, workflow, monetization, 30/60/90 sequencing
|
||||
- `seo-aeo-geo-expert`: SEO/AEO/GEO detail and content shaping
|
||||
- `keyword-research`: cluster design and SERP-driven prioritization
|
||||
- `conversion`: page-level conversion flow and CTA decisions
|
||||
- `analytics-tracking`: event taxonomy and measurement QA
|
||||
- `site-architecture`: hub, URL, and internal-link structure
|
||||
|
||||
## Output contract
|
||||
|
||||
Return outputs in this order when doing planning work:
|
||||
|
||||
1. `TL;DR`
|
||||
2. `Sub-Niche Thesis`
|
||||
3. `QRMaster Baseline Audit`
|
||||
4. `Competitor Gap Analysis`
|
||||
5. `SERP Pattern Summary`
|
||||
6. `Top 30 Page Backlog`
|
||||
7. `Internal Linking Model`
|
||||
8. `Priority Scores`
|
||||
9. `30/60/90 Plan`
|
||||
10. `Tracking Spec`
|
||||
11. `Assumptions`
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Do not treat all QR traffic as equal; prioritize workflows with update or tracking value.
|
||||
- Do not add pages without a real product-fit angle.
|
||||
- Do not separate SEO from signup and activation measurement.
|
||||
- Do not expand beyond the core wedge until the first cluster set shows repeatable ROI.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
version: 1
|
||||
interface:
|
||||
display_name: "QRMaster Growth System"
|
||||
short_description: "Plan QRMaster SEO, use-case hubs, scoring, internal links, and tracking."
|
||||
default_prompt: "Audit qrmaster.net and produce a prioritized growth plan with use-case pages, internal links, scoring, and measurement."
|
||||
|
||||
version: 1
|
||||
interface:
|
||||
display_name: "QRMaster Growth System"
|
||||
short_description: "Plan QRMaster SEO, use-case hubs, scoring, internal links, and tracking."
|
||||
default_prompt: "Audit qrmaster.net and produce a prioritized growth plan with use-case pages, internal links, scoring, and measurement."
|
||||
|
||||
|
||||
@@ -1,155 +1,155 @@
|
||||
# QRMaster Core Plan
|
||||
|
||||
## Positioning
|
||||
|
||||
QRMaster should not try to win broad generic QR traffic first.
|
||||
|
||||
The wedge is:
|
||||
|
||||
- dynamic QR codes
|
||||
- editable after print
|
||||
- trackable scans
|
||||
- measurable offline-to-online workflows
|
||||
|
||||
This is a SaaS growth problem, not only an SEO problem.
|
||||
|
||||
## Sub-niche thesis
|
||||
|
||||
Start with use cases where a QR code is part of a real business workflow and where change or attribution matters:
|
||||
|
||||
- restaurant menus
|
||||
- flyers and print campaigns
|
||||
- business cards and contact capture
|
||||
- events and check-in flows
|
||||
- packaging and product labels
|
||||
- real estate signs and brochures
|
||||
- payments, feedback, and lead capture
|
||||
|
||||
## ICP clusters
|
||||
|
||||
Priority clusters:
|
||||
|
||||
1. Restaurants
|
||||
2. Small business / print marketing
|
||||
3. Events
|
||||
4. Real estate
|
||||
5. Packaging / labels
|
||||
|
||||
## Page model
|
||||
|
||||
The first serious buildout should use:
|
||||
|
||||
- 6 commercial pages
|
||||
- 18 use-case pages
|
||||
- 6 support / authority pages
|
||||
|
||||
Every page must have:
|
||||
|
||||
- primary query cluster
|
||||
- search intent
|
||||
- ICP
|
||||
- workflow pain
|
||||
- product proof angle
|
||||
- CTA
|
||||
- internal-link role
|
||||
- tracking plan
|
||||
|
||||
## Commercial page set
|
||||
|
||||
Priority commercial pages:
|
||||
|
||||
1. Dynamic QR Code Generator
|
||||
2. Bulk QR Code Generator
|
||||
3. QR Code Analytics
|
||||
4. Custom / Branded QR Code Generator
|
||||
5. QR Code Tracking / Trackable QR Codes
|
||||
6. QR Codes for Marketing Campaigns
|
||||
|
||||
## Internal linking model
|
||||
|
||||
Use a 3-layer structure:
|
||||
|
||||
- Layer 1: commercial money pages
|
||||
- Layer 2: use-case pages
|
||||
- Layer 3: support / authority hubs
|
||||
|
||||
Rules:
|
||||
|
||||
- every use-case page links to exactly 1 primary commercial page
|
||||
- every use-case page links to the main `/use-cases` hub
|
||||
- every use-case page links to up to 2 sibling use cases
|
||||
- every support page links upward into 1 commercial page and 2 use-case pages
|
||||
- every commercial page links down into 3 to 5 strongest use cases
|
||||
- no planned page should be an orphan
|
||||
|
||||
## AEO / GEO operating spec
|
||||
|
||||
For P1 and P2 pages, require:
|
||||
|
||||
- one direct answer block near the top
|
||||
- one extractable proof paragraph
|
||||
- three to six FAQ candidates
|
||||
- one comparison or checklist block if the SERP suggests it
|
||||
- clear entity reinforcement for QRMaster, dynamic QR, analytics, and the use case
|
||||
|
||||
## Scoring model
|
||||
|
||||
Use:
|
||||
|
||||
`Priority Score = ((Impact x Confidence x Strategic Fit x Time-to-Signal) / Effort) x 4`
|
||||
|
||||
Factor definitions:
|
||||
|
||||
- Impact: likely effect on qualified organic visibility or assisted conversions
|
||||
- Confidence: strength of evidence from SERPs, current fit, or competitor patterns
|
||||
- Strategic Fit: closeness to QRMaster's actual product strengths
|
||||
- Time-to-Signal: expected speed of measurable movement
|
||||
- Effort: total work across content, SEO, design, dev, and review
|
||||
|
||||
Modifiers:
|
||||
|
||||
- `+20%` dependencies already clear
|
||||
- `+15%` strong support for a money page
|
||||
- `-25%` weak baseline or weak measurement
|
||||
- `-30%` slow-signal initiative
|
||||
- `-40%` high guardrail risk
|
||||
- `-50%` weak product proof or weak differentiation
|
||||
- `-35%` if the page is likely to bring generic hobby traffic with poor SaaS intent
|
||||
|
||||
Priority classes:
|
||||
|
||||
- `P1`: `>= 70`
|
||||
- `P2`: `50-69`
|
||||
- `P3`: `< 50`
|
||||
|
||||
Hard gate:
|
||||
|
||||
- if the page cannot clearly demonstrate a real workflow problem solved by QRMaster, it cannot be `P1`
|
||||
|
||||
## 30 / 60 / 90
|
||||
|
||||
### Days 1-30
|
||||
|
||||
- audit current QRMaster inventory
|
||||
- classify existing pages into commercial, use-case, support
|
||||
- map 5 ICP workflows
|
||||
- compare against the named competitors
|
||||
- define the Top 30 backlog
|
||||
- lock the internal-link structure
|
||||
- choose the first 5 to 8 `P1` pages
|
||||
|
||||
### Days 31-60
|
||||
|
||||
- standardize page templates
|
||||
- standardize AEO / GEO blocks
|
||||
- refine CTAs and conversion flow for the first P1 pages
|
||||
- re-score backlog after evidence review
|
||||
- define distribution angles from the first pages
|
||||
|
||||
### Days 61-90
|
||||
|
||||
- expand the strongest use-case clusters
|
||||
- reinforce internal linking
|
||||
- standardize the operating model
|
||||
- define the next-quarter page set
|
||||
|
||||
# QRMaster Core Plan
|
||||
|
||||
## Positioning
|
||||
|
||||
QRMaster should not try to win broad generic QR traffic first.
|
||||
|
||||
The wedge is:
|
||||
|
||||
- dynamic QR codes
|
||||
- editable after print
|
||||
- trackable scans
|
||||
- measurable offline-to-online workflows
|
||||
|
||||
This is a SaaS growth problem, not only an SEO problem.
|
||||
|
||||
## Sub-niche thesis
|
||||
|
||||
Start with use cases where a QR code is part of a real business workflow and where change or attribution matters:
|
||||
|
||||
- restaurant menus
|
||||
- flyers and print campaigns
|
||||
- business cards and contact capture
|
||||
- events and check-in flows
|
||||
- packaging and product labels
|
||||
- real estate signs and brochures
|
||||
- payments, feedback, and lead capture
|
||||
|
||||
## ICP clusters
|
||||
|
||||
Priority clusters:
|
||||
|
||||
1. Restaurants
|
||||
2. Small business / print marketing
|
||||
3. Events
|
||||
4. Real estate
|
||||
5. Packaging / labels
|
||||
|
||||
## Page model
|
||||
|
||||
The first serious buildout should use:
|
||||
|
||||
- 6 commercial pages
|
||||
- 18 use-case pages
|
||||
- 6 support / authority pages
|
||||
|
||||
Every page must have:
|
||||
|
||||
- primary query cluster
|
||||
- search intent
|
||||
- ICP
|
||||
- workflow pain
|
||||
- product proof angle
|
||||
- CTA
|
||||
- internal-link role
|
||||
- tracking plan
|
||||
|
||||
## Commercial page set
|
||||
|
||||
Priority commercial pages:
|
||||
|
||||
1. Dynamic QR Code Generator
|
||||
2. Bulk QR Code Generator
|
||||
3. QR Code Analytics
|
||||
4. Custom / Branded QR Code Generator
|
||||
5. QR Code Tracking / Trackable QR Codes
|
||||
6. QR Codes for Marketing Campaigns
|
||||
|
||||
## Internal linking model
|
||||
|
||||
Use a 3-layer structure:
|
||||
|
||||
- Layer 1: commercial money pages
|
||||
- Layer 2: use-case pages
|
||||
- Layer 3: support / authority hubs
|
||||
|
||||
Rules:
|
||||
|
||||
- every use-case page links to exactly 1 primary commercial page
|
||||
- every use-case page links to the main `/use-cases` hub
|
||||
- every use-case page links to up to 2 sibling use cases
|
||||
- every support page links upward into 1 commercial page and 2 use-case pages
|
||||
- every commercial page links down into 3 to 5 strongest use cases
|
||||
- no planned page should be an orphan
|
||||
|
||||
## AEO / GEO operating spec
|
||||
|
||||
For P1 and P2 pages, require:
|
||||
|
||||
- one direct answer block near the top
|
||||
- one extractable proof paragraph
|
||||
- three to six FAQ candidates
|
||||
- one comparison or checklist block if the SERP suggests it
|
||||
- clear entity reinforcement for QRMaster, dynamic QR, analytics, and the use case
|
||||
|
||||
## Scoring model
|
||||
|
||||
Use:
|
||||
|
||||
`Priority Score = ((Impact x Confidence x Strategic Fit x Time-to-Signal) / Effort) x 4`
|
||||
|
||||
Factor definitions:
|
||||
|
||||
- Impact: likely effect on qualified organic visibility or assisted conversions
|
||||
- Confidence: strength of evidence from SERPs, current fit, or competitor patterns
|
||||
- Strategic Fit: closeness to QRMaster's actual product strengths
|
||||
- Time-to-Signal: expected speed of measurable movement
|
||||
- Effort: total work across content, SEO, design, dev, and review
|
||||
|
||||
Modifiers:
|
||||
|
||||
- `+20%` dependencies already clear
|
||||
- `+15%` strong support for a money page
|
||||
- `-25%` weak baseline or weak measurement
|
||||
- `-30%` slow-signal initiative
|
||||
- `-40%` high guardrail risk
|
||||
- `-50%` weak product proof or weak differentiation
|
||||
- `-35%` if the page is likely to bring generic hobby traffic with poor SaaS intent
|
||||
|
||||
Priority classes:
|
||||
|
||||
- `P1`: `>= 70`
|
||||
- `P2`: `50-69`
|
||||
- `P3`: `< 50`
|
||||
|
||||
Hard gate:
|
||||
|
||||
- if the page cannot clearly demonstrate a real workflow problem solved by QRMaster, it cannot be `P1`
|
||||
|
||||
## 30 / 60 / 90
|
||||
|
||||
### Days 1-30
|
||||
|
||||
- audit current QRMaster inventory
|
||||
- classify existing pages into commercial, use-case, support
|
||||
- map 5 ICP workflows
|
||||
- compare against the named competitors
|
||||
- define the Top 30 backlog
|
||||
- lock the internal-link structure
|
||||
- choose the first 5 to 8 `P1` pages
|
||||
|
||||
### Days 31-60
|
||||
|
||||
- standardize page templates
|
||||
- standardize AEO / GEO blocks
|
||||
- refine CTAs and conversion flow for the first P1 pages
|
||||
- re-score backlog after evidence review
|
||||
- define distribution angles from the first pages
|
||||
|
||||
### Days 61-90
|
||||
|
||||
- expand the strongest use-case clusters
|
||||
- reinforce internal linking
|
||||
- standardize the operating model
|
||||
- define the next-quarter page set
|
||||
|
||||
|
||||
@@ -1,57 +1,57 @@
|
||||
# QRMaster Current-State Findings
|
||||
|
||||
These findings came from a local repo review of `C:\Users\a931627\Documents\QRMASTER`.
|
||||
|
||||
## Existing structural strengths
|
||||
|
||||
- QRMASTER already has several commercial marketing routes:
|
||||
- `/dynamic-qr-code-generator`
|
||||
- `/bulk-qr-code-generator`
|
||||
- `/custom-qr-code-generator`
|
||||
- `/qr-code-tracking`
|
||||
- There is already a `Learn` hub and pillar structure:
|
||||
- `/learn`
|
||||
- `/learn/basics`
|
||||
- `/learn/tracking`
|
||||
- `/learn/use-cases`
|
||||
- `/learn/security`
|
||||
- `/learn/developer`
|
||||
- There is a large blog data layer with many QR use-case and tracking posts.
|
||||
- There is a tool layer under `/tools/*` that already covers many practical generators.
|
||||
|
||||
## Existing content opportunities
|
||||
|
||||
The repo already includes or strongly hints at:
|
||||
|
||||
- restaurant menu content
|
||||
- business card / vCard content
|
||||
- event content
|
||||
- QR marketing / tracking content
|
||||
- print-size and dynamic-vs-static support content
|
||||
- Instagram, WhatsApp, PayPal, Event, and other tool pages that can support use-case clusters
|
||||
|
||||
This means the next growth step should usually be:
|
||||
|
||||
- improve surfacing
|
||||
- improve internal linking
|
||||
- improve commercial-parent relationships
|
||||
- improve measurement
|
||||
|
||||
not blindly create 30 net-new pages first
|
||||
|
||||
## Observed gaps
|
||||
|
||||
- no dedicated `/use-cases` hub was evident in the reviewed route set
|
||||
- use-case content appears spread across blog, learn, and tools
|
||||
- the site likely needs stronger internal-link choreography between commercial pages, use-case content, and support content
|
||||
- current tracking appeared stronger on product actions than on marketing CTAs
|
||||
|
||||
## Practical implication
|
||||
|
||||
For future QRMASTER repo work:
|
||||
|
||||
1. surface the existing use-case inventory better
|
||||
2. connect it to the correct commercial parent pages
|
||||
3. add consistent CTA and landing-page measurement
|
||||
4. then expand the page set based on score and proof
|
||||
|
||||
# QRMaster Current-State Findings
|
||||
|
||||
These findings came from a local repo review of `C:\Users\a931627\Documents\QRMASTER`.
|
||||
|
||||
## Existing structural strengths
|
||||
|
||||
- QRMASTER already has several commercial marketing routes:
|
||||
- `/dynamic-qr-code-generator`
|
||||
- `/bulk-qr-code-generator`
|
||||
- `/custom-qr-code-generator`
|
||||
- `/qr-code-tracking`
|
||||
- There is already a `Learn` hub and pillar structure:
|
||||
- `/learn`
|
||||
- `/learn/basics`
|
||||
- `/learn/tracking`
|
||||
- `/learn/use-cases`
|
||||
- `/learn/security`
|
||||
- `/learn/developer`
|
||||
- There is a large blog data layer with many QR use-case and tracking posts.
|
||||
- There is a tool layer under `/tools/*` that already covers many practical generators.
|
||||
|
||||
## Existing content opportunities
|
||||
|
||||
The repo already includes or strongly hints at:
|
||||
|
||||
- restaurant menu content
|
||||
- business card / vCard content
|
||||
- event content
|
||||
- QR marketing / tracking content
|
||||
- print-size and dynamic-vs-static support content
|
||||
- Instagram, WhatsApp, PayPal, Event, and other tool pages that can support use-case clusters
|
||||
|
||||
This means the next growth step should usually be:
|
||||
|
||||
- improve surfacing
|
||||
- improve internal linking
|
||||
- improve commercial-parent relationships
|
||||
- improve measurement
|
||||
|
||||
not blindly create 30 net-new pages first
|
||||
|
||||
## Observed gaps
|
||||
|
||||
- no dedicated `/use-cases` hub was evident in the reviewed route set
|
||||
- use-case content appears spread across blog, learn, and tools
|
||||
- the site likely needs stronger internal-link choreography between commercial pages, use-case content, and support content
|
||||
- current tracking appeared stronger on product actions than on marketing CTAs
|
||||
|
||||
## Practical implication
|
||||
|
||||
For future QRMASTER repo work:
|
||||
|
||||
1. surface the existing use-case inventory better
|
||||
2. connect it to the correct commercial parent pages
|
||||
3. add consistent CTA and landing-page measurement
|
||||
4. then expand the page set based on score and proof
|
||||
|
||||
|
||||
@@ -1,79 +1,79 @@
|
||||
# QRMaster Top 30 Backlog
|
||||
|
||||
This is the initial candidate backlog for the first serious QRMaster growth sprint.
|
||||
It is not a promise to build every page immediately; it is the structured pool to score and sequence.
|
||||
|
||||
## 1. Commercial pages
|
||||
|
||||
| Bucket | Page | Primary cluster | Route status | Notes |
|
||||
|---|---|---|---|---|
|
||||
| Commercial | Dynamic QR Code Generator | dynamic qr code generator | existing | Core money page, strongest wedge fit |
|
||||
| Commercial | Bulk QR Code Generator | bulk qr code generator | existing | Strong for teams, labels, events |
|
||||
| Commercial | QR Code Analytics | qr code analytics | existing content / upgrade | Needs stronger SaaS CTA alignment |
|
||||
| Commercial | Custom QR Code Generator | custom qr code generator | existing | Strong for branded print use cases |
|
||||
| Commercial | QR Code Tracking | qr code tracking, trackable qr codes | existing | Bridge between SEO and product proof |
|
||||
| Commercial | QR Codes for Marketing Campaigns | qr code marketing | likely upgrade/new | Important parent for flyer/poster clusters |
|
||||
|
||||
## 2. Use-case pages
|
||||
|
||||
| Cluster | Page | Primary cluster | Route status | Primary commercial parent |
|
||||
|---|---|---|---|---|
|
||||
| Restaurants | Restaurant Menu QR Codes | qr code for restaurant menu | existing blog post | Dynamic QR Code Generator |
|
||||
| Restaurants | Table Ordering QR Codes | qr code for table ordering | future | Dynamic QR Code Generator |
|
||||
| Print / SMB | Flyer QR Codes | qr code for flyer | future | QR Codes for Marketing Campaigns |
|
||||
| Print / SMB | Brochure QR Codes | qr code for brochure | future | QR Codes for Marketing Campaigns |
|
||||
| Print / SMB | Coupon QR Codes | qr code for coupons | future | QR Code Tracking |
|
||||
| Print / SMB | Small Business QR Codes | qr code for small business | existing blog post | Dynamic QR Code Generator |
|
||||
| Business Cards | vCard QR Codes | vcard qr code | existing tool + blog | Dynamic QR Code Generator |
|
||||
| Business Cards | Business Card QR Codes | qr on business card | existing blog post | Dynamic QR Code Generator |
|
||||
| Events | Event QR Codes | qr code for events | existing tool + blog | QR Code Tracking |
|
||||
| Events | Event Ticket QR Codes | qr code for event ticket | future | QR Code Tracking |
|
||||
| Events | Trade Show Booth QR Codes | qr code for trade show booth | future | QR Codes for Marketing Campaigns |
|
||||
| Packaging | Packaging QR Codes | qr code for packaging | future | QR Code Analytics |
|
||||
| Packaging | Product Label QR Codes | qr code for product labels | future | Bulk QR Code Generator |
|
||||
| Packaging | QR Codes for Inserts / Manuals | qr code for product manuals | future | QR Code Analytics |
|
||||
| Real Estate | Real Estate Sign QR Codes | qr code for real estate signs | future | QR Code Tracking |
|
||||
| Real Estate | Property Flyer QR Codes | qr code for property flyers | future | QR Codes for Marketing Campaigns |
|
||||
| Payments | Payment QR Codes | qr code for payment | future | Dynamic QR Code Generator |
|
||||
| Feedback | Feedback QR Codes | qr code for feedback collection | future | QR Code Tracking |
|
||||
|
||||
## 3. Support / authority pages
|
||||
|
||||
| Bucket | Page | Primary cluster | Route status | Notes |
|
||||
|---|---|---|---|---|
|
||||
| Support | Use Cases Hub | qr code use cases | future | Main hub and distribution point |
|
||||
| Support | Dynamic vs Static QR Codes | dynamic vs static qr codes | existing blog post | Supports the wedge education |
|
||||
| Support | QR Code Print Size Guide | qr code print size | existing blog post | Supports print-heavy use cases |
|
||||
| Support | UTM Parameters with QR Codes | utm parameters qr codes | existing blog post | Supports attribution and tracking wedge |
|
||||
| Support | Trackable QR Codes | trackable qr codes | existing blog post | Supports analytics and ROI framing |
|
||||
| Support | Best QR Code Generator Comparison | best qr code generator 2026 | existing blog post | Comparison and alternatives support |
|
||||
|
||||
## Prioritization logic
|
||||
|
||||
Default early `P1` pool:
|
||||
|
||||
1. Dynamic QR Code Generator
|
||||
2. QR Code Tracking
|
||||
3. Restaurant Menu QR Codes
|
||||
4. Flyer QR Codes
|
||||
5. Business Card QR Codes
|
||||
6. Event QR Codes
|
||||
7. Packaging QR Codes
|
||||
8. Use Cases Hub
|
||||
|
||||
Likely early `P2` pool:
|
||||
|
||||
- Bulk QR Code Generator
|
||||
- QR Code Analytics
|
||||
- vCard QR Codes
|
||||
- UTM Parameters with QR Codes
|
||||
- Trackable QR Codes
|
||||
- Small Business QR Codes
|
||||
- Real Estate Sign QR Codes
|
||||
|
||||
Likely `P3` until proof improves:
|
||||
|
||||
- low-intent vanity generators
|
||||
- generic "free QR" comparison pages without wedge fit
|
||||
- pages with weak product proof or unclear CTA path
|
||||
|
||||
# QRMaster Top 30 Backlog
|
||||
|
||||
This is the initial candidate backlog for the first serious QRMaster growth sprint.
|
||||
It is not a promise to build every page immediately; it is the structured pool to score and sequence.
|
||||
|
||||
## 1. Commercial pages
|
||||
|
||||
| Bucket | Page | Primary cluster | Route status | Notes |
|
||||
|---|---|---|---|---|
|
||||
| Commercial | Dynamic QR Code Generator | dynamic qr code generator | existing | Core money page, strongest wedge fit |
|
||||
| Commercial | Bulk QR Code Generator | bulk qr code generator | existing | Strong for teams, labels, events |
|
||||
| Commercial | QR Code Analytics | qr code analytics | existing content / upgrade | Needs stronger SaaS CTA alignment |
|
||||
| Commercial | Custom QR Code Generator | custom qr code generator | existing | Strong for branded print use cases |
|
||||
| Commercial | QR Code Tracking | qr code tracking, trackable qr codes | existing | Bridge between SEO and product proof |
|
||||
| Commercial | QR Codes for Marketing Campaigns | qr code marketing | likely upgrade/new | Important parent for flyer/poster clusters |
|
||||
|
||||
## 2. Use-case pages
|
||||
|
||||
| Cluster | Page | Primary cluster | Route status | Primary commercial parent |
|
||||
|---|---|---|---|---|
|
||||
| Restaurants | Restaurant Menu QR Codes | qr code for restaurant menu | existing blog post | Dynamic QR Code Generator |
|
||||
| Restaurants | Table Ordering QR Codes | qr code for table ordering | future | Dynamic QR Code Generator |
|
||||
| Print / SMB | Flyer QR Codes | qr code for flyer | future | QR Codes for Marketing Campaigns |
|
||||
| Print / SMB | Brochure QR Codes | qr code for brochure | future | QR Codes for Marketing Campaigns |
|
||||
| Print / SMB | Coupon QR Codes | qr code for coupons | future | QR Code Tracking |
|
||||
| Print / SMB | Small Business QR Codes | qr code for small business | existing blog post | Dynamic QR Code Generator |
|
||||
| Business Cards | vCard QR Codes | vcard qr code | existing tool + blog | Dynamic QR Code Generator |
|
||||
| Business Cards | Business Card QR Codes | qr on business card | existing blog post | Dynamic QR Code Generator |
|
||||
| Events | Event QR Codes | qr code for events | existing tool + blog | QR Code Tracking |
|
||||
| Events | Event Ticket QR Codes | qr code for event ticket | future | QR Code Tracking |
|
||||
| Events | Trade Show Booth QR Codes | qr code for trade show booth | future | QR Codes for Marketing Campaigns |
|
||||
| Packaging | Packaging QR Codes | qr code for packaging | future | QR Code Analytics |
|
||||
| Packaging | Product Label QR Codes | qr code for product labels | future | Bulk QR Code Generator |
|
||||
| Packaging | QR Codes for Inserts / Manuals | qr code for product manuals | future | QR Code Analytics |
|
||||
| Real Estate | Real Estate Sign QR Codes | qr code for real estate signs | future | QR Code Tracking |
|
||||
| Real Estate | Property Flyer QR Codes | qr code for property flyers | future | QR Codes for Marketing Campaigns |
|
||||
| Payments | Payment QR Codes | qr code for payment | future | Dynamic QR Code Generator |
|
||||
| Feedback | Feedback QR Codes | qr code for feedback collection | future | QR Code Tracking |
|
||||
|
||||
## 3. Support / authority pages
|
||||
|
||||
| Bucket | Page | Primary cluster | Route status | Notes |
|
||||
|---|---|---|---|---|
|
||||
| Support | Use Cases Hub | qr code use cases | future | Main hub and distribution point |
|
||||
| Support | Dynamic vs Static QR Codes | dynamic vs static qr codes | existing blog post | Supports the wedge education |
|
||||
| Support | QR Code Print Size Guide | qr code print size | existing blog post | Supports print-heavy use cases |
|
||||
| Support | UTM Parameters with QR Codes | utm parameters qr codes | existing blog post | Supports attribution and tracking wedge |
|
||||
| Support | Trackable QR Codes | trackable qr codes | existing blog post | Supports analytics and ROI framing |
|
||||
| Support | Best QR Code Generator Comparison | best qr code generator 2026 | existing blog post | Comparison and alternatives support |
|
||||
|
||||
## Prioritization logic
|
||||
|
||||
Default early `P1` pool:
|
||||
|
||||
1. Dynamic QR Code Generator
|
||||
2. QR Code Tracking
|
||||
3. Restaurant Menu QR Codes
|
||||
4. Flyer QR Codes
|
||||
5. Business Card QR Codes
|
||||
6. Event QR Codes
|
||||
7. Packaging QR Codes
|
||||
8. Use Cases Hub
|
||||
|
||||
Likely early `P2` pool:
|
||||
|
||||
- Bulk QR Code Generator
|
||||
- QR Code Analytics
|
||||
- vCard QR Codes
|
||||
- UTM Parameters with QR Codes
|
||||
- Trackable QR Codes
|
||||
- Small Business QR Codes
|
||||
- Real Estate Sign QR Codes
|
||||
|
||||
Likely `P3` until proof improves:
|
||||
|
||||
- low-intent vanity generators
|
||||
- generic "free QR" comparison pages without wedge fit
|
||||
- pages with weak product proof or unclear CTA path
|
||||
|
||||
|
||||
@@ -1,78 +1,78 @@
|
||||
# QRMaster Tracking Spec
|
||||
|
||||
## Why this exists
|
||||
|
||||
QRMaster growth pages should not be judged by traffic alone.
|
||||
Each page must support a measurable movement into signup or first product value.
|
||||
|
||||
## Core event set
|
||||
|
||||
Required marketing events:
|
||||
|
||||
- `landing_page_viewed`
|
||||
- `cta_clicked`
|
||||
- `signup_started`
|
||||
- `signup_completed`
|
||||
- `login_started`
|
||||
- `login_completed`
|
||||
- `qr_created_first`
|
||||
- `tool_qr_generated` (optional, for free tools)
|
||||
|
||||
## Required properties
|
||||
|
||||
Use these whenever possible:
|
||||
|
||||
- `landing_page_slug`
|
||||
- `page_type`
|
||||
- `cluster`
|
||||
- `use_case`
|
||||
- `cta_label`
|
||||
- `cta_location`
|
||||
- `destination`
|
||||
- `utm_source`
|
||||
- `utm_medium`
|
||||
- `utm_campaign`
|
||||
- `utm_content`
|
||||
|
||||
## Page-type model
|
||||
|
||||
Recommended `page_type` values:
|
||||
|
||||
- `homepage`
|
||||
- `commercial`
|
||||
- `use_case_hub`
|
||||
- `use_case`
|
||||
- `blog_post`
|
||||
- `learn_hub`
|
||||
- `pillar`
|
||||
- `tool`
|
||||
- `auth`
|
||||
|
||||
## Funnel interpretation
|
||||
|
||||
The minimum useful path is:
|
||||
|
||||
`landing_page_viewed -> cta_clicked -> signup_started -> signup_completed -> qr_created_first`
|
||||
|
||||
Use this to answer:
|
||||
|
||||
- which pages bring qualified visitors
|
||||
- which pages push users into signup
|
||||
- which signups actually reach first QR creation
|
||||
|
||||
## Known repo findings from prior QRMaster review
|
||||
|
||||
- PostHog is the real custom-event system.
|
||||
- GA is wired mainly for pageviews.
|
||||
- Cookie consent is client-side via `localStorage['cookieConsent']`.
|
||||
- CTA tracking was previously inconsistent.
|
||||
- Prior analysis suggested likely duplicate pageviews from repeated PostHog/Facebook pixel mounts.
|
||||
|
||||
If you implement tracking later in the QRMaster repo, verify those points again before shipping changes.
|
||||
|
||||
## Decision rules
|
||||
|
||||
- do not create new events that do not support a decision
|
||||
- do not track only clicks without tying them to page context
|
||||
- do not judge SEO pages only by sessions; inspect signup and activation movement too
|
||||
|
||||
# QRMaster Tracking Spec
|
||||
|
||||
## Why this exists
|
||||
|
||||
QRMaster growth pages should not be judged by traffic alone.
|
||||
Each page must support a measurable movement into signup or first product value.
|
||||
|
||||
## Core event set
|
||||
|
||||
Required marketing events:
|
||||
|
||||
- `landing_page_viewed`
|
||||
- `cta_clicked`
|
||||
- `signup_started`
|
||||
- `signup_completed`
|
||||
- `login_started`
|
||||
- `login_completed`
|
||||
- `qr_created_first`
|
||||
- `tool_qr_generated` (optional, for free tools)
|
||||
|
||||
## Required properties
|
||||
|
||||
Use these whenever possible:
|
||||
|
||||
- `landing_page_slug`
|
||||
- `page_type`
|
||||
- `cluster`
|
||||
- `use_case`
|
||||
- `cta_label`
|
||||
- `cta_location`
|
||||
- `destination`
|
||||
- `utm_source`
|
||||
- `utm_medium`
|
||||
- `utm_campaign`
|
||||
- `utm_content`
|
||||
|
||||
## Page-type model
|
||||
|
||||
Recommended `page_type` values:
|
||||
|
||||
- `homepage`
|
||||
- `commercial`
|
||||
- `use_case_hub`
|
||||
- `use_case`
|
||||
- `blog_post`
|
||||
- `learn_hub`
|
||||
- `pillar`
|
||||
- `tool`
|
||||
- `auth`
|
||||
|
||||
## Funnel interpretation
|
||||
|
||||
The minimum useful path is:
|
||||
|
||||
`landing_page_viewed -> cta_clicked -> signup_started -> signup_completed -> qr_created_first`
|
||||
|
||||
Use this to answer:
|
||||
|
||||
- which pages bring qualified visitors
|
||||
- which pages push users into signup
|
||||
- which signups actually reach first QR creation
|
||||
|
||||
## Known repo findings from prior QRMaster review
|
||||
|
||||
- PostHog is the real custom-event system.
|
||||
- GA is wired mainly for pageviews.
|
||||
- Cookie consent is client-side via `localStorage['cookieConsent']`.
|
||||
- CTA tracking was previously inconsistent.
|
||||
- Prior analysis suggested likely duplicate pageviews from repeated PostHog/Facebook pixel mounts.
|
||||
|
||||
If you implement tracking later in the QRMaster repo, verify those points again before shipping changes.
|
||||
|
||||
## Decision rules
|
||||
|
||||
- do not create new events that do not support a decision
|
||||
- do not track only clicks without tying them to page context
|
||||
- do not judge SEO pages only by sessions; inspect signup and activation movement too
|
||||
|
||||
|
||||
Reference in New Issue
Block a user