fix(public): replace label-only meta descriptions on five trust and support pages - #27
Merged
Merged
Conversation
…upport pages
Five public pages - terms, the Promptly and Drishti support/privacy
pairs - carried thin label-only descriptions ("Support page for Promptly
by Tiny Studio." and similar) that restated the page title without
telling a searcher what the page actually covers.
Replace each with a substantive description drawn from the page's own
copy: what the page covers, the app context (Promptly as the booking and
no-show prevention app, Drishti as the mindful screen time app), and the
practical next step (email route for booking, reminder, payment, and
client-link issues; support, retention, and privacy choices). All stay
under 160 characters, stay truthful to the pre-launch status of the
closed app pages, and keep og:description and twitter:description in
sync. The Promptly privacy JSON-LD description is updated to match so
structured data stays truthful to the page.
verify: npm test; npm run ci; git diff --check
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe pull request expands metadata descriptions for Drishti, Promptly, and the Tiny Studio terms page. It updates standard, Open Graph, Twitter, and Promptly JSON-LD descriptions. ChangesPage metadata updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This was referenced Aug 10, 2026
This was referenced Aug 12, 2026
nish3451
added a commit
that referenced
this pull request
Aug 14, 2026
…ked on missing Cloudflare token (#150) Lane 1 verification report: the five-page meta description fix (PR #27, 9a73040) is already merged to main; live delivery is blocked only by the missing CLOUDFLARE_API_TOKEN secret (NEEDS-NISH, deploy-pipeline item). Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
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
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.
What
Five public pages carried thin, label-only meta descriptions that just restated the page title:
/terms//promptly/support//promptly/privacy//drishti/support//drishti/privacy/Why
Search results for these pages render as bare labels with no description of what the page covers. Every other public page (
/support/,/contact/,/privacy/,/privacy-choices/) already has a substantive description; these five closed/ppages were the gap.Change
Each description is now drawn from the page's own copy — what the page covers, the app context (Promptly = booking and no-show prevention app; Drishti = mindful screen time app), and the practical next step (support email route; data, retention, and privacy choices). All five:
og:descriptionandtwitter:descriptionin sync with the meta descriptiondescriptionto match, so structured data stays truthful to the pageVerify
npm test— all suites pass (0 failures)npm run ci— 0 failuresgit diff --check— clean/promptly/privacy/Summary by CodeRabbit