Industrial SEO that ranks for AI search, not just Google

TL;DRAKS Otomasyon ranks in Google AND gets cited by ChatGPT, Claude, Perplexity and Google AI Overview. The architecture: climate-zone content blocks across 81 Turkish cities, multi-schema bundling per page, Speakable + HowTo schema where they fit, and a robots.txt that allows AI search bots while blocking training crawlers.

Most local SEO advice in 2026 is still optimizing for the 2015 Google SERP — LocalBusiness schema, NAP consistency, citation building, the keyword <service> in <city>. It still works. It is also no longer enough.

AKS Otomasyon sells industrial automatic doors, shutters and barriers to facility managers across Turkey. The shopping journey now routes through ChatGPT, Claude, Perplexity, and Google's own AI Overview as often as it does the traditional SERP. We built the SEO layer for that future — and the same architecture happens to dominate the traditional ten-blue-links view as a side effect.

This is the actual architecture, not a trend forecast.

Skip the framework, look at the content

Every local SEO consultant will sell you "81 city landing pages, programmatic SEO at scale." AKS has them — Istanbul, Ankara, Izmir, all the way down to Bayburt and Ardahan, every province in Turkey — plus ten district pages and six brand-service pages on top. But the framework that matters isn't the count. It's how each city page says something genuinely different.

The cities array carries a climate-zone classification: coastal-humid, continental, or mediterranean. That classification drives the technical-spec paragraph on every city page. Istanbul's coastal-humid air corrodes motors, so its page recommends IP55+ rated motors and paslanmaz 304 stainless housings. Ankara's continental swing — 40°C winter-to-summer differential — calls for 60mm thermal-break panels and EPDM perimeter gaskets. Izmir's mediterranean UV beats up powder coating, so the recommendation shifts to UV-stable paint and galvanized frames.

A facility manager in Izmir reading the Izmir page sees a page that knows what their building actually goes through in July. That isn't a vibe — it's the page being generated from real climate data and a recommendation map.

The blocks per city

Each city page has four blocks. None are pure templates:

1. Block A — Overview. Geography, dominant economic sectors, population, key districts. Pulls from a per-city description written by hand, not a slot machine.
2. Block B — Climate-driven recommendations. 120-180 words of technical specs tied to the climate classification. This is the load-bearing block for SEO.
3. Block C — Service area. Districts within the city, neighbouring provinces (mentioned as text, not linked — more on that below), and the contact CTA.
4. Block D — Parametric FAQ. Three questions auto-generated from the climate zone, the top recommended product, and district context.

Block B is what gives Google something to differentiate and what gives an AI Overview an actual specific paragraph to cite when summarizing "best automatic doors for coastal cities in Turkey." Pages without Block B would still rank — they wouldn't get cited.

Schema choices, with the reasons

Three deliberate JSON-LD decisions, each saying no to a more obvious choice:

LocalBusiness, not ProfessionalService. Advice blogs recommend ProfessionalService because it's "more specific." Google treats the difference as ranking-neutral. We use LocalBusiness because the city-variant emission deliberately drops the hardcoded HQ address — we don't want every city page declaring the same PostalAddress, which Google reads as location-spam.

Service, not Product. Industrial doors look like products, so the instinct is Product schema with Offer and AggregateRating. We use Service. Reason: Google Merchant Center has a strict policy on Product schema — price, availability, return policy required. For a B2B service business, those don't apply. Service sidesteps the policy entirely, gives us provider, areaServed, and serviceType, and never triggers Merchant Center warnings.

FAQPage + BreadcrumbList + LocalBusiness bundled per page. Single- schema pages rank fine. Bundled-schema pages tend to dominate AI citation. We emit all three on every city page — the argument is structural: each schema gives the parser a different facet of the same page (business identity, navigation context, Q&A), and AI engines that resolve entity facts across schemas have more to work with than they would from a single block.

The AI-first additions

Two schema types most SEO checklists skip:

Speakable schema. Flags specific DOM selectors as "this is the spoken-answer block." We tag the answer nodes inside FAQ regions — schema.org acceptedAnswer markers plus the explicit answer-wrapper elements that surround them. When Google's voice assistant — or any AI summarizer — needs a clean answer, those nodes are the obvious source.

HowTo on tutorial blog posts. When a post is genuinely a how-to (installing a sectional door, replacing a photocell sensor), we emit HowTo schema with an explicit step array. Each step has a position, name, text, and anchor URL. AI tools that summarize procedures pick this up cleanly because the structure matches their parsing model.

Together these turn AKS's content from "rank-able pages" into "citation-able sources."

Bot routing as a strategy

The robots.txt is the most underrated SEO artifact in 2026. AKS routes bots into two buckets:

• Blocked: GPTBot, ClaudeBot, Google-Extended, CCBot, Bytespider, FacebookBot, Amazonbot, Applebot-Extended. These crawl for training data, not for search.
• Allowed: OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, PerplexityBot-User, Googlebot, Bingbot, DuckDuckBot, YandexBot. These crawl for live citations.

This is a deliberate stance: we want our content cited in AI search results, but not vacuumed up as anonymous training data that competing AI products will then reproduce without attribution. The distinction matters and the bots respect the directive — at least the ones whose business model depends on appearing to.

Cross-locale via a 308 redirect mesh

AKS runs in Turkish (primary) and English (secondary). Thirteen of the roughly thirty TR blog posts have English counterparts; the rest are TR-only. We auto-generate 308 redirects from the filesystem so an English-locale visitor landing on a TR-only post is redirected to the TR canonical instead of getting a soft 404.

The redirect rules are computed at build time from next.config.ts reading the content directory plus a routePairs array that maps paired slugs. Every cross-locale URL has a definitive 308 destination. There are no soft 404s on language switching, and Google's hreflang signal stays clean.

What we deliberately skipped

• Cross-city internal linking. The conventional advice is "every city links to three nearest cities." We don't. Once we tried it, the link graph started to look like exactly what it was — algorithmic — and we worried about equity dilution into pages nobody actually navigates to. City pages link to recommended products. Districts link to parent cities. The mesh is small and intentional.
• Fake review schema. Reviews are real or absent. No review markup for unwon trust.
• AggregateRating. Same reason.
• Hidden text, doorway pages. Every page is its own answer.

What moved rankings, in order

If we had to attribute the first months of AKS organic growth:

1. Climate-driven Block B content — the single biggest unlock for AI Overview citation.
2. Multi-schema bundling per city (LocalBusiness + FAQPage + BreadcrumbList).
3. AI search bot allowlist + training bot blocklist in robots.txt.
4. Speakable + HowTo on the pages where they actually fit.
5. 308 redirect mesh for cross-locale hygiene.
6. Sitemap discipline with honest lastmod values.

The standard SEO checklist — meta titles, image alt, header tags — sits in tier two. Real work, but the last fifteen percent of impact. Spend your time on the first six and you'll outrank shops doing the inverse.

Related caseAKS Otomasyon — Industrial Door Services SEO PlatformAKS Otomasyon · Web Design + SEO · 2026Read the case study →

If you run an industrial service business and the conventional local SEO playbook isn't moving the needle, the gap is usually content specificity and AI-readiness — both fixable. See our SEO service or talk to us directly.