Selected work
Technical SEO and automation in practice.
Explore dated SEO results and automation outputs, with the screenshots, methods, and limits behind each one.
01SEO experiments
Source changes. Dated results.
Experiments on floxolab.com, with the method and the boundary of each measurement.
Source auditTechnical SEO audit with GPT-6 Astra
10 code-confirmed priorities
Findings checked in the FloxoLab source and implemented in the recorded September 5, 2026 release.
Recorded experiment; derived findings map
GPT-6 Astra · source review · regression checks
Read the experiment ↗
Performance experimentCore Web Vitals, fixed in the code
77 → 98 mobile Lighthouse performance score
FloxoLab’s July 2026 PageSpeed Insights lab result and the source changes behind it. Lab scores do not establish field CWV.
Dated lab measurement; July 2026
PageSpeed Insights · Lighthouse · site source
Read the experiment ↗
Search measurementAI search citations, measured by page
About 6.4K citations for one filtered page
Bing AI Performance activity from August 14–29, 2026. A citation count for one page, not a ranking or traffic.
Recorded observation; derived evidence diagram
Bing AI Performance · Search Console
Read the experiment ↗02Automation builds
A draft, a record, an answer, or a listing.
Choose the output closest to your task, then inspect the documented inputs and review requirements.
Sales outreachLead outreach drafts with n8n
Reviewed draft queue with done and blocked rows
Turn public company information into a short outreach draft. Review the research and message in Airtable before sending.
Demo screenshots
n8n · Airtable · Groq · DeepSeek
View the build ↗
Lead intakeForm and AI chat intake with n8n
Lead record, private alert, and map email
Capture the details needed to route an enquiry. Compare the simple form path with an AI chat path and the handoff to a reviewer.
Demo screenshots
n8n · Groq · Notion
View the build ↗
Email operationsAI email routing with n8n
Defined email routes with validation and review
Sort incoming messages into defined routes and keep uncertain classifications visible. The walkthrough separates the demo from production checks.
Workflow walkthrough
n8n · Gmail · Groq · Sheets
View the build ↗
Internal knowledgeSlack knowledge bot with n8n
Answers retrieved from documents with source references
Retrieve answers from approved documents in Slack. Inspect the source references and how low-confidence questions are handled.
Demo screenshots
n8n · Drive · Qdrant · Slack
View the build ↗
Ecommerce operationsProduct photo to WooCommerce listing
Photo converted into a WooCommerce listing
Turn a product image into a listing that someone can review. The case explains demo defaults and which product facts need a trusted source.
Demo listing; product facts require review
n8n · Telegram · WooCommerce
View the build ↗03Technical builds
Alerts, infrastructure, and an internal assistant.
Documented configurations and workflow paths, with setup and operating responsibilities.
ReliabilityWebsite uptime monitoring with n8n
Scheduled status check and private alert path
Inspect a scheduled website check and its alert path. The walkthrough also covers what to verify when an alert fires and how to reduce misleading alerts.
Workflow walkthrough
n8n · HTTP · Telegram
View the build ↗
InfrastructureSelf-hosted n8n deployment
Self-hosted n8n behind a secure HTTPS endpoint
Review the documented deployment using Docker, PostgreSQL, and Cloudflare. Use its setup, access, backup, and maintenance questions to scope your own environment.
Configuration screenshots
Docker · PostgreSQL · Cloudflare
View the build ↗
Internal AISelf-hosted Hermes Agent with Telegram
Installed assistant with Telegram and persistent memory
Explore the documented self-hosted assistant and its Telegram interface. Check access controls, persistent memory, and the setup limitations before adapting it.
Installation screenshots; July 18, 2026 recheck
Hermes · Telegram · model API
View the build ↗04Compare the pattern
Read the workflow from input to handoff.
A useful comparison records what is transferable to your process and what needs a different rule, test, or connection.
- 01Input and trigger
What starts the workflow? Check the required fields, source of truth, and handling of incomplete input.
- 02Rules and routing
Follow the transformations and branches. Keep a distinction between a business rule and an AI suggestion.
- 03Review and recovery
Find the human checkpoint, uncertainty path, and the response when a step fails or repeats.
- 04Evidence and handoff
Check the screenshots, logs, limitations, and follow-up work described in the case. Define acceptance checks for your version.
The collection includes demos and technical builds. Each case explains its own context; a workflow for your business needs agreed access, test inputs, and acceptance criteria.
05FloxoLab tools
Inspect your own inputs.
Browser tools for placement evidence, workflow review, and planning assumptions. Each tool states what its output can establish.
06Useful next reads
Test the part you want to adapt.
Use the relevant guide to qualify your inputs, add an approval step, or diagnose a failure before expanding the workflow.
07Next step
Bring the result you need and your current setup.
Share the closest example and what needs to change. Start with an SEO audit or a workflow audit.