212 lines
5.5 KiB
Markdown
212 lines
5.5 KiB
Markdown
# QRMaster SEO Sprint Machine
|
|
|
|
## Goal
|
|
|
|
Run a weekly controlled SEO sprint that chooses the right pages, creates or
|
|
updates them, adds internal links, and ships through a reviewed PR.
|
|
|
|
## Why This Exists
|
|
|
|
QRMaster should not publish random daily content. The goal is to build
|
|
commercially useful SEO clusters around dynamic QR codes, tracking, tool pages,
|
|
comparison pages, and industry workflows.
|
|
|
|
## Plugins And Skills
|
|
|
|
| Need | Use |
|
|
|---|---|
|
|
| Repository changes and PRs | GitHub plugin |
|
|
| Keyword and performance imports | Coupler, CSV exports, Google Search Console export |
|
|
| Page creation and refactors | Codex |
|
|
| SEO/content planning | `content-strategy`, `ai-seo` skills |
|
|
| Copy generation | `copywriting` skill |
|
|
| Verification | GitHub Actions, `qa` skill |
|
|
|
|
## Weekly Inputs
|
|
|
|
- Current keyword backlog:
|
|
- `marketing/programmatic-seo-top-50.md`
|
|
- `marketing/keyword-strategy-seo-plan.md`
|
|
- `seo-keywords.csv`
|
|
- Existing product positioning:
|
|
- `.agents/product-marketing-context.md`
|
|
- Performance data when available:
|
|
- Google Search Console export
|
|
- signup/conversion report
|
|
- top landing pages by traffic
|
|
- Sprint focus:
|
|
- Dynamic QR
|
|
- Tracking/analytics
|
|
- Restaurant/menu QR
|
|
- Print marketing
|
|
- Bulk QR
|
|
- Comparison/alternatives
|
|
|
|
## Scoring Model
|
|
|
|
Score each candidate from 0-100:
|
|
|
|
| Factor | Weight |
|
|
|---|---:|
|
|
| Product fit | 30 |
|
|
| Commercial intent | 25 |
|
|
| Differentiation potential | 15 |
|
|
| Cluster leverage | 10 |
|
|
| Search winability | 10 |
|
|
| Production effort | 10 |
|
|
|
|
Do not select pages only because they have volume. Prefer pages where QRMaster
|
|
can naturally sell dynamic QR, scan tracking, bulk creation, or privacy-first
|
|
analytics.
|
|
|
|
## On-Page And Agentic Search Rules
|
|
|
|
Every new or refreshed page must follow these checks before review:
|
|
|
|
- Identify the primary keyword and intent type: informational, commercial,
|
|
transactional, or navigational.
|
|
- Cover the query fan-out: list the related subtopics an AI/search system would
|
|
need to answer the query well.
|
|
- Put the primary keyword naturally near the start of the title tag and H1.
|
|
- Keep title tags under roughly 60 characters when possible.
|
|
- Keep meta descriptions concise, benefit-led, and naturally keyword-aligned.
|
|
- Use one clear H1 and a logical H2/H3 hierarchy.
|
|
- Start each section with a direct answer to the heading.
|
|
- Use short paragraphs, bullets, and comparison tables where they improve
|
|
scanning and AI extraction.
|
|
- Add descriptive internal links with natural anchor text.
|
|
- Add useful visuals, screenshots, or examples where the page needs them.
|
|
- Add schema when the page type supports it.
|
|
- Check mobile readability, CTA tap targets, and obvious speed risks.
|
|
- Verify robots/indexing assumptions for important SEO pages.
|
|
|
|
## Default Weekly Sprint
|
|
|
|
1. Select one cluster.
|
|
2. Create 3 new pages.
|
|
3. Refresh 2 existing pages with impressions, weak CTR, or position 8-20.
|
|
4. Add internal links in both directions.
|
|
5. Create one GitHub PR.
|
|
6. Run `qrmaster-pr-seo-review.md`.
|
|
7. Produce social and outreach drafts after the PR is ready.
|
|
|
|
## Page Types
|
|
|
|
### Tool Pages
|
|
|
|
Examples:
|
|
|
|
- `/tools/pdf-qr-code`
|
|
- `/tools/vcard-qr-code`
|
|
- `/tools/wifi-qr-code`
|
|
- `/tools/menu-qr-code`
|
|
- `/tools/google-review-qr-code`
|
|
|
|
Must include:
|
|
|
|
- direct tool-oriented hero
|
|
- use cases
|
|
- dynamic vs static guidance
|
|
- FAQ
|
|
- CTA into the app
|
|
- internal links to related use cases
|
|
|
|
### Industry Workflow Pages
|
|
|
|
Examples:
|
|
|
|
- `/qr-code-for/restaurants/menu-updates`
|
|
- `/qr-code-for/events/check-in`
|
|
- `/qr-code-for/real-estate/open-house-flyers`
|
|
|
|
Must include:
|
|
|
|
- specific audience pain
|
|
- example workflow
|
|
- print-risk or tracking angle
|
|
- CTA matching the industry
|
|
|
|
### Comparison Pages
|
|
|
|
Examples:
|
|
|
|
- `/compare/dynamic-vs-static-qr-codes`
|
|
- `/compare/free-vs-paid-qr-code-generator`
|
|
- `/compare/flowcode-alternative`
|
|
|
|
Must include:
|
|
|
|
- comparison table
|
|
- fair positioning
|
|
- current facts verified before publishing
|
|
- "who this is best for" section
|
|
- CTA to the best-fit QRMaster feature
|
|
|
|
## Codex Sprint Prompt
|
|
|
|
```text
|
|
Run the QRMaster SEO Sprint Machine.
|
|
|
|
Use:
|
|
- docs/automations/qrmaster-seo-sprint-machine.md
|
|
- docs/automations/qrmaster-pr-seo-review.md
|
|
- .agents/product-marketing-context.md
|
|
- marketing/programmatic-seo-top-50.md
|
|
- marketing/keyword-strategy-seo-plan.md
|
|
|
|
Sprint focus: [cluster]
|
|
Target output: 3 new SEO/tool pages, 2 page refreshes, internal links, and one PR-ready diff.
|
|
|
|
Rules:
|
|
- Follow existing code and page patterns.
|
|
- Do not invent competitor pricing or claims.
|
|
- Prioritize dynamic QR, edit-after-print, analytics, bulk, and privacy-first messaging.
|
|
- Add metadata, FAQ/schema where local patterns support it.
|
|
- Apply the on-page and agentic search rules from the automation doc.
|
|
- Keep pages specific enough to avoid thin programmatic content.
|
|
- Run build/lint or explain why not.
|
|
|
|
Return:
|
|
1. selected pages and scoring
|
|
2. target keyword, intent, and fan-out subtopics per page
|
|
3. files changed
|
|
4. internal links added
|
|
5. PR summary
|
|
6. SEO review status
|
|
7. follow-up social/outreach package
|
|
```
|
|
|
|
## Sprint Output Template
|
|
|
|
```markdown
|
|
# QRMaster SEO Sprint: [Cluster]
|
|
|
|
## Selected Work
|
|
| Type | URL | Score | Reason |
|
|
|---|---|---:|---|
|
|
|
|
## Keyword Intent And Fan-Out
|
|
|
|
| URL | Primary keyword | Intent | Fan-out subtopics |
|
|
|---|---|---|---|
|
|
|
|
## New Pages
|
|
|
|
## Updated Pages
|
|
|
|
## Internal Links
|
|
|
|
## PR Summary
|
|
|
|
## Verification
|
|
|
|
## Social/Outreach Follow-Up
|
|
```
|
|
|
|
## Success Criteria
|
|
|
|
- Each new page has clear commercial intent or cluster leverage.
|
|
- Refreshed pages have a measurable reason for the update.
|
|
- Internal links support money pages.
|
|
- PR SEO Review passes before merge.
|