What I changed on my own Cape Town page, and what the data shows

In May 2026 I searched "custom software developer Cape Town" and found my own page on the first page of Google. I took a screenshot. That was one search, on one day, from one place. Over the three months that followed, Google's own data shows the page averaging position 25 across all the searches it appeared for. So this isn't a story about ranking first. It's what I changed on my own page, what I saw, and what the numbers say since.

What I Saw in May 2026, and What the Data Says Since

The original case study records a manually observed first-page Google result for custom software developer Cape Town in May 2026. The screenshot in this post preserves that point-in-time observation. It was not a continuous rank-tracking study: device, personalization settings, and a repeatable observation window were not recorded.

That matters. Google results vary by time, location, device, query interpretation, and result type. Between 24 May and 24 August 2026, Google's own Search Console data shows the page averaging position 25 across all the searches it appeared for. This is historical engineering evidence, not a claim that the page currently holds a first-page position or that the same work will produce it for another business. Current performance must be checked against dated Search Console and controlled SERP data.

What I Changed on the Page

In plain words: the page answers one local question, names a real registered company (Villiers Vision Works (Pty) Ltd) and a real Cape Town address, shows real projects before it makes claims, and links to the matching service page and case studies rather than sitting on its own.

The page repeats real Cape Town and South African context: SA-registered company, business hours, Afrikaans/English, in-person availability, local payment gateway integration, POPIA-aware data handling, load shedding resilience. Not generic "we serve Cape Town" copy, the kind of operational detail a real local operator writes.

It lists concrete project evidence with real platforms and real scale before making any claim: e-commerce work on WooCommerce and Shopify for shops in the US, UK, Europe, Australia, and South Africa; a POPIA-compliant medical and dental practice platform with patient records, clinical notes, and medical aid claims; and BX1X, a business operations platform with more than 1,900 endpoints.

It positions around senior, direct access: no account managers, no handoffs, an honest fit assessment, and a registered company behind it. It links to /contact, /projects, the relevant service pages, /reviews/client-reviews, /blog, /about, and /faq, so the page sits inside the rest of the site rather than standing alone. It is listed in the sitemap with an accurate, self-referencing canonical.

The Structured Data

The page carries three schema types: one local-business entity (ProfessionalService with a referenceable @id), FAQPage, and BreadcrumbList. The local-business block names the real registered company, a real Cape Town address, geo coordinates, opening hours, phone, and email. Other service pages on the site reference the same entity by @id rather than redeclaring it.

This is the part most generic output skips. You cannot fake a registered company, a phone number, and opening hours. Accurate structured data helps clarify those facts, but it is not a ranking or answer-engine shortcut.

What This Means for Answer-Engine Visibility

The same clarity work can make a page easier for people and answer engines to interpret: accurate entity information, factual sections, useful sources, clear ownership, and consistent identity. Google says its normal SEO foundations apply to generative Search features and that no special markup is required. Other answer engines make their own inclusion and citation decisions.

A page built this way has a stronger evidence and accessibility baseline. Citation tracking on this site is part of the measurement loop, and observed citations can be logged over an engagement window. That tracking does not turn a result into a promise.

Why This Was Buildable in the First Place

26 years in IT. Software for clients in South Africa, the UK, Europe, the US and Australia since 2011. E-commerce work on WooCommerce and Shopify, a POPIA-compliant medical and dental practice platform, and BX1X as my own business operations platform. The kind of work that ships, runs under load, and survives audits.

Independent since 2001 means I also see software from the business-owner side. Scopes, quotes, deadlines, support tickets, cash flow, and content that has to actually drive enquiries rather than just sound clever. That is the side of the work off-the-shelf AI tools cannot help with, because they were not designed against it.

Years of building with AI systems day-to-day, watching them produce confident output that turns out to be wrong, means the strengths and failure modes of large language models are concrete to me, not theoretical. This post exists because the engineering work is the offer. Not productisation, not a SaaS, not a licence, but the natural extension of work that earns its keep first inside the operator's own business.

The Honest Disclaimers

There is no guaranteed-ranking promise. Nobody can responsibly make one. The defensible claim is that an engineered recipe with governance gates, accurate information, first-hand evidence, and a real supporting cluster gives people and search systems useful material to evaluate. It does not guarantee a result.

If You Want This Applied to Your Business

The toolbox is private. Engagements are scoped one outcome at a time. Fit is decided in a consultation. If you want to talk through what your page should be doing for your business in search results or answer tools, book the consultation. I review every enquiry personally. I do not take every project. I will tell you on the call if it is not a fit.