aufräumen
This commit is contained in:
48
AI-SEO-CONTENT-PRIORITIES.md
Normal file
48
AI-SEO-CONTENT-PRIORITIES.md
Normal file
@@ -0,0 +1,48 @@
|
||||
# AI SEO Content Priorities
|
||||
|
||||
Last updated: 2026-04-14
|
||||
|
||||
Purpose: prioritize the next content pass after the raw rollout, visible freshness fix, and `llms.txt` expansion.
|
||||
|
||||
## Priority 1
|
||||
|
||||
1. `qr-code-scan-statistics-2026`
|
||||
Reason: strongest citation potential because statistics pages are the easiest source type for LLMs to quote.
|
||||
Next move: verify every stat has a current primary source and an explicit inline citation in the article body.
|
||||
|
||||
2. `qr-code-analytics`
|
||||
Reason: high commercial intent and strong fit for QR Master's differentiation around measurement and ROI.
|
||||
Next move: sharpen answer blocks around scan metrics, dashboards, and campaign decisions.
|
||||
|
||||
3. `qr-code-marketing`
|
||||
Reason: bridges informational and product-intent queries around campaign ROI, CTAs, and tracking.
|
||||
Next move: tighten the first-screen answer and add more comparative guidance for common campaign use cases.
|
||||
|
||||
4. `free-vs-paid-qr-generator`
|
||||
Reason: strong comparison intent and a natural path into dynamic QR, tracking, and upgrade logic.
|
||||
Next move: strengthen side-by-side comparison blocks and source any claims about reliability or limits.
|
||||
|
||||
## Priority 2
|
||||
|
||||
5. `best-qr-code-generator-2026`
|
||||
Reason: "best" queries are heavily represented in AI answers but need balanced, defensible comparisons.
|
||||
Next move: review neutrality, keep claims sourced, and make evaluation criteria more explicit.
|
||||
|
||||
6. `bulk-qr-code-generator-excel`
|
||||
Reason: strong workflow intent and direct fit with a high-value product capability.
|
||||
Next move: improve step extraction and source support for operational best practices where possible.
|
||||
|
||||
7. `qr-code-events`
|
||||
Reason: clear use-case page with practical intent and good overlap with tracking and dynamic QR value.
|
||||
Next move: add stronger answer passages around tickets, check-in, UTMs, and event ROI.
|
||||
|
||||
8. `qr-code-security`
|
||||
Reason: security content earns citations when it is current, specific, and source-heavy.
|
||||
Next move: validate the quishing data points and make safe-deployment recommendations easier to quote.
|
||||
|
||||
## Review Criteria
|
||||
|
||||
- The first 40 to 60 words should answer the core query directly.
|
||||
- Major claims should point to a primary source, not an unsourced assertion.
|
||||
- Comparison and checklist content should prefer tables or tightly structured blocks over long prose.
|
||||
- Posts that support product evaluation should link clearly into the relevant QR Master marketing pages.
|
||||
Reference in New Issue
Block a user