[Ingest] Update title for data ingestion documentation #2842
Conversation
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
🔍 Preview links for changed docs |
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.
Update title to enhance reader scanability and improve SEO.
Scanability
Leadership recently said, "To truly keep a modern enterprise secure, you need to ingest, retain and analyze all data." [emphasis mine]. "Ingest" is a word that users are likely to scan the TOC for as part of a normal workflow, so let's make it easy for them to find.
SEO rankings
Search terms in headings get higher relevance rankings. By removing "ingest" or "ingestion" from the heading, we're missing an opportunity for better rankings.