feat(seo): competitor comparison pages batch 2 (PRD follow-on) - #79
Open
aleexwong wants to merge 1 commit into
Open
feat(seo): competitor comparison pages batch 2 (PRD follow-on)#79aleexwong wants to merge 1 commit into
aleexwong wants to merge 1 commit into
Conversation
Ships the "Part 2" follow-on from PRD_COMPETITOR_COMPARISON_SEO.md §10 — five more config-only PSEO comparison landings, extending coverage from paid-app competitors into VDOT calculators, device ecosystems, and training-log platforms: - trainpace-vs-vdot-o2 -> /vdot - trainpace-vs-mcmillan-running-calculator -> /calculator - trainpace-vs-garmin-coach -> /plan - trainpace-vs-nike-run-club -> /plan - trainpace-vs-final-surge -> /plan Each is a single SeoPageConfig appended to calculatorSeoPages, so routing, prerendering, and the sitemap pick them up automatically. Fair, factual positioning per the PRD guardrails; distinct intro/bullets/FAQ per page. Verification: npm run build (tsc + prerender, all 5 render to static HTML with correct title/meta/H1/canonical) and npm run lint pass clean; sitemap regenerated (255 urls); validateAllPages reports avg score 95, all pages valid, 0 duplicates, 0 broken links, no new cannibalization. PRD §10 updated to record batch 2 as shipped. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013AuUXYd2ZC4r5EjRMmoxTt
✅ Deploy Preview for trainpace ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ships the "Part 2" follow-on from PRD_COMPETITOR_COMPARISON_SEO.md §10 —
five more config-only PSEO comparison landings, extending coverage from
paid-app competitors into VDOT calculators, device ecosystems, and
training-log platforms:
Each is a single SeoPageConfig appended to calculatorSeoPages, so routing,
prerendering, and the sitemap pick them up automatically. Fair, factual
positioning per the PRD guardrails; distinct intro/bullets/FAQ per page.
Verification: npm run build (tsc + prerender, all 5 render to static HTML
with correct title/meta/H1/canonical) and npm run lint pass clean; sitemap
regenerated (255 urls); validateAllPages reports avg score 95, all pages
valid, 0 duplicates, 0 broken links, no new cannibalization.
PRD §10 updated to record batch 2 as shipped.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_013AuUXYd2ZC4r5EjRMmoxTt