murattunalı.
Reading

@type
Service
@id
/en/services/seo-consulting/#service
serviceType
SEO Consulting
provider
/#org
areaServed
Istanbul Q406 · Turkey Q43 · Europe Q46
availableChannel
ServiceChannel · /en/contact/ · tr en de
hasOfferCatalog
OfferCatalog · 5 Offer
audience
Audience · audienceType
url
/en/services/seo-consulting/

SEO Consulting.

A search engine can only rank what it can read. We build pages that get crawled, indexed and read correctly.

The person who runs the audit also makes the fix in the source code: the report is not handed off, and no team change sits between finding and fix.

Tell me about your project

DELIVERABLEShasOfferCatalog › Offer × 5in schema
  1. Technical SEO audit and fix plan
  2. Structured data: schema + entity
  3. Content architecture and templates
  4. Multilingual hreflang setup
  5. Measurement: verifiable metrics only
TIMING—not in schema · human only
Technical fixes usually surface in crawl and index data within 2–6 weeks.
EVIDENCEObservation × 3in schema
Mikro Yazılım Destek: 121 addresses in the sitemap · llms.txt present · 6 schema typesOctober 15 – 23, 2026 · Playwright cold load, 1440×900 · a machine-readability measure, not a ranking result · Case sheet
@idvariableMeasuredvalueobservationDate
/isler/mikro-yazilim-destek/#olcum-sitemapSitemap URL count121 URL2026-10-15
/isler/mikro-yazilim-destek/#olcum-llmsllms.txt presenttrue2026-10-15
/isler/mikro-yazilim-destek/#olcum-semaSchema.org types (JSON-LD)62026-10-15
WHO IT IS FORaudience.audienceTypein schema
Corporate sites that are searched for but not found, publish in several languages or across many pages, and want to fix that by measuring it.
NOT FOR—not in schema · human only
We do not take on projects that want a promise of first place for a single keyword, traffic reports that cannot be measured, or bought links.

PROCESSHow does SEO consulting work?

  1. Audit

    Technical SEO + current visibility: where you stand and why.

  2. Architecture

    Crawlable HTML, schema coverage, entity consistency — a machine-readable base.

  3. Content system

    The Journal engine: writing structured clearly enough for models to cite.

  4. Monitoring

    Only what is measured gets reported; no invented metrics.

People search

query → results → click

Models answer

question → synthesis → source.

MEASURED DIAGRAMS

Three engines, one structure

HTML

SEO Search engine sitemap.xml · hreflang · lastmod · Core Web Vitals
AEO Answer engine FAQPage · HowTo · Article · BreadcrumbList
GEO Generative engine llms.txt · robots.txt · Organization + Person
All three layers feed on the same HTML: the search engine ranks, the answer engine quotes, the generative engine cites — and all three first depend on the page being crawled and indexed. Every layer’s instruments are built and measured on this site.

Three languages, one cluster

Türkçe English Deutsch x-default

The map is not decoration: it is drawn from this very page’s hreflang set — three languages declare each other both ways, and x-default points to the Turkish root.

An open door for AI crawlers

OpenAI GPTBot · OAI-SearchBot · ChatGPT-User Allow: /
Anthropic ClaudeBot · Claude-User · Claude-SearchBot Allow: /
Perplexity PerplexityBot · Perplexity-User Allow: /
Google Google-Extended Allow: /
Apple Applebot · Applebot-Extended Allow: /
Microsoft Bingbot Allow: /
Common Crawl CCBot Allow: /
Meta meta-externalagent Allow: /
Amazon Amazonbot Allow: /
DuckDuckGo DuckAssistBot Allow: /
The list is generated from robots.txt itself: every crawler group is welcomed by name and no path is blocked. AI access on this site is a decision, not an oversight.

WHY THIS WAY

Three layers, three separate jobs

Search engine optimization, answer engine optimization and generative engine optimization are not the same thing. Classic search returns a list of pages and aims for the click. An answer engine writes an answer and cites sources; the goal is not to appear in a list but to be named inside the answer. A generative engine decides which passage to quote while it produces the answer; there, what wins is not the page but the paragraph. All three share a single condition: being indexed. A page that is not indexed cannot be named in any answer. The full difference is written up separately.

Index first, then visibility

When the order is reversed the work is wasted, and the concrete example is this site’s own history. The Search Console reading of 22 August 2026 was this: 57 pages indexed, 13 pages crawled but NOT indexed, one impression in total. Crawled but not indexed is not a crawl error but a quality verdict — Google saw the page and judged it not worth including. No visibility work done before that verdict is closed produces results.

In the same reading our own measurement said the same thing: of 58 pages, zero passed the 800-word threshold. Two independent measurements, one conclusion. That is why the order of work is always the same: measurement baseline first, then content depth, then the structure layer, and notification last.

What the structure layer is for

When an answer engine reads a page it looks at two things: the text itself and the structure that says what the text is. The second is written in JSON-LD, and the nodes are linked to each other through stable identifiers — organisation, person, site, page, article, breadcrumb. On this site every route has a WebPage node, the service pages have FAQ and how-to nodes, and those questions are visible on screen too. Hidden text starts a step behind in both accessibility and citation. The basics of the structure are written up separately.

The second part is the map given to model crawlers. This site’s llms.txt file offers models a short index of 56 URLs; the full list is in llms-full.txt (242 URLs) and is generated from the collection: when a new article lands, that file grows by itself. The third part is notification — IndexNow alerts Bing and the Yandex family instantly; Google does not use this protocol and goes by the sitemap. The difference between the two and how notification works are explained separately.

Cluster architecture

Standalone articles accumulate but do not carry each other. Cluster architecture builds a topic as a pillar page with spokes attached to it; the pillar defines the term, the spokes answer individual questions, and all of them link to one another. The measurable difference is this: a single spoke page is weak on its own, while the cluster as a whole builds topical authority.

On this site 8 clusters are live: accessibility, answer engines, performance, multilingual, being found on Google, site migration, commissioning a website, export websites. In total 109 guides and 53 glossary entries; every guide is at least 800 words, every term between 300 and 600. The numbers are not a preference but a contract: they sit as separate tests in the verification suite, and a page that falls below the threshold cannot be published. The whole layer is on the pillar page.

Building this layer is tied to a measurement ledger: how many words each page carries, whether each page receives links from body text, which heading skips a level of the hierarchy — all counted from disk, and the thresholds come from there. The principles of the same discipline are on the approach page, and how the three services draw on one set of decisions is on the services overview.

SCOPEWhat does SEO consulting include?

What does an SEO consultant deliver?

The delivery is not a report but an applied fix list. Audit findings are ordered by weight, each item is written with a measurable threshold, and the same measurement is repeated after the fix. If the number does not hold, the item does not close — this site’s own performance budget works by the same rule.

What does a technical SEO audit cover?

Crawlability and indexation, Core Web Vitals field data, canonical consistency, the hreflang matrix, structured-data coverage and the internal link graph. The audit measures from the browser and the server; a dashboard screenshot is not evidence. The answer-engine side is a separate layer, built under GEO consulting.

Technical SEO consultant versus content consultant

A technical SEO consultant makes the page readable; a content consultant makes it worth reading. Here the two are not bought separately: the content template is built while the architecture is built, because without semantic structure even good writing stays invisible at passage level.

Enterprise SEO consulting: multilingual, multi-team

In an enterprise project the constraint is process, not technique: several teams, several languages, an approval chain. Enterprise SEO consulting is therefore delivered as a layer of rules — multilingual site architecture, schema at template level, and audit steps that run before release. Rules that are not written down disappear by the third sprint.

LOCATION: ISTANBUL

Istanbul, TR — remote by default; on site when it matters.

Related

FREQUENTLY ASKED QUESTIONS

SOURCES