Conversation
…h 1/3) Apply BLUF openings, question-style headings, FAQ sections, and keywords frontmatter to the 7 highest-opportunity Security/SOAR/Compliance pages from the GEO Page Backlog report, to improve AI citation share. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Apply BLUF openings, question-style headings, FAQ sections, and keywords frontmatter to the 8 Cloud SIEM/CSE pages from the GEO Page Backlog report, to improve AI citation share. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…batch 3/3) Apply BLUF openings, FAQ sections, and keywords frontmatter to the 6 Log analytics/Metrics/Manage pages from the GEO Page Backlog report, to improve AI citation share. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…dditions
Rewrite new FAQ headings from first person ("Can I...", "How do I...")
to second person ("Can you...", "How do you...") per style convention,
and rewrite the three renamed section headings from "How do I X?" to
"How to X" to match this repo's GEO heading format.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add GEO Backlog report-matched prompts as FAQ entries on cloud-soar/introduction.md, top up every Security/SOAR/Compliance page to at least 5 FAQ items, and convert genuine overview/concept headings to question form (leaving procedural "Create X" and UI-label headings untouched to match existing site convention). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add GEO Backlog report-matched prompts as FAQ entries on intro-for-analysts.md and about-automation-service-and-cloud-siem.md, top up every Cloud SIEM/CSE page to at least 5 FAQ items, and convert genuine overview/concept headings to question form. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Top up every Log analytics/Metrics/Manage page to at least 5 FAQ items (including a new 5-item FAQ section for product-list-a-l.md, which had none), convert genuine overview/concept headings to question form, and fix the one cross-file anchor reference affected by a heading rename. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Purpose of this pull request
This pull request applies GEO (Generative Engine Optimization) fixes to the 21 pages listed in the Profound "Page Backlog (ranked by opportunity)" report, to improve AI citation share:
cloud-soar/introduction.md,cse/get-started-with-cloud-siem/intro-for-analysts.md, andcse/automation/about-automation-service-and-cloud-siem.mdkeywordsfrontmatter on all 21 pagesNo pages were split or newly created, and no sidebar or redirect changes were made — everything is an in-place edit to existing pages. Page-splitting for the largest pages (
cloud-soar/introduction.md, bothintro-for-*pages,kubernetes.md,metric-query-best-practices.md,cloud-siem-automation-examples.md,sumo-logic-flex-accounts.md,cloud-infrastructure-security-for-aws.md) is deferred to a future follow-up under DOCS-1869.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1869