SEO: reflect all delivery destinations in site metadata - #26
Merged
Conversation
A Search Console audit showed the site's highest-weight SEO fields still
described Notipus as Slack-only, even though Telegram and Microsoft Teams
now ship as delivery destinations. This left those keywords uncovered and
the copy inaccurate.
- hugo.toml <title> and homepage title: "…for Slack" →
"Payment Alerts for Slack, Telegram & Teams".
- Site + homepage meta description: "enriched Slack notifications" →
"enriched alerts in Slack, Telegram & Microsoft Teams" (also flows into
the Organization / WebSite JSON-LD description).
- FAQ page description: broadened to Slack, Telegram, and Microsoft Teams.
Per-integration page titles ("Stripe Slack Notifications", etc.) are left
as-is: Search Console shows them ranking for exactly those high-intent
queries, so the dedicated-landing-page approach stays.
Verified: hugo --minify renders the new <title>, meta description, OG
title, and Organization schema; bun lint:css / lint:md / format:check
pass. (Local build confirmed with the PostCSS asset step bypassed — the
pre-existing Bun/PostCSS env issue reproduces on clean master and does not
affect CI.)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GMSEWRc8EtJUAeRWEJLw8u
vpetersson
approved these changes
Jul 28, 2026
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.
Summary
A Google Search Console audit (via the read-only service account) found notipus.com is indexed and healthy — every key page returns
PASS / Submitted and indexed, structured data (Organization, WebSite, SoftwareApplication, Product/Offer, FAQPage), canonicals, robots, and OG/Twitter are all present and correct.The one systemic, fixable issue: the site's highest-weight SEO fields still described Notipus as Slack-only, even though Telegram and Microsoft Teams now ship as delivery destinations. That's both inaccurate and leaves the Telegram/Teams keywords uncovered.
Changes
<title>(hugo.toml+ homepage):…Payment Notifications for Slack→Payment Alerts for Slack, Telegram & Teams.enriched Slack notifications→enriched alerts in Slack, Telegram & Microsoft Teams.Deliberately NOT changed
Stripe Slack Notifications,Shopify Slack Notifications,Maxio (Chargify) Slack Notifications) — Search Console shows these ranking for exactly those high-intent queries (stripe slack integration,shopify slack integration), so the dedicated-landing-page approach stays./integrations/showing "unknown to Google" — it's already in the sitemap and linked from the hero, body, and nav, so that's crawl latency from the recent redesign, not a code issue.Verification
hugo --minifyrenders the new<title>, meta description, OG title, and Organization schema description; no Slack-only metadata remains in home/faq/pricing.bun run lint:css/lint:md/format:checkall pass.🤖 Generated with Claude Code