erenakkoc.online

No JSON-LD and no microdata anywhere on the page.

Structured data is the only part of your page an agent can consume without interpretation. Everything else it has to infer, and inference is where it invents facts about you.

Copy<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your company",
  "url": "https://example.com",
  "description": "One sentence an assistant can quote.",
  "sameAs": ["https://x.com/you", "https://github.com/you"]
}
</script>

No /llms.txt or /llms-full.txt at https://erenakkoc.online.

Without it, an assistant deciding what your site is about crawls whatever it happens to find. llms.txt is the cheapest way to control that first impression, and today most of your competitors do not have one either.

Copy# Example Inc

> One paragraph an assistant can quote verbatim about what you do and who it is for.

## Docs
- [Quickstart](https://example.com/docs/quickstart): Get running in five minutes.
- [API reference](https://example.com/docs/api): Every endpoint with examples.

## Product
- [Pricing](https://example.com/pricing): Plans, limits and exact prices.
- [Changelog](https://example.com/changelog): What shipped, newest first.

## Policies
- [Terms](https://example.com/terms)
- [Contact](https://example.com/contact): support@example.com

Only 1 internal link on the page.

A page with no onward links is a cul-de-sac. Everything you publish that is not linked from a crawlable page effectively does not exist.

No well-known agent manifest, no OpenAPI reference and no developer docs link found.

This is the frontier of AX: sites that publish a machine-callable surface get used by agents directly instead of being scraped approximately.

Copy{
  "name": "Example",
  "description": "What an agent can do with this service.",
  "documentation": "https://example.com/docs",
  "endpoints": [
    { "type": "openapi", "url": "https://example.com/openapi.json" }
  ]
}

No /.well-known/mcp.json and no ai-plugin.json.

This is the highest-leverage unclaimed slot on the web right now. The sites that publish a callable surface get used directly instead of guessed at.

Copy{
  "schema_version": "2025-06-18",
  "name": "example",
  "description": "Search the catalogue and check availability.",
  "documentation": "https://example.com/docs",
  "servers": [
    { "type": "http", "url": "https://mcp.example.com" }
  ],
  "contact": "support@example.com"
}

No Last-Modified, ETag, dateModified or <time> element anywhere.

Agents deprioritise content they cannot date, and re-fetch undated pages more often, which costs you bandwidth for nothing.

Copy{"@type":"Article","datePublished":"2026-01-15","dateModified":"2026-08-01"}

No Organization structured data on the page.

Entity resolution is how assistants decide two mentions are the same company. Unresolved entities get merged with, or mistaken for, someone else.

Copy{"@context":"https://schema.org","@type":"Organization","name":"Example Inc","url":"https://example.com","logo":"https://example.com/logo.png","sameAs":["https://x.com/example","https://github.com/example","https://www.linkedin.com/company/example"]}

No rel="license" link and no license or copyright fields in structured data.

If you care how your content is reused, say so where machines can read it. A footer copyright line is not machine-readable.

Copy<link rel="license" href="https://example.com/terms">

No crawlable GET search form and no SearchAction.

Without a GET-addressable search, an agent looking for one specific page on your site has to fetch dozens of pages to find it, and usually gives up first.

Only one weak contact signal found.

"How do I get in touch with them" is one of the most common agent-mediated questions about a company. Make the answer machine-readable.

Copy{"@type":"Organization","contactPoint":[{"@type":"ContactPoint","contactType":"customer support","email":"support@example.com","url":"https://example.com/contact"}]}

1 of 5 blocked by robots.txt: Amazonbot.

These crawlers are the ones that put your link inside an AI answer. Blocking them removes the referral traffic, not just the training use.

• Amazonbot (Amazon) - Excluded from Alexa and Rufus style shopping answers.

CopyUser-agent: Amazonbot
Allow: /

HTTP 200 in 132 ms.

The baseline: an agent with no browser, no cookies and no JavaScript received your page.

The response body was the real page, not a challenge or block screen.

Bot protection that cannot tell a shopping assistant from a scraper silently removes you from AI answers, with no error anyone on your team will ever see.

325 words of readable text arrived in the HTML itself.

Most crawling agents never execute JavaScript. Whatever is not in the raw HTML does not exist for them.

robots.txt served with 11 user-agent groups.

A valid robots.txt is how you talk to crawlers before they read a single page.

All 3 crawlers in this group may fetch /.

These fetches happen because a human just pasted your link into an assistant. A block here fails in front of a real person who wanted to read you.

All 2 crawlers in this group may fetch /.

AI Overviews and Copilot answers are grounded on the classic search index. Blocking Googlebot or Bingbot now also removes you from AI surfaces.

Robots directives present and permissive: index,follow,max-image-preview:large

noindex and nosnippet remove you from the surfaces that would otherwise quote and link you.

The URL served content directly with no redirect.

Every hop costs latency and some agents cap redirects at two or three.

Full response in 132 ms.

Agents fetch many pages per answer and drop the slow ones. Speed is a ranking input you control.

10 KB of HTML, 0% of it inline script.

Agents truncate long documents. Anything past the cut simply is not read.

Content-Type: text/html; charset=utf-8

A declared charset avoids mojibake when an agent quotes your text back to a user.

"Eren Akkoç — Dijital Ürün Geliştirici" (37 characters).

This is the label assistants attach to you when they cite this page.

72 characters: "Noralith Labs kurucusu Eren Akkoç'un ürünleri, yaklaşımı ve çalışmaları."

This is the summary assistants reuse verbatim more often than any other field.

"Fikirleri, kullanılan ürünlere çeviriyorum."

The h1 is the strongest in-page signal of what the document is about.

8 headings with no skipped levels.

A clean outline is what lets an agent quote the right section instead of the whole page.

325 words of readable text.

Assistants prefer sources with enough material to answer a question outright rather than pages that just point elsewhere.

26.4% of the payload is readable text.

A high ratio means an agent spends its limited context on your content instead of your tooling.

<html lang="tr">

Language is how an assistant decides whether to answer a user in your words or translate them.

5 of 7 images described; 2 intentionally marked decorative.

Alt text is the only way the content of an image reaches an agent.

<main> present with <article>; 4 of 4 landmark regions used.

The <main> element tells an extractor where your content stops and your chrome starts. It is the difference between quoting your argument and quoting your nav bar.

26% of structural elements are semantic (17 semantic vs 48 div).

Semantic tags carry meaning an agent can use; a div carries none.

Site root.

Assistants show the URL next to the citation, and readable URLs get clicked more than opaque ids.

og:title, og:description, og:type, og:url and og:image all present.

Open Graph is the fallback summary almost every crawler reads when it cannot parse the page body.

Canonical: https://erenakkoc.online/

Agents dedupe sources by canonical URL, and cross-origin canonicals hand your citation to somebody else.

https://erenakkoc.online/sitemap.xml lists 2 URLs.

A sitemap is how a crawler discovers the pages your navigation hides behind JavaScript menus.

4 twitter:* tags present.

Several agents fall back to card metadata when they cannot extract the body reliably.

All 16 links resolve to a real URL.

Real hrefs are the only navigation primitive an agent has.

100% of links have descriptive text.

Link text is how an agent decides which link to follow when it is looking for something specific.

robots.txt names specific AI crawlers rather than relying on the wildcard group.

Naming crawlers explicitly is how you separate "do not train on me" from "do not send me traffic". The wildcard group cannot express that distinction.

/.well-known/security.txt is served.

It is the standard machine-readable place to say who to contact. Agents and researchers both look there first.

Live user-agent probing was not run for this scan.

Some sites answer 200 to a generic client and 403 to a named AI crawler. Only a live probe finds that.

Not needed: the page already server-renders its content.

No JSON-LD to validate.

No JSON-LD to evaluate.

No prices detected in the page text.

Top-level page; breadcrumbs are not expected.

No microdata; JSON-LD is the preferred format anyway.

No interactive form fields on this page.

No interactive form fields on this page.

No text-like fields on this page.

No button-like controls detected.

No llms.txt to evaluate.