A technical look at how I restructured NythosX so AI crawlers, LLM answer engines, and voice assistants can read and cite it accurately, without changing anything visual.
A growing share of the traffic hitting NythosX now comes from autonomous crawlers and LLMs, not human visitors. OpenAI's GPTBot, Google's various crawlers, Anthropic's ClaudeBot, Amazonbot, Applebot, and others regularly request the site to build or refresh whatever summary they hold of who I am and what I've built. Most of them fetch the raw HTML once and never execute JavaScript, which is a real problem for a single-page React app: without help, they see an almost-empty page shell and nothing else. The first fix was structural. The site used to live at nythosx.pages.dev, and I moved it to the custom domain nythosx.com. Rather than rely on client-side routing that a non-JS crawler ignores, the redirect happens at the edge: a Cloudflare Pages Function checks the request hostname on every hit and issues a real 301 before anything else runs, so crawl weight carries over to the new domain instead of splitting between two. I also went back and fixed every canonical URL, Open Graph tag, and JSON-LD id across the site that still quietly pointed at the old pages.dev domain after the move, along with the sitemap and the robots.txt Sitemap directive. For GEO, the goal is making sure a model that only reads raw HTML still gets an accurate, complete picture instead of guessing from a near-empty shell. The same edge function that handles the redirect also injects a visually hidden text block into every page, sourced live from the same API the React app itself calls, so it can never drift out of sync with the real data. It lists every project with its live, demo, and GitHub links plus results, and a short factual summary of the site's actual features, like the persistent nav, the testimonials section, and the chatbot, so an AI scan doesn't report something as missing just because it can't run the JavaScript that renders it. It uses the standard screen-reader-only CSS clipping technique, not aria-hidden, specifically so assistive tech still gets the same content a sighted visitor does. I also added a proper /about page instead of leaving that URL to 404, since it's one of the first paths both humans and AI profile-builders go looking for, and it pulls its content from the database and is fully editable from the admin panel instead of being hardcoded, so it never goes stale. On top of that, I keep an llms.txt file at the root listing the key pages and project summaries in plain text, a convention some LLM tools are starting to read directly instead of parsing HTML at all. Part of this pass was also just fixing broken identity signals. My GitHub username changed from Antrax-Inhaler to nythosx a while back, and the social link in the site's own settings still pointed at the old one, which would have quietly undermined the entity linking I was trying to build. I also set up a profile repository at github.com/nythosx/nythosx, GitHub's convention for a repo that matches your username and renders as a profile README, so anything resolving the NythosX identity through GitHub lands on something intentional instead of nothing. AEO is about giving answer engines and voice assistants something structured enough to cite directly instead of summarizing a paragraph in their own words. The site carries several separate JSON-LD blocks rather than one bundled graph: a Person node identifying me, with sameAs links to GitHub, LinkedIn, and Facebook pulled live from the same settings the admin panel edits, so they can't drift out of date the way the GitHub link just had; a WebSite node; a CreativeWork entry per project page with its category, tech stack, results, and repository link; an Article entity for posts like this one; and an FAQPage block on the homepage. Keeping them as separate typed nodes rather than one deeply nested structure makes each one easier to validate and easier to extend later without touching the others. To actually check whether any of this was working, I did not want to rely on third-party analytics that might not distinguish bots
A 24/7 market-alert SaaS I designed, coded and shipped solo. It watches crypto, US stocks and forex, explains every chart in plain language, and paper-trades its own signals so its accuracy is proven, not promised.
Category: SaaS / FinTech. Role: Solo developer: product, algorithms, backend, frontend and infrastructure. Tech stack: Cloudflare, JavaScript, SQL, TypeScript.
Key results: 15 markets watched 24/7; Checks every 15 minutes on the edge; Every call graded against real candles; Runs on Cloudflare's free tier; Solo build: idea to production.
Live site: https://market.nythosx.com. Live demo: https://market.nythosx.com/?embed=1.
A B2B GPS field-operations and expense platform built solo across three surfaces: a Laravel + PostgreSQL REST API, a React admin dashboard, and a React Native mobile app. Field workers get geofenced check-ins and automatic mileage tracking, while admins see live team locations and anomaly-flagged activity in real time.
Category: B2B Software. Role: Full Stack Developer. Tech stack: TypeScript, PostgreSQL, Expo, Laravel, MUI, React, React Native.
Key results: Owned every layer solo: a Laravel/PostgreSQL REST API, a React admin dashboard, and a React Native mobile app; Replaced self-reported travel claims with geofenced check-ins and automatic mileage/fare calculation; Real-time team location and anomaly-flagged activity pushed via Laravel Reverb WebSockets; Offline-tolerant mobile check-ins that queue requests when signal drops.
Replaced a legacy PHP system with a Laravel 12 REST API and React frontend to centralize operations for a national organization. Role-based access enforces strict per-role data isolation across 17 distinct roles and 4,000+ users, keeping the dashboard fast even as member records scale into the thousands, and automated navigation streamlined national staff operations by 40%.
Category: Business System. Role: Full Stack Developer. Tech stack: Cloudways, Supabase, Laravel, React.
Key results: 17 distinct user roles; 4,000+ users served with customized portal experiences; Streamlined national staff operations by 40% through centralized management and automated role-based navigation.
Source code (GitHub): https://github.com/nythosx/National-Staff-Management-System-Backend-Laravel-Supabase-.
Modernized legacy HRIS modules into Laravel 12 microservices covering recruitment, placement, and employee health. Recruitment services handle applicant tracking and multi-stage screening, while the health service manages records, vaccinations, and wellness programs, all documented with Swagger.
Category: HRIS. Role: Full Stack Developer / Backend Developer. Tech stack: MySQL, Laravel, React.
Key results: Decomposed a fragile legacy PHP HRIS into independent Laravel 12 microservices for recruitment, placement, and employee health; Isolated sensitive employee health records behind their own service and role-based access control, with no shared blast radius with recruitment logic; Documented every endpoint with Swagger so existing payroll and employee-management systems could integrate against a trusted contract; Replaced legacy modules in production without breaking systems already depending on them.
Source code (GitHub): https://github.com/nythosx/ihris-ms-recruitment.
An anonymous mobile venting app built around a paper-plane metaphor, matching strangers in real time via Socket.io and Redis sorted sets. Field-level AES-256 encryption and AI-powered moderation from Google Vertex AI keep the platform safe, backed by an ethical, non-addictive gamification system.
Category: AI / Mobile. Role: Full Stack Mobile Developer. Tech stack: Google Vertex AI, PostgreSQL, Prisma, Redis, Expo, Express, Node.js, React Native.
Key results: AES-256-GCM field-level encryption for every rant and message, with IP addresses stored as bcrypt hashes rather than plaintext; Two-layer moderation: a synchronous rule-based layer blocking harassment/crisis language instantly, plus an asynchronous Google Vertex AI layer re-scoring ongoing conversations; Real-time matchmaking via Socket.io with Redis sorted sets indexing every live rant; Purely cosmetic ten-tier reward system with no functional gating, keeping appreciation genuine rather than performative.
A Windows desktop app that turns long-form video into TikTok-ready clips: cut, captioned, templated, and uploaded automatically. Its AI runs through a personal DeepSeek chat session instead of a paid API, so there is no per-token cost, and it posts directly through TikTok's real Content Posting API.
Category: AI / Creator Tools. Role: Solo Developer. Tech stack: Rust, TypeScript, React, Tailwind CSS, Tauri.
Key results: Zero per-token AI cost, drives a real, logged-in DeepSeek browser session instead of a paid LLM API; Real TikTok Content Posting API integration with correct chunked upload for large clips; Konva-based visual template editor whose crop/watermark/caption layout is mirrored pixel-for-pixel by the actual FFmpeg render; One-click Auto Upload pipeline: slice → caption → render → queue across every connected account.
Live demo: https://clipflow24.netlify.app/#demo. Source code (GitHub): https://github.com/nythosx/clip-flow.
A free AI coding agent (CLI, Chrome extension, and native host) that runs a planner and executor loop through a logged-in DeepSeek chat session instead of a paid API. The read-only Planner decomposes tasks while the Executor makes changes and verifies them with a real tool call before reporting done.
Category: AI / Developer Tools. Role: Solo Developer. Tech stack: JavaScript, Node.js.
Key results: Zero-API-cost coding agent driven through a real, logged-in DeepSeek chat session instead of a metered LLM API; Planner/Executor separation with no shared context, so every action the Executor takes was explicitly authorized rather than assumed; Executor required to verify its own changes with a real tool call before reporting a task done; Mocked fake-backend of the chat UI enabling local development and testing without touching a live session.
Source code (GitHub): https://github.com/nythosx/deepseek-orchestrator.
A Laravel business system built for a real, operating broiler poultry enterprise in the Philippines. It tracks batches from chick intake to market age, feed and inventory, mortality, sales, and expenses, generating the profitability reports the farm uses for DTI and YEF documentation.
Category: Business System. Role: Solo Developer. Tech stack: PHP, Alpine.js, Laravel, Tailwind CSS.
Key results: Replaced notebooks and scattered spreadsheets with one system tracking a batch of birds from chick intake to market age; Unified feed/inventory, mortality/health, customer/order, delivery, and sales/expense tracking into shared profitability reports; Reports double as DTI and Youth Entrepreneurship Fund financial documentation, exported to PDF via DomPDF; Role-based access via Laravel Breeze and Spatie, built for a non-technical farm manager to trust and use daily.
An unofficial pulse-check survey platform gauging public sentiment ahead of the Philippines' 2028 elections. A deterrence-based fraud-scoring model with device fingerprinting and IP velocity checks protects voting integrity, while a Redis-backed batching layer keeps results updating in real time under load.
Category: Civic Tech. Role: Solo Developer. Tech stack: Vercel, TypeScript, Redis, Supabase, Next.js.
Key results: Deterrence-based fraud-scoring model combining device fingerprinting, IP/ASN velocity checks, and a disposable-email blocklist; Redis-backed batching layer absorbs high-frequency "heart" interactions and flushes to Postgres on a schedule instead of hitting the database per tap; Separate read-cache layer keeps ordinary page views off the primary database; Admin panel for reviewing and correcting the seeded candidate list as the real race clarifies.
A social platform connecting alumni and tracking their career paths geographically in real time via the Google Maps API. Batch-based communication tools and a versioned REST API keep graduates engaged with their institution long after they have left.
Category: Social Platform. Role: Full Stack Developer. Tech stack: MySQL, Inertia.js, Laravel, Vue.js, Google Maps API.
Key results: Real-time geo-tracking of alumni via the Google Maps API; RESTful architecture with proper API versioning; Enhanced alumni engagement through a batch communication system.
Source code (GitHub): https://github.com/nythosx/Alumni-Management-System-with-Social-Media-SaaS.
A multi-tenant agricultural management platform serving multiple farm operators on shared infrastructure with fully isolated data per tenant. AI-powered crop analysis via the Gemini API, live weather forecasting, and geographical farm mapping give each operator real operational insight.
Category: AgriTech. Role: Full Stack Developer. Tech stack: Gemini API, PHP, MySQL, Google Maps API, OpenWeather API.
Key results: Multi-tenant architecture supporting diverse user types; AI-driven crop analysis via the Gemini API; Real-time weather forecasting integration; Geographical farm mapping with Google Maps.
Source code (GitHub): https://github.com/nythosx/-PHP--Multi-Tenant-Crop-Farm-Management-System-with-Integrated-Analytics-and-Mapping-Features.
A full-stack fitness app for meal planning, workout logging, and nutrition analytics, built on ASP.NET Core with a React and TypeScript frontend. Personalized dashboards track calories and progress over time, all secured with JWT authentication.
Category: Full-Stack App. Role: Full Stack Developer. Tech stack: TypeScript, SQL Server, ASP.NET Core, Bootstrap, Entity Framework, React.
Key results: Personalized meal plans; Real-time calorie tracking; Workout logging with progress analytics; Secure JWT authentication.
Source code (GitHub): https://github.com/nythosx/fitness-planner.
A freelance-built HR platform unifying multi-type payroll processing, biometric fingerprint attendance, and a recruitment job portal that auto-generates PDS documents. Built to replace a client's separate, disconnected HR tools with one centralized system.
Category: HRIS. Role: Freelance Full Stack Developer. Tech stack: JavaScript, MySQL, Laravel.
Key results: Multi-type payroll processing; Biometric fingerprint attendance integration; Automated PDS document generation; Centralized employee management.
Source code (GitHub): https://github.com/nythosx/Integrated-HRIS-with-Multi-Payroll-Processing-Biometric-Attendance-and-Recruitment-Portal.