fix: correct metadata dates, remove draft note, remove duplicate section
- Fixed all 'undefined NaN, NaN' dates in metadata divs across all 22 posts - Removed draft instruction from qr-code-scan-statistics-2026 - Removed duplicate 'Trackable / dynamic QR code' section from trackable-qr-codes - All posts now have proper 'Last updated' dates showing January 26, 2026
This commit is contained in:
Timo Knuth
155
qrmaster-growth-system/references/core-plan.md
Normal file
155
qrmaster-growth-system/references/core-plan.md
Normal file
@@ -0,0 +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
|
||||
|
||||
Reference in New Issue
Block a user