Skip to content

Add semantic search messaging across landing pages and metadata#96

Merged
jfrench9 merged 2 commits intomainfrom
feature/semantic-search-description
Mar 22, 2026
Merged

Add semantic search messaging across landing pages and metadata#96
jfrench9 merged 2 commits intomainfrom
feature/semantic-search-description

Conversation

@jfrench9
Copy link
Member

@jfrench9 jfrench9 commented Mar 22, 2026

Summary

This PR updates the landing page content, application metadata, and documentation to reflect the introduction of semantic search as a core platform capability alongside existing full-text search. Changes span across 8 files, primarily focused on copy/content updates and metadata revisions to ensure consistent messaging about the new AI-powered search features.

Changes

Documentation

  • README.md: Updated search capability references to include semantic search alongside full-text search.

Metadata & SEO

  • src/app/layout.tsx: Revised application metadata (title, description, Open Graph tags, etc.) for improved clarity and consistency, emphasizing semantic search and AI capabilities.

Landing Page Content Updates

  • FeaturesGrid.tsx: Reworked feature card descriptions to detail both full-text and semantic document search functionalities. Adjusted grid content to better communicate the depth of search capabilities.
  • HeroSection.tsx: Updated hero copy to highlight semantic search as a primary value proposition.
  • ProductOverview.tsx: Revised product overview messaging to reflect the integration of semantic search.
  • IntegrationsSection.tsx: Minor copy adjustment to align with the new search-focused messaging.
  • SECRepositorySection.tsx: Updated SEC repository section to emphasize semantic search over SEC filings and documents.

Pricing

  • src/app/(landing)/pricing/content.tsx: Updated pricing tier descriptions and feature lists to reflect new AI/semantic search capabilities.

Key UI/UX Improvements

  • Consistent messaging: All user-facing landing sections now uniformly communicate the platform's dual search approach (full-text + semantic).
  • Clearer value proposition: The features grid now provides more detailed, descriptive content about document search functionalities rather than generic feature bullets.
  • Improved metadata: Better SEO and social sharing previews through revised Open Graph and meta description content.

Breaking Changes

None. This PR is purely a content and metadata update — no component API changes, no routing changes, and no structural modifications.

Testing Notes for Reviewers

  1. Visual review: Navigate through all landing page sections (Hero, Features Grid, Product Overview, Integrations, SEC Repository, Pricing) and verify copy reads naturally and there are no truncation or layout overflow issues from longer/shorter text.
  2. Metadata verification: Inspect the <head> tag in the rendered HTML to confirm updated <title>, <meta name="description">, and Open Graph tags are correctly applied.
  3. Responsive design: Ensure the updated FeaturesGrid descriptions (net +7 lines of content changes) render correctly across mobile, tablet, and desktop breakpoints — particularly check that card heights remain balanced.
  4. Pricing page: Verify pricing tiers display correctly with the updated feature descriptions and no layout shifts occur.
  5. README: Confirm markdown renders properly on GitHub.

Browser Compatibility Considerations

No concerns — this PR contains only text/content and metadata changes with no new CSS, JavaScript behavior, or DOM structure modifications. All existing browser compatibility remains unchanged.

🤖 Generated with Claude Code

Branch Info:

  • Source: feature/semantic-search-description
  • Target: main
  • Type: feature

Co-Authored-By: Claude noreply@anthropic.com

@jfrench9
Enhance documentation and features overview by updating search capabi…
1afca09 
…lities to include semantic search. Revise metadata for improved clarity and consistency across the application. Update pricing content to reflect new AI capabilities and enhance the FeaturesGrid with detailed descriptions of document search functionalities. Adjust various sections to emphasize the integration of full-text and semantic search across the platform.
@jfrench9
Copy link
Member Author

jfrench9 commented Mar 22, 2026

@claude please review this PR

@claude
Copy link

claude bot commented Mar 22, 2026 •
edited
Loading

Claude finished @jfrench9's task in 1m 4s —— View job

PR Review

  • Gather context and understand request
  • Read changed files
  • Provide review feedback

Summary: Clean, focused content PR. The semantic search messaging is applied consistently across all 8 files. No structural or API changes. A few minor observations below.

✅ What looks good

  • Consistent messaging: Every user-facing surface (hero, features, product overview, integrations, SEC section, pricing FAQ, metadata) now uniformly says "full-text and semantic search". No missed spots.
  • FeaturesGrid new card (FeaturesGrid.tsx:107–157): The new Document Search card is well-structured. Using emerald as the accent color differentiates it visually from the existing cards.
  • Pricing FAQ fix (pricing/content.tsx:82): Correctly removes "RAG-powered search" from the "coming next" list now that it has shipped. Good catch.
  • Metadata keywords (layout.tsx:22–32): Adding "document search", "semantic search", "SEC filings search", and "OpenSearch" while removing "QuickBooks integration" better reflects the current product focus.
  • Hero copy (HeroSection.tsx:50): Changing "semantic memory that persists" → "AI memory that persists" avoids confusion between vector/semantic memory and the search capability. Cleaner.

⚠️ Minor observations

1. Lost feature coverage from removed "Isolated & Organized" card (FeaturesGrid.tsx)

The old card included bullets for "AI memory workspaces and subgraphs" and "One-click backup and restore". These were merged into the "Security & Isolation" card, but neither bullet appears in the new card — the card now focuses on isolation and encryption only. If backups are still a marketed feature, consider adding a bullet to the new Security card or surfacing it elsewhere.

2. Technical jargon on a marketing page (FeaturesGrid.tsx:142)

KNN vector similarity with 384-dim embeddings

"384-dim embeddings" is accurate but unusually specific for a landing page feature card. Consider softening to something like "KNN vector similarity search" or "Dense vector similarity search" unless the intent is to signal technical depth to a developer audience.

3. Long line in SECRepositorySection (SECRepositorySection.tsx:151)

+            semantic search across MD&amp;A, risk factors, and disclosure notes. Subscribe once

The second line runs long (~95 chars). Minor formatting nit — no functional impact.

4. Title SEO trade-off (layout.tsx:16)

"Financial Knowledge Graphs for AI-Powered Intelligence" → "Financial Intelligence Platform" is cleaner but loses keyword specificity. "Knowledge graph" was a differentiating term. If SEO rankings for that term matter, worth monitoring. Not a blocker, just worth being aware of.

Verdict

Approved with minor suggestions. The changes are well-scoped, consistently applied, and improve the accuracy of the product messaging. No bugs, no regressions, no structural risk. The observations above are all optional — none are blockers.

@jfrench9
Refine pricing and SEC repository content for clarity. Adjusted text …
8144e64 
…in the pricing section to improve readability and updated the SEC repository section to enhance the description of market intelligence access. These changes aim to provide a clearer understanding of AI capabilities and subscription benefits.
@jfrench9 jfrench9 merged commit af2fed2 into main Mar 22, 2026
7 checks passed
@jfrench9 jfrench9 deleted the feature/semantic-search-description branch March 22, 2026 06:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jfrench9