This post is the engineering recipe for building a Cape Town service landing page that competes for search visibility and is structured to be cited by LLM answer engines. It is the recipe I use, applied first to my own service pages and then through client engagements.
Most "AI SEO" output does not earn visibility because it is not engineered. It is generated. Generic prompts, generic articles, generic publish-and-pray. Search engines do not reward generic. Neither do the LLM answer engines that increasingly intercept buyer intent before search results do.
The recipe transfers. The rest of this post is the recipe.
The recipe, in concrete terms
The recipe is recorded as a reusable formula:
exact local intent
+ real local entity proof
+ specific project proof
+ FAQ/schema
+ internal topical links
+ broader blog/project/review authority
+ clean sitemap/canonical/metadata
+ human, senior, direct positioning
= a service page that competes against generic recruiter, agency, and job-board results
What follows is each ingredient, with what it actually looks like in production.
Exact local intent match
The page aligns the target intent across URL, title, H1, description, keywords, and body language:
- URL reflects the buyer query, no fluff.
- Title is the buyer query without keyword stuffing.
- Canonical points to itself.
- H1 is a service promise written for a human, not for a crawler.
- Description opens with the operator, the city, the years of experience, and the offer.
Keyword placement is direct, but the body reads as a service page, not as keyword stuffing. That distinction is a writing problem, not an SEO problem.
Local entity and business signals
The page injects four schema types: a single canonical local-business entity (ProfessionalService with a referenceable @id), FAQPage, and BreadcrumbList. The local-business block names a real registered company (Villiers Vision Works (Pty) Ltd), a real Cape Town address, geo coordinates, opening hours, phone, email, and price range. Other service pages on the site reference the same entity by @id rather than redeclaring it. One canonical entity. Many services. No duplication.
This is the part most "AI SEO" output skips. You cannot fake a registered company, a phone number, and opening hours. The schema is one of the strongest entity signals available to a local service page.
Strong local proof
The page repeats real Cape Town and South African context: SA-registered company, business hours, Afrikaans/English, in-person availability, PayFast/Peach/Ozow integration, POPIA-aware data handling, load shedding resilience, fibre + LTE backup. Not generic "we serve Cape Town" copy. The kind of operational detail a real local operator writes.
Proof before claims
The page lists concrete project evidence with real platforms and real scale: 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; BX1X as a 37+ module SaaS business operations platform; and platform-scale work for South African enterprises. Numbers, industries, and named platforms beat "we build custom software" every time.
Differentiation against agencies and recruiters
The page positions around senior-direct access, no account managers, no handoffs, honest fit assessment, registered company accountability. This is what makes it competitive against recruiter pages and large agency pages. It answers a different but adjacent intent ("I need a software developer in Cape Town") rather than the recruiter intent ("I need a job listing").
Internal linking cluster
The page links to /contact, /projects, four service pages (/services/wordpress-woocommerce, /services/cloud-applications, /services/api-servers-microservices, /services/mobile-app-development), /reviews/client-reviews, /blog, /about, and /faq. The homepage's BentoServices "Popular entry pages" links back. This page is not orphaned. It sits inside an authority graph.
Shared landing-page system
The page renders through components/LandingPageLayout.js. The layout handles meta, schema injection, hero, trust strip, fit/local relevance section, services, projects, testimonials, process, typical engagements, FAQ, and CTA. Every new landing page on the site uses the same layout. The schema and structure are consistent across pages. That consistency is a signal LLMs reward as much as search engines do.
Sitemap priority and crawlability
next-sitemap.config.js lists this URL under the landingPages group at priority 0.85, monthly changefreq, automatic lastmod gated to actual file change. Pages without sitemap discipline take weeks to index. This page indexed quickly because the discipline was in place before publish.
Supporting topical authority
The site contains 35+ blog posts, 43+ project case studies, and 100+ review files. Multiple adjacent landing pages: /web-developer-south-africa, /hire-developer-from-south-africa, /senior-software-engineer-cape-town, /wordpress-developer-cape-town, /wordpress-developer-south-africa, /shopify-developer-cape-town, /shopify-developer-south-africa, /nodejs-api-developer-south-africa, /react-nextjs-developer-south-africa, /ecommerce-development, /medical-practice-software, /pos-system-development, /booking-system-development. The Cape Town page sits inside a topical graph. It is not a one-off keyword page.
The 22-article governed content run
A separate run produced 22 supporting articles. Recorded log: 22 drafts, ~45,000 words, every article passed governance checks, every article links to a service page and a project case study, no AI-tell phrasing, no invented facts.
The articles support the topical cluster. The cluster supports the landing page.
The toolbox behind the recipe
Four AI pipelines, combined into the SEO AI Toolbox:
- Site Intelligence: captures the current state of the site as the source of truth. Full HTML, screenshots, headings, links, sitemap, technical observations.
- Search Project: maps the search opportunity, classifies intent, and identifies where the page can compete.
- Content Marketer: produces the supporting articles under governance gates. No invented facts, no AI-tell, every piece links a service page and a case study.
- Social Publisher: exists for downstream amplification.
The toolbox is not for sale. The system is operated by one person and applied to your business pages through an AI App Development engagement, not licensed to anyone.
What this means for LLM answer visibility
The same engineering that earns search visibility also makes pages citable in ChatGPT, Claude, Perplexity, and Gemini answers. LLM answer engines reward the same structures: strong entity definitions, paragraph-level facts, FAQ schema, citable URLs, consistent identity across pages.
A page built with this recipe passes all of those checks. Citation tracking on this site is part of the measurement loop. Observed citations are logged over the engagement window. Most "AI SEO" providers cannot speak to LLM visibility yet. The toolbox treats both surfaces as one engineering problem.
Why this was buildable in the first place
Twenty-five years in technology. Fifteen building production software for clients in the US, UK, Europe, Australia, and South Africa. E-commerce work on WooCommerce and Shopify, a POPIA-compliant medical and dental practice platform, and BX1X as my own SaaS business operations platform with 37+ modules. The kind of work that ships, runs under load, and survives audits.
Running my own SA-registered company 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.
Three years of building with AI systems day-to-day, watching them produce confident output that turns out to be wrong. The strengths and failure modes of large language models are concrete to me, not theoretical. That is why these pipelines have eval gates, source-of-truth handling, and governance rules. The apps were built for my own business first, then opened to client engagements once the pipelines and governance held up across multiple production runs.
This post exists because the engineering work is the offer. Not productisation, not a SaaS, not a licence — 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, proper entity signals, and a real supporting cluster — applied with judgement — is more likely to produce a result than generic AI content with none of those properties.
The system is applied per engagement, scoped to one outcome at a time, measured at 30, 60, and 90 days. Measurement is part of the engagement, not an upsell.
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 in LLM answers), 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.