SEO Fixes: CyberWorld Builders — 2026-03-20#232
Closed
jaylong255 wants to merge 4 commits intomainfrom
Closed
Conversation
Affects 1 pages. Auto-fix by GusClaw SEO pipeline.
Affects 15 pages. Auto-fix by GusClaw SEO pipeline.
Affects 30 pages. Auto-fix by GusClaw SEO pipeline.
Affects 1 pages. Auto-fix by GusClaw SEO pipeline.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
gus-adastra
pushed a commit
that referenced
this pull request
Apr 6, 2026
Consolidates all open SEO fix PRs into a single clean branch against current main. Accessibility: - All Image alt="" replaced with descriptive alt text (BlogPostList, ServiceCard, ServicePageLayout, MetaServicePageLayout, TerminalWhisper) Structured data: - Blog post schema datePublished/dateModified now ISO 8601 format - Blog index CollectionPage schema gains datePublished - Tag page schema gains datePublished - Tags index page gains CollectionPage schema - Semantic <time> elements for published/updated dates Crawlers: - robots.ts: AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) get explicit allow rules - /cdn-cgi/ added to disallow for all user agents Performance: - ServiceCard gains priority prop, services index passes priority for LCP images Freshness signals: - Blog index shows "Last updated" with <time> element - Tag pages show "Updated" date when modifiedDate differs from publishedDate - modifiedDate threaded through blog index data pipeline Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6 tasks
jaylong255
added a commit
that referenced
this pull request
Apr 6, 2026
* SEO: unified fixes from PRs #232, #237, #249, #262 Consolidates all open SEO fix PRs into a single clean branch against current main. Accessibility: - All Image alt="" replaced with descriptive alt text (BlogPostList, ServiceCard, ServicePageLayout, MetaServicePageLayout, TerminalWhisper) Structured data: - Blog post schema datePublished/dateModified now ISO 8601 format - Blog index CollectionPage schema gains datePublished - Tag page schema gains datePublished - Tags index page gains CollectionPage schema - Semantic <time> elements for published/updated dates Crawlers: - robots.ts: AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) get explicit allow rules - /cdn-cgi/ added to disallow for all user agents Performance: - ServiceCard gains priority prop, services index passes priority for LCP images Freshness signals: - Blog index shows "Last updated" with <time> element - Tag pages show "Updated" date when modifiedDate differs from publishedDate - modifiedDate threaded through blog index data pipeline Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * update featured posts to reflect current content strategy Replace stale Oct 2025 / early March featured posts with recent high-value content that aligns with service offerings (AI agents, cloud infra, custom SaaS). Featured: - What a $100K Employee Costs Me Now (business case for AI) - I Saved a Client $5K/Year on AWS (client proof) - Why My AI OS Survived Anthropic's Harness Lockdown (thought leadership) - Agent Specialists Changed How I Build Software (methodology) - Why Assembling Freelancers Kills Web Projects (sales positioning) - Software Engineers Got Disrupted First (industry insight) - One Week with Claude Code (capability showcase) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * update services section to match current market demand Based on Upwork data (3,156 jobs): AI Agent Development is now a distinct skill (36 mentions), Claude appears by name (21), n8n declining relative to direct agent work. GEO not yet mainstream on Upwork = early differentiator. - Digital Marketing → Digital Marketing & SEO (add GEO, AI Search Readiness tags) - Automation → Custom AI Agents (lead with agents, drop n8n from headline) - Custom SaaS → Custom SaaS & MVPs (add Supabase, AWS & DevOps tags) - Descriptions rewritten to match how buyers are searching Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <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.
SEO Fixes: CyberWorld Builders
Generated by GusClaw SEO auto-fixer on 2026-03-20 04:46.
This PR modifies AI crawler rules in
robots.txt(or its dynamic equivalent).Why: Allowing AI crawlers (GPTBot, ClaudeBot, PerplexityBot) enables your
content to appear in AI search results and chatbot citations.
Risk: If you have proprietary content you don't want AI models training on,
review the specific rules before merging. Most public-facing marketing/blog
sites benefit from AI crawler access.
Auto-Applied Changes
app/robots.tscomponents/BlogPostList.tsxcomponents/MetaServicePageLayout.tsxcomponents/ServiceCard.tsxcomponents/ServicePageLayout.tsxcomponents/TerminalWhisper.tsxapp/blog/[slug]/page.tsxapp/blog/page.tsxapp/blog/tag/[tag]/page.tsxapp/services/ServicesIndexContent.tsxcomponents/ServiceCard.tsxManual Tasks (cannot be automated)
Page returned HTTP 404.
Action: Fix or remove broken link (verify intended URL)
Outbound link to https://www.upwork.com/freelancers/jaylongcyberworld returned HTTP 403.
Action: Fix or remove broken outbound link
Outbound link to https://twitter.com/intent/tweet?text=Chatbot%20Breakthrough%3A%20How%20OpenAI's%20Web%20Crawling%20Validates%20Generative%20SEO%20for%20Smarter%20Site%20Interactions&url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Fchatbot-breakthrough-how-openais-web-crawling-validates-generative-seo-for-smarter-site-interactions&via=cyberbuilders returned HTTP 403.
Action: Fix or remove broken outbound link
Outbound link to https://twitter.com/intent/tweet?text=Everything%20Compounds%20Now&url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Feverything-compounds-now&via=cyberbuilders returned HTTP 403.
Action: Fix or remove broken outbound link
Outbound link to https://reddit.com/submit?url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Ffirst-pitch-meeting-reflections-lessons-confidence-and-alignment-in-death-care-and-ar-innovation&title=First%20Pitch%20Meeting%20Reflections%3A%20Lessons%2C%20Confidence%2C%20and%20Alignment%20in%20Death%20Care%20and%20AR%20Innovation returned HTTP 404.
Action: Fix or remove broken outbound link
Outbound link to https://reddit.com/submit?url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Ffirst-real-outage-autonomous-systems&title=My%20First%20Real%20Outage%20and%20What%20It%20Taught%20Me%20About%20Autonomous%20Systems returned HTTP 404.
Action: Fix or remove broken outbound link
Outbound link to https://reddit.com/submit?url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Ffrom-hybrid-intel-trio-to-drum-note-evolving-ai-human-synergy-in-music-collaboration&title=From%20Hybrid%20Intel%20Trio%20to%20Drum%20Note%3A%20Evolving%20AI-Human%20Synergy%20in%20Music%20Collaboration returned HTTP 404.
Action: Fix or remove broken outbound link
Outbound link to https://reddit.com/submit?url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Ffrom-zapier-to-n8n-automation-practice&title=From%20Zapier%20to%20n8n%3A%20Why%20I'm%20Building%20an%20Automation%20Practice returned HTTP 404.
Action: Fix or remove broken outbound link
Outbound link to https://reddit.com/submit?url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Fone-week-claude-code-publishing-pipeline&title=One%20Week%20with%20Claude%20Code%3A%20Building%20an%20AI-Powered%20Publishing%20Pipeline returned HTTP 404.
Action: Fix or remove broken outbound link
Outbound link to https://reddit.com/submit?url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Fstop-nickel-and-diming-ai-tools-go-all-in&title=Stop%20Nickel-and-Diming%20Your%20AI%20Tools%20and%20Go%20All%20In returned HTTP 404.
Action: Fix or remove broken outbound link
Outbound link to https://twitter.com/intent/tweet?text=What%20Crawling%20Upwork%20Every%20Day%20Taught%20Me%20About%20Where%20to%20Go%20Next&url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Fupwork-automation-strategy-insights&via=cyberbuilders returned HTTP 403.
Action: Fix or remove broken outbound link
Outbound link to https://twitter.com/intent/tweet?text=Where%20I'm%20Going%20Next&url=https%3A%2F%2Fcyberworldbuilders.com%2Fblog%2Fwhere-im-going-next&via=cyberbuilders returned HTTP 403.
Action: Fix or remove broken outbound link
Outbound link to https://www.cloudflare.com/sign-up?utm_source=email_protection returned HTTP 403.
Action: Fix or remove broken outbound link
Page has 6 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page has 6 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page has 6 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page has 6 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page has 5 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page has 7 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page has 9 subheadings but none are question-based. AI engines favor Q&A-style headers that match user queries.
Action: Rewrite H2/H3 headings as questions users would ask
Page found by crawler but not in sitemap.xml.
Action: Review: Page found by crawler but not in sitemap.xml.
Missing Content-Security-Policy header. Prevents XSS and data injection attacks.
Action: Review: Missing Content-Security-Policy header. Prevents XSS and data injection attacks.
Missing Permissions-Policy header. Controls browser feature access (camera, mic, geolocation).
Action: Review: Missing Permissions-Policy header. Controls browser feature access (camera, mic, geolocation).
HTTP→HTTPS redirect uses 308 instead of 301. Use 301 for SEO link equity transfer.
Action: Review: HTTP→HTTPS redirect uses 308 instead of 301. Use 301 for SEO link equity transfer.
Duplicate meta description shared with 1 other page(s).
Action: Write unique meta descriptions for each page
Duplicate meta description shared with 1 other page(s).
Action: Write unique meta descriptions for each page
Duplicate title "Custom Software, AI Automation & Web Development | CyberWorld Builders" shared with 1 other page(s).
Action: Write unique titles for each page
Duplicate title "Custom Software, AI Automation & Web Development | CyberWorld Builders" shared with 1 other page(s).
Action: Write unique titles for each page
Content-heavy page (843 words) has no H2 subheadings. Break content into sections for better AI parsing.
Action: Break long content into H2 sections
Content page has only 123 words. AI engines prefer comprehensive content (500+ words) with depth on the topic.
Action: Expand page content to 500+ words with depth
Page has noindex directive: noindex, nofollow
Action: Review noindex directive — is this intentional?
After merging, re-run
gus seo auditto verify fixes.