About Webmaster Gateway

Running a website changed more in the last two years than in the ten before them. Agents write the code now. AI answers the question before anyone clicks through to your page. Content that used to take a week takes an hour, and most of it is worth less than what it replaced.

The server still goes down at 3am, though. The backups still need testing. The migration still breaks something you did not plan for. The bill still arrives on the first.

Webmaster Gateway is about both halves of that. What AI actually changed, and what it did not.

What you will find here

Getting found, in both directions: classic search engine optimization alongside the newer work of earning citations in AI Overviews, ChatGPT and Perplexity. Schema, llms.txt, crawler policy, and what to do about a search landscape where fewer people click.

Building and shipping, including AI site builders, coding agents, and where they save real time versus where they quietly create work.

Publishing, including automated content pipelines and the editorial gates that keep them on the right side of Google's rules. And the fundamentals that never went anywhere: hosting, speed, uptime, security, backups, migrations, WordPress and Ghost, analytics, monetization, and domains treated as assets rather than line items.

Roughly half of what gets published here has an AI angle. The other half is ordinary craft, because that is still most of the job.

What you will not find

No hype. No ultimate guides. No listicles that survey ten options and refuse to pick one. No breathless coverage of a tool nobody has opened.

Posts here lead with the answer, name the actual tools and the actual prices, and end with a recommendation rather than a menu.

Why I am the one writing this

I am Matthew Pomar, and this is the part that should decide whether you keep reading.

I have written the code. I have been building websites since the classic ASP era, back when webmaster was a job title and you configured your own server because there was no one else to do it. I still build today, with AI coding agents, every day. I am not a spectator at either end of that arc, which is the whole reason I can tell you which parts of it genuinely changed.

I have run the hardware. For years I ran servers of my own in a colocation facility, along with the storage and networking behind them. Patching, security, hardware that fails at inconvenient hours, and the particular feeling of needing to touch a machine you cannot reach. I run a home lab too. When I write about uptime or backups or a migration going sideways, it is not a category I researched.

I have owned the domains. More than 160 of them. Bought, held, developed, parked, and in some cases quietly renewed for years longer than they deserved. I have opinions about backlink profiles and domain value that were expensive to acquire.

What that means for what you read

It means I care about total cost of ownership rather than the launch-day demo, because I am the one still running it in year three. It means I can usually tell the genuinely new from the thing that already came through once under a different name and did not survive. A lot of what gets sold as revolutionary is the latter.And it means I will not recommend something I would not run myself.

How this site is made

Posts here are drafted with AI and reviewed and edited by me before they publish, using HandsFreeBlog, which I build. That is not a disclosure buried in a footer. It is the point.

A site about running websites in the AI era should be honest about being one, and should be judged on whether the output actually holds up. Most of this industry is doing the same thing right now and would rather you did not think about it.The editorial judgment is mine. So is the responsibility when something is wrong.

If something here is wrong

Tell me and I will fix it. That is a standing offer, not a formality.