Copy updates: pricing, marketing-campaigns page, signup, tool pages
This commit is contained in:
120
CLAUDE.md
120
CLAUDE.md
@@ -259,6 +259,38 @@ ALTER TYPE "ContentType" ADD VALUE 'BARCODE';
|
||||
- Sitemap generation via next-sitemap
|
||||
- Google Indexing API + IndexNow submission scripts available
|
||||
|
||||
## AI SEO / AEO Tracking (AI Answer Engine Visibility)
|
||||
|
||||
Ongoing effort to increase QR Master's presence in AI-generated answers (ChatGPT, Perplexity, AI Overviews, etc.) for QR-code-generator-related queries. Update this section after each audit/build cycle so future sessions build on prior findings instead of re-deriving them.
|
||||
|
||||
### Baseline audit (2026-07-22)
|
||||
|
||||
Query-fanout data (what an AI model searches for while answering a prompt) showed QR Master already being cited in AI-generated answers for 3 of 9 tested query themes: "best QR code generator for marketing campaigns", "QR code generator with analytics and tracking", and "affordable dynamic QR code generator for small business" — positioned as the budget/SMB pick alongside Uniqode, QR TIGER, Bitly, Flowcode, and Hovercode.
|
||||
|
||||
No QR Master citation appeared for: "best dynamic QR code generator 2026", "best QR code generator for businesses", "best QR code generator for agencies", "alternatives to QR TIGER", "QR code generator with unlimited scans", "free dynamic QR code generator unlimited scans".
|
||||
|
||||
Existing on-site AEO infrastructure found during the audit:
|
||||
- `public/llms.txt` present — lists core pages and cornerstone guides for AI retrieval
|
||||
- `/alternatives/` pages exist only for: qr-code-generator.com, Flowcode, Beaconstac, Bitly
|
||||
- `/vs/` pages exist only for: Beaconstac
|
||||
- `/compare/[slug]` dynamic comparison route exists (e.g. `free-vs-paid-qr-code-generator`)
|
||||
- Blog cornerstones: best-qr-code-generator-2026, free-vs-paid-qr-generator, qr-code-tracking-guide-2025, dynamic-vs-static-qr-codes, qr-code-small-business, qr-code-scan-statistics-2026, etc.
|
||||
|
||||
Pattern observed: QR Master gets cited by AI models only where first-party comparison/guide content already exists on the domain. The fanout queries repeatedly run `site:` searches against Uniqode, QR TIGER (qrcode-tiger.com), Hovercode, Scanova, and QRCodeChimp — none of which currently have a matching QR Master alternatives/vs page.
|
||||
|
||||
### Priority backlog (from this audit)
|
||||
1. Build `/alternatives/uniqode`, `/alternatives/qr-code-tiger`, `/alternatives/hovercode` (highest fanout frequency, in that order)
|
||||
2. Build matching `/vs/uniqode`, `/vs/qr-code-tiger`, `/vs/hovercode` (same format as `/vs/beaconstac`)
|
||||
3. New cornerstone guide: "QR code generator for agencies" (white-label, bulk creation, API) — zero QR Master positioning currently exists for this query cluster
|
||||
4. Update `public/llms.txt` once the new pages ship, so they enter the AI retrieval list
|
||||
5. Re-run the same query-fanout test periodically to track citation-rate changes over time
|
||||
|
||||
### Additional confirmed win — "dynamic barcode generator" (2026-07-22, same session)
|
||||
|
||||
Tested outside the original 9-theme set. QR Master is cited as the "Best overall option" for this query — credited for trackable/editable dynamic barcodes, bulk generation, unified analytics, and UTM tracking, plus static EAN-13/UPC-A/Code 128 support when editability isn't needed. The AI answer also included a "requirement → recommended format" decision table (dynamic QR vs. EAN-13/UPC-A vs. Code 128 vs. GS1 Digital Link) that maps closely to existing on-site content.
|
||||
|
||||
This maps directly to the live `/dynamic-barcode-generator` page and `/tools/barcode-generator` tool, reinforcing the pattern above: dedicated first-party pages targeting a query cluster get cited, gaps without dedicated pages don't. Counts as a 4th confirmed positive theme alongside the original 3 from the baseline audit.
|
||||
|
||||
## Deployment Notes
|
||||
|
||||
### Docker (Self-Hosted)
|
||||
@@ -273,47 +305,47 @@ docker-compose exec web npx prisma migrate deploy # Run migrations in container
|
||||
- Requires external PostgreSQL database (Vercel Postgres, Supabase, etc.)
|
||||
- Redis is optional
|
||||
|
||||
## Additional Resources
|
||||
|
||||
- README.md - Detailed setup and feature overview
|
||||
- DOCKER_SETUP.md - Complete Docker deployment guide
|
||||
- prisma/schema.prisma - Database schema and relationships
|
||||
- env.example - Environment variable template
|
||||
|
||||
## gstack (REQUIRED — global install)
|
||||
|
||||
Before doing any AI-assisted work in this repo, verify gstack is installed globally:
|
||||
|
||||
```bash
|
||||
test -d ~/.claude/skills/gstack/bin && echo "GSTACK_OK" || echo "GSTACK_MISSING"
|
||||
```
|
||||
|
||||
If `GSTACK_MISSING`: stop and install it:
|
||||
|
||||
```bash
|
||||
git clone --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack
|
||||
cd ~/.claude/skills/gstack && ./setup --team
|
||||
```
|
||||
|
||||
After install, use gstack skills where appropriate, especially `/browse`, `/review`, `/investigate`, `/qa`, `/ship`, and `/cso`.
|
||||
Use `~/.claude/skills/gstack/...` for gstack file paths because this repo does not vendor the pack locally.
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
## Additional Resources
|
||||
|
||||
- README.md - Detailed setup and feature overview
|
||||
- DOCKER_SETUP.md - Complete Docker deployment guide
|
||||
- prisma/schema.prisma - Database schema and relationships
|
||||
- env.example - Environment variable template
|
||||
|
||||
## gstack (REQUIRED — global install)
|
||||
|
||||
Before doing any AI-assisted work in this repo, verify gstack is installed globally:
|
||||
|
||||
```bash
|
||||
test -d ~/.claude/skills/gstack/bin && echo "GSTACK_OK" || echo "GSTACK_MISSING"
|
||||
```
|
||||
|
||||
If `GSTACK_MISSING`: stop and install it:
|
||||
|
||||
```bash
|
||||
git clone --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack
|
||||
cd ~/.claude/skills/gstack && ./setup --team
|
||||
```
|
||||
|
||||
After install, use gstack skills where appropriate, especially `/browse`, `/review`, `/investigate`, `/qa`, `/ship`, and `/cso`.
|
||||
Use `~/.claude/skills/gstack/...` for gstack file paths because this repo does not vendor the pack locally.
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
|
||||
Reference in New Issue
Block a user