Skip to content

feat(seo/aso): implement semantic entity markup, sitemap, and RAG-optimization#76

Open
rajesh-puripanda wants to merge 1 commit into
coder-zs-cse:mainfrom
rajesh-puripanda:feat/seo-optimization-and-rag-discovery
Open

feat(seo/aso): implement semantic entity markup, sitemap, and RAG-optimization#76
rajesh-puripanda wants to merge 1 commit into
coder-zs-cse:mainfrom
rajesh-puripanda:feat/seo-optimization-and-rag-discovery

Conversation

@rajesh-puripanda

Copy link
Copy Markdown

Description

Implements a comprehensive technical SEO and ASO strategy to maximize shabble.xyz discoverability for search engines and LLM-based RAG agents.

Key Improvements:

  • Semantic Entity Mapping: Added JSON-LD Schema (Game, WebApplication, WebSite, FAQPage) to explicitly define game mechanics and identity for LLMs.
  • Next.js Native Crawlability: Implemented dynamic robots.ts and sitemap.ts to guide search crawlers and LLM indexers efficiently.
  • Metadata & OG Hygiene: Upgraded layout.tsx with robust OG/Twitter tags, canonical URLs, and h1 semantic correction.
  • LLM/RAG Optimization: Added an entity-rich /about page featuring clear value propositions and FAQ structured data, designed to be easily ingested by AI search contexts.
  • Build Integrity: Ensured all changes pass tsc type-checking and project build requirements.

Audit Result

  • Before: No robots.txt, sitemap.xml, or structured data. Client-rendered main context prevented deep crawling.
  • After: Full search-engine compliance with explicit entity definition and machine-readable data structures.

Verification Checklist for Maintainers

  1. Verify robots.txt points to the correct sitemap.xml.
  2. Validate Schema.org structures for Game and FAQPage via Schema Markup Validator.
  3. Confirm crawl accessibility for /daily and /about paths.

Closes #26

@vercel

vercel Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

@rajesh-puripanda is attempting to deploy a commit to the coderzs' projects Team on Vercel.

A member of the Team first needs to authorize it.

@rajesh-puripanda

Copy link
Copy Markdown
Author

Hey @coder-zs-cse ! 👋

Quick follow-up on PR #76 — the SEO/RAG optimization PR I submitted. It's been open for a few days and I wanted to check in on a couple of things:

  1. Vercel Deployment Check It's failing with "Authorization required" — could you authorize the Vercel integration so the check passes?

  2. GSSOC Labels I want to make sure the PR is properly labeled before merging so it counts correctly for GSSOC. Based on the scope (7 files, JSON-LD schemas, sitemap, robots.ts, metadata overhaul, new /about page),

here are labels that would apply:

feature — new SEO/RAG functionality
level: critical— multi-concern work across structured data, Next.js metadata API, and RAG optimization
quality: exceptional — clean, type-checked, follows Next.js conventions
performance / seo / devops — if any of these exist in the repo

No pressure at all — just want to make sure things are set up right before the merge. Happy to make any changes to the PR if needed!

Thanks for your time 🙏

@rajesh-puripanda rajesh-puripanda mentioned this pull request Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SEO and ASO

1 participant