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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user