|
| 1 | +# Organic Search Opportunity Map |
| 2 | + |
| 3 | +**Measurement window:** April 27–July 26, 2026 |
| 4 | + |
| 5 | +**Search market:** Google, English-led with localized landing pages |
| 6 | + |
| 7 | +**Primary goal:** Increase non-brand impressions, top-10 rankings, and organic click-through rate |
| 8 | + |
| 9 | +## Search Performance Baseline |
| 10 | + |
| 11 | +Google Search Console reported: |
| 12 | + |
| 13 | +| Metric | Value | |
| 14 | +|---|---:| |
| 15 | +| Clicks | 2 | |
| 16 | +| Impressions | 601 | |
| 17 | +| Click-through rate | 0.3% | |
| 18 | +| Average position | 39.2 | |
| 19 | + |
| 20 | +The strongest existing landing pages were: |
| 21 | + |
| 22 | +| Landing page | Clicks | Impressions | Average position | Opportunity | |
| 23 | +|---|---:|---:|---:|---| |
| 24 | +| `/models` | 1 | 67 | 13.5 | Highest-priority striking-distance page | |
| 25 | +| `/model-providers` | 0 | 16 | 14.3 | Striking-distance category page | |
| 26 | +| `/` | 1 | 46 | 36.3 | Broad discovery page | |
| 27 | +| `/zh-Hant/ides/vscode` | 0 | 108 | 32.6 | High-impression product page | |
| 28 | +| `/ides/kiro` | 0 | 77 | 59.8 | Brand/product content opportunity | |
| 29 | +| `/zh-Hant/vendors/xai` | 0 | 29 | 33.8 | Brand/vendor content opportunity | |
| 30 | + |
| 31 | +## Keyword-to-Landing-Page Map |
| 32 | + |
| 33 | +Search volume is marked `N/A` because no reliable keyword-volume provider was available. Search Console impressions are first-party observations, not monthly search volume. |
| 34 | + |
| 35 | +| Search theme | Observed queries | Intent | Measured signal | Target landing page | Action | |
| 36 | +|---|---|---|---|---|---| |
| 37 | +| AI coding models | `AI coding models`, `LLM for coding`, model names | Commercial investigation | `/models`: 67 impressions, position 13.5 | `/models` | Improve title, description, comparison guidance, and links to model comparison/providers | |
| 38 | +| Model API providers | `model provider`, `LLM API provider` | Commercial investigation | `/model-providers`: 16 impressions, position 14.3 | `/model-providers` | Expand comparison criteria and provider-selection guidance | |
| 39 | +| VS Code with AI | `vscode ai` (69 impressions), `visual code ai ide` (12) | Product discovery | Query positions 24.7 and 19.4 | `/ides/vscode` and localized equivalents | Add AI feature coverage and clarify the relationship between VS Code and AI extensions | |
| 40 | +| Codex CLI | `codex cli` (8 impressions), `codex-cli`, `does codex have a cli` | Navigational and informational | Positions 14.9–16.0 | `/clis/codex-cli` | Add a direct answer, setup overview, supported workflows, and official-source references | |
| 41 | +| Kiro IDE | `aws kiro` (18), `kiro ai` (17), `kiro ide` (13), `kiro aws` (10) | Product discovery | Positions 53.9–68.7 | `/ides/kiro` | Expand AWS/Kiro entity context, use cases, pricing, and comparison links | |
| 42 | +| AI coding tools | `aicoding`, `ai coding stack`, `coding stack` | Broad discovery | Homepage: 46 impressions, position 36.3 | `/` | Target directory and comparison intent in the title and description | |
| 43 | +| AI coding stack | `ai coding stack`, `coding stack` | Category education | Query positions 40.0–53.7 | `/ai-coding-stack` | Keep as the ecosystem/category architecture page to avoid homepage cannibalization | |
| 44 | +| OpenCode | `open code`, `opencode` | Navigational | Positions 9.0–10.0 | Relevant OpenCode detail page | Preserve exact entity naming and strengthen internal links | |
| 45 | + |
| 46 | +## SERP and Content-Gap Findings |
| 47 | + |
| 48 | +For broad commercial searches, current results are dominated by dated, comparison-led pages with a quick answer, consistent evaluation criteria, pricing, best-fit guidance, trade-offs, and a comparison table. Representative results include: |
| 49 | + |
| 50 | +- [Every AI Coding Tool Compared: The 2026 Matrix](https://www.developersdigest.tech/blog/ai-coding-tools-comparison-matrix-2026) |
| 51 | +- [The Best AI Coding Assistants in 2026, Compared](https://daily.dev/blog/best-ai-coding-assistants-comparison/) |
| 52 | +- [The 9 best AI coding tools in 2026](https://zapier.com/blog/ai-coding-tools/) |
| 53 | +- [Best LLM for Coding in 2026: Ranked by Benchmarks](https://www.tembo.io/blog/best-llm-for-coding) |
| 54 | + |
| 55 | +AI Coding Stack has stronger structured catalog data than many editorial competitors, but its category pages provide less decision guidance. The defensible gap is a source-backed comparison layer built on the existing manifests: |
| 56 | + |
| 57 | +1. Define stable comparison criteria for each category. |
| 58 | +2. Explain which fields matter for different workflows. |
| 59 | +3. Link category guidance to the existing comparison tools and verified detail pages. |
| 60 | +4. Publish recommendation content only when the supporting data and methodology are explicit. |
| 61 | + |
| 62 | +## Prioritized Work |
| 63 | + |
| 64 | +| Priority | Work item | Rationale | Status | |
| 65 | +|---|---|---|---| |
| 66 | +| P0 | Remove repeated brand names and excessive examples from page titles | Existing list titles exceed normal snippet length and repeat `AI Coding Stack` | Implemented in working tree | |
| 67 | +| P0 | Optimize `/models` for comparison intent | It is the strongest striking-distance page | Implemented in working tree | |
| 68 | +| P0 | Complete `/models/compare` metadata | The comparison route lacked canonical, hreflang, robots, and complete social metadata | Implemented in working tree | |
| 69 | +| P0 | Reposition homepage metadata around “AI coding tools directory and comparisons” | Aligns the broad landing page with non-brand discovery intent | Implemented in working tree | |
| 70 | +| P1 | Expand `/model-providers` selection guidance | Average position 14.3 indicates near-term potential | Planned | |
| 71 | +| P1 | Expand `/clis/codex-cli` with a direct answer and setup coverage | Multiple queries rank between positions 14.9 and 16.0 | Planned | |
| 72 | +| P1 | Expand `/ides/vscode` for “VS Code AI” intent | Highest observed product-query impressions | Planned | |
| 73 | +| P1 | Expand `/ides/kiro` for AWS/Kiro entity coverage | Multiple related queries already receive impressions | Planned | |
| 74 | +| P2 | Create a source-backed cross-category comparison guide | Broad SERPs reward tested comparison and best-fit guidance | Planned | |
| 75 | + |
| 76 | +## On-Page Audit: `/models` |
| 77 | + |
| 78 | +The baseline score applies the repository's weighted on-page rubric to the production page observed during the measurement period. The working-tree score reflects the implemented metadata and guidance changes; production scoring remains unchanged until deployment. |
| 79 | + |
| 80 | +| Section | Weight | Baseline | Working tree | Finding | |
| 81 | +|---|---:|---:|---:|---| |
| 82 | +| Title tag | 15 | 4 | 14 | Baseline title was long, stale, and repeated the brand; working title is concise and localized | |
| 83 | +| Meta description | 5 | 2 | 5 | Baseline description was too short; working description explains comparison criteria | |
| 84 | +| Header structure | 10 | 8 | 9 | One H1 and lifecycle H2s; working tree adds a descriptive comparison H2 | |
| 85 | +| Content quality | 25 | 12 | 17 | Catalog data is useful; working tree adds decision guidance but is not yet a full editorial guide | |
| 86 | +| Keyword optimization | 15 | 9 | 13 | Working copy covers coding models, context, pricing, lifecycle, providers, and comparison | |
| 87 | +| Internal/external links | 10 | 8 | 9 | Working tree adds contextual links to comparison and provider pages | |
| 88 | +| Image optimization | 10 | 10 | 10 | The catalog does not depend on content images; route-level social imagery is separate | |
| 89 | +| Page-level technical | 10 | 9 | 10 | Canonical and locale alternates remain intact; the comparison destination now receives complete metadata | |
| 90 | +| **Overall** | **100** | **62 (C)** | **87 (A)** | Production changes after the GitHub Actions deployment | |
| 91 | + |
| 92 | +## Measurement Plan |
| 93 | + |
| 94 | +After deployment, compare 28-day periods in Search Console: |
| 95 | + |
| 96 | +- `/models`: impressions, CTR, and average position |
| 97 | +- `/models/compare`: indexed state and query discovery |
| 98 | +- Homepage: non-brand impressions for AI coding tool terms |
| 99 | +- `/clis/codex-cli`, `/ides/vscode`, and `/ides/kiro`: query-level position and CTR |
| 100 | + |
| 101 | +The first decision threshold is movement into positions 4–10 for `/models`. The next content batch should use the first 28 days of post-deployment data rather than assumed keyword volume. |
0 commit comments