WITTIGONIA Lab - Log #SEOWITTIGONIA Lab - Log #SEOhttps://lab.wittigonia.net/log/tag/seoMon, 23 Mar 2026 02:06:09 +0100http://zoho.com/sites/<![CDATA[Architecting for the Agentic Web]]>https://lab.wittigonia.net/log/post/agentic-web-architectureUpdating website for the agentic web architecture to facilitate visibility and discoverability.]]>

Why we updated our insights for the Agentic Web

// Context


The Shift: From Browsers to Retrievers 


For the last decade, SEO was about keywords. You optimized a page so a human would click it, read it, and stay on the site. Today, we are optimizing for AI Agents.

LLMs (Large Language Models) like ChatGPT, Claude, and Gemini do not "browse" like humans. They retrieve, synthesize, and cite. When an AI crawls a website, it doesn't look for pretty design; it looks for Semantic Structure.


To align with this reality, we just executed a complete restructuring of the WITTIGONIA digital footprint.


The Strategy: Semantic Silos 


We moved from a flat URL structure (domain.com/post-name) to a strict semantic hierarchy:

  • Old Way: Flat, ambiguous. An AI sees a list of 100 posts and has to guess which ones are related.

  • New Way (The Agentic Protocol):

    • /insights/digital-strategy/  (Context: Architecture)

    • /insights/data-intelligence/  (Context: Truth)

    • /insights/business-dynamics/  (Context: Systems)

By grouping content into these "Silos," we force the crawler to understand the relationship between topics before it even reads a single word.


Agentic AI Web Readiness
Illustration: Agentic AI Web Readiness: Example website content structure. From flat legacy content to topical clusters.

// Protocol


The Protocol: llms.txt 

Alongside the URL migration, we deployed our llms.txt protocol. This is a markdown file specifically designed for AI scrapers. It strips away the HTML, CSS, and JavaScript bloat and offers a clean "Knowledge Graph" of our core capabilities. Note: llms.txt is still an early approach. And at this stage the impact is not entirely clear. It may very well be that crawlers, bots and AI agents pick up the information or simply ignore it. 


The "Hidden" Gotcha (Developer Note) 

During deployment, we encountered a critical infrastructure nuance that many businesses miss. Modern CMS setups often virtualize the robots.txt file. However, strict crawlers (Lighthouse, Googlebot) expect a physical file at the absolute server root.

  • The Trap: We had files in /html/ (Generic Root) instead of /wittigonia.net/ (Application Root).

  • The Result: Browsers saw the file, but bots saw a 404.

  • The Fix: We bypassed the CMS and hard-coded the llms.txt and robots.txt into the physical server directory.


// Conclusion


The Takeaway 

Digital Transformation isn't just about buying software. It is about Data Architecture. If your business logic isn't structured in a way that an AI can easily retrieve, you are invisible to the next generation of search.


Another step close to AI and Agent Readiness. We will check later when the crawlers revisited the site and see if they can make sense out of the changes and new structure and content. 

]]>Sun, 08 Feb 2026 16:01:00 +0100<![CDATA[Optimizing a Zoho Sites website]]>https://lab.wittigonia.net/log/post/how-to-optimise-zoho-sites-websiteA hands-on review of how we optimized a Zoho Sites website for performance and SEO, AEO, GEO.]]>

Can a Zoho Sites based website be optimized for speed?

his is a question we hear quite often. Many believe that using a closed software as a service platform means giving up control over performance. We decided to treat our own site as a proving ground to see what is actually possible.


// CONTEXT


Why speed matters for growth 

Our primary motivation was simple: user experience comes first. A fast site feels better for the visitor. Beyond that, search engines and modern artificial intelligence tools prioritize sites that are technically sound and quick to load. If the foundation is slow, the content loses its impact.

Read the article about the importance of SEO for AI.


The reality of a moving target 

This process taught us that optimization is very much a moving target. The technology stack behind every website is constantly shifting. For example, during our audit, we discovered that the LinkedIn Insights Tag was pulling in an outdated library. This was flagged under best practices even though we had not changed anything ourselves. External scripts and tools evolve, and they can impact your scores without warning. It is always a work in progress.

Image showing a screenshot from Google PageSpeed Insights tool with Core Web Vital metrics after optimization. On the right side a circle showing the continuous improvement steps: Prioritize, Deploy, Analyze, Adjust.
Illustration: Results from Google Page Speed Insights after optimization.

// Our Optimization Protocol 


We followed a specific checklist to get our mobile scores into a better range.

  • Audit the Third-Party Weight: We moved all non-essential tracking pixels into Google Tag Manager to prevent them from slowing down the initial page load.

  • Strategic Deferral: We configured heavy scripts like live chat to load only after the main page content was fully ready.

  • Image Precision: We swapped heavy png and jpeg files for modern formats like webp.

  • Accessibility First: We replaced or removed any elements that made it difficult for visitors to navigate or read comfortably, such as color-dependent links.


// TECH STACK


The Tools of the Trade 

To get the job done, we relied on a specific set of tools: Google Search Console, PageSpeed Insights, Zoho Sites, Usercentrics for consent management, and Google Tag Manager to orchestrate the timing of our scripts.


Continuous Improvement: The PDCA Cycle translated to SEO 

To stay ahead, we apply the PDCA framework to our digital ecosystem:

  • Prioritize: Identify the bottlenecks that impact users and search ranking.
  • Optimize: Deploy technical fixes, from image compression to script deferral.
  • Analyse: Check the data to see if the changes actually improved performance.
  • Adjust: Refine the strategy as the tech stack and search requirements evolve.
PDCA Cycle translated into SEO: Prioritize, Deploy, Check, Adjust.
Framework: Applying Quality Management practices to SEO, AEO, GEO - optimization for humans and AI.

// Summary: 5 Steps to Optimize Zoho Sites for Speed


Based on our lab findings, follow this technical protocol to improve your digital performance:

  1. Audit Third-Party Weight: Audit and move non-essential tracking pixels into Google Tag Manager to prevent them from slowing down the initial page load.
  2. Configure Strategic Deferral: Set heavy scripts, such as Zoho SalesIQ live chat, to load only after the main page content is fully ready using the Window Loaded trigger.
  3. Optimize Image Precision: Convert heavy PNG and JPEG files into modern WebP formats and ensure every image has explicit width and height dimensions to prevent layout shifts.
  4. Clean Header Code: Identify and remove redundant synchronous scripts from the Zoho Sites Header and replace them with asynchronous versions.
  5. Prioritize Accessibility: Verify that all links are distinguishable and meet contrast requirements, replacing color-dependent links with high-contrast, accessible buttons.


// Conclusion 


The results show that you can achieve high performance while staying on a platform you enjoy using. It just takes a bit of technical curiosity and a willingness to keep testing. If you find yourself needing some help with optimizing your own site or working through these technical hurdles, please feel free to reach out to us. We would be happy to discuss how we can apply these lab-tested strategies to your project.


TL;DR Optimizing a Zoho Site is entirely feasible but requires staying proactive. Because technology is always changing, performance is a moving target rather than a one-time fix. Focus on the user experience and the technical scores will follow.

]]>Sun, 08 Feb 2026 13:33:00 +0100