seo(content): seed contextual /platform/ backlinks from 8 blog posts#19
Merged
Conversation
…avored posts Follow-up to PR #18. The repositioning gave us two landing pages (/ai/ and /platform/) that GSC sees with just 1 impression each over 28 days. PR #18 fixed /ai/ inbound by repointing two blog /mcp/ links; /platform/ had nothing pointing at it from content, only nav and footer. Adds one contextual /platform/ link to the closing paragraph of every blog post whose subject is pure platform / API-gateway material: - api-retirement-done-right (API lifecycle) - authorization-at-the-gateway (CEL/OPA) - beyond-configuration-drift (spec-first compilation) - compliance-by-construction-part-1 (compliance evidence) - compliance-by-construction-part-2 (compliance controls) - how-we-build-our-roadmap (roadmap principles) - one-gateway-many-specs (multi-spec compilation) - strangler-fig-pattern-api-gateway (migration) Anchor text is varied per post topic (platform-teams page, platform team story, capabilities platform teams reach for first, ...) so this does not read as exact-match anchor spam. Each link is on-topic to the post's own subject; nothing was forced into a post where it would not naturally fit. Also swaps one em dash in beyond-configuration-drift's footer for a hyphen, per project preference. The three AI-adjacent posts (what-is-an-mcp-gateway, why-agents-break- where-developers-cope, barbacane-vs-portkey-litellm) already link to /ai/ from PR #18 and are intentionally left alone.
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
1 participant
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.
Summary
Follow-up to #18. Both new landing pages (`/ai/`, `/platform/`) showed 1 GSC impression in 28 days. PR #18 fixed `/ai/` inbound by repointing the two blog `/mcp/` links to `/ai/`. `/platform/` had no inbound from content, only from nav/footer.
This PR adds one contextual `/platform/` link to the closing paragraph of every blog post whose subject is pure platform / API-gateway material:
Anchor text is intentionally varied per post (`platform-teams page`, `platform-team story`, `capabilities platform teams reach for first`, ...) so this does not read as exact-match anchor spam. Each link is on-topic to the post's own subject; no AI/MCP links were forced into platform posts.
The three AI-adjacent posts (`what-is-an-mcp-gateway`, `why-agents-break-where-developers-cope`, `barbacane-vs-portkey-litellm`) already link to `/ai/` from PR #18 and are intentionally left alone.
Also fixes one em dash in `beyond-configuration-drift`'s footer.
Test plan