Add SEO optimization and Schema.org structured data for Fortinet comp… #116
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
…arison page SEO Enhancements: - Update title to include year (2025) for freshness signal - Optimize meta description with focus on FortiGate vulnerabilities - Add TechArticle Schema.org for technical content ranking - Add dynamic FAQPage Schema.org for rich snippets in search results Content Improvements: - Add Key Takeaways section with 4 critical points (Architecture, Resilience, Transparency, Cost) - Standardize product naming throughout: Fortinet (company), FortiGate (appliance), FortiClient (endpoint) - Emphasize FortiGate as specific target of COATHANGER malware (20,000+ devices compromised) - Update Strategic Difference table headers for clarity New Components: - TechArticleJSONLD.astro - Schema.org for technical articles with publication date - FAQPageJSONLD.astro - Dynamic FAQ schema generation from page content Enhanced Sections: - Setup: Distinguish test environment (one-line install) from production (Docker/K8s/Terraform) - Cost: Add mandatory support contracts, link to VPN MFA page - Security: Precise FortiGate vulnerability references with external links to CVE-2024-21762 and Volt Typhoon - FAQ: Add new question about open-source security advantages - Architecture: Update diagram to GitBook hosted image Link Updates: - ACL documentation: Fixed to correct docs.defguard.net/features/access-control-list - MFA link: Added to vpn_mfa page in Cost section - All deployment guides updated with correct paths
Critical SEO Fix: - Move FAQ data from client-side script to server-side frontmatter - Generate Schema.org JSON-LD at build time, not runtime - Ensure search engines always see structured data Benefits: - Search engine crawlers see FAQ schema immediately (no JavaScript required) - Single source of truth for FAQ content in frontmatter - Eliminates fragile DOM parsing logic - No risk of duplicate entries from hardcoded data Implementation: - Define faqEntries array in frontmatter with all Q&A pairs - FAQPageJSONLD.astro now accepts entries prop and renders at build time - FAQ section HTML generated from same faqEntries data using .map() - Supports HTML formatting in answers (links, bold text)
Critical Improvements: - Move all Schema.org generation to server-side (build time) - Add dynamic dates to TechArticle schema (publishedDate, lastUpdated) - Implement stripHtml in FAQPage schema for clean text - Single source of truth: faqEntries in frontmatter Schema.org Components (Production Ready): - TechArticleJSONLD: Now accepts publishedDate and lastUpdated props - FAQPageJSONLD: Server-side only, strips HTML tags for clean schema - Both components render at build time, guaranteed to be crawled SEO Benefits: - Search engines see structured data immediately (no JS execution needed) - Rich snippets for FAQ in Google search results - TechArticle schema improves technical content ranking - Dates provide freshness signals to search engines Content Updates: - Add 'Key Takeaways' to sidebar navigation - Simplify FAQ answers for better readability - Add id='key-takeaways' for anchor navigation - Optimize faqEntries text for Schema.org compliance Testing: - All linter checks passed - No JavaScript required for Schema.org data - FAQ HTML and JSON-LD generated from same data source
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.
…arison page
SEO Enhancements:
Content Improvements:
New Components:
Enhanced Sections:
Link Updates: