I have spent most of my career delivering technical solutions for businesses that had real pressure on the line. Revenue targets, public launches, legacy systems that could not fail, and teams who needed answers, not buzzwords.

When you work inside a technical team, everyone speaks the same language. Acronyms, frameworks, deployment patterns, they are all shorthand. The moment you step into a room with founders, marketers, or operations leaders, that language can become a barrier instead of a bridge.

Over the years at Saigon Digital and my previous role as a technical lead and developer, I have learned that the real skill is not choosing the right technology. It is explaining why that technology exists in terms the business actually cares about.

The reality clients live in

Most clients default to what feels safe. WordPress, traditional CMS stacks, familiar hosting setups. And honestly, most of the time those tools work just fine. We still deploy WordPress when it fits the problem.

But there are moments when reliability, security, performance, and scalability stop being “nice to have” and start becoming business risks. That is where modern Jamstack style architectures make sense.

The challenge is not technical. The challenge is communication.

Clients do not wake up wanting a headless CMS or static site generation. They wake up wanting fewer outages, better conversions, and less stress when traffic spikes.

A real migration we delivered

One of our largest migrations involved a legacy platform that had grown for nearly a decade. Multiple plugins, tightly coupled systems, slow deployments, and constant security patching. Marketing teams were afraid to publish. Developers were afraid to touch core logic. Every campaign launch felt risky.

Instead of pitching Jamstack as a “better stack,” we reframed the conversation.

We showed what the business was losing every time pages slowed down, every time the CMS locked up under load, and every time security updates delayed releases. Then we mapped how a decoupled architecture solved those specific pains.

The result was a staged migration to a headless CMS with a static-first frontend. Page speed improved dramatically. Security incidents dropped. Editorial workflows became simpler. Most importantly, the client stopped worrying about whether the website would survive peak demand.

That project reinforced something I now train my entire team on.

The SD Translation Framework

At Saigon Digital, we use a simple internal framework to help our team communicate complex technical ideas clearly. I personally coach developers and strategists on this, especially juniors who are brilliant technically but struggle to explain value.

The SD Translation Framework has four steps:

1. Start with the business pressure

Before any tech discussion, we identify the pressure points. Revenue goals, growth plans, campaign timelines, compliance risks, team frustration. Technology is never the starting point.

2. Map tech features to business outcomes

Performance becomes engagement. Security becomes continuity. Scalability becomes protected revenue during spikes. We ban jargon until the outcome is understood.

3. Use familiar anchors

If a client knows WordPress, we start there. We explain what WordPress does well, where it struggles, and how a Jamstack approach keeps the good parts while removing the bottlenecks. Analogies matter.

4. Show, do not tell

We use real examples, traffic scenarios, and case studies from our own work. A product launch failing due to load is far more persuasive than any benchmark chart.

Turning Jamstack benefits into business language

From a technical perspective, Jamstack offers performance, security, and scalability. From a business perspective, it offers peace of mind.

Faster load times mean users stay longer and convert more. That is not theory, it shows up in analytics.

Decoupled systems reduce attack surfaces. That means fewer emergencies, fewer consultants called in at short notice, and lower long-term maintenance costs.

Scalability means launch days are exciting, not terrifying. When traffic spikes, the site holds. Orders go through. Marketing campaigns deliver ROI instead of apology emails.

These are the conversations clients actually want to have.

Why illustration beats explanation

I rarely “explain” Jamstack anymore. I illustrate it.

I describe a campaign launch where thousands of users hit a page at once. In a traditional setup, the CMS slows down or crashes. Revenue stalls. Teams scramble.

Then I show the same scenario with a static-first architecture. Pages are served instantly. Infrastructure absorbs the load. The business keeps moving.

Once clients see the difference, the technology choice becomes obvious.

Communication is the real skill

Clients come to us because they expect expertise. That does not mean they want lectures.

Over time, I have settled on four rules that I drill into my team:

• Be patient and listen before proposing anything
• Always prioritise the client’s goals over your favourite tools
• Communicate positively, this project matters deeply to them
• Be responsive, clarity builds trust even when answers take time

Most communication today happens in Slack, email, and documents. That makes tone and clarity even more important. Being human is not optional.

The real job of a technical partner

Our job is not to sell Jamstack. Our job is to help businesses make better decisions with technology.

When clients understand why a solution exists and how it impacts revenue, experience, and risk, they stop resisting modern approaches. They start asking smarter questions.

That is when partnerships work.

If you are sitting on a legacy platform that feels fragile, slow, or risky, there is probably a better way forward. It does not start with a framework or a CMS. It starts with a conversation.

If you have a project where performance, security, or scalability actually matter, we can help you map the right approach and explain it in plain business terms.

The post Translating Tech Into Business Value appeared first on Nicholas Rowe.

As a kid, I was obsessed with how things worked. Not just software, but hardware. I spent hours building PCs, swapping components, fixing broken machines, and learning through trial and error. That curiosity, pulling systems apart to understand them, never really left. It just evolved.

Today, I work with large language models, AI search systems, and modern digital platforms. Instead of motherboards and CPUs, I now spend my time thinking about data structures, retrieval systems, search behaviour, and how intelligence is formed, surfaced, and trusted online.

I started by taking computers apart.

The tools have changed. The mindset hasn’t.

Learning by Building, Not by Theory

My early years were shaped by experimentation. I was never interested in theory without application. If something could be built, I wanted to build it. If it broke, I wanted to understand why.

That approach carried through everything I did next.

I moved into web design and development at a time when the internet was still messy and unpolished. Websites were static, slow, and often poorly thought through. But that chaos was an opportunity. You could see clearly how structure, performance, and clarity affected user behaviour.

From there, I began freelancing and consulting, working with businesses at very different stages. Startups trying to find traction. Established companies trying to modernise. Teams with tools and budgets, but no real digital strategy.

What I learned quickly was this.

Most problems were not technical.
They were structural and strategic.

From Freelancing to Founding Saigon Digital

Freelancing gave me exposure. Consulting gave me perspective. But neither solved the deeper problem I kept seeing.

Digital work was fragmented.

Design sat in one corner. Development in another. SEO somewhere else. Paid media disconnected from product. Nobody owned the system end to end.

That gap is why I co-founded Saigon Digital.

The goal was never just to build websites or run campaigns. It was to create a full-service digital agency that understood how all the parts connect. Strategy, design, development, SEO, data, performance, and now AI.

Today, Saigon Digital works with brands across the UK, US, Europe, and Asia. We help companies build scalable platforms, grow sustainably, and adapt to how search and discovery are changing.

Which brings me to AI.

The Shift From Search Engines to Intelligence Engines

Traditional search rewarded optimisation.

AI search rewards understanding.

Working with large language models has made one thing painfully clear. These systems do not think in keywords. They think in entities, relationships, intent, and trust signals.

This is where my background matters.

Because AI search behaves less like a list of results and more like a system trying to understand reality. It ingests structure, consistency, authority, and clarity. If your brand does not present a coherent story across the web, AI struggles to place you.

This is what led me deep into AI search optimisation and GEO, Generative Engine Optimisation.

Not as a buzzword. As a discipline.

What Being an AI Search and GEO Expert Actually Means

Being an AI search expert is not about prompts or hype.

It is about understanding how AI systems learn, retrieve, rank, and recommend.

At a practical level, that means working across:

• Structured data and schema
• Content designed for comprehension, not volume
• Entity clarity and brand consistency
• Technical performance and UX
• Authority signals, citations, and references
• How LLMs source and synthesise information

GEO focuses on one core outcome.

When a user asks an AI a buyer-intent question, does your brand appear as an answer or recommendation?

If not, you are invisible.

This is the work I now spend most of my time on, both personally and through Saigon Digital. Auditing AI visibility. Fixing clarity gaps. Building content and systems that machines and humans can both understand.

Why My Background Matters in the AI Era

AI rewards systems thinkers.

Building computers taught me to respect fundamentals. Freelancing taught me adaptability. Consulting taught me how businesses actually work. Running an agency taught me scale and accountability.

Working with LLMs ties it all together.

AI search does not care how clever your copy is. It cares whether your signals align. Whether your story is consistent. Whether your digital foundations are strong.

In many ways, we are back to basics. Just at a much higher level of abstraction.

The Future I Am Building Toward

I believe the next era of digital will be defined by clarity.

Not louder marketing. Not more content. But clearer positioning, better systems, and trust earned over time.

As an AI search and GEO expert, my focus is on helping brands:

• Become understandable to AI systems
• Become recommendable, not just discoverable
• Build digital assets that compound in value
• Stay relevant as search behaviour changes

This is not theory. It is already happening.

And the brands adapting now will dominate tomorrow.

Should You Backlink From Your Personal Blog to Saigon Digital?

Yes. But only if you do it properly.

A personal brand blog linking to your agency is absolutely worth it, especially when:

• The personal brand has clear topical authority
• The content is genuinely insightful
• The link is contextual, not forced
• You are positioning yourself as a founder and expert, not hiding the relationship

This type of link helps in three ways:

1. SEO and Entity Association

Google and AI systems connect you as an individual entity to Saigon Digital as a business entity. That strengthens authority around expertise keywords like AI search expert and GEO expert.

2. Trust and Conversion

People researching you personally will naturally want to understand who you work with. A clean, contextual link increases trust and leads qualified traffic.

3. AI Training Signals

LLMs learn relationships. Founder → expert → agency is a strong, natural signal when consistently reinforced across the web.

Best Practice

• Link naturally within context, not in footers or keyword spam
• Use branded anchor text like “Saigon Digital” or “my agency Saigon Digital”
• Do not over-optimise with exact match anchors
• Keep your personal blog authentic, not salesy

Done right, this is one of the highest quality links you can create.

The post From Building Computers to Building Intelligence: My Journey Into AI Search appeared first on Nicholas Rowe.

For over two decades, search has followed the same basic pattern.

You type a query.
You scan a list of links.
You click, compare, and decide.

That model is breaking.

By 2026, search will no longer be about finding websites. It will be about receiving answers, recommendations, and decisions made on your behalf by AI systems.

This isn’t a small evolution. It’s a fundamental shift in how people discover information, evaluate options, and choose brands.

From Search Engines to Answer Engines

Traditional search rewarded whoever could rank highest on a page of ten blue links. AI search flips this on its head.

Large language models and AI-powered search interfaces don’t present options equally. They synthesize, filter, and recommend.

Instead of ten results, users increasingly see:

• One summarized answer
• A shortlist of recommended brands
• A suggested next action

The user doesn’t “search” as much anymore. They ask, and expect clarity, confidence, and speed in return.

This changes the core question from
“How do we rank?”
to
“How do we become the answer?”

User Behaviour in 2026: Faster, More Trust-Based, Less Exploratory

AI search is shaping behaviour in three clear ways.

First, users are becoming less patient.
If an AI can give a confident answer in seconds, the tolerance for slow websites, vague copy, or unclear value propositions disappears.

Second, users are becoming more trust-driven.
AI systems favour sources that appear authoritative, consistent, and widely referenced. Users mirror that trust. If an AI recommends a brand, it carries implied credibility.

Third, users are exploring less, but committing faster.
Instead of opening ten tabs, users often act on one or two AI-curated suggestions. Discovery shrinks, but decision speed increases.

For brands, this means fewer chances to make an impression, but higher intent when you do.

Why I Care About This Shift (And Why It Feels Familiar)

This shift feels familiar to me, because I’ve seen it before, just in different industries.

Outside of tech and business, I’ve been lucky enough to DJ around the world, sharing my love for vinyl, underground music, and festival culture. Music scenes evolve fast. Platforms change. Gatekeepers appear and disappear.

If you’ve spent time in underground music, you learn quickly that attention is scarce, trust is everything, and recommendation beats discovery.

Some of my favourite moments have been behind decks at festivals and clubs where the crowd didn’t come to “search” for music. They came because someone they trusted said, “You need to hear this.”
Glastonbury is one of those places for me. It’s not just a festival, it’s a living system of culture, reputation, and shared signals.

AI search works the same way.

People aren’t browsing endlessly. They’re leaning on trusted curators. Only now, that curator is an algorithm trained on the signals we put into the world.

From Freelancing to Consulting to Building Systems

Before building Saigon Digital, I freelanced and consulted across design, development, and digital strategy. I worked inside businesses at different stages, startups, scale-ups, and established companies trying to modernise.

That experience taught me something important.

Most businesses don’t fail because they lack tools.
They fail because they lack clarity.

AI search brutally exposes that.

If your positioning is vague, your messaging inconsistent, or your digital foundations weak, AI systems struggle to understand you. And if AI can’t understand you, it won’t recommend you.

SEO Is Splitting Into Two Disciplines

By 2026, “SEO” will no longer mean one thing.

It will split into:

• Index SEO: Optimising for traditional search engines and crawlers
• AI Visibility: Optimising for how AI systems understand, reference, and recommend your brand

Ranking #1 on Google will still matter, but it won’t be enough.

Brands will need to ask:

• Does AI understand what we do clearly?
• Are we cited or referenced in AI-generated answers?
• Do we appear as a recommended option for buyer-intent questions?

This requires structured data, clear positioning, consistent messaging across the web, and content written for comprehension, not keyword density.

Websites Become Trust Hubs, Not Just Traffic Funnels

In an AI-first search world, websites are less about attracting mass traffic and more about validating trust.

When AI sends a user your way, that user arrives with expectations:

• Clear answers
• Proof of credibility
• Frictionless experience

Your website becomes a confirmation layer. If it’s slow, confusing, or inconsistent, the trust transfer breaks instantly.

This is why performance, clarity, and UX matter more than ever. Not because of rankings, but because AI is pre-qualifying your visitors.

Brands Will Compete on Clarity, Not Just Content

AI systems reward clarity.

Vague positioning, generic service pages, and buzzword-heavy copy don’t translate well into AI understanding. Clear brands win.

The winners in 2026 will be the companies that can clearly answer:

• Who they help
• What problem they solve
• Why they’re trusted
• What makes them different

Not in ten pages. In one concise, machine-readable narrative.

The Quiet Shift Most Businesses Are Missing

The biggest mistake businesses are making right now is treating AI search as a future problem.

By the time it’s obvious in analytics, it’s already too late.

AI models learn from today’s data. The brands being referenced, cited, and understood now are training the systems that will dominate discovery in 2026.

This creates a compounding advantage. Early clarity leads to repeated recommendation. Repeated recommendation leads to market dominance.

Final Thought

AI search won’t kill websites. It will expose weak ones.

Just like in music, the artists and labels that endure aren’t the loudest, they’re the ones people trust to deliver consistently.

In 2026, the brands that win won’t be the noisiest or the most aggressive. They’ll be the clearest, the most trusted, and the easiest for both humans and machines to understand.

The future of search isn’t about fighting algorithms.

It’s about earning recommendation.

The post Who will win in AI Search in 2026? A CEO & Founders Perspective appeared first on Nicholas Rowe.

Reference:

https://howdns.works

The post DNS – How a website is found on the internet appeared first on Nicholas Rowe.

Download and Install NodeJS

If you haven’t installed Node yet, download the latest stable release of NodeJS from https://nodejs.org and install using all the default options.

Install the http-server package from npm

Install the http-server globally on your machine using the node package manager (npm) command line tool, this will allow you to run a web server from anywhere on your computer.

Open a command prompt / command line window and enter the following:

"npm install -g http-server"

Browse to your local website with a browser

Open your browser and go to the address http://localhost:8080 and you should see your local website.

The post NodeJS – Setup a Simple HTTP Server / Local Web Server appeared first on Nicholas Rowe.

When your page is accessed over HTTPS, but the Load Balancer is performing SSL offloading and actually requesting your content on the non-SSL port 80, the webserver, PHP, or anything else for that matter, does not understand or see that it’s being accessed over https://.

The fix for this, is that Load Balancer sends the de-facto standard X-Forwareded-Proto HTTP header, which we can use to figure out which protocol the client is actually using on the other side of the Load Balancer.

With Apache 2.2, you could use something along the lines of:

<IfModule mod_setenvif.c>

SetEnvIf X-Forwarded-Proto “^https$” HTTPS

</IfModule>

This simply reads the X-Forwared-Proto header, and if it equals https then, sets the HTTPS environment variable to 1. PHP will see this environment variable, and eventually it will become $_SERVER[‘HTTPS’] that equals 1 — just like it would be for a “real” native SSL request.

The solution

Websites behind load balancers or reverse proxies that support HTTP_X_FORWARDED_PROTO can be fixed by adding the following code to the wp-config.php file

if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’] == ‘https’)

$_SERVER[‘HTTPS’]=’on’;

Then to redirect any http requests to https, we need to define the following In the .htaccess file:

<IfModule mod_rewrite.c>

RewriteEngine On

RewriteCond %{HTTP:X-Forwarded-Proto} !https

RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

RewriteBase /

RewriteRule ^index\.php$ – [L]

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

</IfModule>

The important parts here are in bold. Under usual circumstances inside the .htaccess file the rewrite condition would be to check for https to be set to OFF:

RewriteCond %{HTTPS} off

When behind some forms of proxying, whereby the client is connecting via HTTPS to a proxy, load balancer, Passenger application, etc., the %{HTTPS} variable may never be on and cause a rewrite loop. This is because your application is actually receiving plain HTTP traffic even though the client and the proxy/load balancer are using HTTPS. In these cases, check the X-Forwarded-Proto header.

References:

http://stackoverflow.com/questions/452375/detecting-https-requests-in-php

http://stackoverflow.com/questions/13977851/htaccess-redirect-to-https-www

The post WordPress SSL Offloading appeared first on Nicholas Rowe.

The post Fonts. What and where. appeared first on Nicholas Rowe.

.parent{
display: table;
width: 100%;
}
.child{
display: table-cell;
text-align: center;
vertical-align: middle;
}

This method works good across all browsers and includes solid IE support down to IE7. The downfall of this particular method is that it requires two html elements in order for it to work (a parent and a child).

Using CSS3 transforms property, we can now vertically align elements with just 3 lines of css:

.element {
  position: relative;
  top: 50%;
  transform: translateY(-50%);
}

Transforming the element on the Y axis with a negative 50% of the height the element is currently contained in will pull it up half way (more than likely outside the parents width and height).

Now if we add a top: 50% it will pull the element back down directly in the center of whatever parent container the element is sitting inside of.

The post Vertically aligning elements appeared first on Nicholas Rowe.

I stumbled across a handy piece of jQquery that makes use of jQuery height element, below is the snippet:

function stretch_pc() {
var height = $(window).height();
var stretch = (80 * height) / 100;
thirtypc = parseInt(thirtypc) + 'px';
$("div").css('height',stretch);
}

$(document).ready(function() {
stretch_pc();
$(window).bind('resize', stretch_pc);
});

This is essentially a function that is defining two variables height and stretch. The height variable is simply just finding the height of the windows viewport. By reading the jQuery documentation here

The difference between .css('height') and .height() is that the latter returns a unit-less pixel value (for example, 400) while the former returns a value with units intact (for example, 400px). The .height() method is recommended when an element’s height needs to be used in a mathematical calculation.

The second variable stretch is going to be 80 percent of the viewport  * the height of the document and then divided by 100 to give us 80 percent of the viewport height. You may change 80 to match whatever you find sufficient, I opted for this as the height element does not take in to account any padding or margin, so you will get a bit of excess if you decide to have these in your css.

Lastly, after the function, the jquery will load on the document ready and initialise the function, making the ‘div’ height match the percentage defined in the function.

Further reading: jQuery Documentation

Source: link

The post Element height based on viewport height appeared first on Nicholas Rowe.

Some of the buddypress pages used different templates and I found it misleading sometimes as to which pages where using which templates. I found a great little bit of code that will show only the administrator who is logged in which template the current page is using. Great for debugging and other little things.

First of all we need to register a new little function, with which we will be using a global var. Put this in to your themes functions.php file.

add_filter( 'template_include', 'var_template_include', 1000 );
function var_template_include( $t ){
$GLOBALS['current_theme_template'] = basename($t);
return $t;
}

function get_current_template( $echo = false ) {
if( !isset( $GLOBALS['current_theme_template'] ) )
return false;
if( $echo )
echo $GLOBALS['current_theme_template'];
else
return $GLOBALS['current_theme_template'];
}

Once we have registered our new function, we will want to call it in our theme files somewhere. I simply added the below snippet to my header.php file of my theme. This code will print out the current page template by using the function we registered before.

// If the current user can manage options(ie. an admin)
if( current_user_can( 'manage_options' ) )
// Print the saved global
printf( '
<div><strong>Current template:</strong> %s</div>
', get_current_template() );
?&gt;

So there you have it, if you ever get stuck needing to find out what page is using what template (great for plugins) you can use this.

Edit: I also found this little snippet and it can be used in the same manner:

add_action('wp_head', 'show_template');
function show_template() {
global $template;
print_r($template);
}

The post Find out what template a WordPress theme is using. appeared first on Nicholas Rowe.