I have optimized for search engines since 1999.
Now for the ones that answer.

From AltaVista to ChatGPT

I started in 1999 with AltaVista, when optimization still meant counting meta keywords. Then Google arrived and turned the field over twice before it had settled once. The marketplaces came next: eBay and Amazon are search engines with laws of their own, and anyone selling there learns fast that "ranking" never means the same thing twice. Over the years I wrote several SEO books published on Amazon, and worked in agencies.

The tooling years — and the grind behind them

For years I worked with what this industry works with: Rank Math in daily production, SEMrush and Sistrix for visibility and competition, Google Search Console and Analytics for what actually happens, Google Ads for what clicks cost, and Google Cloud for everything that had to scale afterwards. Those tools are good at what they do: they show you the problem.

What none of them takes off your hands is the work that follows. I spent too many evenings trimming titles to 60 characters, writing meta descriptions for 300 product pages, mapping keywords, filling in alt text — tasks that eat concentration and stay grind regardless. That is exactly where I wanted AI: on the titles, the descriptions, the keywords, the rewrites. Not as a gimmick, but so the hours go back to what needs a human — strategy, structure, decisions.

WordPress from the inside: WP Soforthilfe

With WP Soforthilfe I spent years doing the work nobody sees: rescuing other people's WordPress installations that have to be running again by morning. Broken updates, plugin conflicts, orphaned database tables, themes that write the page head three times. That knowledge is in every line of the plugin — for instance in the rule that every output has exactly one owner, and that AI Rank Suite never switches another plugin off for you.

Code, e-commerce and a CRM of my own

Alongside that I stayed a developer: e-commerce projects, Next.js on Vercel, and a CRM I built and still run myself. I am also SAP certified (SD and MM) — understanding enterprise processes taught me more about data quality than any SEO tool did.

A team across three time zones — and AI as a tool

We built the plugin with my team in Dubai and Bali, plus remote work from Hamburg. It is financed by exactly one person: me. No investor, no board, no round that wants growth in twelve months — which is why we could design the business model the way it is right for customers rather than the way it flatters a metric.

AI was a tool here, not the author. Claude Code and Codex as development partners and a second pair of eyes in review, Cursor in the daily work on the code, Perplexity for checking sources and competitor figures. Every architectural decision, every product rule and every trade-off is ours — and testing is done by people, on real sites. Working that way teaches you very quickly where AI genuinely saves time and where it only produces text. That dividing line is what the plugin is built on.

Dubai, doctors, real estate — and first place

In Dubai I built two medical companies serving doctors and worked in real estate. Two markets where visibility decides existence: if you do not answer a patient's or a buyer's question, you do not get the call. Several of the sites I ran held first place — and that is exactly where I first noticed that first place is not enough once the answer no longer comes from a list.

Why a plugin — and not a SaaS or an agency service

That was the most important decision, and it has four reasons:

1. The data already lives in WordPress. A SaaS has to crawl your site from the outside and guess the rest. A plugin sees the actual post, its meta fields, its taxonomies, its history — and writes the correction back into the same field. Between "here is a problem" and "the problem is fixed" an external tool puts a CSV export; a plugin puts a click.
2. The work happens in the editor. Optimization belongs where the writing happens, not in a second browser tab. Score, suggestion and preview sit beside the text while it is being written.
3. It stays yours. A plugin is GPL-licensed and lives on your server. When a SaaS subscription ends, access ends; when an agency relationship ends, the logins often go with it. What AI Rank Suite writes into your database stays your database — and because the AI runs on your key, no third-party server ever has to see your content. For clients under NDA that is not a detail, it is the condition.
4. The price can be honest. A SaaS has to price servers, crawlers and AI cost into a subscription — which is why credits exist. A plugin runs on infrastructure you already have. That is why Pro is $99 a year instead of $29 a month, and why I can say: no credits, no seats.

The stress test

I tested this version on a site of roughly one million pages across 15 languages — without trouble. That is what the architecture is for: inventory, scores, llms.txt and crawler control have to keep working when the page count is seven digits and every language has its own URLs.

What I hope the release brings

Customers who win answers instead of counting clicks. Feedback that makes the plugin better. And honestly: new friends in an industry that is reinventing itself all over again. If you use it and something is missing — write to me. I read every email myself.

Nami Shams
contact@airanksuite.com