tknuth/QR-master
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

aufräumen

Browse Source
This commit is contained in:
Timo Knuth
2026-04-14 11:21:17 +02:00
parent ff3294291f
commit 82101ca08f
16 changed files with 653 additions and 2737 deletions
Download Patch File Download Diff File Expand all files Collapse all files

419
AI-SEO-TOP5-REWRITE-PLAN.md Normal file
View File

@@ -0,0 +1,419 @@
# AI SEO Top 5 Rewrite Plan
Last updated: 2026-04-14
Method: `ai-seo`
Goal: define the exact AEO/GEO rewrite moves for the five blog posts with the strongest combination of keyword demand, product fit, and AI citation potential.
## 1. `dynamic-vs-static-qr-codes`
File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:707)
### Target queries
- `dynamic qr code`
- `dynamic qr code generator`
- `create dynamic qr code`
- `static qr codes`
- `editable qr code`
### What already works
- Strong `quickAnswer`
- Clear FAQ intent
- Good internal link path into tracking and comparison content
- Sources already exist
### Exact sections to change
1. Replace the opening body paragraph with a direct definition + decision summary.
Current issue: the intro starts with a conversational framing instead of a highly extractable answer block.
Change to: a 40 to 60 word paragraph that answers:
"A static QR code cannot be edited after printing. A dynamic QR code can be updated, tracked, and reused. For business campaigns, menus, and promotions, dynamic QR codes are usually the better choice because they prevent reprints and enable analytics."
2. Add an early comparison table directly after the intro.
New section:
`## Static vs Dynamic QR Code Comparison`
Include rows for:
- editable after printing
- analytics
- best use case
- risk of reprint cost
- ideal for marketing
- ideal for permanent utility use
3. Add a decision section that maps user intent to format choice.
New section:
`## When To Use Static QR Codes`
New section:
`## When To Use Dynamic QR Codes`
Each section should open with a one-sentence answer, then 3 to 5 bullets.
4. Add a cost/risk section.
New section:
`## Why Dynamic QR Codes Save Money`
This should translate product value into a business outcome:
- changed menu URL
- campaign landing page update
- print correction avoidance
5. Expand FAQ to cover high-intent objections.
Add:
- "Are dynamic QR codes worth paying for?"
- "Can a dynamic QR code become inactive?"
- "Is a static QR code ever better than a dynamic one?"
### AEO focus
- Make the first screen answer self-contained.
- Prefer table + decision logic over generic prose.
- Keep the distinction between "editable" and "trackable" explicit in every major section.
### Authority upgrades
- Add at least one explicit sourced statement in the intro or first comparison section.
- Where possible, cite original sources for adoption or tracking claims rather than broad vendor summaries.
### Internal linking
- Link to `/dynamic-qr-code-generator`
- Link to `/qr-code-tracking`
- Link to `/pricing`
- Keep links to `trackable-qr-codes` and `free-vs-paid-qr-generator`
## 2. `qr-code-tracking-guide-2025`
File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:653)
### Target queries
- `qr code tracking`
- `track qr scans`
- `dynamic qr code analytics`
- `google analytics qr`
- `utm qr codes`
### What already works
- High commercial relevance
- Strong `quickAnswer`
- Good `keySteps`
- FAQ already aligned to the query
### Exact sections to change
1. Replace `Why Track QR Codes?` with a sharper query-matching heading.
Rename to:
`## What Is QR Code Tracking?`
The first paragraph should define tracking in one extractable block:
"QR code tracking means measuring what happens after a scan. With a dynamic QR code, you can log scan time, device type, location, and destination performance. If you also add UTM parameters, you can measure campaign attribution in tools like GA4."
2. Split "tracking" and "analytics" clearly.
New section:
`## QR Code Tracking vs QR Code Analytics`
Reason: this is already in the FAQ and deserves a visible answer block because it is highly citable.
3. Add a metrics section with a structured list.
New section:
`## What Metrics Should You Track?`
Use a table with:
- total scans
- unique scans
- scan time
- device type
- location
- landing page conversions
- cost per conversion
4. Add an implementation section for GA4 and UTMs.
New section:
`## How To Track QR Codes In Google Analytics 4`
Keep it procedural:
- create dynamic QR destination
- append UTM parameters
- define conversion event in GA4
- compare placements
5. Add a limitations section.
New section:
`## What QR Tracking Can And Cannot Measure`
This improves trust and helps citation because it sounds more rigorous.
### AEO focus
- The first H2 should match the core query exactly.
- One section should answer "Can I track a static QR code?" before the FAQ.
- Use one metric table instead of only prose.
### Authority upgrades
- Keep Bitly and Google Analytics references, but tighten them around specific claims.
- If scan or attribution claims are broad, attach dates and exact measurement context.
### Internal linking
- Link to `/qr-code-tracking`
- Link to `utm-parameter-qr-codes`
- Link to `qr-code-analytics`
- Link to `/dynamic-qr-code-generator`
## 3. `bulk-qr-code-generator-excel`
File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:759)
### Target queries
- `bulk qr code generator`
- `qr code generator bulk`
- `qr code generator excel`
- `qr codes from excel`
- `csv qr code generator`
### What already works
- Strong workflow intent
- Good step list
- Good FAQ coverage
- Strong product fit for a paid/business feature
### Exact sections to change
1. Rewrite the intro to answer the exact workflow query faster.
Current issue: the intro starts with narrative scale examples before the direct instruction.
Change to:
"To generate bulk QR codes from Excel, prepare a spreadsheet with one row per QR destination, export it as CSV, upload it to a bulk QR generator, and download the generated batch. This is the standard workflow for product labels, badges, inventory, and large campaigns."
2. Add a file format section.
New section:
`## Excel vs CSV: Which Format Do You Actually Need?`
This should explicitly explain that CSV is usually the upload format even when users say Excel.
3. Add a required-column section.
New section:
`## Recommended Spreadsheet Columns`
Use a table:
- `url`
- `label`
- `campaign`
- `utm_source`
- `utm_medium`
- `utm_campaign`
- optional `filename`
4. Add a common-errors section.
New section:
`## Common Bulk QR Upload Errors`
Include:
- broken URLs
- inconsistent columns
- spaces in headers
- mixed protocols
- untested redirect destinations
5. Add a dynamic-vs-static decision block for batches.
New section:
`## Should Bulk QR Codes Be Static Or Dynamic?`
This should explicitly tie bulk use cases to tracking, editing, and reprint risk.
6. Add a QA checklist before production.
New section:
`## Pre-Print Quality Check`
Use a numbered list with 5 to 7 checks.
### AEO focus
- This post should behave like a procedural answer, not a generic guide.
- The column table and error list are likely the most citable parts.
- Make "Excel" and "CSV" relationship explicit because users search for Excel but often need CSV.
### Authority upgrades
- Existing sources are serviceable, but add at least one stronger operational source if available.
- Where no authoritative external source exists, use precise first-party workflow guidance without overclaiming.
### Internal linking
- Link to `/bulk-qr-code-generator`
- Link to `qr-code-print-size-guide`
- Link to `qr-code-tracking-guide-2025`
- Link to `dynamic-vs-static-qr-codes`
## 4. `vcard-qr-code-generator`
File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:504)
### Target queries
- `vcard qr code generator`
- `vcard qr code`
- `vcard generator`
- `vcard qr`
- `create vcard qr code`
### What already works
- Good keyword fit
- Good query-to-tool match
- Strong utility use case
### Exact sections to change
1. Tighten the opening definition.
The first paragraph should answer:
"A vCard QR code stores contact details such as name, phone number, email, company, and website. When someone scans it, they can save the contact directly to their phone without typing."
2. Add a static-vs-dynamic contact section.
New section:
`## Static vs Dynamic vCard QR Codes`
Cover:
- when static is enough
- when dynamic is better
- when tracking matters
3. Add a field breakdown section.
New section:
`## What Information Can A vCard QR Code Include?`
Use a compact list or table:
- full name
- phone
- email
- company
- job title
- website
- address
- social profile
4. Add a use-case section.
New section:
`## Best Use Cases For vCard QR Codes`
Examples:
- business cards
- trade shows
- packaging inserts
- storefronts
- service professionals
5. Add a scannability and contact-save section.
New section:
`## Best Practices For High Save Rates`
Focus on CTA language:
- scan to save contact
- add me instantly
- connect without typing
### AEO focus
- Treat this as a definitional + use-case post, not just a tool page.
- The definition block and field list are the most important extractable components.
### Authority upgrades
- If current sources are weak or missing, add at least one standards-oriented or platform-oriented source.
- Avoid unsupported claims around conversion unless sourced.
### Internal linking
- Link to the vCard tool page
- Link to `business-card-qr-code`
- Link to `dynamic-vs-static-qr-codes`
- Link to `/pricing` if dynamic/contact-management features are relevant
## 5. `qr-code-print-size-guide`
File reference: [src/lib/blog-data.ts](/abs/path/C:/Users/a931627/Documents/QRMASTER/src/lib/blog-data.ts:604)
### Target queries
- `minimum qr code size`
- `qr code print size`
- `qr code size guide`
- `qr code scanning distance`
### What already works
- Very strong query structure
- Excellent snippet potential
- Good `quickAnswer`
- Good FAQ fit
### Exact sections to change
1. Keep the 10:1 rule, but make it the first body paragraph in exact answer form.
Suggested phrasing:
"The standard starting rule for QR print size is 10:1: the code should be about one-tenth of the expected scanning distance. A QR code scanned from 2 meters away should usually be around 20 centimeters wide."
2. Add a distance-to-size table immediately after the intro.
New section:
`## QR Code Size Chart By Scanning Distance`
Include examples for:
- 20 cm
- 50 cm
- 1 m
- 2 m
- 5 m
3. Add format-specific minimums.
New section:
`## Minimum QR Code Sizes For Common Print Formats`
Use rows for:
- business card
- flyer
- poster
- packaging
- menu stand
- window signage
4. Add a density warning section.
New section:
`## Why More Data Requires A Larger QR Code`
Cover:
- long URLs
- vCard payloads
- WiFi payloads
- error correction tradeoffs
5. Add a print-production checklist.
New section:
`## Print Checklist Before You Go Live`
Include:
- SVG preferred
- 300 DPI minimum for raster
- quiet zone intact
- strong contrast
- test in real lighting
- test with average phones, not only flagship devices
### AEO focus
- This post should be built around tables and formulas, not narrative.
- The size chart is likely the strongest snippet and AI Overview asset.
- Keep measurements concrete and example-heavy.
### Authority upgrades
- If possible, support the 10:1 rule with an external reference or state it clearly as an operational best-practice baseline.
- Avoid over-precision if it is based on heuristics rather than a standard.
### Internal linking
- Link to `business-card-qr-code`
- Link to `qr-code-restaurant-menu`
- Link to `bulk-qr-code-generator-excel`
- Link to relevant tool or generator pages
## Execution Order
1. `dynamic-vs-static-qr-codes`
2. `qr-code-tracking-guide-2025`
3. `bulk-qr-code-generator-excel`
4. `qr-code-print-size-guide`
5. `vcard-qr-code-generator`
## Acceptance Criteria
- The first paragraph on each post answers the target query directly.
- Each post includes at least one visibly structured block that is easy to quote:
table, checklist, comparison block, or metric summary.
- Claims that imply data, performance, or market adoption are tied to a source.
- The post clearly routes users into the relevant QR Master product or feature page.